Ansicht
Dokumentation
V_NSDM_MDOC_DA_C - Define Data Aging for Material Documents
ROGBILLS - Synchronize billing plans BAL Application Log DocumentationThis documentation is copyright by SAP AG.
In this customizing activity, you define the residence time in days and per plant for material documents in current data.
You can define the residence time for a specific plant or, by using the wildcard *, for all plants. If more than one entry applies for the same plant, the system always uses the most exact entry. The residence time must at least be 1 day.
Only complete material documents are moved to historical data. If material document items refer to different plants 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 material documents, but not as fast as before. Once material documents have been moved to the historical data you can still display them in display transactions (such as MIGO) and in the document flow.
When you change the residence time, this has no immediate effect on the material documents 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 material documents to historical data.
- If you increase the residence time, the next data aging run will not move material documents 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 material documents will never be aged from the current and the previous posting period.
If no residence time is maintained at all a default residence time of 731 days (2 years) is assumed. If residence times are maintained for specific plants only, material documents referring to plants for that no residence time has been maintained will not be aged.
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 2171 Date: 20240523 Time: 212952 sap01-206 ( 62 ms )
