SAP HR_GET_ENTRY_FEATURE Function Module for









HR_GET_ENTRY_FEATURE is a standard hr get entry feature 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 hr get entry feature FM, simply by entering the name HR_GET_ENTRY_FEATURE into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_GET_ENTRY_FEATURE 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_GET_ENTRY_FEATURE'"
EXPORTING
PERSNR = "
* IM_DATE = "
* RCLAS = "
* VARKY = "
* INITIALIZE_PS_BUFFER = 'X' "

IMPORTING
EX_SWITCH = "

EXCEPTIONS
PERNR_NOT_ASSIGNED = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLRPAI_001 User Exit for HR_ENTRY_DATE
EXIT_SAPLRPAI_002 User Exit for HR_LEAVING_DATE

IMPORTING Parameters details for HR_GET_ENTRY_FEATURE

PERSNR -

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

IM_DATE -

Data type: D
Optional: Yes
Call by Reference: Yes

RCLAS -

Data type: RCLAS_HR
Optional: Yes
Call by Reference: Yes

VARKY -

Data type: VARKY1
Optional: Yes
Call by Reference: Yes

INITIALIZE_PS_BUFFER -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for HR_GET_ENTRY_FEATURE

EX_SWITCH -

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

EXCEPTIONS details

PERNR_NOT_ASSIGNED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_GET_ENTRY_FEATURE 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_persnr  TYPE P_PERNR, "   
lv_ex_switch  TYPE HRPAD_ENTRY_SWITCH, "   
lv_pernr_not_assigned  TYPE HRPAD_ENTRY_SWITCH, "   
lv_im_date  TYPE D, "   
lv_rclas  TYPE RCLAS_HR, "   
lv_varky  TYPE VARKY1, "   
lv_initialize_ps_buffer  TYPE XFELD. "   'X'

  CALL FUNCTION 'HR_GET_ENTRY_FEATURE'  "
    EXPORTING
         PERSNR = lv_persnr
         IM_DATE = lv_im_date
         RCLAS = lv_rclas
         VARKY = lv_varky
         INITIALIZE_PS_BUFFER = lv_initialize_ps_buffer
    IMPORTING
         EX_SWITCH = lv_ex_switch
    EXCEPTIONS
        PERNR_NOT_ASSIGNED = 1
. " HR_GET_ENTRY_FEATURE




ABAP code using 7.40 inline data declarations to call FM HR_GET_ENTRY_FEATURE

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_initialize_ps_buffer) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!