SAP BBP_IMS_LOG_FILL Function Module for Erzeugt einen Log Eintrag









BBP_IMS_LOG_FILL is a standard bbp ims log fill SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Erzeugt einen Log Eintrag processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for bbp ims log fill FM, simply by entering the name BBP_IMS_LOG_FILL into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_IV_IMS
Program Name: SAPLBBP_IV_IMS
Main Program: SAPLBBP_IV_IMS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function BBP_IMS_LOG_FILL pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'BBP_IMS_LOG_FILL'"Erzeugt einen Log Eintrag
  EXPORTING
   IV_LOG_EVENT =  "IMS Log Ereingis
*  IV_EMAIL =  "E-Mail-Adresse
*  IV_SENDER =  "Benutzername
*  IS_EXCEPTION =  "Struktur für Ereignisse und Ausnahmen
*  IV_EXCP_GUID =  "Globally Unique Identifier
*  IV_DOC_GUID =  "Globally Unique Identifier
*  IV_STATUS_OLD =  "Einstelliges Kennzeichen
*  IV_PROCESSOR_OLD =  "Benutzername
*  IS_MSG =  "Fehlermeldungen zu einer PD-Methode
*  IT_ATTACH =  "Attachment.
*  IV_NOTICE =  "char255
.



IMPORTING Parameters details for BBP_IMS_LOG_FILL

IV_LOG_EVENT - IMS Log Ereingis

Data type: IMS_LOG_EVENT
Optional: No
Call by Reference: No ( called with pass by value option)

IV_EMAIL - E-Mail-Adresse

Data type: BBP_EMAIL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SENDER - Benutzername

Data type: UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_EXCEPTION - Struktur für Ereignisse und Ausnahmen

Data type: BBPS_EVENT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_EXCP_GUID - Globally Unique Identifier

Data type: BBP_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_DOC_GUID - Globally Unique Identifier

Data type: BBP_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_STATUS_OLD - Einstelliges Kennzeichen

Data type: CHAR1
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PROCESSOR_OLD - Benutzername

Data type: UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_MSG - Fehlermeldungen zu einer PD-Methode

Data type: BBP_PDS_MESSAGES
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_ATTACH - Attachment.

Data type: BBPT_ATTACHMENT_BCS
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NOTICE - char255

Data type: CHAR255
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_IMS_LOG_FILL Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_iv_log_event  TYPE IMS_LOG_EVENT, "   
lv_iv_email  TYPE BBP_EMAIL, "   
lv_iv_sender  TYPE UNAME, "   
lv_is_exception  TYPE BBPS_EVENT, "   
lv_iv_excp_guid  TYPE BBP_GUID, "   
lv_iv_doc_guid  TYPE BBP_GUID, "   
lv_iv_status_old  TYPE CHAR1, "   
lv_iv_processor_old  TYPE UNAME, "   
lv_is_msg  TYPE BBP_PDS_MESSAGES, "   
lv_it_attach  TYPE BBPT_ATTACHMENT_BCS, "   
lv_iv_notice  TYPE CHAR255. "   

  CALL FUNCTION 'BBP_IMS_LOG_FILL'  "Erzeugt einen Log Eintrag
    EXPORTING
         IV_LOG_EVENT = lv_iv_log_event
         IV_EMAIL = lv_iv_email
         IV_SENDER = lv_iv_sender
         IS_EXCEPTION = lv_is_exception
         IV_EXCP_GUID = lv_iv_excp_guid
         IV_DOC_GUID = lv_iv_doc_guid
         IV_STATUS_OLD = lv_iv_status_old
         IV_PROCESSOR_OLD = lv_iv_processor_old
         IS_MSG = lv_is_msg
         IT_ATTACH = lv_it_attach
         IV_NOTICE = lv_iv_notice
. " BBP_IMS_LOG_FILL




ABAP code using 7.40 inline data declarations to call FM BBP_IMS_LOG_FILL

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!