SAP CUCB_COPY_CONFIGURATION Function Module for NOTRANSL: Erzeugen einer Konfiguration im Puffer
CUCB_COPY_CONFIGURATION is a standard cucb copy 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: Erzeugen einer Konfiguration im Puffer 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 copy configuration FM, simply by entering the name CUCB_COPY_CONFIGURATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUCB
Program Name: SAPLCUCB
Main Program: SAPLCUCB
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUCB_COPY_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_COPY_CONFIGURATION'"NOTRANSL: Erzeugen einer Konfiguration im Puffer.
EXPORTING
SOURCE_INSTANCE = "CUIB: System-Dependent Configuration Reference
* IS_SOURCE_OBSERVER = "
* IV_SOURCE_MOMENT = "IB: Time Stamp of Owner's or Observer's Version
* IV_TARGET_INSTANCE = "CUIB: System-Dependent Configuration Reference
* IV_ONLY_SINGLE_LEVEL = "
* IV_INVALID_POSSIBLE = "Invalid Instance Allowed
IMPORTING
CONFIGURATION = "New Configuration
ET_MATCH_INSTANCE = "Assignment Between Old and New CUOBJ
ES_INSTANCE_REC = "
EXCEPTIONS
INVALID_INSTANCE = 1 INSTANCE_IS_A_CLASSIFICATION = 2
IMPORTING Parameters details for CUCB_COPY_CONFIGURATION
SOURCE_INSTANCE - CUIB: System-Dependent Configuration Reference
Data type: CUIB_CUOBJOptional: No
Call by Reference: Yes
IS_SOURCE_OBSERVER -
Data type: CUIB_BUSINESS_OBJECTOptional: Yes
Call by Reference: Yes
IV_SOURCE_MOMENT - IB: Time Stamp of Owner's or Observer's Version
Data type: TIMESTAMPOptional: Yes
Call by Reference: Yes
IV_TARGET_INSTANCE - CUIB: System-Dependent Configuration Reference
Data type: CUIB_CUOBJOptional: Yes
Call by Reference: Yes
IV_ONLY_SINGLE_LEVEL -
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_INVALID_POSSIBLE - Invalid Instance Allowed
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CUCB_COPY_CONFIGURATION
CONFIGURATION - New Configuration
Data type: IBCO2_INSTANCE_TAB2Optional: No
Call by Reference: Yes
ET_MATCH_INSTANCE - Assignment Between Old and New CUOBJ
Data type: CUIB_MATCH_INSTANCE_TABOptional: No
Call by Reference: Yes
ES_INSTANCE_REC -
Data type: IBCO2_INSTANCE_REC2Optional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INSTANCE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INSTANCE_IS_A_CLASSIFICATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUCB_COPY_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_configuration | TYPE IBCO2_INSTANCE_TAB2, " | |||
| lv_source_instance | TYPE CUIB_CUOBJ, " | |||
| lv_invalid_instance | TYPE CUIB_CUOBJ, " | |||
| lv_et_match_instance | TYPE CUIB_MATCH_INSTANCE_TAB, " | |||
| lv_is_source_observer | TYPE CUIB_BUSINESS_OBJECT, " | |||
| lv_instance_is_a_classification | TYPE CUIB_BUSINESS_OBJECT, " | |||
| lv_es_instance_rec | TYPE IBCO2_INSTANCE_REC2, " | |||
| lv_iv_source_moment | TYPE TIMESTAMP, " | |||
| lv_iv_target_instance | TYPE CUIB_CUOBJ, " | |||
| lv_iv_only_single_level | TYPE XFELD, " | |||
| lv_iv_invalid_possible | TYPE XFELD. " |
|   CALL FUNCTION 'CUCB_COPY_CONFIGURATION' "NOTRANSL: Erzeugen einer Konfiguration im Puffer |
| EXPORTING | ||
| SOURCE_INSTANCE | = lv_source_instance | |
| IS_SOURCE_OBSERVER | = lv_is_source_observer | |
| IV_SOURCE_MOMENT | = lv_iv_source_moment | |
| IV_TARGET_INSTANCE | = lv_iv_target_instance | |
| IV_ONLY_SINGLE_LEVEL | = lv_iv_only_single_level | |
| IV_INVALID_POSSIBLE | = lv_iv_invalid_possible | |
| IMPORTING | ||
| CONFIGURATION | = lv_configuration | |
| ET_MATCH_INSTANCE | = lv_et_match_instance | |
| ES_INSTANCE_REC | = lv_es_instance_rec | |
| EXCEPTIONS | ||
| INVALID_INSTANCE = 1 | ||
| INSTANCE_IS_A_CLASSIFICATION = 2 | ||
| . " CUCB_COPY_CONFIGURATION | ||
ABAP code using 7.40 inline data declarations to call FM CUCB_COPY_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