Ansicht
Dokumentation

Abolishing the Run Schedule Header ( RELNPP_REM_46A_SA )

PERFORM Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Abolishing the Run Schedule Header

Scope of Functions

In earlier releases, you had to create a run schedule header for make-to-stock REM. The run schedule header contained outline data for repetitive manufacturing, such as the product cost collector and the production versions. This, however, was only necessary for make-to-stock REM and not for either make-to-order REM or production by lots. In order to make the processes in repetitive manufacturing more consistent, the run schedule header has been completely abolished. In future, for all production types, you only have to create the production version (that is, basic data, BOM data and planned data) and the product cost collector.

The abolishion of the run schedule header reduces the amount of master data you have to maintain for repetitive manufacturing. You can now maintain the production version using the function production version: mass maintenance (transaction C223). Previously you had to maintain the production version in the material master record.

The indicator RS header allowed which you previously had to set when creating a production version has been renamed and is now called REM allowed. This indicator validates the poduction version for repetitive manufacturing.

Previously when creating run schedule headers, the system automatically created an inspection lot. In future, you can create the inspection lot for the production version using function processing inspection lots (transaction MFPR).

Effects on Existing Data

Effects on Data Transfer

If you only work with one valid run schedule header, you should not have any processing or conversion problems.

No run schedule header is deleted. There are three different scenarios for the conversion of the run schedule headers:

1. A run schedule header that is still valid at the time of the release change is automatically replaced by the appropriate production version. This can be carried out with no extra effort as a run schedule header always belongs to one production version only. Any existing reporting point files, inspection lots and sample drawings refer in future to the production version. The original run schedule header is not deleted but has no further function in repetitive manufacturung.
2. A run schedule header that is no longer valid at the time of the release change remains in the system. If the run schedule header is not yet completed (that is, if it has not yet been settled by Controlling), you can still post data to it. However, you can no longer change the run schedule header. It is only possible to set the deletion indicator in function Change RS header (transaction MF02).
3. A run schedule header that lies completely in the future at the time of the release change cannot be dealt with automatically by the system. Therefore, you have to manually process these run schedule headers.

Effects on System Administration

Effects on Customizing

The function for making the run schedule header either visible or invisible for backflushing no longer exists.

You no longer have to maintain a number range for the run schedule header.

Further Information

BAL Application Log Documentation   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 3545 Date: 20240523 Time: 042618     sap01-206 ( 82 ms )