SAP CUKO_DDB_HAS_COMPONENTS Function Module for NOTRANSL: Liefert alle Komponenten einer Instanz

Search SAP Function Modules

CUKO_DDB_HAS_COMPONENTS is a standard cuko ddb has components 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: Liefert alle Komponenten einer Instanz 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 ddb has components FM, simply by entering the name CUKO_DDB_HAS_COMPONENTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: CUKO
Program Name: SAPLCUKO
Main Program: SAPLCUKO
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUKO_DDB_HAS_COMPONENTS 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_DDB_HAS_COMPONENTS'"NOTRANSL: Liefert alle Komponenten einer Instanz
  EXPORTING
*  IV_CUOBJ =  "Configuration (Internal Object Number)

 IMPORTING
   ROOT_INSTANCE =  "
   ET_CHANGED_HEADER =  "

TABLES
   EXP_STPO =  "
   EXP_INDEX =  "

EXCEPTIONS
   NOT_FOUND = 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_DDB_HAS_COMPONENTS

IV_CUOBJ - Configuration (Internal Object Number)

Data type: INOB-CUOBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CUKO_DDB_HAS_COMPONENTS

ROOT_INSTANCE -

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

ET_CHANGED_HEADER -

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

TABLES Parameters details for CUKO_DDB_HAS_COMPONENTS

EXP_STPO -

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

EXP_INDEX -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for CUKO_DDB_HAS_COMPONENTS 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.

ABAP code using 7.40 inline data declarations to call FM CUKO_DDB_HAS_COMPONENTS

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.

Search for further information about these or an SAP related objects