SAP ICLE_DI_DATA_PROCESS Function Module for Background Maintenance: Process Data

Search SAP Function Modules

ICLE_DI_DATA_PROCESS is a standard icle di data process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Background Maintenance: Process Data 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 icle di data process FM, simply by entering the name ICLE_DI_DATA_PROCESS into the relevant SAP transaction such as SE37 or SE38.

Function Group: ICLE_DI
Program Name: SAPLICLE_DI
Main Program: SAPLICLE_DI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICLE_DI_DATA_PROCESS 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 'ICLE_DI_DATA_PROCESS'"Background Maintenance: Process Data
  EXPORTING
*  I_XCOMMIT = 'X' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XUPDTASK = ' ' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XBAPI =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XTEST =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  I_XCALL_FROM_BDT_IN_SUBSCR =  "Module Within BDT Is Called in Subscreen
*  IV_XKEEP_LOCKS =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

 IMPORTING
   E_XERROR =  "Single-Character Flag

TABLES
*  IT_DATA =  "BP: Direct input, record (record type 1, 2 or 3)
*  ET_KEYVALUE =  "BP control: Key field values (Direct Input)
*  ET_MESSAGE =  "CBP: Messages for Each Object
*  ET_MESSAGE_DI =  "BP: DI Interface For Error Processing

.

IMPORTING Parameters details for ICLE_DI_DATA_PROCESS

I_XCOMMIT - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_XUPDTASK - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_XBAPI - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

I_XTEST - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

I_XCALL_FROM_BDT_IN_SUBSCR - Module Within BDT Is Called in Subscreen

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

IV_XKEEP_LOCKS - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

EXPORTING Parameters details for ICLE_DI_DATA_PROCESS

E_XERROR - Single-Character Flag

Data type: BUS000FLDS-CHAR1
Optional: No
Call by Reference: Yes

TABLES Parameters details for ICLE_DI_DATA_PROCESS

IT_DATA - BP: Direct input, record (record type 1, 2 or 3)

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

ET_KEYVALUE - BP control: Key field values (Direct Input)

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

ET_MESSAGE - CBP: Messages for Each Object

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

ET_MESSAGE_DI - BP: DI Interface For Error Processing

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

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

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