Clean up data
Use this function to delete the files and buffer table entries generated by the asynchronous Data Requests. This is useful when Data Requests are cancelled or the files are no longer required and are occupying memory space.
The file log will be updated by a deletion stamp.
You can call this function via the /AUDIC/SE_CLEAN transaction.
The following selection screen is displayed:
Figure: Selection screen of /AUDIC/SE_CLEAN
| Selections | |
|---|---|
|
Request ID |
Specifies the Request ID of the Data Request to be deleted, Match code search using F4. |
|
Requested by |
SmartExporter Windows user who ran the request (Data Request) |
|
SAP User |
SAP® user who ran the request (Data Request) |
|
Created on |
Date on which the request (Data Request) was created The program presets a date that is less than or equal to the current date - 7. This means that all files older than 7 days will be deleted. |
|
Time created |
Creation time of the request (Data Request) |
|
Comment |
Comment which was passed on when the request (Data Request) was run |
|
Mode |
Mode of the Data Request to be deleted The only ones making sense here are: A = asynchronous B = buffer table method As the data is only generated here on the SAP® system. By default S (= synchronous) and C (= count mode (table size)) cannot be selected. |
|
Test run |
There will only be a test run. No files will be deleted. An overview of the Data Requests and the data to be deleted is displayed. |
| Older than ... days | Only executed runs that are older than n days will be considered |
| Newer than ... days | To reduce the runtime only executed runs younger than n days will be considered. |
Table: Parameters of /AUDIC/SE_CLEAN
The request overview marks files as „deleted“.
The /AUDIC/SE_CLEAN transaction can be run regularly as a background job to delete both the requested files in the export directory and the content of the buffer table from the cancelled Data Requests. In the background all files older than 7 days will be deleted automatically. Please note that for the background job a variant (e.g. CUS&_BATCH) has to be used that is not marked as test run.