Kontakt

Ansicht
Dokumentation

V_EKKO_DAAG_CUST - Define Residence Times for Purchase Orders

V_EKKO_DAAG_CUST - Define Residence Times for Purchase Orders

TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Define Residence Times for Purchase Orders

The data aging run carries out implicit checks for purchase orders which are based on the pre-processing report RM06EV70 for archiving object MM_EKKO. Only purchase orders are considered in the data aging runs.

In this implementation activity, you define the additional criteria according to which purchase orders are included in a data aging run.

If the implementation activity is not maintained, the data aging run selects all purchase orders with a default residence time of 1096 days.

The system selects purchase orders relevant for data aging based on business rules and on the residence time. The document selection is done in three steps, checking the following date fields:

  1. Last date (either EKKO-BEDAT or EKKO-AEDAT)
  2. Purchase order item change date (EKPO-AEDAT)
  3. Day on which the last follow-on document was entered (EKBE-CPUDT or EKBZ-CPUDT)

Note:

Once purchase orders have been moved to the historical area as a result of a data aging run, you can only display them in transaction ME23N and in the document flow.

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

You can customize the residence time for purchase orders based on the following entries:

  • Purchasing organization
  • Purchasing group
  • Company code
  • Purchasing document category only ‘F’ (Purchase order)
  • Order type

All entries are linked with AND. You can use wildcards or choose a value using value help.

The entry in the residence time field controls the data selection of purchase orders. The minimum residence time is one day. If a purchase order has passed all checks, the ISAGED field in the header table EKKO is set to "X" by the system.

The header data of a purchase order is kept in the current area. All other data linked to the purchase order, which is included in the data aging object MM_EKKO, is moved to the historical area by the system.






BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 2458 Date: 20240523 Time: 202212     sap01-206 ( 50 ms )