CLIST_API_GET_CONFIG_CHECK SAP Function module - CList API: Get data from MRO components

CLIST_API_GET_CONFIG_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CLIST_API_GET_CONFIG_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CCCL_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CLIST_API_GET_CONFIG_CHECK - CLIST API GET CONFIG CHECK

CALL FUNCTION 'CLIST_API_GET_CONFIG_CHECK' "CList API: Get data from MRO components
* EXPORTING
*   it_ordernumbers =           " tt_api_order_key  CList API: Order numbers
*   it_operationkeys =          " tt_api_operation_key  CList API: Operation keys
*   it_componentkeys =          " tt_api_component_key  CList API: Component keys
  IMPORTING
    et_components =             " tt_api_component_data  CList API: MRO components data
    et_configcheck =            " bapirettab    Messages from configuration check results
    et_return =                 " bapirettab    Error, warning and success messages
    .  "  CLIST_API_GET_CONFIG_CHECK

ABAP code example for Function Module CLIST_API_GET_CONFIG_CHECK

The ABAP code below is a full code listing to execute function module CLIST_API_GET_CONFIG_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_components  
 
 TYPE TT_API_COMPONENT_DATA
,
ld_et_configcheck  
 
 TYPE BAPIRETTAB
,
ld_et_return  
 
 TYPE BAPIRETTAB
.


DATA(ld_it_ordernumbers) = 'Check type of data required'.

DATA(ld_it_operationkeys) = 'Check type of data required'.

DATA(ld_it_componentkeys) = 'Check type of data required'.
.

CALL FUNCTION 'CLIST_API_GET_CONFIG_CHECK'
* EXPORTING
*   it_ordernumbers =            ld_it_ordernumbers
*   it_operationkeys =           ld_it_operationkeys
*   it_componentkeys =           ld_it_componentkeys
  IMPORTING
    et_components =              ld_et_components
    et_configcheck =             ld_et_configcheck
    et_return =                  ld_et_return
    .  "  CLIST_API_GET_CONFIG_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_components
 
 TYPE TT_API_COMPONENT_DATA ,
ld_it_ordernumbers
 
 TYPE TT_API_ORDER_KEY ,
ld_et_configcheck
 
 TYPE BAPIRETTAB ,
ld_it_operationkeys
 
 TYPE TT_API_OPERATION_KEY ,
ld_et_return
 
 TYPE BAPIRETTAB ,
ld_it_componentkeys
 
 TYPE TT_API_COMPONENT_KEY .


ld_it_ordernumbers = 'Check type of data required'.
ld_it_operationkeys = 'Check type of data required'.
ld_it_componentkeys = 'Check type of data required'.

SAP Documentation for FM CLIST_API_GET_CONFIG_CHECK