SAP CUCB_GET_CONFIGURATION_TYPE Function Module for NOTRANSL: Liefert Konfigurationstype (VC oder SCE)
CUCB_GET_CONFIGURATION_TYPE is a standard cucb get configuration type 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 Konfigurationstype (VC oder SCE) 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 cucb get configuration type FM, simply by entering the name CUCB_GET_CONFIGURATION_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUCB
Program Name: SAPLCUCB
Main Program: SAPLCUCB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CUCB_GET_CONFIGURATION_TYPE 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 'CUCB_GET_CONFIGURATION_TYPE'"NOTRANSL: Liefert Konfigurationstype (VC oder SCE).
EXPORTING
INSTANCE = "CUIB: System-Dependent Configuration Reference
EXCEPTIONS
INVALID_INPUT = 1 SCE = 2 VARIANT_CONFIGURATOR = 3 INVALID_INSTANCE = 4 INSTANCE_IS_A_CLASSIFICATION = 5
IMPORTING Parameters details for CUCB_GET_CONFIGURATION_TYPE
INSTANCE - CUIB: System-Dependent Configuration Reference
Data type: CUIB_CUOBJOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INPUT -
Data type:Optional: No
Call by Reference: Yes
SCE - SCE Configuration
Data type:Optional: No
Call by Reference: Yes
VARIANT_CONFIGURATOR - R/3 Configuration
Data type:Optional: No
Call by Reference: Yes
INVALID_INSTANCE - Configuration not found
Data type:Optional: No
Call by Reference: Yes
INSTANCE_IS_A_CLASSIFICATION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CUCB_GET_CONFIGURATION_TYPE 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_instance | TYPE CUIB_CUOBJ, " | |||
lv_invalid_input | TYPE CUIB_CUOBJ, " | |||
lv_sce | TYPE CUIB_CUOBJ, " | |||
lv_variant_configurator | TYPE CUIB_CUOBJ, " | |||
lv_invalid_instance | TYPE CUIB_CUOBJ, " | |||
lv_instance_is_a_classification | TYPE CUIB_CUOBJ. " |
  CALL FUNCTION 'CUCB_GET_CONFIGURATION_TYPE' "NOTRANSL: Liefert Konfigurationstype (VC oder SCE) |
EXPORTING | ||
INSTANCE | = lv_instance | |
EXCEPTIONS | ||
INVALID_INPUT = 1 | ||
SCE = 2 | ||
VARIANT_CONFIGURATOR = 3 | ||
INVALID_INSTANCE = 4 | ||
INSTANCE_IS_A_CLASSIFICATION = 5 | ||
. " CUCB_GET_CONFIGURATION_TYPE |
ABAP code using 7.40 inline data declarations to call FM CUCB_GET_CONFIGURATION_TYPE
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