SAP HR_99S_DAQ_FIELD_EXAMPLE Function Module for Retrieve field values
HR_99S_DAQ_FIELD_EXAMPLE is a standard hr 99s daq field example SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve field values 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 99s daq field example FM, simply by entering the name HR_99S_DAQ_FIELD_EXAMPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HR99S00_DAQ
Program Name: SAPLHR99S00_DAQ
Main Program: SAPLHR99S00_DAQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_99S_DAQ_FIELD_EXAMPLE 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_99S_DAQ_FIELD_EXAMPLE'"Retrieve field values.
EXPORTING
IM_DAQ = "Control parameters
IM_TAB_PAY = "
IM_TAB_TIME = "
* IM_TAB_PRELP = "Infotype table
* IM_TAB_USER = "User defined additional table
IM_FORM = "Form instance
* IM_WAFOR = "Process only selected sections
* IM_TAB_FODAT = "Table with already computed fields of form
IMPORTING
EX_TAB_VALUE = "
EX_RETURNCODE = "Return value, return value after ABAP statements
CHANGING
* CH_TAB_ERROR = "
* CH_MISC = "
IMPORTING Parameters details for HR_99S_DAQ_FIELD_EXAMPLE
IM_DAQ - Control parameters
Data type: P99SD_CODAQOptional: 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 - Infotype table
Data type: P99SG_TAB_PRELPOptional: Yes
Call by Reference: Yes
IM_TAB_USER - User defined additional table
Data type:Optional: Yes
Call by Reference: Yes
IM_FORM - Form instance
Data type: CL_HR99S00_DAQOptional: No
Call by Reference: Yes
IM_WAFOR - Process only selected sections
Data type: P99SD_WAFOROptional: Yes
Call by Reference: Yes
IM_TAB_FODAT - Table with already computed fields of form
Data type: P99SD_TAB_FODATOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HR_99S_DAQ_FIELD_EXAMPLE
EX_TAB_VALUE -
Data type: P99SD_TAB_VALUEOptional: No
Call by Reference: Yes
EX_RETURNCODE - Return value, return value after ABAP statements
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
CHANGING Parameters details for HR_99S_DAQ_FIELD_EXAMPLE
CH_TAB_ERROR -
Data type: P99SF_TAB_ERROROptional: Yes
Call by Reference: Yes
CH_MISC -
Data type: ANYOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for HR_99S_DAQ_FIELD_EXAMPLE 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_im_daq | TYPE P99SD_CODAQ, " | |||
| lv_ch_tab_error | TYPE P99SF_TAB_ERROR, " | |||
| lv_ex_tab_value | TYPE P99SD_TAB_VALUE, " | |||
| lv_ch_misc | TYPE ANY, " | |||
| lv_im_tab_pay | TYPE ANY, " | |||
| lv_ex_returncode | TYPE SY-SUBRC, " | |||
| lv_im_tab_time | TYPE SY, " | |||
| lv_im_tab_prelp | TYPE P99SG_TAB_PRELP, " | |||
| lv_im_tab_user | TYPE P99SG_TAB_PRELP, " | |||
| lv_im_form | TYPE CL_HR99S00_DAQ, " | |||
| lv_im_wafor | TYPE P99SD_WAFOR, " | |||
| lv_im_tab_fodat | TYPE P99SD_TAB_FODAT. " |
|   CALL FUNCTION 'HR_99S_DAQ_FIELD_EXAMPLE' "Retrieve field values |
| EXPORTING | ||
| IM_DAQ | = lv_im_daq | |
| IM_TAB_PAY | = lv_im_tab_pay | |
| IM_TAB_TIME | = lv_im_tab_time | |
| IM_TAB_PRELP | = lv_im_tab_prelp | |
| IM_TAB_USER | = lv_im_tab_user | |
| IM_FORM | = lv_im_form | |
| IM_WAFOR | = lv_im_wafor | |
| IM_TAB_FODAT | = lv_im_tab_fodat | |
| IMPORTING | ||
| EX_TAB_VALUE | = lv_ex_tab_value | |
| EX_RETURNCODE | = lv_ex_returncode | |
| CHANGING | ||
| CH_TAB_ERROR | = lv_ch_tab_error | |
| CH_MISC | = lv_ch_misc | |
| . " HR_99S_DAQ_FIELD_EXAMPLE | ||
ABAP code using 7.40 inline data declarations to call FM HR_99S_DAQ_FIELD_EXAMPLE
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 SUBRC FROM SY INTO @DATA(ld_ex_returncode). | ||||
Search for further information about these or an SAP related objects