SAP CS_CL_S_ITM_LOAD_CHECK Function Module for NOTRANSL: Prüfung der Gültigkeit geladener Stücklistenpositionen
CS_CL_S_ITM_LOAD_CHECK is a standard cs cl s itm load 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 der Gültigkeit geladener 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 cl s itm load check FM, simply by entering the name CS_CL_S_ITM_LOAD_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CSCL
Program Name: SAPLCSCL
Main Program: SAPLCSCL
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CS_CL_S_ITM_LOAD_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 'CS_CL_S_ITM_LOAD_CHECK'"NOTRANSL: Prüfung der Gültigkeit geladener Stücklistenpositionen.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_DATE_TO = DATE-MAX_GRG "Valid-to date
* I_STLTY = "BOM category
* I_STLNR = "Bill of material
* I_STLAL = "Alternative BOM
* I_IDENT = "Item ID
* I_STVKN = "Inherited node number of BOM item
IMPORTING
E_FLG_ITM_EXISTS = "Generic Type
EXCEPTIONS
WRONG_KEY = 1
IMPORTING Parameters details for CS_CL_S_ITM_LOAD_CHECK
I_DATE_FROM - Valid-From Date
Data type: ITM_CLASS_DATA-DATUVDefault: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_TO - Valid-to date
Data type: ITM_CLASS_DATA-DATUBDefault: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_STLTY - BOM category
Data type: ITM_CLASS_DATA-STLTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STLNR - Bill of material
Data type: ITM_CLASS_DATA-STLNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_STLAL - Alternative BOM
Data type: ITM_CLASS_DATA-STLALOptional: Yes
Call by Reference: No ( called with pass by value option)
I_IDENT - Item ID
Data type: ITM_CLASS_DATA-IDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STVKN - Inherited node number of BOM item
Data type: ITM_CLASS_DATA-STVKNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CS_CL_S_ITM_LOAD_CHECK
E_FLG_ITM_EXISTS - Generic Type
Data type: COptional: No
Call by Reference: Yes
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_CL_S_ITM_LOAD_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.| DATA: | ||||
| lv_wrong_key | TYPE STRING, " | |||
| lv_i_date_from | TYPE ITM_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
| lv_e_flg_itm_exists | TYPE C, " | |||
| lv_i_date_to | TYPE ITM_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. " |
|   CALL FUNCTION 'CS_CL_S_ITM_LOAD_CHECK' "NOTRANSL: Prüfung der Gültigkeit geladener 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 | |
| IMPORTING | ||
| E_FLG_ITM_EXISTS | = lv_e_flg_itm_exists | |
| EXCEPTIONS | ||
| WRONG_KEY = 1 | ||
| . " CS_CL_S_ITM_LOAD_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM CS_CL_S_ITM_LOAD_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.| "SELECT single DATUV FROM ITM_CLASS_DATA INTO @DATA(ld_i_date_from). | ||||
| DATA(ld_i_date_from) | = DATE-MIN_GRG. | |||
| "SELECT single DATUB FROM ITM_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). | ||||
Search for further information about these or an SAP related objects