SAP CS_CL_P_BOM_MASS_CHANGE Function Module for NOTRANSL: Massenänderung von Stücklistenkopffeldern









CS_CL_P_BOM_MASS_CHANGE is a standard cs cl p bom mass 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: Massenänderung von Stücklistenkopffeldern 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 p bom mass change FM, simply by entering the name CS_CL_P_BOM_MASS_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:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CS_CL_P_BOM_MASS_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_P_BOM_MASS_CHANGE'"NOTRANSL: Massenänderung von Stücklistenkopffeldern
EXPORTING
* I_ECN_S = ' ' "Change Number
I_KEY_DATE_S = "Date and Time, Current (Application Server) Date
I_BOM_CLASS_DATA = "Data for the class of bills of material
I_BOM_FIELDS_TO_BE_CHANGED = "
* I_FLG_BOM_VERSIONS_UPDATE = ' ' "Update Changes

IMPORTING
E_ECM_DATA_ERROR_TYPE = "

EXCEPTIONS
BOM_NOT_CHANGED = 1 NO_VALID_BOM = 2 BOM_NOT_LOCKED = 3 NO_AUTHORITY = 4
.



IMPORTING Parameters details for CS_CL_P_BOM_MASS_CHANGE

I_ECN_S - Change Number

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

I_KEY_DATE_S - Date and Time, Current (Application Server) Date

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

I_BOM_CLASS_DATA - Data for the class of bills of material

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

I_BOM_FIELDS_TO_BE_CHANGED -

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

I_FLG_BOM_VERSIONS_UPDATE - Update Changes

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

EXPORTING Parameters details for CS_CL_P_BOM_MASS_CHANGE

E_ECM_DATA_ERROR_TYPE -

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

EXCEPTIONS details

BOM_NOT_CHANGED -

Data type:
Optional: No
Call by Reference: Yes

NO_VALID_BOM - Bill of material is not valid

Data type:
Optional: No
Call by Reference: Yes

BOM_NOT_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CS_CL_P_BOM_MASS_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_changed  TYPE BOM_CLASS_DATA, "   
lv_e_ecm_data_error_type  TYPE CPCC_MESSAGE_TYPE, "   
lv_i_key_date_s  TYPE SY-DATUM, "   
lv_no_valid_bom  TYPE SY, "   
lv_bom_not_locked  TYPE SY, "   
lv_i_bom_class_data  TYPE BOM_CLASS_DATA, "   
lv_no_authority  TYPE BOM_CLASS_DATA, "   
lv_i_bom_fields_to_be_changed  TYPE GECL_STD_TAB_TYPE, "   
lv_i_flg_bom_versions_update  TYPE C. "   SPACE

  CALL FUNCTION 'CS_CL_P_BOM_MASS_CHANGE'  "NOTRANSL: Massenänderung von Stücklistenkopffeldern
    EXPORTING
         I_ECN_S = lv_i_ecn_s
         I_KEY_DATE_S = lv_i_key_date_s
         I_BOM_CLASS_DATA = lv_i_bom_class_data
         I_BOM_FIELDS_TO_BE_CHANGED = lv_i_bom_fields_to_be_changed
         I_FLG_BOM_VERSIONS_UPDATE = lv_i_flg_bom_versions_update
    IMPORTING
         E_ECM_DATA_ERROR_TYPE = lv_e_ecm_data_error_type
    EXCEPTIONS
        BOM_NOT_CHANGED = 1
        NO_VALID_BOM = 2
        BOM_NOT_LOCKED = 3
        NO_AUTHORITY = 4
. " CS_CL_P_BOM_MASS_CHANGE




ABAP code using 7.40 inline data declarations to call FM CS_CL_P_BOM_MASS_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 DATUM FROM SY INTO @DATA(ld_i_key_date_s).
 
 
 
 
 
 
DATA(ld_i_flg_bom_versions_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!