SAP CP_CL_S_TSK_LTEXT_CREATE Function Module for NOTRANSL: Anlegen des Langtextes zu einem Plankopf
CP_CL_S_TSK_LTEXT_CREATE is a standard cp cl s tsk ltext create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Anlegen des Langtextes zu einem Plankopf 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 cp cl s tsk ltext create FM, simply by entering the name CP_CL_S_TSK_LTEXT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPCL_TSK
Program Name: SAPLCPCL_TSK
Main Program: SAPLCPCL_TSK
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CP_CL_S_TSK_LTEXT_CREATE 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 'CP_CL_S_TSK_LTEXT_CREATE'"NOTRANSL: Anlegen des Langtextes zu einem Plankopf.
EXPORTING
I_KEY_DATE = "Valid-From Date
I_ECN_S = "Change Number
I_PLNTY = "
I_PLNNR = "Key for Task List Group
I_PLNAL = "Group Counter
* I_LANGUAGE = SY-LANGU "Current Language
TABLES
I_TEXT = "SAPscript: Text Lines
EXCEPTIONS
NO_VALID_TASK = 1 WRONG_KEY = 2 TEXT_PROCESSING_ABORTED = 3 TASK_NOT_CHANGED = 4 TEXT_ALREADY_EXISTS = 5
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCPCL_TSK_001 Customer authorization check for the task list headers (EWB)
EXIT_SAPLCPCL_TSK_002 Customer units of measure test for reference to operation set (EWB)
EXIT_SAPLCPCL_TSK_003 Customer authorization checks for material/routing assignment (EWB)
IMPORTING Parameters details for CP_CL_S_TSK_LTEXT_CREATE
I_KEY_DATE - Valid-From Date
Data type: TSK_CLASS_DATA-DATUVOptional: No
Call by Reference: No ( called with pass by value option)
I_ECN_S - Change Number
Data type: TSK_CLASS_DATA-AENNROptional: No
Call by Reference: No ( called with pass by value option)
I_PLNTY -
Data type: TSK_CLASS_DATA-PLNTYOptional: No
Call by Reference: No ( called with pass by value option)
I_PLNNR - Key for Task List Group
Data type: TSK_CLASS_DATA-PLNNROptional: No
Call by Reference: No ( called with pass by value option)
I_PLNAL - Group Counter
Data type: TSK_CLASS_DATA-PLNALOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - Current Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CP_CL_S_TSK_LTEXT_CREATE
I_TEXT - SAPscript: Text Lines
Data type: TLINEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_VALID_TASK -
Data type:Optional: No
Call by Reference: Yes
WRONG_KEY -
Data type:Optional: No
Call by Reference: Yes
TEXT_PROCESSING_ABORTED -
Data type:Optional: No
Call by Reference: Yes
TASK_NOT_CHANGED -
Data type:Optional: No
Call by Reference: Yes
TEXT_ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CP_CL_S_TSK_LTEXT_CREATE 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: | ||||
| lt_i_text | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_i_key_date | TYPE TSK_CLASS_DATA-DATUV, " | |||
| lv_no_valid_task | TYPE TSK_CLASS_DATA, " | |||
| lv_i_ecn_s | TYPE TSK_CLASS_DATA-AENNR, " | |||
| lv_wrong_key | TYPE TSK_CLASS_DATA, " | |||
| lv_i_plnty | TYPE TSK_CLASS_DATA-PLNTY, " | |||
| lv_text_processing_aborted | TYPE TSK_CLASS_DATA, " | |||
| lv_i_plnnr | TYPE TSK_CLASS_DATA-PLNNR, " | |||
| lv_task_not_changed | TYPE TSK_CLASS_DATA, " | |||
| lv_i_plnal | TYPE TSK_CLASS_DATA-PLNAL, " | |||
| lv_text_already_exists | TYPE TSK_CLASS_DATA, " | |||
| lv_i_language | TYPE SY-LANGU. " SY-LANGU |
|   CALL FUNCTION 'CP_CL_S_TSK_LTEXT_CREATE' "NOTRANSL: Anlegen des Langtextes zu einem Plankopf |
| EXPORTING | ||
| I_KEY_DATE | = lv_i_key_date | |
| I_ECN_S | = lv_i_ecn_s | |
| I_PLNTY | = lv_i_plnty | |
| I_PLNNR | = lv_i_plnnr | |
| I_PLNAL | = lv_i_plnal | |
| I_LANGUAGE | = lv_i_language | |
| TABLES | ||
| I_TEXT | = lt_i_text | |
| EXCEPTIONS | ||
| NO_VALID_TASK = 1 | ||
| WRONG_KEY = 2 | ||
| TEXT_PROCESSING_ABORTED = 3 | ||
| TASK_NOT_CHANGED = 4 | ||
| TEXT_ALREADY_EXISTS = 5 | ||
| . " CP_CL_S_TSK_LTEXT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM CP_CL_S_TSK_LTEXT_CREATE
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.| "SELECT single DATUV FROM TSK_CLASS_DATA INTO @DATA(ld_i_key_date). | ||||
| "SELECT single AENNR FROM TSK_CLASS_DATA INTO @DATA(ld_i_ecn_s). | ||||
| "SELECT single PLNTY FROM TSK_CLASS_DATA INTO @DATA(ld_i_plnty). | ||||
| "SELECT single PLNNR FROM TSK_CLASS_DATA INTO @DATA(ld_i_plnnr). | ||||
| "SELECT single PLNAL FROM TSK_CLASS_DATA INTO @DATA(ld_i_plnal). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_language). | ||||
| DATA(ld_i_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects