SAP Function Modules
ICL_DI_DATA_PROCESS SAP Function module - Background Maintenance: Process Data
ICL_DI_DATA_PROCESS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name ICL_DI_DATA_PROCESS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
ICL_DI
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM ICL_DI_DATA_PROCESS - ICL DI DATA PROCESS
CALL FUNCTION 'ICL_DI_DATA_PROCESS' "Background Maintenance: Process Data
* EXPORTING
* i_xcommit = 'X' " boole-boole Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* i_xupdtask = SPACE " boole-boole Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* i_xbapi = " boole-boole Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* i_xtest = " boole-boole Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* i_xcall_from_bdt_in_subscr = " boole-boole Module Within BDT Is Called in Subscreen
* iv_xkeep_locks = " boole_d Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* iv_xwait_for_dequeue = " boole_d Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* iv_xdlve2_on_commit = " boole_d Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
IMPORTING
e_xerror = " bus000flds-char1 Single-Character Flag
* TABLES
* it_data = " bussdi BP: Direct input, record (record type 1, 2 or 3)
* et_keyvalue = " busskeyval BP control: Key field values (Direct Input)
* et_message = " bus0msg1 CBP: Messages for Each Object
* et_message_di = " bussprot_x BP: DI Interface For Error Processing
. " ICL_DI_DATA_PROCESS
ABAP code example for Function Module ICL_DI_DATA_PROCESS
The ABAP code below is a full code listing to execute function module ICL_DI_DATA_PROCESS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_e_xerror | TYPE BUS000FLDS-CHAR1 , |
| it_it_data | TYPE STANDARD TABLE OF BUSSDI,"TABLES PARAM |
| wa_it_data | LIKE LINE OF it_it_data , |
| it_et_keyvalue | TYPE STANDARD TABLE OF BUSSKEYVAL,"TABLES PARAM |
| wa_et_keyvalue | LIKE LINE OF it_et_keyvalue , |
| it_et_message | TYPE STANDARD TABLE OF BUS0MSG1,"TABLES PARAM |
| wa_et_message | LIKE LINE OF it_et_message , |
| it_et_message_di | TYPE STANDARD TABLE OF BUSSPROT_X,"TABLES PARAM |
| wa_et_message_di | LIKE LINE OF it_et_message_di . |
DATA(ld_i_xcommit) = some text here
DATA(ld_i_xupdtask) = some text here
DATA(ld_i_xbapi) = some text here
DATA(ld_i_xtest) = some text here
DATA(ld_i_xcall_from_bdt_in_subscr) = some text here
DATA(ld_iv_xkeep_locks) = 'Check type of data required'.
DATA(ld_iv_xwait_for_dequeue) = 'Check type of data required'.
DATA(ld_iv_xdlve2_on_commit) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_it_data to it_it_data.
"populate fields of struture and append to itab
append wa_et_keyvalue to it_et_keyvalue.
"populate fields of struture and append to itab
append wa_et_message to it_et_message.
"populate fields of struture and append to itab
append wa_et_message_di to it_et_message_di. . CALL FUNCTION 'ICL_DI_DATA_PROCESS' * EXPORTING * i_xcommit = ld_i_xcommit * i_xupdtask = ld_i_xupdtask * i_xbapi = ld_i_xbapi * i_xtest = ld_i_xtest * i_xcall_from_bdt_in_subscr = ld_i_xcall_from_bdt_in_subscr * iv_xkeep_locks = ld_iv_xkeep_locks * iv_xwait_for_dequeue = ld_iv_xwait_for_dequeue * iv_xdlve2_on_commit = ld_iv_xdlve2_on_commit IMPORTING e_xerror = ld_e_xerror * TABLES * it_data = it_it_data * et_keyvalue = it_et_keyvalue * et_message = it_et_message * et_message_di = it_et_message_di . " ICL_DI_DATA_PROCESS
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_e_xerror | TYPE BUS000FLDS-CHAR1 , |
| ld_i_xcommit | TYPE BOOLE-BOOLE , |
| it_it_data | TYPE STANDARD TABLE OF BUSSDI , |
| wa_it_data | LIKE LINE OF it_it_data, |
| ld_i_xupdtask | TYPE BOOLE-BOOLE , |
| it_et_keyvalue | TYPE STANDARD TABLE OF BUSSKEYVAL , |
| wa_et_keyvalue | LIKE LINE OF it_et_keyvalue, |
| ld_i_xbapi | TYPE BOOLE-BOOLE , |
| it_et_message | TYPE STANDARD TABLE OF BUS0MSG1 , |
| wa_et_message | LIKE LINE OF it_et_message, |
| ld_i_xtest | TYPE BOOLE-BOOLE , |
| it_et_message_di | TYPE STANDARD TABLE OF BUSSPROT_X , |
| wa_et_message_di | LIKE LINE OF it_et_message_di, |
| ld_i_xcall_from_bdt_in_subscr | TYPE BOOLE-BOOLE , |
| ld_iv_xkeep_locks | TYPE BOOLE_D , |
| ld_iv_xwait_for_dequeue | TYPE BOOLE_D , |
| ld_iv_xdlve2_on_commit | TYPE BOOLE_D . |
ld_i_xcommit = some text here
"populate fields of struture and append to itab
append wa_it_data to it_it_data.
ld_i_xupdtask = some text here
"populate fields of struture and append to itab
append wa_et_keyvalue to it_et_keyvalue.
ld_i_xbapi = some text here
"populate fields of struture and append to itab
append wa_et_message to it_et_message.
ld_i_xtest = some text here
"populate fields of struture and append to itab
append wa_et_message_di to it_et_message_di.
ld_i_xcall_from_bdt_in_subscr = some text here
ld_iv_xkeep_locks = 'Check type of data required'.
ld_iv_xwait_for_dequeue = 'Check type of data required'.
ld_iv_xdlve2_on_commit = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ICL_DI_DATA_PROCESS or its description.
ICL_DI_DATA_PROCESS - Background Maintenance: Process Data ICL_DI_DATA_GET - Transfers Global Data Table ICL_DI_DATA_COLLECT - Background Maintenance: Collect Claim Data ICL_DIVIDE_AND_ROUND_UP - ICL_DISTRIBUTE_AMOUNT - ICL_DISTANCE_INDICATOR_2 - Determination of Distance Between Two Addresses (International)