SAP HR_BR_GET_OPERATIONAL_DATE Function Module for
HR_BR_GET_OPERATIONAL_DATE is a standard hr br get operational date 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 br get operational date FM, simply by entering the name HR_BR_GET_OPERATIONAL_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPAYBR99
Program Name: SAPLHRPAYBR99
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_BR_GET_OPERATIONAL_DATE 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_BR_GET_OPERATIONAL_DATE'".
EXPORTING
P_DATE = "
* PABKRS = "
* PPABRJ = "
* PPABRP = "
* APER_BEGDA = "
* APER_ENDDA = "
* PAYTY = "
* IBEGD = "
BONDT = "
OCCAT = "
IABKRS = "
IPABRJ = "
IPABRP = "
* SW_PROT = PBR99_OFF "
SW_AUFROLLUNG = "
* LEGAL_ENTITY = 0 "
IMPORTING
CHKDT = "
TAB_DATE = "
IMPORTING Parameters details for HR_BR_GET_OPERATIONAL_DATE
P_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
PABKRS -
Data type: P0001-ABKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
PPABRJ -
Data type: T549Q-PABRJOptional: Yes
Call by Reference: No ( called with pass by value option)
PPABRP -
Data type: T549Q-PABRPOptional: Yes
Call by Reference: No ( called with pass by value option)
APER_BEGDA -
Data type: P0001-BEGDAOptional: Yes
Call by Reference: No ( called with pass by value option)
APER_ENDDA -
Data type: P0001-ENDDAOptional: Yes
Call by Reference: No ( called with pass by value option)
PAYTY -
Data type: COptional: Yes
Call by Reference: Yes
IBEGD -
Data type: SY-DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
BONDT -
Data type: PC261-BONDTOptional: No
Call by Reference: No ( called with pass by value option)
OCCAT -
Data type: T52OCC-OCCATOptional: No
Call by Reference: No ( called with pass by value option)
IABKRS -
Data type: P0001-ABKRSOptional: No
Call by Reference: No ( called with pass by value option)
IPABRJ -
Data type: T549Q-PABRJOptional: No
Call by Reference: No ( called with pass by value option)
IPABRP -
Data type: T549Q-PABRPOptional: No
Call by Reference: No ( called with pass by value option)
SW_PROT -
Data type: PBR99_FLAGDefault: PBR99_OFF
Optional: Yes
Call by Reference: No ( called with pass by value option)
SW_AUFROLLUNG -
Data type: PBR99_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
LEGAL_ENTITY -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for HR_BR_GET_OPERATIONAL_DATE
CHKDT -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
TAB_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HR_BR_GET_OPERATIONAL_DATE 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_chkdt | TYPE SY-DATUM, " | |||
| lv_p_date | TYPE SY-DATUM, " | |||
| lv_pabkrs | TYPE P0001-ABKRS, " | |||
| lv_ppabrj | TYPE T549Q-PABRJ, " | |||
| lv_ppabrp | TYPE T549Q-PABRP, " | |||
| lv_aper_begda | TYPE P0001-BEGDA, " | |||
| lv_aper_endda | TYPE P0001-ENDDA, " | |||
| lv_payty | TYPE C, " | |||
| lv_ibegd | TYPE SY-DATUM, " | |||
| lv_bondt | TYPE PC261-BONDT, " | |||
| lv_tab_date | TYPE SY-DATUM, " | |||
| lv_occat | TYPE T52OCC-OCCAT, " | |||
| lv_iabkrs | TYPE P0001-ABKRS, " | |||
| lv_ipabrj | TYPE T549Q-PABRJ, " | |||
| lv_ipabrp | TYPE T549Q-PABRP, " | |||
| lv_sw_prot | TYPE PBR99_FLAG, " PBR99_OFF | |||
| lv_sw_aufrollung | TYPE PBR99_FLAG, " | |||
| lv_legal_entity | TYPE I. " 0 |
|   CALL FUNCTION 'HR_BR_GET_OPERATIONAL_DATE' " |
| EXPORTING | ||
| P_DATE | = lv_p_date | |
| PABKRS | = lv_pabkrs | |
| PPABRJ | = lv_ppabrj | |
| PPABRP | = lv_ppabrp | |
| APER_BEGDA | = lv_aper_begda | |
| APER_ENDDA | = lv_aper_endda | |
| PAYTY | = lv_payty | |
| IBEGD | = lv_ibegd | |
| BONDT | = lv_bondt | |
| OCCAT | = lv_occat | |
| IABKRS | = lv_iabkrs | |
| IPABRJ | = lv_ipabrj | |
| IPABRP | = lv_ipabrp | |
| SW_PROT | = lv_sw_prot | |
| SW_AUFROLLUNG | = lv_sw_aufrollung | |
| LEGAL_ENTITY | = lv_legal_entity | |
| IMPORTING | ||
| CHKDT | = lv_chkdt | |
| TAB_DATE | = lv_tab_date | |
| . " HR_BR_GET_OPERATIONAL_DATE | ||
ABAP code using 7.40 inline data declarations to call FM HR_BR_GET_OPERATIONAL_DATE
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_chkdt). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_p_date). | ||||
| "SELECT single ABKRS FROM P0001 INTO @DATA(ld_pabkrs). | ||||
| "SELECT single PABRJ FROM T549Q INTO @DATA(ld_ppabrj). | ||||
| "SELECT single PABRP FROM T549Q INTO @DATA(ld_ppabrp). | ||||
| "SELECT single BEGDA FROM P0001 INTO @DATA(ld_aper_begda). | ||||
| "SELECT single ENDDA FROM P0001 INTO @DATA(ld_aper_endda). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_ibegd). | ||||
| "SELECT single BONDT FROM PC261 INTO @DATA(ld_bondt). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_tab_date). | ||||
| "SELECT single OCCAT FROM T52OCC INTO @DATA(ld_occat). | ||||
| "SELECT single ABKRS FROM P0001 INTO @DATA(ld_iabkrs). | ||||
| "SELECT single PABRJ FROM T549Q INTO @DATA(ld_ipabrj). | ||||
| "SELECT single PABRP FROM T549Q INTO @DATA(ld_ipabrp). | ||||
| DATA(ld_sw_prot) | = PBR99_OFF. | |||
Search for further information about these or an SAP related objects