SAP SXMB_GET_MESSAGE_TRACE Function Module for Returns trace of message

Search SAP Function Modules

SXMB_GET_MESSAGE_TRACE is a standard sxmb get message trace SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns trace of message 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 sxmb get message trace FM, simply by entering the name SXMB_GET_MESSAGE_TRACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXMB_MONI
Program Name: SAPLSXMB_MONI
Main Program: SAPLSXMB_MONI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SXMB_GET_MESSAGE_TRACE 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 'SXMB_GET_MESSAGE_TRACE'"Returns trace of message
  EXPORTING
   IM_MSGKEY =  "XI Message Key
*  IM_ARCHIVE =  "(1=Read from Archive, 0 = Read from Database)
*  IM_VERSION =  "Sequential number for ID of Message log

 IMPORTING
   EX_TRACE =  "Trace bytes

EXCEPTIONS
   NOT_AUTHORIZED = 1    NO_MESSAGE = 2    INTERNAL_ERROR = 3 

.

IMPORTING Parameters details for SXMB_GET_MESSAGE_TRACE

IM_MSGKEY - XI Message Key

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

IM_ARCHIVE - (1=Read from Archive, 0 = Read from Database)

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

IM_VERSION - Sequential number for ID of Message log

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

EXPORTING Parameters details for SXMB_GET_MESSAGE_TRACE

EX_TRACE - Trace bytes

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

EXCEPTIONS details

NOT_AUTHORIZED - Not authorized to display message payload

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

NO_MESSAGE - Message not found

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

INTERNAL_ERROR - Internal error

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

Copy and paste ABAP code example for SXMB_GET_MESSAGE_TRACE 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.

ABAP code using 7.40 inline data declarations to call FM SXMB_GET_MESSAGE_TRACE

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