SAP FDC_TIMER_DAEMON_CLEAN_UP Function Module for Timer daemon: clean up
FDC_TIMER_DAEMON_CLEAN_UP is a standard fdc timer daemon clean up SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Timer daemon: clean up 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 fdc timer daemon clean up FM, simply by entering the name FDC_TIMER_DAEMON_CLEAN_UP into the relevant SAP transaction such as SE37 or SE38.
Function Group: FDC_TIMER_DAEMON
Program Name: SAPLFDC_TIMER_DAEMON
Main Program: SAPLFDC_TIMER_DAEMON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FDC_TIMER_DAEMON_CLEAN_UP 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 'FDC_TIMER_DAEMON_CLEAN_UP'"Timer daemon: clean up.
EXPORTING
* IV_DO_HELD_DOC_CLEAN_UP = "Single-Character Flag
* IV_RETENTION_FOR_HELD_DOC = "Retention Period ifor held Documents in Days
IMPORTING Parameters details for FDC_TIMER_DAEMON_CLEAN_UP
IV_DO_HELD_DOC_CLEAN_UP - Single-Character Flag
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_RETENTION_FOR_HELD_DOC - Retention Period ifor held Documents in Days
Data type: FDC_RETENTION_DAYSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FDC_TIMER_DAEMON_CLEAN_UP 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_iv_do_held_doc_clean_up | TYPE FLAG, " | |||
| lv_iv_retention_for_held_doc | TYPE FDC_RETENTION_DAYS. " |
|   CALL FUNCTION 'FDC_TIMER_DAEMON_CLEAN_UP' "Timer daemon: clean up |
| EXPORTING | ||
| IV_DO_HELD_DOC_CLEAN_UP | = lv_iv_do_held_doc_clean_up | |
| IV_RETENTION_FOR_HELD_DOC | = lv_iv_retention_for_held_doc | |
| . " FDC_TIMER_DAEMON_CLEAN_UP | ||
ABAP code using 7.40 inline data declarations to call FM FDC_TIMER_DAEMON_CLEAN_UP
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