SAP ICL_PERFORM_GROUP_ACTTASK_NAV Function Module for









ICL_PERFORM_GROUP_ACTTASK_NAV is a standard icl perform group acttask nav SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 perform group acttask nav FM, simply by entering the name ICL_PERFORM_GROUP_ACTTASK_NAV into the relevant SAP transaction such as SE37 or SE38.

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



Function ICL_PERFORM_GROUP_ACTTASK_NAV 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_PERFORM_GROUP_ACTTASK_NAV'"
EXPORTING
IV_ACTNAV = "Navigation to Execution of Task
IV_SUBCLAIM = "Subclaim
* IV_SUBOBJCAT = "Claims Management Subobject Category
* IV_SUBOBJECT = "Participant Occurrence Subobject
* IV_ACTIVITY = "
* IV_XDONE = "Task Completed
* IV_EVENT = "Activity Management: Status-Changing Event
* IV_SUBACTIVITY = "Activity Management: Activity
* IS_TASK = "Screen Fields for Activities

IMPORTING
EV_XDONE = "
EV_PROCESSING_CANCELLED = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
EV_EVENT_DONE = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

CHANGING
* CV_DUEDATE = "Due Date

EXCEPTIONS
NO_NAVIGATION_TARGET = 1 W_MESSAGE = 2 E_MESSAGE = 3 A_MESSAGE = 4
.



IMPORTING Parameters details for ICL_PERFORM_GROUP_ACTTASK_NAV

IV_ACTNAV - Navigation to Execution of Task

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

IV_SUBCLAIM - Subclaim

Data type: ICL_SUBCL
Optional: No
Call by Reference: Yes

IV_SUBOBJCAT - Claims Management Subobject Category

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

IV_SUBOBJECT - Participant Occurrence Subobject

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

IV_ACTIVITY -

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

IV_XDONE - Task Completed

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

IV_EVENT - Activity Management: Status-Changing Event

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

IV_SUBACTIVITY - Activity Management: Activity

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

IS_TASK - Screen Fields for Activities

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

EXPORTING Parameters details for ICL_PERFORM_GROUP_ACTTASK_NAV

EV_XDONE -

Data type: ICL_XDONE
Optional: No
Call by Reference: Yes

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

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

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

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

CHANGING Parameters details for ICL_PERFORM_GROUP_ACTTASK_NAV

CV_DUEDATE - Due Date

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

EXCEPTIONS details

NO_NAVIGATION_TARGET -

Data type:
Optional: No
Call by Reference: Yes

W_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

E_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

A_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ICL_PERFORM_GROUP_ACTTASK_NAV 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_ev_xdone  TYPE ICL_XDONE, "   
lv_iv_actnav  TYPE ICL_ACTNAV, "   
lv_cv_duedate  TYPE ICL_DUEDATE, "   
lv_no_navigation_target  TYPE ICL_DUEDATE, "   
lv_w_message  TYPE ICL_DUEDATE, "   
lv_iv_subclaim  TYPE ICL_SUBCL, "   
lv_ev_processing_cancelled  TYPE BOOLE_D, "   
lv_e_message  TYPE BOOLE_D, "   
lv_iv_subobjcat  TYPE ICL_SUBOBJCAT, "   
lv_ev_event_done  TYPE BOOLE_D, "   
lv_a_message  TYPE BOOLE_D, "   
lv_iv_subobject  TYPE ICL_SUBOBJECT, "   
lv_iv_activity  TYPE ICL_ACTIVITY, "   
lv_iv_xdone  TYPE ICL_XDONE, "   
lv_iv_event  TYPE ICL_ACTLOG_EVENT, "   
lv_iv_subactivity  TYPE ICL_SUBACTIVITY, "   
lv_is_task  TYPE ICL_ACTIVITY_EXT. "   

  CALL FUNCTION 'ICL_PERFORM_GROUP_ACTTASK_NAV'  "
    EXPORTING
         IV_ACTNAV = lv_iv_actnav
         IV_SUBCLAIM = lv_iv_subclaim
         IV_SUBOBJCAT = lv_iv_subobjcat
         IV_SUBOBJECT = lv_iv_subobject
         IV_ACTIVITY = lv_iv_activity
         IV_XDONE = lv_iv_xdone
         IV_EVENT = lv_iv_event
         IV_SUBACTIVITY = lv_iv_subactivity
         IS_TASK = lv_is_task
    IMPORTING
         EV_XDONE = lv_ev_xdone
         EV_PROCESSING_CANCELLED = lv_ev_processing_cancelled
         EV_EVENT_DONE = lv_ev_event_done
    CHANGING
         CV_DUEDATE = lv_cv_duedate
    EXCEPTIONS
        NO_NAVIGATION_TARGET = 1
        W_MESSAGE = 2
        E_MESSAGE = 3
        A_MESSAGE = 4
. " ICL_PERFORM_GROUP_ACTTASK_NAV




ABAP code using 7.40 inline data declarations to call FM ICL_PERFORM_GROUP_ACTTASK_NAV

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!