Ansicht
Dokumentation

FRE_OP_PO_KEY_REORG - Deletion of Completed Records From Key Table for Purchase Orders

BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Purpose

This program reorganizes table FRE_OP_PO_KEY in which key information on the order items transferred to SAP F&R and, in some cases, the SAP F&R order proposal numbers are saved.

With SAP Note 898932, the logic of deletion of completed records has been changed. Before this note, completed records were deleted immediately from the table. As of SAP Note 898932 the completed records receive a "completed date". This became necessary as a result of problems when resending order proposals from SAP F&R. By means of the "completed date", incoming records from SAP F&R can be checked to see if these order proposals have already been created, processed and completed as purchase orders (for details, see SAP Note 898932).

This report deletes records where the completed-date lies before the end of a latency period calculated in days from the current date. The latency period can be defined by the user. The user may not set the latency period to "zero". This guarantees that the functionality for checking inbound order proposals from SAP F&R is enabled for at least one day. The default value for the latency period is seven days.

A check can also be made if the order item is still relevant to SAP F&R at all. This check is only carried out for data records whose "completed date" has not yet been set. Records that are no longer relevant are also deleted.

Since, under certain circumstances, there can be a large number of records whose "completed date" has not yet been set , there is a facility to restrict processing by selection of single or multiple sites, or a range of sites. This way, you can reduce the run time. However, in this case, you must restart the program several times.

The program can be started or scheduled online. In both cases the numberof deleted records, and any problems with deletion, are output in the user interface (transaction FRE_UI; interface "OU"). If the program is scheduled for background processing, then the protocol information is also transferred to the job log. Single record documentation does not occur.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 2485 Date: 20240531 Time: 233924     sap01-206 ( 67 ms )