SAP HR_EFI_MATCH_RECORD Function Module for match records in the table
HR_EFI_MATCH_RECORD is a standard hr efi match record SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for match records in the table 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 hr efi match record FM, simply by entering the name HR_EFI_MATCH_RECORD into the relevant SAP transaction such as SE37 or SE38.
Function Group: HREFIGB_FUNC
Program Name: SAPLHREFIGB_FUNC
Main Program: SAPLHREFIGB_FUNC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_EFI_MATCH_RECORD 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 'HR_EFI_MATCH_RECORD'"match records in the table.
EXPORTING
* PROPOSED_PERNR = "Personnel number
CHANGING
S_5GEF01 = "HR-GB: filing - Store parsed recording coming in from GG
TABLES
PT_INS_5GEF01 = "table of unmatched records
EXCEPTIONS
MOD_EXCEP = 1
IMPORTING Parameters details for HR_EFI_MATCH_RECORD
PROPOSED_PERNR - Personnel number
Data type: PERSNOOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for HR_EFI_MATCH_RECORD
S_5GEF01 - HR-GB: filing - Store parsed recording coming in from GG
Data type: T5GEF01Optional: No
Call by Reference: Yes
TABLES Parameters details for HR_EFI_MATCH_RECORD
PT_INS_5GEF01 - table of unmatched records
Data type: T5GEF01Optional: No
Call by Reference: Yes
EXCEPTIONS details
MOD_EXCEP - module exception
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_EFI_MATCH_RECORD 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_s_5gef01 | TYPE T5GEF01, " | |||
lv_mod_excep | TYPE T5GEF01, " | |||
lt_pt_ins_5gef01 | TYPE STANDARD TABLE OF T5GEF01, " | |||
lv_proposed_pernr | TYPE PERSNO. " |
  CALL FUNCTION 'HR_EFI_MATCH_RECORD' "match records in the table |
EXPORTING | ||
PROPOSED_PERNR | = lv_proposed_pernr | |
CHANGING | ||
S_5GEF01 | = lv_s_5gef01 | |
TABLES | ||
PT_INS_5GEF01 | = lt_pt_ins_5gef01 | |
EXCEPTIONS | ||
MOD_EXCEP = 1 | ||
. " HR_EFI_MATCH_RECORD |
ABAP code using 7.40 inline data declarations to call FM HR_EFI_MATCH_RECORD
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