SAP DMC_IUC_BUFFER_EXTRACTION Function Module for MWB-Upgrade: Extract and Analyze Upgrade Buffer
DMC_IUC_BUFFER_EXTRACTION is a standard dmc iuc 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 MWB-Upgrade: Extract and Analyze Upgrade Buffer 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 dmc iuc buffer extraction FM, simply by entering the name DMC_IUC_BUFFER_EXTRACTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMC_IU
Program Name: SAPLDMC_IU
Main Program: SAPLDMC_IU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function DMC_IUC_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 'DMC_IUC_BUFFER_EXTRACTION'"MWB-Upgrade: Extract and Analyze Upgrade Buffer.
EXPORTING
IM_UPG_ID = "Upgrade ID
IM_RFC_UPGSYS = "RFC connection to upgrade system
IM_TABIM_BUFF = "TABIM buffer name
IM_XPRAS_BUFF = "XPRA buffer name
IM_SAVE_TRKORR_OBJ = "Extract data from transports in buffer
IM_BUFFER_PATH = "Deviating path to buffer files
IMPORTING Parameters details for DMC_IUC_BUFFER_EXTRACTION
IM_UPG_ID - Upgrade ID
Data type: DMC_IU_HDR-IDENTOptional: No
Call by Reference: No ( called with pass by value option)
IM_RFC_UPGSYS - RFC connection to upgrade system
Data type: DMC_SCREEN-RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
IM_TABIM_BUFF - TABIM buffer name
Data type: DMC_IU_DTYPE-CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
IM_XPRAS_BUFF - XPRA buffer name
Data type: DMC_IU_DTYPE-CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
IM_SAVE_TRKORR_OBJ - Extract data from transports in buffer
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IM_BUFFER_PATH - Deviating path to buffer files
Data type: DMC_IU_DTYPE-BTCXPGPAROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DMC_IUC_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_upg_id | TYPE DMC_IU_HDR-IDENT, " | |||
lv_im_rfc_upgsys | TYPE DMC_SCREEN-RFCDEST, " | |||
lv_im_tabim_buff | TYPE DMC_IU_DTYPE-CHAR32, " | |||
lv_im_xpras_buff | TYPE DMC_IU_DTYPE-CHAR32, " | |||
lv_im_save_trkorr_obj | TYPE BOOLEAN, " | |||
lv_im_buffer_path | TYPE DMC_IU_DTYPE-BTCXPGPAR. " |
  CALL FUNCTION 'DMC_IUC_BUFFER_EXTRACTION' "MWB-Upgrade: Extract and Analyze Upgrade Buffer |
EXPORTING | ||
IM_UPG_ID | = lv_im_upg_id | |
IM_RFC_UPGSYS | = lv_im_rfc_upgsys | |
IM_TABIM_BUFF | = lv_im_tabim_buff | |
IM_XPRAS_BUFF | = lv_im_xpras_buff | |
IM_SAVE_TRKORR_OBJ | = lv_im_save_trkorr_obj | |
IM_BUFFER_PATH | = lv_im_buffer_path | |
. " DMC_IUC_BUFFER_EXTRACTION |
ABAP code using 7.40 inline data declarations to call FM DMC_IUC_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_upg_id). | ||||
"SELECT single RFCDEST FROM DMC_SCREEN INTO @DATA(ld_im_rfc_upgsys). | ||||
"SELECT single CHAR32 FROM DMC_IU_DTYPE INTO @DATA(ld_im_tabim_buff). | ||||
"SELECT single CHAR32 FROM DMC_IU_DTYPE INTO @DATA(ld_im_xpras_buff). | ||||
"SELECT single BTCXPGPAR FROM DMC_IU_DTYPE INTO @DATA(ld_im_buffer_path). | ||||
Search for further information about these or an SAP related objects