SAP BAPI_XMI_ENTER_LOGMSG Function Module for Enter External Message in XMI Log
BAPI_XMI_ENTER_LOGMSG is a standard bapi xmi enter logmsg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enter External Message in XMI Log 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 bapi xmi enter logmsg FM, simply by entering the name BAPI_XMI_ENTER_LOGMSG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXMI
Program Name: SAPLSXMI
Main Program: SAPLSXMI
Appliation area: S
Release date: 29-Apr-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_XMI_ENTER_LOGMSG 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 'BAPI_XMI_ENTER_LOGMSG'"Enter External Message in XMI Log.
EXPORTING
* EXTUSER = "Tool user affected by the message
* MSGARG3 = "3rd message argument
* ARGTYPE3 = 'C' "Type of 3rd message argument
* MSGARG4 = "4th message argument
* ARGTYPE4 = 'C' "Type of 4th message argument
* INTERFACE = "Interface affected by the message
* OBJECT = "Object affected by the message
* MSGID = "Message ID in manufacturer namespace
MSGTEXT = "Standard message or text message
* MSGARG1 = "1st message argument
* ARGTYPE1 = 'C' "Type of 1st message argument
* MSGARG2 = "2nd message argument
* ARGTYPE2 = 'C' "Type of 2nd message argument
IMPORTING
RETURN = "
IMPORTING Parameters details for BAPI_XMI_ENTER_LOGMSG
EXTUSER - Tool user affected by the message
Data type: BAPIXMLOGR-EXTUSEROptional: Yes
Call by Reference: No ( called with pass by value option)
MSGARG3 - 3rd message argument
Data type: BAPIXMLOGR-MSGARG3Optional: Yes
Call by Reference: No ( called with pass by value option)
ARGTYPE3 - Type of 3rd message argument
Data type: BAPIXMLOGR-ARGTYPE3Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGARG4 - 4th message argument
Data type: BAPIXMLOGR-MSGARG4Optional: Yes
Call by Reference: No ( called with pass by value option)
ARGTYPE4 - Type of 4th message argument
Data type: BAPIXMLOGR-ARGTYPE4Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
INTERFACE - Interface affected by the message
Data type: BAPIXMLOGR-INTERFACEOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT - Object affected by the message
Data type: BAPIXMLOGR-OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
MSGID - Message ID in manufacturer namespace
Data type: BAPIXMLOGR-MSGIDOptional: Yes
Call by Reference: No ( called with pass by value option)
MSGTEXT - Standard message or text message
Data type: BAPIXMLOGR-MSGTEXTOptional: No
Call by Reference: No ( called with pass by value option)
MSGARG1 - 1st message argument
Data type: BAPIXMLOGR-MSGARG1Optional: Yes
Call by Reference: No ( called with pass by value option)
ARGTYPE1 - Type of 1st message argument
Data type: BAPIXMLOGR-ARGTYPE1Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MSGARG2 - 2nd message argument
Data type: BAPIXMLOGR-MSGARG2Optional: Yes
Call by Reference: No ( called with pass by value option)
ARGTYPE2 - Type of 2nd message argument
Data type: BAPIXMLOGR-ARGTYPE2Default: 'C'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_XMI_ENTER_LOGMSG
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_XMI_ENTER_LOGMSG 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_return | TYPE BAPIRET2, " | |||
| lv_extuser | TYPE BAPIXMLOGR-EXTUSER, " | |||
| lv_msgarg3 | TYPE BAPIXMLOGR-MSGARG3, " | |||
| lv_argtype3 | TYPE BAPIXMLOGR-ARGTYPE3, " 'C' | |||
| lv_msgarg4 | TYPE BAPIXMLOGR-MSGARG4, " | |||
| lv_argtype4 | TYPE BAPIXMLOGR-ARGTYPE4, " 'C' | |||
| lv_interface | TYPE BAPIXMLOGR-INTERFACE, " | |||
| lv_object | TYPE BAPIXMLOGR-OBJECT, " | |||
| lv_msgid | TYPE BAPIXMLOGR-MSGID, " | |||
| lv_msgtext | TYPE BAPIXMLOGR-MSGTEXT, " | |||
| lv_msgarg1 | TYPE BAPIXMLOGR-MSGARG1, " | |||
| lv_argtype1 | TYPE BAPIXMLOGR-ARGTYPE1, " 'C' | |||
| lv_msgarg2 | TYPE BAPIXMLOGR-MSGARG2, " | |||
| lv_argtype2 | TYPE BAPIXMLOGR-ARGTYPE2. " 'C' |
|   CALL FUNCTION 'BAPI_XMI_ENTER_LOGMSG' "Enter External Message in XMI Log |
| EXPORTING | ||
| EXTUSER | = lv_extuser | |
| MSGARG3 | = lv_msgarg3 | |
| ARGTYPE3 | = lv_argtype3 | |
| MSGARG4 | = lv_msgarg4 | |
| ARGTYPE4 | = lv_argtype4 | |
| INTERFACE | = lv_interface | |
| OBJECT | = lv_object | |
| MSGID | = lv_msgid | |
| MSGTEXT | = lv_msgtext | |
| MSGARG1 | = lv_msgarg1 | |
| ARGTYPE1 | = lv_argtype1 | |
| MSGARG2 | = lv_msgarg2 | |
| ARGTYPE2 | = lv_argtype2 | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " BAPI_XMI_ENTER_LOGMSG | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_XMI_ENTER_LOGMSG
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.| "SELECT single EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_extuser). | ||||
| "SELECT single MSGARG3 FROM BAPIXMLOGR INTO @DATA(ld_msgarg3). | ||||
| "SELECT single ARGTYPE3 FROM BAPIXMLOGR INTO @DATA(ld_argtype3). | ||||
| DATA(ld_argtype3) | = 'C'. | |||
| "SELECT single MSGARG4 FROM BAPIXMLOGR INTO @DATA(ld_msgarg4). | ||||
| "SELECT single ARGTYPE4 FROM BAPIXMLOGR INTO @DATA(ld_argtype4). | ||||
| DATA(ld_argtype4) | = 'C'. | |||
| "SELECT single INTERFACE FROM BAPIXMLOGR INTO @DATA(ld_interface). | ||||
| "SELECT single OBJECT FROM BAPIXMLOGR INTO @DATA(ld_object). | ||||
| "SELECT single MSGID FROM BAPIXMLOGR INTO @DATA(ld_msgid). | ||||
| "SELECT single MSGTEXT FROM BAPIXMLOGR INTO @DATA(ld_msgtext). | ||||
| "SELECT single MSGARG1 FROM BAPIXMLOGR INTO @DATA(ld_msgarg1). | ||||
| "SELECT single ARGTYPE1 FROM BAPIXMLOGR INTO @DATA(ld_argtype1). | ||||
| DATA(ld_argtype1) | = 'C'. | |||
| "SELECT single MSGARG2 FROM BAPIXMLOGR INTO @DATA(ld_msgarg2). | ||||
| "SELECT single ARGTYPE2 FROM BAPIXMLOGR INTO @DATA(ld_argtype2). | ||||
| DATA(ld_argtype2) | = 'C'. | |||
Search for further information about these or an SAP related objects