Ansicht
Dokumentation

MPE_MIGRATE_CLSRTNG_TO_SFRTGS - Migration of Classic Routings to Version-Controlled Routings

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Purpose

You can use this report to carry out a one-time migration of your classic routings into version-controlled routings (shop floor routings), which are used in SAP S/4HANA Manufacturing for production engineering and operations.

Note: The report is not intended for migrating classic routings (created in transactions CA01 and CA02) on a continuous basis.

Integration

Prerequisites

The following prerequisites and restrictions apply:

• You cannot migrate routings that have an association to phantom BOMs.

• Shop floor routings do not support BOM explosion numbers.

• If a routing's header has been changed multiple times using multiple change numbers, the migration only considers the most recent header data when converting the routings. The migration considers different change numbers with different validity dates used to insert or delete operations.

• Inspection characteristics and PRTs are part of every version, irrespective of the change numbers used while creating the classic routing. Inspection characteristics and PRTs are only relevant while the operation to which they are assigned is valid. The migration considers different change numbers with different validity dates used to insert or delete operations.

• Quantity-dependent lead times cannot be accurately converted during migration. Material requirements planning (MRP) explodes BOMs with date effectivity using the explosion date, which is computed by subtracting the lead time from the requirement date. Quantity-dependent lead time is determined in MRP. For version-controlled BOMs and routings, MRP determines the BOM version using the requirement date only. The production version’s validity dates can be offset, but this offset is not quantity-dependent.

Features

The report searches for existing classic routings based on your selection parameters and the current system date. It migrates only classic BOMs that have not yet been migrated and creates a shop floor routing version for each change state of a classic routing. Operations in the classic routings are copied to the new routing and one operation activity is created for each operation. If texts exist for the operations, they are converted into basic work instructions for the operation activities created for the operations.

Selection

The report allows you to define the following parameters and settings:

• Selection Parameters

Here you specify for which materials you want to convert classic routings into shop floor routings. If necessary, you can specify the relevant plants, MRP controllers, and production supervisors.

• Operation Activity Settings

Here you can make the following settings for the operation activities to be created in the new shop floor routings:

• Select the status and action schema (SAS) to be assigned to the operation activity created for each operation.

• Select the SAS to be assigned if the routing is for a serialized product.

• Enter the ID to be assigned to the operation activity generated for each operation.

• Select Min Routing Quantity under Lot Size for Lead Time if you want to achieve the same BOM explosion result as for a date-effective BOM that is exploded using the order start date. The BOM explosion result is the same only if the order quantity = minimum routing quantity = lot size from.

• Specify the control key to be assigned to subcontracting operations in the new shop floor routing.

• Select whether you want flexible processing to be enabled in the new shop floor routing.

• Production Version Settings

Here you can specify the lock status to be assigned to each production version.

• Execution Mode

Here you have the following options:

• Interactive Mode

Select this option if you want the report to display a list of classic routings to be migrated based on your parameters and settings and allow you to either abort or proceed with the migration.

• Automated Mode

Select this option if you want to execute the BOM migration in the background without any further user input.

Standard Variants

Output

The output is determined by the execution mode:

• Interactive mode: The report outputs a table of routings along with their change states (date effectivity). You also see a table listing materials with invalid routings. To migrate the routings, select all or selected rows in the table and choose Migrate_Routings. The result of the migration is shown in one or more messages.

• Automated mode: The report executes the migration in the background. The result of the migration is then shown in one or more messages

Activities

Example

ROGBILLS - Synchronize billing plans   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 6118 Date: 20240531 Time: 144148     sap01-206 ( 128 ms )