SAP HCM_MAP_FIELDS Function Module for
HCM_MAP_FIELDS is a standard hcm map fields 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 hcm map fields FM, simply by entering the name HCM_MAP_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: HCM_ADDON_INT
Program Name: SAPLHCM_ADDON_INT
Main Program: SAPLHCM_ADDON_INT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HCM_MAP_FIELDS 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 'HCM_MAP_FIELDS'".
EXPORTING
IS_P0000 = "
IS_P0002 = "
IS_P0006 = "
IS_P0105_SUB0005 = "
IS_P0105_SUB0010 = "
IS_P0105_SUB0020 = "
IMPORTING
ES_BP_CENTRAL = "
ES_BP_FAX_X = "
ES_BP_SMTP = "
ES_BP_SMTP_X = "
ET_ERRORS = "
ES_BP_CENTRAL_X = "
ES_BP_PERSON = "
ES_BP_PERSON_X = "
ES_BP_ADDRESS = "
ES_BP_ADDRESS_X = "
ES_BP_TEL = "
ES_BP_TEL_X = "
ES_BP_FAX = "
IMPORTING Parameters details for HCM_MAP_FIELDS
IS_P0000 -
Data type: P0000Optional: No
Call by Reference: Yes
IS_P0002 -
Data type: P0002Optional: No
Call by Reference: Yes
IS_P0006 -
Data type: P0006Optional: No
Call by Reference: Yes
IS_P0105_SUB0005 -
Data type: P0105Optional: No
Call by Reference: Yes
IS_P0105_SUB0010 -
Data type: P0105Optional: No
Call by Reference: Yes
IS_P0105_SUB0020 -
Data type: P0105Optional: No
Call by Reference: Yes
EXPORTING Parameters details for HCM_MAP_FIELDS
ES_BP_CENTRAL -
Data type: BAPIBUS1006_CENTRALOptional: No
Call by Reference: Yes
ES_BP_FAX_X -
Data type: BAPIADFAXXOptional: No
Call by Reference: Yes
ES_BP_SMTP -
Data type: BAPIADSMTPOptional: No
Call by Reference: Yes
ES_BP_SMTP_X -
Data type: BAPIADSMTXOptional: No
Call by Reference: Yes
ET_ERRORS -
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
ES_BP_CENTRAL_X -
Data type: BAPIBUS1006_CENTRAL_XOptional: No
Call by Reference: Yes
ES_BP_PERSON -
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: No
Call by Reference: Yes
ES_BP_PERSON_X -
Data type: BAPIBUS1006_CENTRAL_PERSON_XOptional: No
Call by Reference: Yes
ES_BP_ADDRESS -
Data type: BAPIBUS1006_ADDRESSOptional: No
Call by Reference: Yes
ES_BP_ADDRESS_X -
Data type: BAPIBUS1006_ADDRESS_XOptional: No
Call by Reference: Yes
ES_BP_TEL -
Data type: BAPIADTELOptional: No
Call by Reference: Yes
ES_BP_TEL_X -
Data type: BAPIADTELXOptional: No
Call by Reference: Yes
ES_BP_FAX -
Data type: BAPIADFAXOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HCM_MAP_FIELDS 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_p0000 | TYPE P0000, " | |||
| lv_es_bp_central | TYPE BAPIBUS1006_CENTRAL, " | |||
| lv_es_bp_fax_x | TYPE BAPIADFAXX, " | |||
| lv_es_bp_smtp | TYPE BAPIADSMTP, " | |||
| lv_es_bp_smtp_x | TYPE BAPIADSMTX, " | |||
| lv_et_errors | TYPE BAPIRET2_T, " | |||
| lv_is_p0002 | TYPE P0002, " | |||
| lv_es_bp_central_x | TYPE BAPIBUS1006_CENTRAL_X, " | |||
| lv_is_p0006 | TYPE P0006, " | |||
| lv_es_bp_person | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
| lv_es_bp_person_x | TYPE BAPIBUS1006_CENTRAL_PERSON_X, " | |||
| lv_is_p0105_sub0005 | TYPE P0105, " | |||
| lv_es_bp_address | TYPE BAPIBUS1006_ADDRESS, " | |||
| lv_is_p0105_sub0010 | TYPE P0105, " | |||
| lv_es_bp_address_x | TYPE BAPIBUS1006_ADDRESS_X, " | |||
| lv_is_p0105_sub0020 | TYPE P0105, " | |||
| lv_es_bp_tel | TYPE BAPIADTEL, " | |||
| lv_es_bp_tel_x | TYPE BAPIADTELX, " | |||
| lv_es_bp_fax | TYPE BAPIADFAX. " |
|   CALL FUNCTION 'HCM_MAP_FIELDS' " |
| EXPORTING | ||
| IS_P0000 | = lv_is_p0000 | |
| IS_P0002 | = lv_is_p0002 | |
| IS_P0006 | = lv_is_p0006 | |
| IS_P0105_SUB0005 | = lv_is_p0105_sub0005 | |
| IS_P0105_SUB0010 | = lv_is_p0105_sub0010 | |
| IS_P0105_SUB0020 | = lv_is_p0105_sub0020 | |
| IMPORTING | ||
| ES_BP_CENTRAL | = lv_es_bp_central | |
| ES_BP_FAX_X | = lv_es_bp_fax_x | |
| ES_BP_SMTP | = lv_es_bp_smtp | |
| ES_BP_SMTP_X | = lv_es_bp_smtp_x | |
| ET_ERRORS | = lv_et_errors | |
| ES_BP_CENTRAL_X | = lv_es_bp_central_x | |
| ES_BP_PERSON | = lv_es_bp_person | |
| ES_BP_PERSON_X | = lv_es_bp_person_x | |
| ES_BP_ADDRESS | = lv_es_bp_address | |
| ES_BP_ADDRESS_X | = lv_es_bp_address_x | |
| ES_BP_TEL | = lv_es_bp_tel | |
| ES_BP_TEL_X | = lv_es_bp_tel_x | |
| ES_BP_FAX | = lv_es_bp_fax | |
| . " HCM_MAP_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM HCM_MAP_FIELDS
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