SAP CS_OV_ITM_SCREEN_PROCESS Function Module for NOTRANSL: Darstellung von Stücklistenpositionen









CS_OV_ITM_SCREEN_PROCESS is a standard cs ov itm 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 Stücklistenpositionen 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 cs ov itm screen process FM, simply by entering the name CS_OV_ITM_SCREEN_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_OV_ITM_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 'CS_OV_ITM_SCREEN_PROCESS'"NOTRANSL: Darstellung von Stücklistenpositionen
  EXPORTING
*  I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
*  I_DATE_TO = DATE-MAX_GRG "Valid-To Date
*  I_STLTY =  "PDS Type
*  I_STLNR =  "Key for Task List Group
*  I_STLAL =  "Group Counter
*  I_IDENT =  "Sequence
*  I_STVKN =  "Inherited node number of BOM item
*  I_FLG_SUI_DISPLAY =  "
*  I_FLG_DISPLAY_ONLY = ' ' "Display Only

EXCEPTIONS
   WRONG_KEY = 1
.



IMPORTING Parameters details for CS_OV_ITM_SCREEN_PROCESS

I_DATE_FROM - Valid-From Date

Data type: BOM_CLASS_DATA-DATUV
Default: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DATE_TO - Valid-To Date

Data type: BOM_CLASS_DATA-DATUB
Default: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_STLTY - PDS Type

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

I_STLNR - Key for Task List Group

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

I_STLAL - Group Counter

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

I_IDENT - Sequence

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

I_STVKN - Inherited node number of BOM item

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

I_FLG_SUI_DISPLAY -

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

I_FLG_DISPLAY_ONLY - Display Only

Data type: C
Default: SPACE
Optional: 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 CS_OV_ITM_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 BOM_CLASS_DATA-DATUV, "   DATE-MIN_GRG
lv_i_date_to  TYPE BOM_CLASS_DATA-DATUB, "   DATE-MAX_GRG
lv_i_stlty  TYPE ITM_CLASS_DATA-STLTY, "   
lv_i_stlnr  TYPE ITM_CLASS_DATA-STLNR, "   
lv_i_stlal  TYPE ITM_CLASS_DATA-STLAL, "   
lv_i_ident  TYPE ITM_CLASS_DATA-IDENT, "   
lv_i_stvkn  TYPE ITM_CLASS_DATA-STVKN, "   
lv_i_flg_sui_display  TYPE C, "   
lv_i_flg_display_only  TYPE C. "   SPACE

  CALL FUNCTION 'CS_OV_ITM_SCREEN_PROCESS'  "NOTRANSL: Darstellung von Stücklistenpositionen
    EXPORTING
         I_DATE_FROM = lv_i_date_from
         I_DATE_TO = lv_i_date_to
         I_STLTY = lv_i_stlty
         I_STLNR = lv_i_stlnr
         I_STLAL = lv_i_stlal
         I_IDENT = lv_i_ident
         I_STVKN = lv_i_stvkn
         I_FLG_SUI_DISPLAY = lv_i_flg_sui_display
         I_FLG_DISPLAY_ONLY = lv_i_flg_display_only
    EXCEPTIONS
        WRONG_KEY = 1
. " CS_OV_ITM_SCREEN_PROCESS




ABAP code using 7.40 inline data declarations to call FM CS_OV_ITM_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 BOM_CLASS_DATA INTO @DATA(ld_i_date_from).
DATA(ld_i_date_from) = DATE-MIN_GRG.
 
"SELECT single DATUB FROM BOM_CLASS_DATA INTO @DATA(ld_i_date_to).
DATA(ld_i_date_to) = DATE-MAX_GRG.
 
"SELECT single STLTY FROM ITM_CLASS_DATA INTO @DATA(ld_i_stlty).
 
"SELECT single STLNR FROM ITM_CLASS_DATA INTO @DATA(ld_i_stlnr).
 
"SELECT single STLAL FROM ITM_CLASS_DATA INTO @DATA(ld_i_stlal).
 
"SELECT single IDENT FROM ITM_CLASS_DATA INTO @DATA(ld_i_ident).
 
"SELECT single STVKN FROM ITM_CLASS_DATA INTO @DATA(ld_i_stvkn).
 
 
DATA(ld_i_flg_display_only) = ' '.
 


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!