SAP® Documentation

Single view

/PLMI/RCP_MIGRATION - Recipe Development - Migrate Formula and Recipe

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

Purpose

With this report, you can migrate existing data of Recipe Management (PLM-RM) to Recipe Development (PLM-WUI-RCP).

The migration provides the following functionality:

  • Selection of recipes/formulas to be migrated
  • Tracking of the migration process by a migration status
  • Simulation mode that allows you to check whether migration is possible
  • Restart of migration process
  • Tracking of migrated objects

The structure of a recipe in Recipe Management is different than the structure of a recipe in Recipe Development, hence a direct mapping of structural elements is not feasible. Moreover, Recipe Development does not provide the functionality of independent formulas and therefore independent formulas of Recipe Management are copied into recipes in Recipe Development.

Independent formulas or recipes of Recipe Management can be changed by using Engineering Change Management (ECM). This report provides two alternative options, as follows:

  • Radio button Use Data of Key Date:
    Migration of recipe/formula data valid at a given key date. One recipe is created.
  • Radio button Create One Recipe Version:
    Migration of all change states of the recipe/formula:
  • In case that a change state is in the past, one recipe alternative is created with the change number valid on the day of the migration. The data of the change states of the past are written into this recipe and changes are documented by change documents.

  • In case that the change state is in the future, a new recipe version is created.

Note
If you copy the change states, the data is read for each change state. In addition, change documents might be created. This influences the time needed to migrate a recipe object.
If you want to skip migration of past change states, you can use method SKIP_PAST_CHANGE_STATES of BAdI /PLMI/EX_RCP_MIG_VISITOR_OBJ.

Migration Process

The migration process is controlled by the status of the migration administration record. The following statuses exist:

  • Status Start
This is the start status of the migration process. With the run of the migration report, the migration of the recipe or formula is simulated. If the simulation is successful, the migration administration record receives the status Simulated.
  • Status Simulated
A simulated migration can be migrated. The migration changes to status Migrated.
  • Status Migrated
The recipe or formula has been successfully migrated and the migration process is finished. The name of the created recipe is displayed in the migration administration record.
  • Status Rejected
The migration of a recipe or formula can be rejected by using the status Rejected. Only migration administration records with the status Start or Simulated can be rejected. Status Rejected can only be changed to status Start, in other words, the migration process has to be started from the beginning.
  • Status Skipped
The migration of a change state has been skipped by the system. Status Skipped can only be set by the program.

Steps Overview

You have to carry out the following steps to migrate a recipe or formula:

  • Load migration administration record.
This step is only carried out once before you start the migration for the recipes or formulas you want to migrate. The migration administration records are stored in the mapping table.
  • Start the migration process by simulating the migration.
Simulation is possible for all records with status Start. After simulation, the status Start is converted to status Simulated.
  • Start migration.
Status Simulated is changed to status Migrated.
Note
On the entry screen of transaction /PLMI/RCP_MIGRATION you can select migration administration records according to the status (Use Statuscheckbox). You can only carry out the different migration steps if the migration administration records are selected by the status.
If you want to search for a specific migration administration record, do not select the checkbox. In this case, the migration administration record is selected independent of the status.

Integration

The migration will not change or delete the data of classic Recipe Management. The data can still be displayed in the Recipe Management Workbench but it is locked against changes.

Prerequisites

Mapping of specification type to recipe type

You mapped the types of recipes and independent formulas in Recipe Management to the recipe type in Recipe Development using view cluster /PLMI/VC_RCP_MIG. Call the view cluster with transaction SM34 (View Cluster Maintenance).

Note
You can influence the mapping by implementation of enhancement spot /PLMI/ES_RCP_MIG_VISITOR_OBJ(method DETERMINE_RECIPE_TYPE).

Activating change documents

If you migrate change states, you have to activate change documents in Customizing, under Production Planning for Process Industries -> Master Data -> Recipe Management -> Recipe -> Recipe Settings. Change states that refer to the future are copied into new versions.

Setting up application log customizing

Application log customizing for migration is set up (object /PLMI/RCP_MIG 'Recipe Migration to WebUI' and subobject RCP 'Recipe').

Activating object type in change number

If you use change number for migration, the change number has to be valid for object type 'PLM4PI: Recipe Management'.

Migrating process parameters

If you use process parameters you have to migrate the master data of the process parameters first using report /PLMI/RCP_MIGRATION_PPM. The report creates the process parameter master data in Recipe Development using the names of the master data in Recipe Management. Messages are recorded in the application log (object /PLMI/RCP_MIG, subobject PPM).

Migrating the classification of recipes

If you have classified recipes in Recipe Management, you have to create the corresponding classes with class type 104 before starting the migration. You copy the Recipe Management class with class type 053 with the same name and the same characteristics.

Authorization

The usage of the migration functionality is controlled by the authorization object PLM_RCPMIG with activities 03 for display of Migration Administration Records and activity 16 for execution of migration (roles). In addition, the usual authorizations for RM are required. To access the application log, you need authorization object S_APPL_LOG with ALG_OBJECT = /PLMI/RCP_MIG and ALG_SUBOBJ = RCP and ACTVT = 03.


Features

The mapping of Recipe Management to Recipe Development data is implemented by the BAdI implementations /PLMI/IM_EX_RCPMIG_VISITOR_FRML (source: independent formula) and /PLMI/IM_EX_RCPMIG_VISITOR_RECIPE (source: recipe) in enhancement spot /PLMI/ES_RCP_MIG_VISITOR. The BAdI implementations are selected by a filter. The value of the filter is provided by method DETERMINE_FILTER of BAdI implementation /PLMI/IM_EX_RCPMIG_VISITOR_OBJ in enhancement spot /PLMI/ES_RCP_MIG_VISITOR_OBJ.

During the migration of data from Recipe Management to Recipe Development, the data is locked in both systems. You can use BAdI RMS_MIG_INTEGRATION for checking the data in Recipe Management and PLMB/RCP_CHECK_MIGRAT_FINISH for checking the data in Recipe Development.

Selection

Standard Variants

Output

Activities

All recipes or formulas you want to migrate have to be included in the mapping table first.

  1. On the initial screen, choose Load Mapping Table.
  2. Select the recipes or formulas you want to migrate.
  3. Choose Execute.
You see the mapping table with all selected objects.
You can deselect objects you do not want to migrate.
  1. Save the mapping table and return to the initial screen.

Before you can start with the migration, you first have to perform a simulation.

  1. On the initial screen, enter the recipes or formulas that are included in the mapping table.
  2. Set indicator 'Use Status' and choose the migration status 'Start'.
This status determines that the migration first has to be simulated before the objects can be migrated.
  1. Select the other relevant settings.
  • You can determine the way in which the change states of a recipe are migrated.

  • You can determine which views you want to migrate.

NOTE:
The Formula Options are only displayed when seperate formula views are used in the classic Recipe Management.
  1. Choose Execute.
On the screen that follows, you see the mapping table with the selected objects.
  1. Choose Simulate Migration.
You can also prevent objects from simulation or migration, by changing their status to 'Rejected'.
When you start the simulation or migration, a pop-up appears that the migration job has been started. The migration of these objects is simulated by background jobs. If the simulation of the migration was successful, the objects receive the status 'Simulated' and disappear from the list.
In case of an error, related objects cannot be migrated. The 'Error' column in the mapping table is marked for the object. The error can be solved by using the application log.

If the simulation was successful, the recipe or formula receives the status 'Simulated' and can then be migrated.

The versions and alternatives displayed in the mapping table after simulation are only preliminary and can change after migration.

  1. Select the objects with status 'Simulated' and choose Execute.
On the screen that follows, you see the mapping table with the selected objects.
  1. Choose Execute Migration.
You can also prevent objects from migration, by changing their status to 'Rejected'.
When you start the migration, a pop-up appears that the migration job has been started. These objects are migrated by background jobs. If the migration was successful, the objects receive the status 'Migrated' and disappear from the list.
In case of an error, related objects cannot be migrated. The 'Error' column in the mapping table will be marked for the object. The error can be solved by using the application log.

Example






PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 13851 Date: 20191206 Time: 191634     sap01-206 ( 53 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.