My Oracle Support Banner

Parent And Child LOV Are Linked In The Different Workspaces (Doc ID 2602383.1)

Last updated on OCTOBER 23, 2019

Applies to:

Siebel CRM - Version 19.6 and later
Information in this document applies to any platform.

Symptoms

After migrated the runtime repository from lower environment to higher environment,  ROW_IDs of the LOVS are created with new values in the higher environment.
But the PAR_ROW_IDs of the child LOVs are not updated with the new ROW_IDs of the parent LOVs in the target environment.

The child LOVs that have a parent LOV are linked with the parent LOV with the one that belongs to the first workspace not the one that belongs to the current workspace  ( which means the PAR_ROW_ID refers to a LOV that is in the original workspace instead of the current one).

The hierarchical list of values are working fine as they use the name to link the 2 lov.    However,   due this behavior,   the sql from custom procedure  is not able to find find the LOV records as the sql is using PAR_ROW_ID = ROW_ID to find the record.

The PAR_ROW_IDs of the child LOVs  should be updated with the new ROW_IDs of the parent LOVs in the target environment.    

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Migrate the runtime repository from lower environment to higher environment
2. Go to database of the higher environment
3. Note  the child LOV still has the same PAR_ROW_ID as in the source env.  (PAR_ROW_ID refers to a LOV that is in the original workspace).


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.