Ansicht
Dokumentation

PPREM_XPRA_NO_RSH - PPREM_XPRA_no_rsh

PERFORM Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Title

Conversion of Run Schedule Headers and Dependent Objects

Purpose

This XPRA is necessary if you use Repetitive Manufacturing with run schedule headers.

Thse use of run schedule headers is no longer necessary from Release 4.6A. The production version is replacing the run schedule header as the central object in repetitive manufacturing. The run schedule header was an object mainly containing data from the production version.

Integration

Also affected by this XPRA are the areas CO-PC and QM as these areas contain objects that depend on the run schedule header. These objects (inspection lots, physical-sample drawings and reporting points) have to be converted when a run schedule header is replaced by the corresponding production version.

Prerequisites

Run schedule headers are not allowed to overlap otherwise the XPRA will not function correctly. This was still possible in Release 2.2. Overlapping run schedule headers generally cause inconsistencies. You have to deal with this before starting the XPRA.

The run schedule header valid on the day of the put is the authoratitive object. Its reporting points are converted. If no valid run schedule header currently exists, you must recalculate the product cost collector after the put so that the respective reporting points are created.

Features

Exactly one run schedule header is converted. The corresponding production version takes its place. Run schedule headers lying in the past are not taken into consideration. You can also continue to execute postings for them as long as they are not completed. You have to execute a special procedure for run schedule headers that lie in the future - especially if they were already posted (please refer to the examples at the end of this documentation).

Activities

1. A current, valid run schedule header exists at the time of the put. This run schedule header is the authoratitive object. It is replaced by the corresponding production version. Any existing reporting point files, inspection lots and physical-sample drawings are converted so that they refer to the production version. The link between the original run schedule header is lost.
2. Run schedule headers that lie completely in the past at the time of the put are not taken into account by the XPRA. As long as they are not yet completed, you can continue posting to these run schedule headers. You can no longer change the run schedule headers. You can only set the deletion indictor.
3. Run schedule headers that lie in the future at the time of the put are not taken into account by the XPRA. THe XPRA log contains appropriate messages on how to deal with these run schedule headers. If these run schedule headers have already been posted you will have to reprocess them.

Example

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3035 Date: 20240531 Time: 114326     sap01-206 ( 78 ms )