SAP COM_CUXI_SET_CFG_READONLY Function Module for









COM_CUXI_SET_CFG_READONLY is a standard com cuxi set cfg readonly SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 com cuxi set cfg readonly FM, simply by entering the name COM_CUXI_SET_CFG_READONLY into the relevant SAP transaction such as SE37 or SE38.

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



Function COM_CUXI_SET_CFG_READONLY 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 'COM_CUXI_SET_CFG_READONLY'"
EXPORTING
IS_CFG_HEAD = "CUIB:Header Data
IT_INSTANCES = "CUIB: Interface Table for Instances to IBase
* IV_HANDLE_APPL_LOG = "Application Log: Log Handle
* IV_OBJECT_APPL_LOG = 'CRM_APO' "Application Log: Object Name (Application Code)
* IV_SUBOBJECT_APPL_LOG = 'T_CNFG' "Application Log: Subobject

IMPORTING
EV_HANDLE_APPL_LOG = "Application Log: Log Handle
ET_RETURN = "Return Parameter Table

EXCEPTIONS
NO_CONFIGURATION_DATA = 1 INTERNAL_ERROR = 2 INVALID_INSTANCE = 3
.



IMPORTING Parameters details for COM_CUXI_SET_CFG_READONLY

IS_CFG_HEAD - CUIB:Header Data

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

IT_INSTANCES - CUIB: Interface Table for Instances to IBase

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

IV_HANDLE_APPL_LOG - Application Log: Log Handle

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

IV_OBJECT_APPL_LOG - Application Log: Object Name (Application Code)

Data type: BALOBJ_D
Default: 'CRM_APO'
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

EXPORTING Parameters details for COM_CUXI_SET_CFG_READONLY

EV_HANDLE_APPL_LOG - Application Log: Log Handle

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

ET_RETURN - Return Parameter Table

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

EXCEPTIONS details

NO_CONFIGURATION_DATA -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Incorrect call

Data type:
Optional: No
Call by Reference: Yes

INVALID_INSTANCE - Unknown configuration instance

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for COM_CUXI_SET_CFG_READONLY 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_head  TYPE CUIB_CBASE_CONF, "   
lv_ev_handle_appl_log  TYPE BALLOGHNDL, "   
lv_no_configuration_data  TYPE BALLOGHNDL, "   
lv_et_return  TYPE BAPIRET2_T, "   
lv_it_instances  TYPE CUIB_IBCO_INSTANCE_T, "   
lv_internal_error  TYPE CUIB_IBCO_INSTANCE_T, "   
lv_invalid_instance  TYPE CUIB_IBCO_INSTANCE_T, "   
lv_iv_handle_appl_log  TYPE BALLOGHNDL, "   
lv_iv_object_appl_log  TYPE BALOBJ_D, "   'CRM_APO'
lv_iv_subobject_appl_log  TYPE BALSUBOBJ. "   'T_CNFG'

  CALL FUNCTION 'COM_CUXI_SET_CFG_READONLY'  "
    EXPORTING
         IS_CFG_HEAD = lv_is_cfg_head
         IT_INSTANCES = lv_it_instances
         IV_HANDLE_APPL_LOG = lv_iv_handle_appl_log
         IV_OBJECT_APPL_LOG = lv_iv_object_appl_log
         IV_SUBOBJECT_APPL_LOG = lv_iv_subobject_appl_log
    IMPORTING
         EV_HANDLE_APPL_LOG = lv_ev_handle_appl_log
         ET_RETURN = lv_et_return
    EXCEPTIONS
        NO_CONFIGURATION_DATA = 1
        INTERNAL_ERROR = 2
        INVALID_INSTANCE = 3
. " COM_CUXI_SET_CFG_READONLY




ABAP code using 7.40 inline data declarations to call FM COM_CUXI_SET_CFG_READONLY

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) = 'CRM_APO'.
 
DATA(ld_iv_subobject_appl_log) = 'T_CNFG'.
 


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!