SAP HRAR_DAQ_FIRE_DATE Function Module for

Search SAP Function Modules

HRAR_DAQ_FIRE_DATE is a standard hrar daq 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 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 hrar daq fire date FM, simply by entering the name HRAR_DAQ_FIRE_DATE into the relevant SAP transaction such as SE37 or SE38.

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

Function HRAR_DAQ_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 'HRAR_DAQ_FIRE_DATE'"
  EXPORTING
   IM_DAQ =  "
   IM_TAB_PAY =  "
   IM_TAB_TIME =  "
*  IM_TAB_PRELP =  "
*  IM_TAB_USER =  "
   IM_FORM =  "
*  IM_WAFOR =  "
*  IM_TAB_FODAT =  "

 IMPORTING
   EX_TAB_VALUE =  "
   EX_RETURNCODE =  "

CHANGING
*  CH_TAB_ERROR =  "
*  CH_MISC =  "

.

IMPORTING Parameters details for HRAR_DAQ_FIRE_DATE

IM_DAQ -

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

IM_TAB_PAY -

Data type:
Optional: No
Call by Reference: Yes

IM_TAB_TIME -

Data type:
Optional: No
Call by Reference: Yes

IM_TAB_PRELP -

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

IM_TAB_USER -

Data type:
Optional: Yes
Call by Reference: Yes

IM_FORM -

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

IM_WAFOR -

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

IM_TAB_FODAT -

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

EXPORTING Parameters details for HRAR_DAQ_FIRE_DATE

EX_TAB_VALUE -

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

EX_RETURNCODE -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

CHANGING Parameters details for HRAR_DAQ_FIRE_DATE

CH_TAB_ERROR -

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

CH_MISC -

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

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