SAP CS_CL_S_ITM_CREATE_COMPLETE Function Module for NOTRANSL: Anlegen einer Stücklistenposition









CS_CL_S_ITM_CREATE_COMPLETE is a standard cs cl s itm create complete 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 einer Stücklistenposition 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 create complete FM, simply by entering the name CS_CL_S_ITM_CREATE_COMPLETE 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_CREATE_COMPLETE 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_CREATE_COMPLETE'"NOTRANSL: Anlegen einer Stücklistenposition
EXPORTING
* I_ECN_S = ' ' "
I_KEY_DATE_S = "
* I_FLG_ITM_CHECK = 'X' "
* I_FLG_DEFAULT_VALUES = 'X' "
I_ITM_CLASS_DATA = "
I_ALTERNATIVES = "

IMPORTING
E_GUIDX = "Global Identification of an Item's Change Status
E_IDENT = "
E_STVKN = "
E_STLKN = "
E_STPOZ = "
E_ECM_DATA_ERROR_TYPE = "

TABLES
* DEP_DATA = "API Structure for Basic Data of Dependency
* DEP_DESCR = "API Structure for Lang-Dependent Dependency Descriptions
* DEP_ORDER = "API Structure for Allocations for Object Dependencies
* DEP_SOURCE = "API Structure for Sources of Dependency
* DEP_DOC = "API Structure for Dependency Documentation
* DOC_LINK = "Document-Object Link
* TEXT_LINES = "SAPscript: Text Lines

EXCEPTIONS
ITEM_NOT_CONSISTENT = 1 DEPENDENCY_ERROR = 10 TEXT_ERROR = 11 NO_AUTHORITY = 2 ITEM_NOT_LOCKED = 3 IDENT_ALREADY_EXISTS = 4 WRONG_IDENT_TYPE = 5 NO_VALID_BOM = 6 INPUT_INCOMPLETE = 7 ECM_DATA_NOT_SUITABLE = 8 DOCUMENT_LINK_ERROR = 9
.



IMPORTING Parameters details for CS_CL_S_ITM_CREATE_COMPLETE

I_ECN_S -

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

I_KEY_DATE_S -

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

I_FLG_ITM_CHECK -

Data type: CSDATA-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_DEFAULT_VALUES -

Data type: CSDATA-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ITM_CLASS_DATA -

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

I_ALTERNATIVES -

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

EXPORTING Parameters details for CS_CL_S_ITM_CREATE_COMPLETE

E_GUIDX - Global Identification of an Item's Change Status

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

E_IDENT -

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

E_STVKN -

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

E_STLKN -

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

E_STPOZ -

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

E_ECM_DATA_ERROR_TYPE -

Data type: CPCC_MESSAGE_TYPE
Optional: No
Call by Reference: Yes

TABLES Parameters details for CS_CL_S_ITM_CREATE_COMPLETE

DEP_DATA - API Structure for Basic Data of Dependency

Data type: RCUKB1
Optional: Yes
Call by Reference: Yes

DEP_DESCR - API Structure for Lang-Dependent Dependency Descriptions

Data type: RCUKBT1
Optional: Yes
Call by Reference: Yes

DEP_ORDER - API Structure for Allocations for Object Dependencies

Data type: RCUOB1
Optional: Yes
Call by Reference: Yes

DEP_SOURCE - API Structure for Sources of Dependency

Data type: RCUKN1
Optional: Yes
Call by Reference: Yes

DEP_DOC - API Structure for Dependency Documentation

Data type: RCUKDOC1
Optional: Yes
Call by Reference: Yes

DOC_LINK - Document-Object Link

Data type: DRAD
Optional: Yes
Call by Reference: Yes

TEXT_LINES - SAPscript: Text Lines

Data type: TLINE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ITEM_NOT_CONSISTENT -

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

DEPENDENCY_ERROR -

Data type:
Optional: No
Call by Reference: Yes

TEXT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

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

ITEM_NOT_LOCKED -

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

IDENT_ALREADY_EXISTS -

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

WRONG_IDENT_TYPE -

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

NO_VALID_BOM -

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

INPUT_INCOMPLETE -

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

ECM_DATA_NOT_SUITABLE -

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

DOCUMENT_LINK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CS_CL_S_ITM_CREATE_COMPLETE 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_e_guidx  TYPE ITM_CLASS_DATA-GUIDX, "   
lv_i_ecn_s  TYPE BOM_CLASS_DATA-AENNR, "   SPACE
lt_dep_data  TYPE STANDARD TABLE OF RCUKB1, "   
lv_item_not_consistent  TYPE RCUKB1, "   
lv_dependency_error  TYPE RCUKB1, "   
lv_text_error  TYPE RCUKB1, "   
lv_e_ident  TYPE ITM_CLASS_DATA-IDENT, "   
lt_dep_descr  TYPE STANDARD TABLE OF RCUKBT1, "   
lv_i_key_date_s  TYPE SY-DATUM, "   
lv_no_authority  TYPE SY, "   
lv_e_stvkn  TYPE ITM_CLASS_DATA-STVKN, "   
lt_dep_order  TYPE STANDARD TABLE OF RCUOB1, "   
lv_item_not_locked  TYPE RCUOB1, "   
lv_i_flg_itm_check  TYPE CSDATA-XFELD, "   'X'
lv_e_stlkn  TYPE ITM_CLASS_DATA-STLKN, "   
lt_dep_source  TYPE STANDARD TABLE OF RCUKN1, "   
lv_ident_already_exists  TYPE RCUKN1, "   
lv_i_flg_default_values  TYPE CSDATA-XFELD, "   'X'
lt_dep_doc  TYPE STANDARD TABLE OF RCUKDOC1, "   
lv_e_stpoz  TYPE ITM_CLASS_DATA-STPOZ, "   
lv_i_itm_class_data  TYPE ITM_CLASS_DATA, "   
lv_wrong_ident_type  TYPE ITM_CLASS_DATA, "   
lt_doc_link  TYPE STANDARD TABLE OF DRAD, "   
lv_no_valid_bom  TYPE DRAD, "   
lv_i_alternatives  TYPE CSCL_ALT_TB_TYPE, "   
lv_e_ecm_data_error_type  TYPE CPCC_MESSAGE_TYPE, "   
lt_text_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_input_incomplete  TYPE TLINE, "   
lv_ecm_data_not_suitable  TYPE TLINE, "   
lv_document_link_error  TYPE TLINE. "   

  CALL FUNCTION 'CS_CL_S_ITM_CREATE_COMPLETE'  "NOTRANSL: Anlegen einer Stücklistenposition
    EXPORTING
         I_ECN_S = lv_i_ecn_s
         I_KEY_DATE_S = lv_i_key_date_s
         I_FLG_ITM_CHECK = lv_i_flg_itm_check
         I_FLG_DEFAULT_VALUES = lv_i_flg_default_values
         I_ITM_CLASS_DATA = lv_i_itm_class_data
         I_ALTERNATIVES = lv_i_alternatives
    IMPORTING
         E_GUIDX = lv_e_guidx
         E_IDENT = lv_e_ident
         E_STVKN = lv_e_stvkn
         E_STLKN = lv_e_stlkn
         E_STPOZ = lv_e_stpoz
         E_ECM_DATA_ERROR_TYPE = lv_e_ecm_data_error_type
    TABLES
         DEP_DATA = lt_dep_data
         DEP_DESCR = lt_dep_descr
         DEP_ORDER = lt_dep_order
         DEP_SOURCE = lt_dep_source
         DEP_DOC = lt_dep_doc
         DOC_LINK = lt_doc_link
         TEXT_LINES = lt_text_lines
    EXCEPTIONS
        ITEM_NOT_CONSISTENT = 1
        DEPENDENCY_ERROR = 10
        TEXT_ERROR = 11
        NO_AUTHORITY = 2
        ITEM_NOT_LOCKED = 3
        IDENT_ALREADY_EXISTS = 4
        WRONG_IDENT_TYPE = 5
        NO_VALID_BOM = 6
        INPUT_INCOMPLETE = 7
        ECM_DATA_NOT_SUITABLE = 8
        DOCUMENT_LINK_ERROR = 9
. " CS_CL_S_ITM_CREATE_COMPLETE




ABAP code using 7.40 inline data declarations to call FM CS_CL_S_ITM_CREATE_COMPLETE

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 GUIDX FROM ITM_CLASS_DATA INTO @DATA(ld_e_guidx).
 
"SELECT single AENNR FROM BOM_CLASS_DATA INTO @DATA(ld_i_ecn_s).
DATA(ld_i_ecn_s) = ' '.
 
 
 
 
 
"SELECT single IDENT FROM ITM_CLASS_DATA INTO @DATA(ld_e_ident).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_key_date_s).
 
 
"SELECT single STVKN FROM ITM_CLASS_DATA INTO @DATA(ld_e_stvkn).
 
 
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_i_flg_itm_check).
DATA(ld_i_flg_itm_check) = 'X'.
 
"SELECT single STLKN FROM ITM_CLASS_DATA INTO @DATA(ld_e_stlkn).
 
 
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_i_flg_default_values).
DATA(ld_i_flg_default_values) = 'X'.
 
 
"SELECT single STPOZ FROM ITM_CLASS_DATA INTO @DATA(ld_e_stpoz).
 
 
 
 
 
 
 
 
 
 
 


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!