Ansicht
Dokumentation

/PLMI/RMSL_MIGRATION - Labeling - Migrate Label Sets

/PLMI/RMSL_MIGRATION - Labeling - Migrate Label Sets

Vendor Master (General Section)   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

With this report, you can migrate existing data of Labeling (PLM-RM-LBL) to Labeling in PLM Web-UI (PLM-WUI-RCP-LBL).

The migration provides the following functionality:

  • Selection of label sets to be migrated
  • Tracking of the migration process by a migration status
  • Tracking of migrated objects
  • Radio button Use Data of Key Date:
    Migration of label set data valid at a given key date. One label set is created.
  • Radio button Create One Label Set Version:
    Migration of current and future change states of the label set:
  • For the current date, a new label set alternative is created.

  • In case that the label set has change state in the future, a new label set version to the label set alternative is created.

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 label set is done. If the migration is successful, the migration administration record receives the status >Migrated.
  • Status Migrated
The label set has been successfully migrated and the migration process is finished. The name of the created label set is displayed in the migration administration record.
  • Status Rejected
The migration of a label set can be rejected by using the status Rejected. Only migration administration records with the status Start 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.

Steps Overview

You have to carry out the following steps to migrate a label set:

  • Load migration administration record.
This step is only carried out once before you start the migration for the label set you want to migrate. The migration administration records are stored in the mapping table.
  • Start migration.
Status Start is changed to status Migrated.
Note
On the entry screen of transaction /PLMI/RMSL_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 label set data. The data can still be displayed in Labeling Application but it is locked against changes.

Authorization

The usage of the migration functionality is controlled by the authorization object PLM_LBLMIG 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/LBL_MIG and ALG_SUBOBJ = LABEL and ACTVT = 03.

Prerequisites

If the data origin of a label set is a recipe or an independent formula of Recipe Management, then the recipe or independent formula has to be migrated first (transaction /PLMI/RCP_MIGRATION).

Implement BAdI /PLMI/EX_LBL_MIGRATION to determine label key. In Standard BAdI implementation /PLMI/CL_IM_MIGRATION_WUI is provided.

Implement BAdI RMSL_MIGRATION to determine new data origin and status. In Standard BAdI implementation /PLMI/CL_IM_MIGRATION is provided.

Features

Selection

Standard Variants

Output

Activities

All label sets 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 label sets 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.

You can start with the migration now.

  1. On the initial screen, enter the label sets that are included in the mapping table.
  2. Select the checkbox 'Use Status' and choose the migration status 'Start'.
This status determines that the migration is done.
  1. Select the other relevant settings.
  • You can determine the way in which the change states of a label set is migrated.

  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 migration, a pop-up appears that the migration job has been started. The migration of these objects is done by background jobs. If the migration was successful, the objects receive the status 'Migrated' and disappear from the list.
In case of an error, label set 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.

Example






Vendor Master (General Section)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 7163 Date: 20240329 Time: 100657     sap01-206 ( 88 ms )