SAP HR_BE_DI_XML_CALLBACK_DATE Function Module for Register XML conversion callback for Date format
HR_BE_DI_XML_CALLBACK_DATE is a standard hr be di xml callback 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 Register XML conversion callback for Date format 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 be di xml callback date FM, simply by entering the name HR_BE_DI_XML_CALLBACK_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPAYBE_DAQ_DI
Program Name: SAPLHRPAYBE_DAQ_DI
Main Program: SAPLHRPAYBE_DAQ_DI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_BE_DI_XML_CALLBACK_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_BE_DI_XML_CALLBACK_DATE'"Register XML conversion callback for Date format.
EXPORTING
IM_XML_DAQ = "CL_HR99S00_XML_DAQ
* IM_TAB_FIELDS = "
IMPORTING Parameters details for HR_BE_DI_XML_CALLBACK_DATE
IM_XML_DAQ - CL_HR99S00_XML_DAQ
Data type: CL_HR99S00_XML_DAQOptional: No
Call by Reference: Yes
IM_TAB_FIELDS -
Data type: P99SD_TAB_OBLIGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for HR_BE_DI_XML_CALLBACK_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_im_xml_daq | TYPE CL_HR99S00_XML_DAQ, " | |||
| lv_im_tab_fields | TYPE P99SD_TAB_OBLIG. " |
|   CALL FUNCTION 'HR_BE_DI_XML_CALLBACK_DATE' "Register XML conversion callback for Date format |
| EXPORTING | ||
| IM_XML_DAQ | = lv_im_xml_daq | |
| IM_TAB_FIELDS | = lv_im_tab_fields | |
| . " HR_BE_DI_XML_CALLBACK_DATE | ||
ABAP code using 7.40 inline data declarations to call FM HR_BE_DI_XML_CALLBACK_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