SAP SXMB_READ_MESSAGE_VERSION_RAW Function Module for









SXMB_READ_MESSAGE_VERSION_RAW is a standard sxmb read message version raw SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 read message version raw FM, simply by entering the name SXMB_READ_MESSAGE_VERSION_RAW into the relevant SAP transaction such as SE37 or SE38.

Function Group: SXMBPERSIST
Program Name: SAPLSXMBPERSIST
Main Program: SAPLSXMBPERSIST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:



Function SXMB_READ_MESSAGE_VERSION_RAW 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_READ_MESSAGE_VERSION_RAW'"
  EXPORTING
   SELECTION =  "
   MESSAGEKEY =  "
   VERSION_REQUEST =  "
   VERSIONTYPE =  "
   MAX_PAYLOAD_SIZE =  "

 IMPORTING
   MESSAGEBYTES =  "
   MESSAGEPAYLOAD =  "
   VERSION_RESPONSE =  "
   MAXVERSION =  "
   TIMESTAMP =  "
   MAIN_ATTR =  "
   DYNAMIC_ATTR =  "
   CODE_VERSION =  "
   EXCEPTION =  "
.



IMPORTING Parameters details for SXMB_READ_MESSAGE_VERSION_RAW

SELECTION -

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

MESSAGEKEY -

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

VERSION_REQUEST -

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

VERSIONTYPE -

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

MAX_PAYLOAD_SIZE -

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

EXPORTING Parameters details for SXMB_READ_MESSAGE_VERSION_RAW

MESSAGEBYTES -

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

MESSAGEPAYLOAD -

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

VERSION_RESPONSE -

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

MAXVERSION -

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

TIMESTAMP -

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

MAIN_ATTR -

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

DYNAMIC_ATTR -

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

CODE_VERSION -

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

EXCEPTION -

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

Copy and paste ABAP code example for SXMB_READ_MESSAGE_VERSION_RAW 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_selection  TYPE SXMS_RETURNING_STEERING, "   
lv_messagebytes  TYPE SXMS_MESSAGEBYTES, "   
lv_messagekey  TYPE SXMSMKEY, "   
lv_messagepayload  TYPE SXMS_MESSAGEPAYLOAD_TAB, "   
lv_version_request  TYPE SXMSLSQNBR, "   
lv_version_response  TYPE SXMSLSQNBR, "   
lv_maxversion  TYPE SXMSLSQNBR, "   
lv_versiontype  TYPE SXMS_VERSIONTYPE, "   
lv_timestamp  TYPE TIMESTAMPL, "   
lv_max_payload_size  TYPE SXMS_PAYLOAD_SIZE, "   
lv_main_attr  TYPE SXMS_MSGHDR30_MAIN, "   
lv_dynamic_attr  TYPE SXMS_MSGHDR30_DYNAMIC_T, "   
lv_code_version  TYPE SXMS_CODE_VERSION, "   
lv_exception  TYPE SXMSEXCEPTION. "   

  CALL FUNCTION 'SXMB_READ_MESSAGE_VERSION_RAW'  "
    EXPORTING
         SELECTION = lv_selection
         MESSAGEKEY = lv_messagekey
         VERSION_REQUEST = lv_version_request
         VERSIONTYPE = lv_versiontype
         MAX_PAYLOAD_SIZE = lv_max_payload_size
    IMPORTING
         MESSAGEBYTES = lv_messagebytes
         MESSAGEPAYLOAD = lv_messagepayload
         VERSION_RESPONSE = lv_version_response
         MAXVERSION = lv_maxversion
         TIMESTAMP = lv_timestamp
         MAIN_ATTR = lv_main_attr
         DYNAMIC_ATTR = lv_dynamic_attr
         CODE_VERSION = lv_code_version
         EXCEPTION = lv_exception
. " SXMB_READ_MESSAGE_VERSION_RAW




ABAP code using 7.40 inline data declarations to call FM SXMB_READ_MESSAGE_VERSION_RAW

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!