FAQ: Migration Recipe Management to Recipe Development
Can the recipes or independent formulas be migrated without primary outputs?
This is not possible. The name of the specification of the primary output is the key of the Recipe Development recipe, which is why without this name no recipes can be created.
With a change state the primary output has been changed. How can this recipe be migrated?
To migrate this recipe "Use Data of Key Date" option can be used.
During the migration, a different component type needs to be used. The recipe type will be specified differently. The recipe key should be specified differently. The recipe status or user status should be assigned differently. What can be done?
The BAdI /PLMI/EX_RCP_MIG_VISITOR_OBJ should be implemented. the default implementation can be copied here and the ABAP code can be adjusted accordingly.
A different assignment of recipe structures is required. The parts of the recipe should not be migrated. What can be done? How can the migration be adjusted individually?
The BAdI /PLMI/EX_RCP_MIG_VISITOR should be implemented. The implementation that is provided in the standard system can be copied and adjusted. To set the BAdI filter value accordingly and to use the implementation the method DETERMINE_FILTER of the BAdI /PLMI/EX_RCP_MIG_VISITOR_OBJ should be used during the migration.
- For the migration own implementation should be created and if an error occurs the migration should be stopped. How can this be done? How to the application log the messages can be written?
Within the migration use the class-based exceptions. Trigger an exception using the class /PLMI/CX_RCP_MIG_VISITOR if an error occurs to stop the migration of a recipe. To the value /PLMI/CX_RCP_MIG_VISITOR=>ERROR_CUSTOMER_IMPLEMENTATION the parameter TEXTID should be set. To add exceptions from customer-specific exception classes the parameter PREVIOUS can be used. Note that this option will be provided to all methods of the BAdI interface.
The statistical method ADD of the class /PLMI/CL_RCP_MIG_APP_LOG can be used if you just want to write information to the application log and do not stop the migration.
How can the migration status of a recipe be determined?
The name of the recipe in transaction /n/PLMI/RCPMIGRATION should be entered and the indicator "Use Status" should be deselected. After execution all of the migration administration records for the recipe should be the displayed by the system.
How from starting immediately the migration job can be prevented?
The parameter ID /PLMI/RCP_MIG_JOB_EX to the value "X" should be set.
Start and process the jobs however, before the migration the program is left. The jobs can be scheduled again; set the parameter ID /PLMI/RCP_MIG_JOB_EX to the value " (that is, empty) here.
What independent formulas or the maximum number of recipes for each job can be processed?
For each job the maximum number of steps is limited to 10 and the maximum number of recipes or independent formulas is limited to 100 for each step. It is not possible to adjust these two values.
What amount of time is taken by the migration of a recipe?
One cannot give a definite answer to this question. The option "Create One Recipe Version" is of importance as stated by both the size of the recipe and the number of change states. A typical recipe can be migrated in a development system to determine the amount of time roughly. In the development system the contents of the table /PLMI/RCP_MIGRAT should be deleted at which point the migration is reset if for one recipe you want to do this several times. The created Recipe Development recipe cannot be deleted manually.
The method SKIP_PAST_CHANGE_STATES of the BAdI /PLMI/IF_RCP_MIG_VISITOR_OBJ should be used to ensure that on the day of the migration only the change states that are valid and migrate all of the future change states. In this case, from the past for the migration of change states the time used is distributed with.
- The recipe has been loaded to the mapping table and in the table one is trying to find it again. However, a message is issued by the system when this is done which informs that in the mapping table no entry was found. How can the entry be viewed?
Set the "Use Status" checkbox so that only the entries are selected that have the relevant recipe migration status. In addition, during the migration this distinguishes whether a key date has been used.
This restriction is not taken into account for the selection if the "Use Status" checkbox is not selected, and regardless of the status of the recipe the mapping table entry is found.
- If the option "Create One Recipe Version" is used and change states are there in the recipe, during the migration where can the change documents created be viewed?
In Recipe Development currently, no such option exists to display the change documents. RSSCD100 is the only generic report.
In Recipe Development for a recipe, during the migration how it was created can be recognized?
Within the recipe in Recipe Development no field exists that refers to a migration in the user interface. The name of the user can be viewed who only in the administration data for the recipe executed the migration.
The name of the Recipe Management recipe should be added in the short text of the Recipe Development recipe during the migration if a reference for the recipe is required for example. The ABAP code of the BAdI should be adjusted to do this.