SAP CUXI_SET_AND_SAVE_SINGLE_CFG Function Module for NOTRANSL: Transformieren ext. in int. Darst. und Sichern einer Konfigurati









CUXI_SET_AND_SAVE_SINGLE_CFG is a standard cuxi set and save single cfg 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: Transformieren ext. in int. Darst. und Sichern einer Konfigurati 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 cuxi set and save single cfg FM, simply by entering the name CUXI_SET_AND_SAVE_SINGLE_CFG into the relevant SAP transaction such as SE37 or SE38.

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



Function CUXI_SET_AND_SAVE_SINGLE_CFG 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 'CUXI_SET_AND_SAVE_SINGLE_CFG'"NOTRANSL: Transformieren ext. in int. Darst. und Sichern einer Konfigurati
  EXPORTING
   IS_CFG_HEADER =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IT_INSTANCES =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IT_PART_OF =  "CUX: Part-Of Data
   IT_VALUES =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   IT_VAR_KEYS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  IT_BLOB =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  IV_OBJECT_APPL_LOG = 'CIF' "Application log: Object name (Application code)
*  IV_SUBOBJECT_APPL_LOG = 'T_CNFG' "Application Log: Subobject
*  IV_ROOT_INSTANCE =  "Instance Reference
*  IV_PLANT =  "Plant
*  IV_STRUCTURE_EXPLOSION_DATE =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  IV_STRUCTURE_EXPLOSION_APPL_ID =  "Application
*  IV_ONLY_SINGLE_LEVEL =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  IV_LOGSYS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  IV_HANDLE_APPL_LOG =  "Application Log: Log Handle
   IS_OWNER =  "CUIB: Business Object

 IMPORTING
   EV_ROOT_INSTANCE =  "Instance Reference
   EV_ROOT_PERSIST_ID =  "Globally Unique Identifier
   EV_HANDLE_APPL_LOG =  "Application Log: Log Handle
   ET_RETURN =  "Return Table

EXCEPTIONS
   NO_CONFIGURATION_DATA = 1    INVALID_INSTANCE = 2    INSTANCE_IS_A_CLASSIFICATION = 3    INTERNAL_ERROR = 4    NO_OWNER_SPECIFIED = 5    NO_PROFILE_FOUND = 6    INVALID_DATA = 7
.



IMPORTING Parameters details for CUXI_SET_AND_SAVE_SINGLE_CFG

IS_CFG_HEADER - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_INSTANCES - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_PART_OF - CUX: Part-Of Data

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

IT_VALUES - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_VAR_KEYS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IT_BLOB - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IV_OBJECT_APPL_LOG - Application log: Object name (Application code)

Data type: BALOBJ_D
Default: 'CIF'
Optional: Yes
Call by Reference: Yes

IV_SUBOBJECT_APPL_LOG - Application Log: Subobject

Data type: BALSUBOBJ
Default: 'T_CNFG'
Optional: Yes
Call by Reference: Yes

IV_ROOT_INSTANCE - Instance Reference

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

IV_PLANT - Plant

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

IV_STRUCTURE_EXPLOSION_DATE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IV_STRUCTURE_EXPLOSION_APPL_ID - Application

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

IV_ONLY_SINGLE_LEVEL - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IV_LOGSYS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IV_HANDLE_APPL_LOG - Application Log: Log Handle

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

IS_OWNER - CUIB: Business Object

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

EXPORTING Parameters details for CUXI_SET_AND_SAVE_SINGLE_CFG

EV_ROOT_INSTANCE - Instance Reference

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

EV_ROOT_PERSIST_ID - Globally Unique Identifier

Data type: IBEXTINST_DATA-EXT_INST_ID
Optional: No
Call by Reference: Yes

EV_HANDLE_APPL_LOG - Application Log: Log Handle

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

ET_RETURN - Return Table

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

EXCEPTIONS details

NO_CONFIGURATION_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INVALID_INSTANCE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INSTANCE_IS_A_CLASSIFICATION - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Unspecified error

Data type:
Optional: No
Call by Reference: Yes

NO_OWNER_SPECIFIED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NO_PROFILE_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CUXI_SET_AND_SAVE_SINGLE_CFG 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_is_cfg_header  TYPE CUXT_CUCFG_S, "   
lv_ev_root_instance  TYPE CUXT_INSTANCE_NO, "   
lv_no_configuration_data  TYPE CUXT_INSTANCE_NO, "   
lv_it_instances  TYPE CUXT_CUINS_T, "   
lv_it_part_of  TYPE CUXT_CUPRT_T, "   
lv_it_values  TYPE CUXT_CUVAL_T, "   
lv_it_var_keys  TYPE CUXT_CUVK_T, "   
lv_it_blob  TYPE CUXT_CUBLB_T, "   
lv_iv_object_appl_log  TYPE BALOBJ_D, "   'CIF'
lv_iv_subobject_appl_log  TYPE BALSUBOBJ, "   'T_CNFG'
lv_invalid_instance  TYPE BALSUBOBJ, "   
lv_iv_root_instance  TYPE CUIB_CUOBJ, "   
lv_ev_root_persist_id  TYPE IBEXTINST_DATA-EXT_INST_ID, "   
lv_iv_plant  TYPE WERKS_D, "   
lv_ev_handle_appl_log  TYPE BALLOGHNDL, "   
lv_instance_is_a_classification  TYPE BALLOGHNDL, "   
lv_et_return  TYPE BAPIRET2_T, "   
lv_internal_error  TYPE BAPIRET2_T, "   
lv_iv_structure_explosion_date  TYPE CUXT_STRUCTURE_EXPLOSION_DATE, "   
lv_no_owner_specified  TYPE CUXT_STRUCTURE_EXPLOSION_DATE, "   
lv_iv_structure_explosion_appl_id  TYPE CAPID, "   
lv_no_profile_found  TYPE CAPID, "   
lv_iv_only_single_level  TYPE CU_CHECKED, "   
lv_iv_logsys  TYPE LOGSYS, "   
lv_invalid_data  TYPE LOGSYS, "   
lv_iv_handle_appl_log  TYPE BALLOGHNDL, "   
lv_is_owner  TYPE CUIB_BUSINESS_OBJECT. "   

  CALL FUNCTION 'CUXI_SET_AND_SAVE_SINGLE_CFG'  "NOTRANSL: Transformieren ext. in int. Darst. und Sichern einer Konfigurati
    EXPORTING
         IS_CFG_HEADER = lv_is_cfg_header
         IT_INSTANCES = lv_it_instances
         IT_PART_OF = lv_it_part_of
         IT_VALUES = lv_it_values
         IT_VAR_KEYS = lv_it_var_keys
         IT_BLOB = lv_it_blob
         IV_OBJECT_APPL_LOG = lv_iv_object_appl_log
         IV_SUBOBJECT_APPL_LOG = lv_iv_subobject_appl_log
         IV_ROOT_INSTANCE = lv_iv_root_instance
         IV_PLANT = lv_iv_plant
         IV_STRUCTURE_EXPLOSION_DATE = lv_iv_structure_explosion_date
         IV_STRUCTURE_EXPLOSION_APPL_ID = lv_iv_structure_explosion_appl_id
         IV_ONLY_SINGLE_LEVEL = lv_iv_only_single_level
         IV_LOGSYS = lv_iv_logsys
         IV_HANDLE_APPL_LOG = lv_iv_handle_appl_log
         IS_OWNER = lv_is_owner
    IMPORTING
         EV_ROOT_INSTANCE = lv_ev_root_instance
         EV_ROOT_PERSIST_ID = lv_ev_root_persist_id
         EV_HANDLE_APPL_LOG = lv_ev_handle_appl_log
         ET_RETURN = lv_et_return
    EXCEPTIONS
        NO_CONFIGURATION_DATA = 1
        INVALID_INSTANCE = 2
        INSTANCE_IS_A_CLASSIFICATION = 3
        INTERNAL_ERROR = 4
        NO_OWNER_SPECIFIED = 5
        NO_PROFILE_FOUND = 6
        INVALID_DATA = 7
. " CUXI_SET_AND_SAVE_SINGLE_CFG




ABAP code using 7.40 inline data declarations to call FM CUXI_SET_AND_SAVE_SINGLE_CFG

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.

 
 
 
 
 
 
 
 
DATA(ld_iv_object_appl_log) = 'CIF'.
 
DATA(ld_iv_subobject_appl_log) = 'T_CNFG'.
 
 
 
"SELECT single EXT_INST_ID FROM IBEXTINST_DATA INTO @DATA(ld_ev_root_persist_id).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!