SAP UKM_EXPORT_KEY_MAPPINGS Function Module for
UKM_EXPORT_KEY_MAPPINGS is a standard ukm export key mappings 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 ukm export key mappings FM, simply by entering the name UKM_EXPORT_KEY_MAPPINGS into the relevant SAP transaction such as SE37 or SE38.
Function Group: UKM_KEY_MAPPING_TRANSPORT
Program Name: SAPLUKM_KEY_MAPPING_TRANSPORT
Main Program: SAPLUKM_KEY_MAPPING_TRANSPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UKM_EXPORT_KEY_MAPPINGS 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 'UKM_EXPORT_KEY_MAPPINGS'".
EXPORTING
* IT_CCT_ID_SASA_ID = "
IV_RFC_DESTINATION = "
* IT_CCT_ID_SAS_ID = "
* IT_CCT_ID_SA_ID = "
* IT_CCT_ID_SV_ID = "
* IT_CCT_ID_S_ID = "
IV_SOURCE_CONTEXT_ID = "
IV_TARGET_CONTEXT_ID = "
* IT_MODIFICATIONS = "
* IV_BLOCK_SIZE = 10000 "
CHANGING
* CS_MESSAGE = "
IMPORTING Parameters details for UKM_EXPORT_KEY_MAPPINGS
IT_CCT_ID_SASA_ID -
Data type: UKM_T_CCT_ID_SASA_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_RFC_DESTINATION -
Data type: RFCDESTOptional: No
Call by Reference: No ( called with pass by value option)
IT_CCT_ID_SAS_ID -
Data type: UKM_T_CCT_ID_SAS_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_CCT_ID_SA_ID -
Data type: UKM_T_CCT_ID_SA_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_CCT_ID_SV_ID -
Data type: UKM_T_CCT_ID_SV_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_CCT_ID_S_ID -
Data type: UKM_T_CCT_ID_S_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SOURCE_CONTEXT_ID -
Data type: UKM_E_MAIN_CONTEXT_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_TARGET_CONTEXT_ID -
Data type: UKM_E_MAIN_CONTEXT_IDOptional: No
Call by Reference: No ( called with pass by value option)
IT_MODIFICATIONS -
Data type: UKM_T_CCT_ID_ATTRIBUTES_PAIRSOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BLOCK_SIZE -
Data type: INT4Default: 10000
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for UKM_EXPORT_KEY_MAPPINGS
CS_MESSAGE -
Data type: UKM_S_MESSAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UKM_EXPORT_KEY_MAPPINGS 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_cs_message | TYPE UKM_S_MESSAGE, " | |||
| lv_it_cct_id_sasa_id | TYPE UKM_T_CCT_ID_SASA_ID, " | |||
| lv_iv_rfc_destination | TYPE RFCDEST, " | |||
| lv_it_cct_id_sas_id | TYPE UKM_T_CCT_ID_SAS_ID, " | |||
| lv_it_cct_id_sa_id | TYPE UKM_T_CCT_ID_SA_ID, " | |||
| lv_it_cct_id_sv_id | TYPE UKM_T_CCT_ID_SV_ID, " | |||
| lv_it_cct_id_s_id | TYPE UKM_T_CCT_ID_S_ID, " | |||
| lv_iv_source_context_id | TYPE UKM_E_MAIN_CONTEXT_ID, " | |||
| lv_iv_target_context_id | TYPE UKM_E_MAIN_CONTEXT_ID, " | |||
| lv_it_modifications | TYPE UKM_T_CCT_ID_ATTRIBUTES_PAIRS, " | |||
| lv_iv_block_size | TYPE INT4. " 10000 |
|   CALL FUNCTION 'UKM_EXPORT_KEY_MAPPINGS' " |
| EXPORTING | ||
| IT_CCT_ID_SASA_ID | = lv_it_cct_id_sasa_id | |
| IV_RFC_DESTINATION | = lv_iv_rfc_destination | |
| IT_CCT_ID_SAS_ID | = lv_it_cct_id_sas_id | |
| IT_CCT_ID_SA_ID | = lv_it_cct_id_sa_id | |
| IT_CCT_ID_SV_ID | = lv_it_cct_id_sv_id | |
| IT_CCT_ID_S_ID | = lv_it_cct_id_s_id | |
| IV_SOURCE_CONTEXT_ID | = lv_iv_source_context_id | |
| IV_TARGET_CONTEXT_ID | = lv_iv_target_context_id | |
| IT_MODIFICATIONS | = lv_it_modifications | |
| IV_BLOCK_SIZE | = lv_iv_block_size | |
| CHANGING | ||
| CS_MESSAGE | = lv_cs_message | |
| . " UKM_EXPORT_KEY_MAPPINGS | ||
ABAP code using 7.40 inline data declarations to call FM UKM_EXPORT_KEY_MAPPINGS
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_block_size) | = 10000. | |||
Search for further information about these or an SAP related objects