SAP CP_MC_BOM_SET Function Module for NOTRANSL: Setzen der Stückliste als Objekt für folgende Nachrichten
CP_MC_BOM_SET is a standard cp mc bom set 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: Setzen der Stückliste als Objekt für folgende Nachrichten 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 cp mc bom set FM, simply by entering the name CP_MC_BOM_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPMC
Program Name: SAPLCPMC
Main Program: SAPLCPMC
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CP_MC_BOM_SET 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 'CP_MC_BOM_SET'"NOTRANSL: Setzen der Stückliste als Objekt für folgende Nachrichten.
EXPORTING
I_MANDT = "
I_STLTY = "BOM Category
I_STLNR = "Bill of Materials No.
* I_STLAL = "Alternative BOM
IMPORTING
E_LOGNUMBER = "
E_HANDLE = "Application Log: Log Handle
EXCEPTIONS
MESSAGE_OBJECT_NOT_SET = 1 OBJECT_NOT_SUPP_BY_HANDLER = 2 LOSS_OF_COLLECTED_MESSAGES = 3
IMPORTING Parameters details for CP_MC_BOM_SET
I_MANDT -
Data type: BOM_CLASS_DATA-MANDTOptional: No
Call by Reference: No ( called with pass by value option)
I_STLTY - BOM Category
Data type: BOM_CLASS_DATA-STLTYOptional: No
Call by Reference: No ( called with pass by value option)
I_STLNR - Bill of Materials No.
Data type: BOM_CLASS_DATA-STLNROptional: No
Call by Reference: No ( called with pass by value option)
I_STLAL - Alternative BOM
Data type: BOM_CLASS_DATA-STLALOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CP_MC_BOM_SET
E_LOGNUMBER -
Data type: BALNRI-LOGNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
E_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MESSAGE_OBJECT_NOT_SET -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_SUPP_BY_HANDLER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOSS_OF_COLLECTED_MESSAGES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CP_MC_BOM_SET 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_mandt | TYPE BOM_CLASS_DATA-MANDT, " | |||
lv_e_lognumber | TYPE BALNRI-LOGNUMBER, " | |||
lv_message_object_not_set | TYPE BALNRI, " | |||
lv_i_stlty | TYPE BOM_CLASS_DATA-STLTY, " | |||
lv_e_handle | TYPE BALLOGHNDL, " | |||
lv_object_not_supp_by_handler | TYPE BALLOGHNDL, " | |||
lv_i_stlnr | TYPE BOM_CLASS_DATA-STLNR, " | |||
lv_loss_of_collected_messages | TYPE BOM_CLASS_DATA, " | |||
lv_i_stlal | TYPE BOM_CLASS_DATA-STLAL. " |
  CALL FUNCTION 'CP_MC_BOM_SET' "NOTRANSL: Setzen der Stückliste als Objekt für folgende Nachrichten |
EXPORTING | ||
I_MANDT | = lv_i_mandt | |
I_STLTY | = lv_i_stlty | |
I_STLNR | = lv_i_stlnr | |
I_STLAL | = lv_i_stlal | |
IMPORTING | ||
E_LOGNUMBER | = lv_e_lognumber | |
E_HANDLE | = lv_e_handle | |
EXCEPTIONS | ||
MESSAGE_OBJECT_NOT_SET = 1 | ||
OBJECT_NOT_SUPP_BY_HANDLER = 2 | ||
LOSS_OF_COLLECTED_MESSAGES = 3 | ||
. " CP_MC_BOM_SET |
ABAP code using 7.40 inline data declarations to call FM CP_MC_BOM_SET
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 MANDT FROM BOM_CLASS_DATA INTO @DATA(ld_i_mandt). | ||||
"SELECT single LOGNUMBER FROM BALNRI INTO @DATA(ld_e_lognumber). | ||||
"SELECT single STLTY FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlty). | ||||
"SELECT single STLNR FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlnr). | ||||
"SELECT single STLAL FROM BOM_CLASS_DATA INTO @DATA(ld_i_stlal). | ||||
Search for further information about these or an SAP related objects