SAP CP_OV_TSK_SCREEN_PROCESS Function Module for NOTRANSL: Darstellung von Planköpfen
CP_OV_TSK_SCREEN_PROCESS is a standard cp ov tsk screen process 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: Darstellung von Planköpfen 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 ov tsk screen process FM, simply by entering the name CP_OV_TSK_SCREEN_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPOV
Program Name: SAPLCPOV
Main Program: SAPLCPOV
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CP_OV_TSK_SCREEN_PROCESS 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_OV_TSK_SCREEN_PROCESS'"NOTRANSL: Darstellung von Planköpfen.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "
* I_FLG_DISPLAY_ONLY = ' ' "Display Only
* I_DATE_TO = DATE-MAX_GRG "
* I_MATERIAL = "Material Number
* I_PLANT = "Plant
* I_SALES_ORDER = "Sales Document
* I_SALES_ORDER_ITEM = "Sales document item
* I_PLNTY = "
* I_PLNNR = "
* I_PLNAL = "
EXCEPTIONS
WRONG_KEY = 1
IMPORTING Parameters details for CP_OV_TSK_SCREEN_PROCESS
I_DATE_FROM -
Data type: TSK_CLASS_DATA-DATUVDefault: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_DISPLAY_ONLY - Display Only
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_TO -
Data type: TSK_CLASS_DATA-DATUBDefault: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MATERIAL - Material Number
Data type: MTK_CLASS_DATA-MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLANT - Plant
Data type: MTK_CLASS_DATA-WERKSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SALES_ORDER - Sales Document
Data type: MTK_CLASS_DATA-VBELNOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SALES_ORDER_ITEM - Sales document item
Data type: MTK_CLASS_DATA-POSNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNTY -
Data type: TSK_CLASS_DATA-PLNTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNNR -
Data type: TSK_CLASS_DATA-PLNNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNAL -
Data type: TSK_CLASS_DATA-PLNALOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CP_OV_TSK_SCREEN_PROCESS 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_wrong_key | TYPE STRING, " | |||
| lv_i_date_from | TYPE TSK_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
| lv_i_flg_display_only | TYPE C, " SPACE | |||
| lv_i_date_to | TYPE TSK_CLASS_DATA-DATUB, " DATE-MAX_GRG | |||
| lv_i_material | TYPE MTK_CLASS_DATA-MATNR, " | |||
| lv_i_plant | TYPE MTK_CLASS_DATA-WERKS, " | |||
| lv_i_sales_order | TYPE MTK_CLASS_DATA-VBELN, " | |||
| lv_i_sales_order_item | TYPE MTK_CLASS_DATA-POSNR, " | |||
| lv_i_plnty | TYPE TSK_CLASS_DATA-PLNTY, " | |||
| lv_i_plnnr | TYPE TSK_CLASS_DATA-PLNNR, " | |||
| lv_i_plnal | TYPE TSK_CLASS_DATA-PLNAL. " |
|   CALL FUNCTION 'CP_OV_TSK_SCREEN_PROCESS' "NOTRANSL: Darstellung von Planköpfen |
| EXPORTING | ||
| I_DATE_FROM | = lv_i_date_from | |
| I_FLG_DISPLAY_ONLY | = lv_i_flg_display_only | |
| I_DATE_TO | = lv_i_date_to | |
| I_MATERIAL | = lv_i_material | |
| I_PLANT | = lv_i_plant | |
| I_SALES_ORDER | = lv_i_sales_order | |
| I_SALES_ORDER_ITEM | = lv_i_sales_order_item | |
| I_PLNTY | = lv_i_plnty | |
| I_PLNNR | = lv_i_plnnr | |
| I_PLNAL | = lv_i_plnal | |
| EXCEPTIONS | ||
| WRONG_KEY = 1 | ||
| . " CP_OV_TSK_SCREEN_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM CP_OV_TSK_SCREEN_PROCESS
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_date_from). | ||||
| DATA(ld_i_date_from) | = DATE-MIN_GRG. | |||
| DATA(ld_i_flg_display_only) | = ' '. | |||
| "SELECT single DATUB FROM TSK_CLASS_DATA INTO @DATA(ld_i_date_to). | ||||
| DATA(ld_i_date_to) | = DATE-MAX_GRG. | |||
| "SELECT single MATNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_material). | ||||
| "SELECT single WERKS FROM MTK_CLASS_DATA INTO @DATA(ld_i_plant). | ||||
| "SELECT single VBELN FROM MTK_CLASS_DATA INTO @DATA(ld_i_sales_order). | ||||
| "SELECT single POSNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_sales_order_item). | ||||
| "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). | ||||
Search for further information about these or an SAP related objects