SAP CP_CL_P_TSK_REF_CHECK Function Module for NOTRANSL: Prüfung bei Anlegen einer Referenz

Search SAP Function Modules

CP_CL_P_TSK_REF_CHECK is a standard cp cl p tsk ref 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 NOTRANSL: Prüfung bei Anlegen einer Referenz 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 p tsk ref check FM, simply by entering the name CP_CL_P_TSK_REF_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function CP_CL_P_TSK_REF_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 'CP_CL_P_TSK_REF_CHECK'"NOTRANSL: Prüfung bei Anlegen einer Referenz
  EXPORTING
   I_KEY_DATE =  "ABAP System Field: Current Date of Application Server
*  I_KEY_DATE_ECM_EVALUATION = ' ' "ABAP System Field: Current Date of Application Server
   I_PLNTY =  "Task List Type
   I_PLNNR =  "Key for Task List Group
   I_PLNAL =  "Group Counter
   I_VPLNR =  "Key for Task List Group
   I_VPLAL =  "Group Counter

 IMPORTING
   E_VPLTY =  "Task List Type
   E_LOSVN =  "From Lot Size
   E_LOSBS =  "To lot size
   E_PLNME =  "Task list unit of measure

EXCEPTIONS
   WRONG_TASK_TYPE = 1    LOTSIZE_INTERVAL_INCOMPATIBLE = 10    NO_VALID_TASK = 2    NO_VALID_REF_TASK = 3    DIFFERENT_UNIT_OF_MEASURE = 4    REF_TASK_NO_VALID_STATUS = 5    REF_TASK_NOT_RELEASED = 6    REF_TASK_NO_COSTING = 7    DIFFERENT_COMPANY_CODES = 8    DIFFERENT_CONTROLLING_AREAS = 9 

.

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_P_TSK_REF_CHECK

I_KEY_DATE - ABAP System Field: Current Date of Application Server

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

I_KEY_DATE_ECM_EVALUATION - ABAP System Field: Current Date of Application Server

Data type: SY-DATUM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLNTY - Task List Type

Data type: TSK_CLASS_DATA-PLNTY
Optional: No
Call by Reference: No ( called with pass by value option)

I_PLNNR - Key for Task List Group

Data type: TSK_CLASS_DATA-PLNNR
Optional: No
Call by Reference: No ( called with pass by value option)

I_PLNAL - Group Counter

Data type: TSK_CLASS_DATA-PLNAL
Optional: No
Call by Reference: No ( called with pass by value option)

I_VPLNR - Key for Task List Group

Data type: TSK_CLASS_DATA-PLNNR
Optional: No
Call by Reference: No ( called with pass by value option)

I_VPLAL - Group Counter

Data type: TSK_CLASS_DATA-PLNAL
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CP_CL_P_TSK_REF_CHECK

E_VPLTY - Task List Type

Data type: TSK_CLASS_DATA-PLNTY
Optional: No
Call by Reference: Yes

E_LOSVN - From Lot Size

Data type: TSK_CLASS_DATA-LOSVN
Optional: No
Call by Reference: Yes

E_LOSBS - To lot size

Data type: TSK_CLASS_DATA-LOSBS
Optional: No
Call by Reference: Yes

E_PLNME - Task list unit of measure

Data type: TSK_CLASS_DATA-PLNME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_TASK_TYPE -

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

LOTSIZE_INTERVAL_INCOMPATIBLE -

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

NO_VALID_TASK -

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

NO_VALID_REF_TASK -

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

DIFFERENT_UNIT_OF_MEASURE -

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

REF_TASK_NO_VALID_STATUS -

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

REF_TASK_NOT_RELEASED -

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

REF_TASK_NO_COSTING -

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

DIFFERENT_COMPANY_CODES -

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

DIFFERENT_CONTROLLING_AREAS -

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

Copy and paste ABAP code example for CP_CL_P_TSK_REF_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.

ABAP code using 7.40 inline data declarations to call FM CP_CL_P_TSK_REF_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