LOV Full Migration is not working correctly with seed migration priority set to Source
(Doc ID 2745393.1)
Last updated on MAY 16, 2023
Applies to:
Siebel CRM - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
Hierarchical LOVs are not migrated correctly through Siebel Migration Application from Source (Design Repository - Development) to Target (Runtime Repository) environment.
The PAR_ROW_ID of hierarchical LOVs have the same PAR_ROW_ID as LOVs from source environment.
In order to reproduce the issue is enough to set System Preference "Seed Migration Priority" to "Source" only in Target environment (RR) and create and then migrate hierarchical LOVs from Design Repository to Runtime Repository through Siebel Migration Application.
The issue can be reproduced at will with the following steps:
2) Create a new LOV entry with:
Type: LOV_TEST
Display Value: LOV1
LIC: LOV1-LIC
3) Repeat the same steps on the Target environment, but set a different value for LIC
Type: LOV_TEST
Display Value: LOV1
LIC: LOV1-LIC-DIFFERENT
4) Set the "Seed Migration Priority" system preference to "Source" on the target environment
5) Perform LOV full migration
Expected behavior: The data (LOVs) on the target environment should be overwritten by the data (LOVs) from the source environment.
Actual behavior: No actual update happens.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |