SAP ICL_IF_ACTIVITYLOG_GET_FOR_OBJ Function Module for Determines Tasks and Log Entries for a Claim
ICL_IF_ACTIVITYLOG_GET_FOR_OBJ is a standard icl if activitylog get for obj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Tasks and Log Entries for a Claim 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 if activitylog get for obj FM, simply by entering the name ICL_IF_ACTIVITYLOG_GET_FOR_OBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_IF1
Program Name: SAPLICL_IF1
Main Program: SAPLICL_IF1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICL_IF_ACTIVITYLOG_GET_FOR_OBJ 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_IF_ACTIVITYLOG_GET_FOR_OBJ'"Determines Tasks and Log Entries for a Claim.
EXPORTING
IV_SUBCL = "Subclaim
IV_SUBOBJCAT = "Subobject Category
IV_SUBOBJECT = "Subclaim Object ID for Navigation
* IV_FILTER = 'P' "Activity: Filter on Log Entry, Task ...
* IV_EXACT = 'X' "X: Exact; ' ': Plus Subobjects
TABLES
ET_ACTIVITY = "Screen Fields for Activities
IMPORTING Parameters details for ICL_IF_ACTIVITYLOG_GET_FOR_OBJ
IV_SUBCL - Subclaim
Data type: ICL_SUBCLOptional: No
Call by Reference: Yes
IV_SUBOBJCAT - Subobject Category
Data type: ICL_SUBOBJCATOptional: No
Call by Reference: Yes
IV_SUBOBJECT - Subclaim Object ID for Navigation
Data type: ICL_SUBOBJECTAOptional: No
Call by Reference: Yes
IV_FILTER - Activity: Filter on Log Entry, Task ...
Data type: ICL_ACTIVITY_FILTERDefault: 'P'
Optional: Yes
Call by Reference: Yes
IV_EXACT - X: Exact; SPACE: Plus Subobjects
Data type: IAM_BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for ICL_IF_ACTIVITYLOG_GET_FOR_OBJ
ET_ACTIVITY - Screen Fields for Activities
Data type: ICL_ACTIVITY_EXTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ICL_IF_ACTIVITYLOG_GET_FOR_OBJ 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_iv_subcl | TYPE ICL_SUBCL, " | |||
| lt_et_activity | TYPE STANDARD TABLE OF ICL_ACTIVITY_EXT, " | |||
| lv_iv_subobjcat | TYPE ICL_SUBOBJCAT, " | |||
| lv_iv_subobject | TYPE ICL_SUBOBJECTA, " | |||
| lv_iv_filter | TYPE ICL_ACTIVITY_FILTER, " 'P' | |||
| lv_iv_exact | TYPE IAM_BOOLE_D. " 'X' |
|   CALL FUNCTION 'ICL_IF_ACTIVITYLOG_GET_FOR_OBJ' "Determines Tasks and Log Entries for a Claim |
| EXPORTING | ||
| IV_SUBCL | = lv_iv_subcl | |
| IV_SUBOBJCAT | = lv_iv_subobjcat | |
| IV_SUBOBJECT | = lv_iv_subobject | |
| IV_FILTER | = lv_iv_filter | |
| IV_EXACT | = lv_iv_exact | |
| TABLES | ||
| ET_ACTIVITY | = lt_et_activity | |
| . " ICL_IF_ACTIVITYLOG_GET_FOR_OBJ | ||
ABAP code using 7.40 inline data declarations to call FM ICL_IF_ACTIVITYLOG_GET_FOR_OBJ
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.| DATA(ld_iv_filter) | = 'P'. | |||
| DATA(ld_iv_exact) | = 'X'. | |||
Search for further information about these or an SAP related objects