SAP DTL_IU_BUFFER_EXTRACTION Function Module for DTL-Upgrade: start extraction of upgrade buffers
DTL_IU_BUFFER_EXTRACTION is a standard dtl iu buffer extraction 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: start extraction of upgrade buffers 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 buffer extraction FM, simply by entering the name DTL_IU_BUFFER_EXTRACTION 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_BUFFER_EXTRACTION 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_BUFFER_EXTRACTION'"DTL-Upgrade: start extraction of upgrade buffers.
EXPORTING
IM_MODE = "Excecute / status / log
* IM_UPGID = "MWB: Ident eines Integrated Upgrade
* IM_PACKID = "Package number to specify CMIS and TDMS packages
* IM_RFC_UPG = "Logical Destination (Specified in Function Call)
IM_SESSION_ID = "MBT PCL SESSION_ID
* IM_BUFFER_PATH = "Directory where buffer is located
IMPORTING
EX_LOGNUMBER = "Application log: log number
TABLES
IT_SND_SYS_DATA = "
IT_RCV_SYS_DATA = "
* ET_STATUS = "Statusinformation für MWB-Aktivitäten
* ET_LOGNUMBERS = "
IMPORTING Parameters details for DTL_IU_BUFFER_EXTRACTION
IM_MODE - Excecute / status / log
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
IM_UPGID - MWB: Ident eines Integrated Upgrade
Data type: DMC_IU_HDR-IDENTOptional: 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_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_RFC_UPG - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_SESSION_ID - MBT PCL SESSION_ID
Data type: DMC_SESSION_IDOptional: No
Call by Reference: No ( called with pass by value option)
IM_BUFFER_PATH - Directory where buffer is located
Data type: DMC_IU_DTYPE-BTCXPGPAROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DTL_IU_BUFFER_EXTRACTION
EX_LOGNUMBER - Application log: log number
Data type: BALOGNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DTL_IU_BUFFER_EXTRACTION
IT_SND_SYS_DATA -
Data type: DMC_IU_SYS_DATAOptional: No
Call by Reference: Yes
IT_RCV_SYS_DATA -
Data type: DMC_IU_SYS_DATAOptional: No
Call by Reference: Yes
ET_STATUS - Statusinformation für MWB-Aktivitäten
Data type: DMC_ACTIVITY_STATUS_INFO_TOptional: Yes
Call by Reference: Yes
ET_LOGNUMBERS -
Data type: DMC_DTL_LOGS_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DTL_IU_BUFFER_EXTRACTION 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_im_mode | TYPE CHAR1, " | |||
| lv_ex_lognumber | TYPE BALOGNR, " | |||
| lt_it_snd_sys_data | TYPE STANDARD TABLE OF DMC_IU_SYS_DATA, " | |||
| lv_im_upgid | TYPE DMC_IU_HDR-IDENT, " | |||
| lt_it_rcv_sys_data | TYPE STANDARD TABLE OF DMC_IU_SYS_DATA, " | |||
| lt_et_status | TYPE STANDARD TABLE OF DMC_ACTIVITY_STATUS_INFO_T, " | |||
| lv_im_packid | TYPE DMC_PACKAGE_ID, " | |||
| lv_im_rfc_upg | TYPE RFCDEST, " | |||
| lt_et_lognumbers | TYPE STANDARD TABLE OF DMC_DTL_LOGS_T, " | |||
| lv_im_session_id | TYPE DMC_SESSION_ID, " | |||
| lv_im_buffer_path | TYPE DMC_IU_DTYPE-BTCXPGPAR. " |
|   CALL FUNCTION 'DTL_IU_BUFFER_EXTRACTION' "DTL-Upgrade: start extraction of upgrade buffers |
| EXPORTING | ||
| IM_MODE | = lv_im_mode | |
| IM_UPGID | = lv_im_upgid | |
| IM_PACKID | = lv_im_packid | |
| IM_RFC_UPG | = lv_im_rfc_upg | |
| IM_SESSION_ID | = lv_im_session_id | |
| IM_BUFFER_PATH | = lv_im_buffer_path | |
| IMPORTING | ||
| EX_LOGNUMBER | = lv_ex_lognumber | |
| TABLES | ||
| IT_SND_SYS_DATA | = lt_it_snd_sys_data | |
| IT_RCV_SYS_DATA | = lt_it_rcv_sys_data | |
| ET_STATUS | = lt_et_status | |
| ET_LOGNUMBERS | = lt_et_lognumbers | |
| . " DTL_IU_BUFFER_EXTRACTION | ||
ABAP code using 7.40 inline data declarations to call FM DTL_IU_BUFFER_EXTRACTION
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.| "SELECT single IDENT FROM DMC_IU_HDR INTO @DATA(ld_im_upgid). | ||||
| "SELECT single BTCXPGPAR FROM DMC_IU_DTYPE INTO @DATA(ld_im_buffer_path). | ||||
Search for further information about these or an SAP related objects