SAP Function Modules

MDG_ID_QUERY_MATCHING SAP Function module - Access key mapping on central registry







MDG_ID_QUERY_MATCHING 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 MDG_ID_QUERY_MATCHING into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MDG_ID_MAPPING_ACCESS
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM MDG_ID_QUERY_MATCHING - MDG ID QUERY MATCHING





CALL FUNCTION 'MDG_ID_QUERY_MATCHING' "Access key mapping on central registry
* EXPORTING
*   it_search_key =             " mdg_t_object_key_bs  Object Key inlcuding Object Type Code
*   iv_target_system =          " sld_bskey     Key Name of Business System
  IMPORTING
    es_matching_objects =       " mdg_s_get_matching_easy_bs  Identifier Set data of multiple pairs of mapped objects
    es_messages =               " bapiret2      Table with BAPI Return Information
    et_matching_objects =       " mdg_t_get_matching_easy_bs  Identifier Set data of multiple pairs of mapped objects
    .  "  MDG_ID_QUERY_MATCHING

ABAP code example for Function Module MDG_ID_QUERY_MATCHING





The ABAP code below is a full code listing to execute function module MDG_ID_QUERY_MATCHING 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_es_matching_objects  TYPE MDG_S_GET_MATCHING_EASY_BS ,
ld_es_messages  TYPE BAPIRET2 ,
ld_et_matching_objects  TYPE MDG_T_GET_MATCHING_EASY_BS .

DATA(ld_it_search_key) = 'Check type of data required'.
DATA(ld_iv_target_system) = 'Check type of data required'. . CALL FUNCTION 'MDG_ID_QUERY_MATCHING' * EXPORTING * it_search_key = ld_it_search_key * iv_target_system = ld_iv_target_system IMPORTING es_matching_objects = ld_es_matching_objects es_messages = ld_es_messages et_matching_objects = ld_et_matching_objects . " MDG_ID_QUERY_MATCHING
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_es_matching_objects  TYPE MDG_S_GET_MATCHING_EASY_BS ,
ld_it_search_key  TYPE MDG_T_OBJECT_KEY_BS ,
ld_es_messages  TYPE BAPIRET2 ,
ld_iv_target_system  TYPE SLD_BSKEY ,
ld_et_matching_objects  TYPE MDG_T_GET_MATCHING_EASY_BS .

ld_it_search_key = 'Check type of data required'.
ld_iv_target_system = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name MDG_ID_QUERY_MATCHING or its description.