SAP ICL_DEATH_DATA_CHECK Function Module for Consistency Check on Death Data
ICL_DEATH_DATA_CHECK is a standard icl death data check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Consistency Check on Death 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 icl death data check FM, simply by entering the name ICL_DEATH_DATA_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_ACCIDENT_INT
Program Name: SAPLICL_ACCIDENT_INT
Main Program: SAPLICL_ACCIDENT_INT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICL_DEATH_DATA_CHECK 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 'ICL_DEATH_DATA_CHECK'"Consistency Check on Death Data.
EXPORTING
IS_DATES = "Death and Notification Dates
IMPORTING
ET_RET_MSG = "Return Table for Check Modules
EXCEPTIONS
READ_BPARTNER_DATA_FAILED = 1
IMPORTING Parameters details for ICL_DEATH_DATA_CHECK
IS_DATES - Death and Notification Dates
Data type: ICL_ACC_DEATH_DATES_S_ALOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ICL_DEATH_DATA_CHECK
ET_RET_MSG - Return Table for Check Modules
Data type: ICL_RET_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
READ_BPARTNER_DATA_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICL_DEATH_DATA_CHECK 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_is_dates | TYPE ICL_ACC_DEATH_DATES_S_AL, " | |||
| lv_et_ret_msg | TYPE ICL_RET_T, " | |||
| lv_read_bpartner_data_failed | TYPE ICL_RET_T. " |
|   CALL FUNCTION 'ICL_DEATH_DATA_CHECK' "Consistency Check on Death Data |
| EXPORTING | ||
| IS_DATES | = lv_is_dates | |
| IMPORTING | ||
| ET_RET_MSG | = lv_et_ret_msg | |
| EXCEPTIONS | ||
| READ_BPARTNER_DATA_FAILED = 1 | ||
| . " ICL_DEATH_DATA_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ICL_DEATH_DATA_CHECK
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