SAP DTL_IU_EXECUTE_XPRAS Function Module for DTL-Upgrade: get all XPRAs from a buffer extraction or sp diff analyse

Search SAP Function Modules

DTL_IU_EXECUTE_XPRAS is a standard dtl iu execute xpras SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DTL-Upgrade: get all XPRAs from a buffer extraction or sp diff analyse 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 dtl iu execute xpras FM, simply by entering the name DTL_IU_EXECUTE_XPRAS into the relevant SAP transaction such as SE37 or SE38.

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

Function DTL_IU_EXECUTE_XPRAS 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 'DTL_IU_EXECUTE_XPRAS'"DTL-Upgrade: get all XPRAs from a buffer extraction or sp diff analyse
  EXPORTING
   IM_MODE =  "DMC: General ID
*  IM_UPGID =  "DMC: General ID
*  IM_PACKID =  "Package number to specify CMIS and TDMS packages
   IM_SESSION_ID =  "MBT PCL SESSION_ID
*  IM_RFC_RCV =  "Logical Destination (Specified in Function Call)
*  IM_RCV_CLNT =  "Client
*  IM_CONTINUE = ' ' "Continue terminated XPRA run
*  IM_RESTORE = ' ' "Restore system after terminated XPRA run

 IMPORTING
   EX_LOGNUMBER =  "Application log: log number

TABLES
*  ET_STATUS =  "Status info for MWB activities
*  ET_LOGNUMBERS =  "table of application log numbers

.

IMPORTING Parameters details for DTL_IU_EXECUTE_XPRAS

IM_MODE - DMC: General ID

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

IM_UPGID - DMC: General ID

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

IM_PACKID - Package number to specify CMIS and TDMS packages

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

IM_SESSION_ID - MBT PCL SESSION_ID

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

IM_RFC_RCV - Logical Destination (Specified in Function Call)

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

IM_RCV_CLNT - Client

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

IM_CONTINUE - Continue terminated XPRA run

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

IM_RESTORE - Restore system after terminated XPRA run

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

EXPORTING Parameters details for DTL_IU_EXECUTE_XPRAS

EX_LOGNUMBER - Application log: log number

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

TABLES Parameters details for DTL_IU_EXECUTE_XPRAS

ET_STATUS - Status info for MWB activities

Data type: DMC_ACTIVITY_STATUS_INFO_T
Optional: Yes
Call by Reference: Yes

ET_LOGNUMBERS - table of application log numbers

Data type: DMC_DTL_LOGS_T
Optional: Yes
Call by Reference: Yes

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

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