SAP LTSK_TASK_SPLIT_MAINTAIN Function Module for Adjust task group reference to new task bundle created









LTSK_TASK_SPLIT_MAINTAIN is a standard ltsk task split maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Adjust task group reference to new task bundle created 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 ltsk task split maintain FM, simply by entering the name LTSK_TASK_SPLIT_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

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



Function LTSK_TASK_SPLIT_MAINTAIN 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 'LTSK_TASK_SPLIT_MAINTAIN'"Adjust task group reference to new task bundle created
EXPORTING
I_LOCAT = "Site
* I_SERVICE_CALLER = "Calling service

TABLES
* IT_TASKS = "Tasks to update
* IT_REQUEST_ITEMS = "Request Work Unit for Task Processing
* IT_LTKPL = "Task pool
.



IMPORTING Parameters details for LTSK_TASK_SPLIT_MAINTAIN

I_LOCAT - Site

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

I_SERVICE_CALLER - Calling service

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

TABLES Parameters details for LTSK_TASK_SPLIT_MAINTAIN

IT_TASKS - Tasks to update

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

IT_REQUEST_ITEMS - Request Work Unit for Task Processing

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

IT_LTKPL - Task pool

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

Copy and paste ABAP code example for LTSK_TASK_SPLIT_MAINTAIN 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_i_locat  TYPE LTRM_LOCAT, "   
lt_it_tasks  TYPE STANDARD TABLE OF LRITK, "   
lt_it_request_items  TYPE STANDARD TABLE OF LTRQ_WORK_UNIT, "   
lv_i_service_caller  TYPE LTRM_SERVICE, "   
lt_it_ltkpl  TYPE STANDARD TABLE OF LTSKT_T_LTKPL. "   

  CALL FUNCTION 'LTSK_TASK_SPLIT_MAINTAIN'  "Adjust task group reference to new task bundle created
    EXPORTING
         I_LOCAT = lv_i_locat
         I_SERVICE_CALLER = lv_i_service_caller
    TABLES
         IT_TASKS = lt_it_tasks
         IT_REQUEST_ITEMS = lt_it_request_items
         IT_LTKPL = lt_it_ltkpl
. " LTSK_TASK_SPLIT_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM LTSK_TASK_SPLIT_MAINTAIN

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!