Ansicht
Dokumentation

LIKP_DA - Define Data Aging for Deliveries

ROGBILLS - Synchronize billing plans   General Data in Customer Master  
This documentation is copyright by SAP AG.

The data aging run carries out implicit checks for deliveries, regardless of the settings defined in Customizing.

In this Customizing activity, you define the additional criteria (which the system determines) according to which deliveries will be included in a data aging run.

These differentiating checks ensure that deliveries are only moved to the historical area during the phase of the process that you want them to be moved.

Processing Options After Data Aging Run

Once deliveries have been moved to the historical area as a result of a data aging run, you can still display them in the display transactions (such as VL03N), and in the document flow.

You can no longer edit these documents in the change transactions (such as VL02N), nor can you use them as references for creating new documents, and they are no longer available in the input help.

The checks for the deliveries take place in combination with the following data:

• Sales Organization

• Delivery Category

• Delivery Type

All entries are linked with AND for the search. You can enter each value with an asterisk (*), or you can enter a fixed value.

Deliveries are subject to the following mandatory and optional checks:

• Residence Time (Days) (mandatory)

• Check Change Date (optional)

• Check Date of Successor Document (optional)

• Check Accounts (optional)

• Do not check Transportation Planning (optional)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 1839 Date: 20240523 Time: 202645     sap01-206 ( 29 ms )