SAP IDOC_DATE_TIME_GET Function Module for
IDOC_DATE_TIME_GET is a standard idoc date time get 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 idoc date time get FM, simply by entering the name IDOC_DATE_TIME_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BDMT
Program Name: SAPLBDMT
Main Program: SAPLBDMT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IDOC_DATE_TIME_GET 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 'IDOC_DATE_TIME_GET'".
EXPORTING
SELECTION_DATE = "
* SOURCE_SYSTEM = "
TABLES
T_IDOCINFO = "
IMPORTING Parameters details for IDOC_DATE_TIME_GET
SELECTION_DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
SOURCE_SYSTEM -
Data type: EDIDC-SNDPRNOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_DATE_TIME_GET
T_IDOCINFO -
Data type: BDI_ZMONI1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_DATE_TIME_GET 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: | ||||
| lt_t_idocinfo | TYPE STANDARD TABLE OF BDI_ZMONI1, " | |||
| lv_selection_date | TYPE SY-DATUM, " | |||
| lv_source_system | TYPE EDIDC-SNDPRN. " |
|   CALL FUNCTION 'IDOC_DATE_TIME_GET' " |
| EXPORTING | ||
| SELECTION_DATE | = lv_selection_date | |
| SOURCE_SYSTEM | = lv_source_system | |
| TABLES | ||
| T_IDOCINFO | = lt_t_idocinfo | |
| . " IDOC_DATE_TIME_GET | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_DATE_TIME_GET
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_selection_date). | ||||
| "SELECT single SNDPRN FROM EDIDC INTO @DATA(ld_source_system). | ||||
Search for further information about these or an SAP related objects