SAP DD_DYSTAMP_TOUCH Function Module for DD: Update screen time stamp of a set of tables
DD_DYSTAMP_TOUCH is a standard dd dystamp touch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DD: Update screen time stamp of a set of tables 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 dd dystamp touch FM, simply by entering the name DD_DYSTAMP_TOUCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDAD
Program Name: SAPLSDAD
Main Program: SAPLSDAD
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DD_DYSTAMP_TOUCH 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 'DD_DYSTAMP_TOUCH'"DD: Update screen time stamp of a set of tables.
EXPORTING
* OFF = 0 "
* LEN = 0 "
* STATE = 'A' "
* PRID = 0 "
* TOUCH_DATE = SY-DATUM "
* TOUCH_TIME = SY-UZEIT "
IMPORTING
READ_ERRORS = "
WRITE_ERRORS = "
UPDATES = "
TABLES
NAMES_TAB = "
EXCEPTIONS
ILLEGAL_VALUE = 1
IMPORTING Parameters details for DD_DYSTAMP_TOUCH
OFF -
Data type: SY-FDPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
LEN -
Data type: SY-FDPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
STATE -
Data type: DDXTT-MODEFLAGDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PRID -
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
TOUCH_DATE -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
TOUCH_TIME -
Data type: SY-UZEITDefault: SY-UZEIT
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_DYSTAMP_TOUCH
READ_ERRORS -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
WRITE_ERRORS -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
UPDATES -
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DD_DYSTAMP_TOUCH
NAMES_TAB -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_DYSTAMP_TOUCH 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_off | TYPE SY-FDPOS, " 0 | |||
| lt_names_tab | TYPE STANDARD TABLE OF SY, " | |||
| lv_read_errors | TYPE SY-TABIX, " | |||
| lv_illegal_value | TYPE SY, " | |||
| lv_len | TYPE SY-FDPOS, " 0 | |||
| lv_write_errors | TYPE SY-TABIX, " | |||
| lv_state | TYPE DDXTT-MODEFLAG, " 'A' | |||
| lv_updates | TYPE SY-TABIX, " | |||
| lv_prid | TYPE SY-TABIX, " 0 | |||
| lv_touch_date | TYPE SY-DATUM, " SY-DATUM | |||
| lv_touch_time | TYPE SY-UZEIT. " SY-UZEIT |
|   CALL FUNCTION 'DD_DYSTAMP_TOUCH' "DD: Update screen time stamp of a set of tables |
| EXPORTING | ||
| OFF | = lv_off | |
| LEN | = lv_len | |
| STATE | = lv_state | |
| PRID | = lv_prid | |
| TOUCH_DATE | = lv_touch_date | |
| TOUCH_TIME | = lv_touch_time | |
| IMPORTING | ||
| READ_ERRORS | = lv_read_errors | |
| WRITE_ERRORS | = lv_write_errors | |
| UPDATES | = lv_updates | |
| TABLES | ||
| NAMES_TAB | = lt_names_tab | |
| EXCEPTIONS | ||
| ILLEGAL_VALUE = 1 | ||
| . " DD_DYSTAMP_TOUCH | ||
ABAP code using 7.40 inline data declarations to call FM DD_DYSTAMP_TOUCH
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 FDPOS FROM SY INTO @DATA(ld_off). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_read_errors). | ||||
| "SELECT single FDPOS FROM SY INTO @DATA(ld_len). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_write_errors). | ||||
| "SELECT single MODEFLAG FROM DDXTT INTO @DATA(ld_state). | ||||
| DATA(ld_state) | = 'A'. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_updates). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_prid). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_touch_date). | ||||
| DATA(ld_touch_date) | = SY-DATUM. | |||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_touch_time). | ||||
| DATA(ld_touch_time) | = SY-UZEIT. | |||
Search for further information about these or an SAP related objects