SAP COM_CUXI_GET_SINGLE_CFG_REMOTE Function Module for

Search SAP Function Modules

COM_CUXI_GET_SINGLE_CFG_REMOTE is a standard com cuxi get single cfg remote 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 get single cfg remote FM, simply by entering the name COM_CUXI_GET_SINGLE_CFG_REMOTE 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_GET_SINGLE_CFG_REMOTE 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_GET_SINGLE_CFG_REMOTE'"
  EXPORTING
*  IV_INSTANCE_GUID =  "Instance Number (Persistent)
*  IV_INSTANCE =  "CUIB: System-Dependent Configuration Reference
*  IV_OBJECT_APPL_LOG = 'CRM_APO' "Application Log: Object Name (Application Code)
*  IV_SUBOBJECT_APPL_LOG = 'T_CNFG' "Application Log: Subobject

 IMPORTING
   ES_CFG_HEAD =  "CUX: Configuration Header Data
   ET_RETURN =  "Return Parameter Table

TABLES
   ET_INSTANCES =  "CUX: Instance Data
   ET_PART_OF =  "CUX: Part-Of Data
   ET_VALUES =  "CUX: Characteristic Value Assignment
   ET_VAR_KEYS =  "CUX: Variant Condition Key for Configuration
*  ET_RESTRICTIONS =  "CUX: Characteristic Value Assignment

.

IMPORTING Parameters details for COM_CUXI_GET_SINGLE_CFG_REMOTE

IV_INSTANCE_GUID - Instance Number (Persistent)

Data type: CUX_PERSIST_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_INSTANCE - CUIB: System-Dependent Configuration Reference

Data type: CUIB_CUOBJ
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OBJECT_APPL_LOG - Application Log: Object Name (Application Code)

Data type: BALOBJ_D
Default: 'CRM_APO'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SUBOBJECT_APPL_LOG - Application Log: Subobject

Data type: BALSUBOBJ
Default: 'T_CNFG'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for COM_CUXI_GET_SINGLE_CFG_REMOTE

ES_CFG_HEAD - CUX: Configuration Header Data

Data type: CUXT_CUCFG_S
Optional: No
Call by Reference: No ( called with pass by value option)

ET_RETURN - Return Parameter Table

Data type: BAPIRET2_T
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for COM_CUXI_GET_SINGLE_CFG_REMOTE

ET_INSTANCES - CUX: Instance Data

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

ET_PART_OF - CUX: Part-Of Data

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

ET_VALUES - CUX: Characteristic Value Assignment

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

ET_VAR_KEYS - CUX: Variant Condition Key for Configuration

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

ET_RESTRICTIONS - CUX: Characteristic Value Assignment

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

Copy and paste ABAP code example for COM_CUXI_GET_SINGLE_CFG_REMOTE 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.

ABAP code using 7.40 inline data declarations to call FM COM_CUXI_GET_SINGLE_CFG_REMOTE

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