Ansicht
Dokumentation
V_OIJ_TKT_DAAG - Define Data Aging
BAL_S_LOG - Application Log: Log header data BAL Application Log DocumentationThis documentation is copyright by SAP AG.
In this customizing activity, you define the residence time in days and per company code for tickets in current data.
You can define the residence time for a specific company code or, by using the wildcard *, for all company codes. If more than one entry applies for the same company code, the system always uses the most exact entry. The residence time must at least be 1 day.
Only complete tickets are moved to historical data. If ticket items refer to different company codes with different residence times, the longest residence time is valid for all items of this document.
During the data aging run the system moves the current data to historical data. You have still access to the historical tickets, but not as fast as before. Once tickets have been moved to the historical data you can still display them in display transactions (such as O4TGN) and in the document flow.
When you change the residence time, this has no immediate effect on the tickets in current data and in historical data. Changes in the residence time have no effect until the next data aging run:
- If you decrease the residence time, the next data aging run will move the corresponding tickets to historical data.
If you increase the residence time, the next data aging run will not move tickets back to current data. This happens even if according to the new setting these would not have been aged. You have to initiate an undo data aging run instead.
Independent from the maintained residence time tickets will never be aged automatically.
General Material Data PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 1787 Date: 20240523 Time: 200831 sap01-206 ( 41 ms )
