SAP HR_FBN_GET_PROCESS_DATES Function Module for Bestimmung der zur Prozessierung nötigen Beginn- und Endedaten
HR_FBN_GET_PROCESS_DATES is a standard hr fbn get process dates SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Bestimmung der zur Prozessierung nötigen Beginn- und Endedaten 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 fbn get process dates FM, simply by entering the name HR_FBN_GET_PROCESS_DATES into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRFBN00GENERAL
Program Name: SAPLHRFBN00GENERAL
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_FBN_GET_PROCESS_DATES 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_FBN_GET_PROCESS_DATES'"Bestimmung der zur Prozessierung nötigen Beginn- und Endedaten.
EXPORTING
* EVENT_DESCRIPTION = "
ENRTY = "
DATUM = "
REACTION = "
IMPORTING
PROCESS_BEGDA = "
PROCESS_ENDDA = "
SUBRC = "
CHANGING
EE_BENEFIT_DATA = "
TABLES
ERROR_TABLE = "
IMPORTING Parameters details for HR_FBN_GET_PROCESS_DATES
EVENT_DESCRIPTION -
Data type: RPBENEVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
ENRTY -
Data type: RPBENRPT01-ENRTYOptional: No
Call by Reference: No ( called with pass by value option)
DATUM -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
REACTION -
Data type: SY-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HR_FBN_GET_PROCESS_DATES
PROCESS_BEGDA -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
PROCESS_ENDDA -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for HR_FBN_GET_PROCESS_DATES
EE_BENEFIT_DATA -
Data type: RPBENEEDATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HR_FBN_GET_PROCESS_DATES
ERROR_TABLE -
Data type: RPBENERROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_FBN_GET_PROCESS_DATES 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: | ||||
| lt_error_table | TYPE STANDARD TABLE OF RPBENERR, " | |||
| lv_process_begda | TYPE SY-DATUM, " | |||
| lv_ee_benefit_data | TYPE RPBENEEDAT, " | |||
| lv_event_description | TYPE RPBENEVENT, " | |||
| lv_enrty | TYPE RPBENRPT01-ENRTY, " | |||
| lv_process_endda | TYPE SY-DATUM, " | |||
| lv_datum | TYPE SY-DATUM, " | |||
| lv_subrc | TYPE SY-SUBRC, " | |||
| lv_reaction | TYPE SY-MSGTY. " |
|   CALL FUNCTION 'HR_FBN_GET_PROCESS_DATES' "Bestimmung der zur Prozessierung nötigen Beginn- und Endedaten |
| EXPORTING | ||
| EVENT_DESCRIPTION | = lv_event_description | |
| ENRTY | = lv_enrty | |
| DATUM | = lv_datum | |
| REACTION | = lv_reaction | |
| IMPORTING | ||
| PROCESS_BEGDA | = lv_process_begda | |
| PROCESS_ENDDA | = lv_process_endda | |
| SUBRC | = lv_subrc | |
| CHANGING | ||
| EE_BENEFIT_DATA | = lv_ee_benefit_data | |
| TABLES | ||
| ERROR_TABLE | = lt_error_table | |
| . " HR_FBN_GET_PROCESS_DATES | ||
ABAP code using 7.40 inline data declarations to call FM HR_FBN_GET_PROCESS_DATES
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.| "SELECT single DATUM FROM SY INTO @DATA(ld_process_begda). | ||||
| "SELECT single ENRTY FROM RPBENRPT01 INTO @DATA(ld_enrty). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_process_endda). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_datum). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_reaction). | ||||
Search for further information about these or an SAP related objects