Ansicht
Dokumentation

RMPE_MIGRATE_UNITIZED_ROUTING - Migration of Classic Routings to Unitized Version-Controlled Routings

RMPE_MIGRATE_UNITIZED_ROUTING - Migration of Classic Routings to Unitized Version-Controlled Routings

CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

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

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

Integration

Prerequisites

You have migrated your classic BOMs for unitized materials into unitized version-controlled BOMs.

Features

The report searches for existing classic routings for unitized materials based on your selection criteria and the current system date. It selects only those classic routings that have not yet been migrated. 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. Before performing the migration, the report prompts you to enter the parameter effectivity for the version-controlled routings.

Selection

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

  • Selection Parameters
Here you specify for which unitized materials you want to convert classic routings into unitized version-controlled 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.

  • 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.

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

  • 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 routing migration in the background without any further user input.

Standard Variants

Output

The report determines the overall effectivity of the BOM associated with the classic routing (which corresponds to the combined effectivity of all BOM components), and adopts this as the overall effectivity in the unitized version-controlled routing.

If there are no components assigned to an operation in the classic routing, the operation and the operation activity in the unitized version-controlled routing inherit the header effectivity from the migrated BOM associated with the classic routing.

If one or more components are assigned to an operation in the classic routing, the combined effectivity of all assigned components is assigned to the operation and operation activity in the unitized shop floor routing.

The unitized version-controlled routing is created in status In Process, which means that it can still be modified (for example, the effectivity can be adjusted). However, this can result in consistency issues, which then need to be checked and resolved.

Activities

Example






Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4929 Date: 20240531 Time: 194207     sap01-206 ( 90 ms )