SAP CS_CL_S_BOM_CHANGE Function Module for NOTRANSL: Ändern eines Stücklistenkopfs









CS_CL_S_BOM_CHANGE is a standard cs cl s bom change 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: Ändern eines Stücklistenkopfs 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 bom change FM, simply by entering the name CS_CL_S_BOM_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function CS_CL_S_BOM_CHANGE 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_BOM_CHANGE'"NOTRANSL: Ändern eines Stücklistenkopfs
EXPORTING
* I_ECN_S = ' ' "
I_KEY_DATE_S = "
* I_FLG_BOM_CHECK = 'X' "
* I_MARK_DOC_UPDATE = ' ' "
* I_MARK_BOM_TXT_UPDATE = ' ' "
* I_MARK_BGR_TXT_UPDATE = ' ' "
I_BOM_CLASS_DATA = "

IMPORTING
E_ECM_DATA_ERROR_TYPE = "
E_GUIDX = "Global Identification of an Item's Change Status
E_STKOZ = "Internal Counter

EXCEPTIONS
BOM_NOT_CONSISTENT = 1 NO_AUTHORITY = 2 NO_VALID_BOM = 3 BOM_NOT_LOCKED = 4 INPUT_INCOMPLETE = 5 ECM_DATA_NOT_SUITABLE = 6
.



IMPORTING Parameters details for CS_CL_S_BOM_CHANGE

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_BOM_CHECK -

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

I_MARK_DOC_UPDATE -

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

I_MARK_BOM_TXT_UPDATE -

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

I_MARK_BGR_TXT_UPDATE -

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

I_BOM_CLASS_DATA -

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

EXPORTING Parameters details for CS_CL_S_BOM_CHANGE

E_ECM_DATA_ERROR_TYPE -

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

E_GUIDX - Global Identification of an Item's Change Status

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

E_STKOZ - Internal Counter

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

EXCEPTIONS details

BOM_NOT_CONSISTENT -

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

NO_AUTHORITY -

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)

BOM_NOT_LOCKED -

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)

Copy and paste ABAP code example for CS_CL_S_BOM_CHANGE 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_i_ecn_s  TYPE BOM_CLASS_DATA-AENNR, "   SPACE
lv_bom_not_consistent  TYPE BOM_CLASS_DATA, "   
lv_e_ecm_data_error_type  TYPE CPCC_MESSAGE_TYPE, "   
lv_e_guidx  TYPE BOM_CLASS_DATA-GUIDX, "   
lv_i_key_date_s  TYPE SY-DATUM, "   
lv_no_authority  TYPE SY, "   
lv_e_stkoz  TYPE BOM_CLASS_DATA-STKOZ, "   
lv_no_valid_bom  TYPE BOM_CLASS_DATA, "   
lv_i_flg_bom_check  TYPE CSDATA-XFELD, "   'X'
lv_bom_not_locked  TYPE CSDATA, "   
lv_i_mark_doc_update  TYPE CSDATA-XFELD, "   SPACE
lv_input_incomplete  TYPE CSDATA, "   
lv_i_mark_bom_txt_update  TYPE TTXCT-FUNCTION, "   SPACE
lv_ecm_data_not_suitable  TYPE TTXCT, "   
lv_i_mark_bgr_txt_update  TYPE TTXCT-FUNCTION, "   SPACE
lv_i_bom_class_data  TYPE BOM_CLASS_DATA. "   

  CALL FUNCTION 'CS_CL_S_BOM_CHANGE'  "NOTRANSL: Ändern eines Stücklistenkopfs
    EXPORTING
         I_ECN_S = lv_i_ecn_s
         I_KEY_DATE_S = lv_i_key_date_s
         I_FLG_BOM_CHECK = lv_i_flg_bom_check
         I_MARK_DOC_UPDATE = lv_i_mark_doc_update
         I_MARK_BOM_TXT_UPDATE = lv_i_mark_bom_txt_update
         I_MARK_BGR_TXT_UPDATE = lv_i_mark_bgr_txt_update
         I_BOM_CLASS_DATA = lv_i_bom_class_data
    IMPORTING
         E_ECM_DATA_ERROR_TYPE = lv_e_ecm_data_error_type
         E_GUIDX = lv_e_guidx
         E_STKOZ = lv_e_stkoz
    EXCEPTIONS
        BOM_NOT_CONSISTENT = 1
        NO_AUTHORITY = 2
        NO_VALID_BOM = 3
        BOM_NOT_LOCKED = 4
        INPUT_INCOMPLETE = 5
        ECM_DATA_NOT_SUITABLE = 6
. " CS_CL_S_BOM_CHANGE




ABAP code using 7.40 inline data declarations to call FM CS_CL_S_BOM_CHANGE

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 AENNR FROM BOM_CLASS_DATA INTO @DATA(ld_i_ecn_s).
DATA(ld_i_ecn_s) = ' '.
 
 
 
"SELECT single GUIDX FROM BOM_CLASS_DATA INTO @DATA(ld_e_guidx).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_key_date_s).
 
 
"SELECT single STKOZ FROM BOM_CLASS_DATA INTO @DATA(ld_e_stkoz).
 
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_i_flg_bom_check).
DATA(ld_i_flg_bom_check) = 'X'.
 
 
"SELECT single XFELD FROM CSDATA INTO @DATA(ld_i_mark_doc_update).
DATA(ld_i_mark_doc_update) = ' '.
 
 
"SELECT single FUNCTION FROM TTXCT INTO @DATA(ld_i_mark_bom_txt_update).
DATA(ld_i_mark_bom_txt_update) = ' '.
 
 
"SELECT single FUNCTION FROM TTXCT INTO @DATA(ld_i_mark_bgr_txt_update).
DATA(ld_i_mark_bgr_txt_update) = ' '.
 
 


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!