SXMI_LOGMSG_ENTER_INT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name SXMI_LOGMSG_ENTER_INT into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
SXMI
Released Date:
01.04.1997
Processing type: Normal fucntion module
CALL FUNCTION 'SXMI_LOGMSG_ENTER_INT' "Enter Internal Message in XMI Log
EXPORTING
* extuser = " txmilograw-extuser External user affected by the message
* interface = " txmilograw-interface Interface affected by the message
* object = " c Object affected by the message
msgid = " c T100 message application area
msgno = " sy-msgno T100 message identification
* msgarg1 = " c 1st message argument
* argtype1 = 'C' " txmilograw-argtype1 Type of 1st message argument
* msgarg2 = " c 2nd message argument
* argtype2 = 'C' " txmilograw-argtype2 Type of 2nd message argument
* msgarg3 = " c 3rd message argument
* argtype3 = 'C' " txmilograw-argtype3 Type of 3rd message argument
* msgarg4 = " c 4th message argument
* argtype4 = 'C' " txmilograw-argtype4 Type of 4th message argument
* auditlevel = '0' " txmilograw-auditlevel Audit level of the message
EXCEPTIONS
INVALID_PARAMETERS = 1 " Arguments have invalid values
CANT_LOG = 2 " Message could not be stored in the log
PROBLEM_DETECTED = 3 " Internal problem (see system log)
. " SXMI_LOGMSG_ENTER_INT
The ABAP code below is a full code listing to execute function module SXMI_LOGMSG_ENTER_INT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
SELECT single EXTUSER
FROM TXMILOGRAW
INTO @DATA(ld_extuser).
SELECT single INTERFACE
FROM TXMILOGRAW
INTO @DATA(ld_interface).
DATA(ld_object) = 'Check type of data required'.
DATA(ld_msgid) = 'Check type of data required'.
DATA(ld_msgno) = 'Check type of data required'.
DATA(ld_msgarg1) = 'some text here'.
SELECT single ARGTYPE1
FROM TXMILOGRAW
INTO @DATA(ld_argtype1).
DATA(ld_msgarg2) = 'some text here'.
SELECT single ARGTYPE2
FROM TXMILOGRAW
INTO @DATA(ld_argtype2).
DATA(ld_msgarg3) = 'some text here'.
SELECT single ARGTYPE3
FROM TXMILOGRAW
INTO @DATA(ld_argtype3).
DATA(ld_msgarg4) = 'some text here'.
SELECT single ARGTYPE4
FROM TXMILOGRAW
INTO @DATA(ld_argtype4).
SELECT single AUDITLEVEL
FROM TXMILOGRAW
INTO @DATA(ld_auditlevel).
. CALL FUNCTION 'SXMI_LOGMSG_ENTER_INT' EXPORTING * extuser = ld_extuser * interface = ld_interface * object = ld_object msgid = ld_msgid msgno = ld_msgno * msgarg1 = ld_msgarg1 * argtype1 = ld_argtype1 * msgarg2 = ld_msgarg2 * argtype2 = ld_argtype2 * msgarg3 = ld_msgarg3 * argtype3 = ld_argtype3 * msgarg4 = ld_msgarg4 * argtype4 = ld_argtype4 * auditlevel = ld_auditlevel EXCEPTIONS INVALID_PARAMETERS = 1 CANT_LOG = 2 PROBLEM_DETECTED = 3 . " SXMI_LOGMSG_ENTER_INT
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_extuser | TYPE TXMILOGRAW-EXTUSER , |
| ld_interface | TYPE TXMILOGRAW-INTERFACE , |
| ld_object | TYPE C , |
| ld_msgid | TYPE C , |
| ld_msgno | TYPE SY-MSGNO , |
| ld_msgarg1 | TYPE C , |
| ld_argtype1 | TYPE TXMILOGRAW-ARGTYPE1 , |
| ld_msgarg2 | TYPE C , |
| ld_argtype2 | TYPE TXMILOGRAW-ARGTYPE2 , |
| ld_msgarg3 | TYPE C , |
| ld_argtype3 | TYPE TXMILOGRAW-ARGTYPE3 , |
| ld_msgarg4 | TYPE C , |
| ld_argtype4 | TYPE TXMILOGRAW-ARGTYPE4 , |
| ld_auditlevel | TYPE TXMILOGRAW-AUDITLEVEL . |
EXAMPLE
...See here for full SAP fm documentation
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SXMI_LOGMSG_ENTER_INT or its description.