SAP HR_RU_FIRE_DATE Function Module for Date of last leaving event

Search SAP Function Modules

HR_RU_FIRE_DATE is a standard hr ru fire date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Date of last leaving event 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 ru fire date FM, simply by entering the name HR_RU_FIRE_DATE into the relevant SAP transaction such as SE37 or SE38.

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

Function HR_RU_FIRE_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_RU_FIRE_DATE'"Date of last leaving event
  EXPORTING
   P_PERNR =  "Personnel Number
   P_BEGDA =  "Start Date
   P_ENDDA =  "End Date
*  P_MOLGA = '33' "Country Grouping
*  P_ENL = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
*  P_NOHOLES = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
*  P_TAB_CLASS =  "
*  P_TAB_CRITERIA =  "

 IMPORTING
   FIREDATE =  "
   ACTIVE =  "

EXCEPTIONS
   NO_MOLGA = 1    NO_INFOTYPE_REG = 2    ERROR = 3 

.

IMPORTING Parameters details for HR_RU_FIRE_DATE

P_PERNR - Personnel Number

Data type: PERNR-PERNR
Optional: No
Call by Reference: Yes

P_BEGDA - Start Date

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

P_ENDDA - End Date

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

P_MOLGA - Country Grouping

Data type: T001P-MOLGA
Default: '33'
Optional: Yes
Call by Reference: Yes

P_ENL - Boolean Variable (X=True, -=False, Space=Unknown)

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

P_NOHOLES - Boolean Variable (X=True, -=False, Space=Unknown)

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

P_TAB_CLASS -

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

P_TAB_CRITERIA -

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

EXPORTING Parameters details for HR_RU_FIRE_DATE

FIREDATE -

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

ACTIVE -

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

EXCEPTIONS details

NO_MOLGA -

Data type:
Optional: No
Call by Reference: Yes

NO_INFOTYPE_REG -

Data type:
Optional: No
Call by Reference: Yes

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_RU_FIRE_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.

ABAP code using 7.40 inline data declarations to call FM HR_RU_FIRE_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.

Search for further information about these or an SAP related objects