SAP CUKO_BOM_EXPLOSION_SET_PARAMS Function Module for NOTRANSL: Setzen Parameter für Stücklistenauflösung
CUKO_BOM_EXPLOSION_SET_PARAMS is a standard cuko bom explosion set params 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 Parameter für Stücklistenauflösung 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 cuko bom explosion set params FM, simply by entering the name CUKO_BOM_EXPLOSION_SET_PARAMS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUKO
Program Name: SAPLCUKO
Main Program: SAPLCUKO
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CUKO_BOM_EXPLOSION_SET_PARAMS 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 'CUKO_BOM_EXPLOSION_SET_PARAMS'"NOTRANSL: Setzen Parameter für Stücklistenauflösung.
EXPORTING
* EXPLOSION_LEVEL = "Dummy for B20 int1 (Local Everywhere)
* EXPLODE_ALL = "Single-Character Indicator
* RESTRICT_TO_CONFIGURABLE = 'X' "Only configurable assemblies
EXCEPTIONS
NO_VALID_LEVEL = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCUKO_001 Additional Check on Configuration
EXIT_SAPLCUKO_002 Level of Detail of Multi-Level Explosion in Configuration
EXIT_SAPLCUKO_003 Post-Processing of Configuration
EXIT_SAPLCUKO_004 Instantiation Parameters
EXIT_SAPLCUKO_005 Save Manual Changes for Scenario Sales Order (SET)
EXIT_SAPLCUKO_006 Import Manual Changes for Scenario Sales Order (SET)
EXIT_SAPLCUKO_007 Exit to 'Correctly' Fix an Order BOM
EXIT_SAPLCUKO_008 No BOM Explosion for Externally Procured Components
EXIT_SAPLCUKO_009 Multistep Configuration with Material Variants
EXIT_SAPLCUKO_010 Enhancement CCUXSETQ, Control: Quantity Comparison Yes/No
EXIT_SAPLCUKO_011 Dialog for Incomplete Assigned Characteristic Values
IMPORTING Parameters details for CUKO_BOM_EXPLOSION_SET_PARAMS
EXPLOSION_LEVEL - Dummy for B20 int1 (Local Everywhere)
Data type: RCUKO-EXPL_LEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPLODE_ALL - Single-Character Indicator
Data type: RCUKO-EXPL_ALLOptional: Yes
Call by Reference: No ( called with pass by value option)
RESTRICT_TO_CONFIGURABLE - Only configurable assemblies
Data type: RCUKO-CBAUGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_VALID_LEVEL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUKO_BOM_EXPLOSION_SET_PARAMS 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_no_valid_level | TYPE STRING, " | |||
lv_explosion_level | TYPE RCUKO-EXPL_LEVEL, " | |||
lv_explode_all | TYPE RCUKO-EXPL_ALL, " | |||
lv_restrict_to_configurable | TYPE RCUKO-CBAUG. " 'X' |
  CALL FUNCTION 'CUKO_BOM_EXPLOSION_SET_PARAMS' "NOTRANSL: Setzen Parameter für Stücklistenauflösung |
EXPORTING | ||
EXPLOSION_LEVEL | = lv_explosion_level | |
EXPLODE_ALL | = lv_explode_all | |
RESTRICT_TO_CONFIGURABLE | = lv_restrict_to_configurable | |
EXCEPTIONS | ||
NO_VALID_LEVEL = 1 | ||
. " CUKO_BOM_EXPLOSION_SET_PARAMS |
ABAP code using 7.40 inline data declarations to call FM CUKO_BOM_EXPLOSION_SET_PARAMS
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 EXPL_LEVEL FROM RCUKO INTO @DATA(ld_explosion_level). | ||||
"SELECT single EXPL_ALL FROM RCUKO INTO @DATA(ld_explode_all). | ||||
"SELECT single CBAUG FROM RCUKO INTO @DATA(ld_restrict_to_configurable). | ||||
DATA(ld_restrict_to_configurable) | = 'X'. | |||
Search for further information about these or an SAP related objects