SAP SXMS_PP_EXEC Function Module for









SXMS_PP_EXEC is a standard sxms pp exec 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 sxms pp exec FM, simply by entering the name SXMS_PP_EXEC into the relevant SAP transaction such as SE37 or SE38.

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



Function SXMS_PP_EXEC 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 'SXMS_PP_EXEC'"
  EXPORTING
   MSGID =  "
   QUEUE =  "
   MAN_RESTART_TRACE =  "
   PID =  "
   RESTART_VERSION =  "
   ERROR_TRACE_STRING =  "
   EOIO_FORCE =  "
   SKIP_XML_VALID =  "
   MANUAL_RETRY =  "
   LAST_VERSION_LOG =  "
   TID_OLD =  "

 IMPORTING
   BAPIRETURN =  "

EXCEPTIONS
   SWITCH_FAILED = 1    NO_RFC_CALL_ALLOWED = 2
.



IMPORTING Parameters details for SXMS_PP_EXEC

MSGID -

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

QUEUE -

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

MAN_RESTART_TRACE -

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

PID -

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

RESTART_VERSION -

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

ERROR_TRACE_STRING -

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

EOIO_FORCE -

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

SKIP_XML_VALID -

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

MANUAL_RETRY -

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

LAST_VERSION_LOG -

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

TID_OLD -

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

EXPORTING Parameters details for SXMS_PP_EXEC

BAPIRETURN -

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

EXCEPTIONS details

SWITCH_FAILED -

Data type:
Optional: No
Call by Reference: Yes

NO_RFC_CALL_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SXMS_PP_EXEC 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_msgid  TYPE SXMSMGUID, "   
lv_bapireturn  TYPE BAPIRET2, "   
lv_switch_failed  TYPE BAPIRET2, "   
lv_queue  TYPE TRFCQNAM, "   
lv_man_restart_trace  TYPE CHAR1, "   
lv_pid  TYPE SXMSPID, "   
lv_no_rfc_call_allowed  TYPE SXMSPID, "   
lv_restart_version  TYPE SXMSLSQNBR, "   
lv_error_trace_string  TYPE STRING, "   
lv_eoio_force  TYPE CHAR1, "   
lv_skip_xml_valid  TYPE SXMS_XMLVAL, "   
lv_manual_retry  TYPE I, "   
lv_last_version_log  TYPE SXMSLSQNBR, "   
lv_tid_old  TYPE ARFCTID. "   

  CALL FUNCTION 'SXMS_PP_EXEC'  "
    EXPORTING
         MSGID = lv_msgid
         QUEUE = lv_queue
         MAN_RESTART_TRACE = lv_man_restart_trace
         PID = lv_pid
         RESTART_VERSION = lv_restart_version
         ERROR_TRACE_STRING = lv_error_trace_string
         EOIO_FORCE = lv_eoio_force
         SKIP_XML_VALID = lv_skip_xml_valid
         MANUAL_RETRY = lv_manual_retry
         LAST_VERSION_LOG = lv_last_version_log
         TID_OLD = lv_tid_old
    IMPORTING
         BAPIRETURN = lv_bapireturn
    EXCEPTIONS
        SWITCH_FAILED = 1
        NO_RFC_CALL_ALLOWED = 2
. " SXMS_PP_EXEC




ABAP code using 7.40 inline data declarations to call FM SXMS_PP_EXEC

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!