SAP CUCB_GET_CONFIGURATION Function Module for NOTRANSL: Lesen einer mehrstufigen Konfigurationstruktur aus der IBAse









CUCB_GET_CONFIGURATION is a standard cucb get configuration 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: Lesen einer mehrstufigen Konfigurationstruktur aus der IBAse 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 FM, simply by entering the name CUCB_GET_CONFIGURATION into the relevant SAP transaction such as SE37 or SE38.

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



Function CUCB_GET_CONFIGURATION 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'"NOTRANSL: Lesen einer mehrstufigen Konfigurationstruktur aus der IBAse
  EXPORTING
   INSTANCE =  "CUIB: System-Dependent Configuration Reference
*  IS_BUSINESS_OBJECT =  "Observer
*  IV_MOMENT =  "IB: Time Stamp of Owner's or Observer's Version
*  IV_WITH_DB_INSTANCE =  "Boolean Variable (X=True, -=False, Space=Unknown)

 IMPORTING
   IBASE =  "
   CONFIGURATION =  "
   EO_CBASE_REF =  "CL_CBASE Events

EXCEPTIONS
   INVALID_INPUT = 1    INVALID_INSTANCE = 2    INSTANCE_IS_A_CLASSIFICATION = 3
.



IMPORTING Parameters details for CUCB_GET_CONFIGURATION

INSTANCE - CUIB: System-Dependent Configuration Reference

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

IS_BUSINESS_OBJECT - Observer

Data type: CUIB_BUSINESS_OBJECT
Optional: Yes
Call by Reference: Yes

IV_MOMENT - IB: Time Stamp of Owner's or Observer's Version

Data type: TIMESTAMP
Optional: Yes
Call by Reference: Yes

IV_WITH_DB_INSTANCE - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CUCB_GET_CONFIGURATION

IBASE -

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

CONFIGURATION -

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

EO_CBASE_REF - CL_CBASE Events

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

EXCEPTIONS details

INVALID_INPUT -

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 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_ibase  TYPE IBCO2_IBASE_REC, "   
lv_instance  TYPE CUIB_CUOBJ, "   
lv_invalid_input  TYPE CUIB_CUOBJ, "   
lv_configuration  TYPE IBCO2_INSTANCE_TAB2, "   
lv_invalid_instance  TYPE IBCO2_INSTANCE_TAB2, "   
lv_is_business_object  TYPE CUIB_BUSINESS_OBJECT, "   
lv_iv_moment  TYPE TIMESTAMP, "   
lv_eo_cbase_ref  TYPE IF_CBASE_E, "   
lv_instance_is_a_classification  TYPE IF_CBASE_E, "   
lv_iv_with_db_instance  TYPE BOOLEAN. "   

  CALL FUNCTION 'CUCB_GET_CONFIGURATION'  "NOTRANSL: Lesen einer mehrstufigen Konfigurationstruktur aus der IBAse
    EXPORTING
         INSTANCE = lv_instance
         IS_BUSINESS_OBJECT = lv_is_business_object
         IV_MOMENT = lv_iv_moment
         IV_WITH_DB_INSTANCE = lv_iv_with_db_instance
    IMPORTING
         IBASE = lv_ibase
         CONFIGURATION = lv_configuration
         EO_CBASE_REF = lv_eo_cbase_ref
    EXCEPTIONS
        INVALID_INPUT = 1
        INVALID_INSTANCE = 2
        INSTANCE_IS_A_CLASSIFICATION = 3
. " CUCB_GET_CONFIGURATION




ABAP code using 7.40 inline data declarations to call FM CUCB_GET_CONFIGURATION

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



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!