SAP HRWPC_EREC_MAP_REQ_DATA Function Module for Mapping Requisition data from ERP to E-Recruiting

Search SAP Function Modules

HRWPC_EREC_MAP_REQ_DATA is a standard hrwpc erec map req data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping Requisition data from ERP to E-Recruiting processing and below is the pattern details for this FM, 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 hrwpc erec map req data FM, simply by entering the name HRWPC_EREC_MAP_REQ_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRWPC_EREC_UTILITIES
Program Name: SAPLHRWPC_EREC_UTILITIES
Main Program: SAPLHRWPC_EREC_UTILITIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRWPC_EREC_MAP_REQ_DATA 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 'HRWPC_EREC_MAP_REQ_DATA'"Mapping Requisition data from ERP to E-Recruiting
 IMPORTING
   BASIC_DATA =  "MSS E-Rec: API structure for Basic Data sent to P5125
   JOB_DATA =  "MSS E-Rec: API structure for Job Data sent to P5126

TABLES
   SPECIAL_DATA =  "Internal Service Request: Values of the Special Fields
   SUPPORTING_TEAM =  "MSS E-Recruiting: API table type for Support Team
   JOB_REQUIREMENTS =  "MSS E-Rec: API table type for Job Requirements sent to P5129
   EDUCATION_REQ =  "MSS E-Rec: API table type for Education data sent to P5128

.

EXPORTING Parameters details for HRWPC_EREC_MAP_REQ_DATA

BASIC_DATA - MSS E-Rec: API structure for Basic Data sent to P5125

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

JOB_DATA - MSS E-Rec: API structure for Job Data sent to P5126

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

TABLES Parameters details for HRWPC_EREC_MAP_REQ_DATA

SPECIAL_DATA - Internal Service Request: Values of the Special Fields

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

SUPPORTING_TEAM - MSS E-Recruiting: API table type for Support Team

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

JOB_REQUIREMENTS - MSS E-Rec: API table type for Job Requirements sent to P5129

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

EDUCATION_REQ - MSS E-Rec: API table type for Education data sent to P5128

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

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

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