SAP HR_SEN_READ_SEL_EXIT Function Module for









HR_SEN_READ_SEL_EXIT is a standard hr sen read sel exit 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 sen read sel exit FM, simply by entering the name HR_SEN_READ_SEL_EXIT into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_SEN_READ_SEL_EXIT 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_SEN_READ_SEL_EXIT'"
  EXPORTING
   P_PERNR =  "
*  IR_LOGINFTY_HANDLER =  "
   P_BEGDA =  "
   P_ENDDA =  "
   P_SDATE =  "
   P_SRULE =  "
   P_SEXIT =  "
   P_CRULE =  "
   P_AUTHO =  "
*  IS_PEAK_CONTROL =  "

TABLES
   P_WPERIOD =  "
   P_PEAK =  "

EXCEPTIONS
   E_UNKNOWN_SEL_EXIT = 1    E_UNCOMPLETED_SEL_EXIT = 2    E_UNRESPECTED_SPECIFICATION = 3    E_UNINTERPRETED_VALUE = 4    E_EXIT_NO_AUTHORIZATION = 5    E_EXIT_INTERNAL_ERROR = 6
.



IMPORTING Parameters details for HR_SEN_READ_SEL_EXIT

P_PERNR -

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

IR_LOGINFTY_HANDLER -

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

P_BEGDA -

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

P_ENDDA -

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

P_SDATE -

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

P_SRULE -

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

P_SEXIT -

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

P_CRULE -

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

P_AUTHO -

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

IS_PEAK_CONTROL -

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

TABLES Parameters details for HR_SEN_READ_SEL_EXIT

P_WPERIOD -

Data type: PSEN_SEL_RULE_WGHT_PERIOD
Optional: No
Call by Reference: No ( called with pass by value option)

P_PEAK -

Data type: PSEN_SEL_RULE_PEAK_DEC
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

E_UNKNOWN_SEL_EXIT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_UNCOMPLETED_SEL_EXIT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_UNRESPECTED_SPECIFICATION -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_UNINTERPRETED_VALUE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

E_EXIT_NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

E_EXIT_INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_SEN_READ_SEL_EXIT 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_p_pernr  TYPE PERSNO, "   
lt_p_wperiod  TYPE STANDARD TABLE OF PSEN_SEL_RULE_WGHT_PERIOD, "   
lv_e_unknown_sel_exit  TYPE PSEN_SEL_RULE_WGHT_PERIOD, "   
lv_ir_loginfty_handler  TYPE CL_HRSEN_LOGINFTY_HANDLER, "   
lt_p_peak  TYPE STANDARD TABLE OF PSEN_SEL_RULE_PEAK_DEC, "   
lv_p_begda  TYPE BEGDA, "   
lv_e_uncompleted_sel_exit  TYPE BEGDA, "   
lv_p_endda  TYPE ENDDA, "   
lv_e_unrespected_specification  TYPE ENDDA, "   
lv_p_sdate  TYPE D, "   
lv_e_uninterpreted_value  TYPE D, "   
lv_p_srule  TYPE HRSEN00_SELECTION_RULE, "   
lv_e_exit_no_authorization  TYPE HRSEN00_SELECTION_RULE, "   
lv_p_sexit  TYPE HRSEN00_SELECTION_EXIT, "   
lv_e_exit_internal_error  TYPE HRSEN00_SELECTION_EXIT, "   
lv_p_crule  TYPE T525U, "   
lv_p_autho  TYPE XFELD, "   
lv_is_peak_control  TYPE PSEN_PEAK_CONTROL. "   

  CALL FUNCTION 'HR_SEN_READ_SEL_EXIT'  "
    EXPORTING
         P_PERNR = lv_p_pernr
         IR_LOGINFTY_HANDLER = lv_ir_loginfty_handler
         P_BEGDA = lv_p_begda
         P_ENDDA = lv_p_endda
         P_SDATE = lv_p_sdate
         P_SRULE = lv_p_srule
         P_SEXIT = lv_p_sexit
         P_CRULE = lv_p_crule
         P_AUTHO = lv_p_autho
         IS_PEAK_CONTROL = lv_is_peak_control
    TABLES
         P_WPERIOD = lt_p_wperiod
         P_PEAK = lt_p_peak
    EXCEPTIONS
        E_UNKNOWN_SEL_EXIT = 1
        E_UNCOMPLETED_SEL_EXIT = 2
        E_UNRESPECTED_SPECIFICATION = 3
        E_UNINTERPRETED_VALUE = 4
        E_EXIT_NO_AUTHORIZATION = 5
        E_EXIT_INTERNAL_ERROR = 6
. " HR_SEN_READ_SEL_EXIT




ABAP code using 7.40 inline data declarations to call FM HR_SEN_READ_SEL_EXIT

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



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!