Parent And Child LOV Are Linked In The Different Workspaces in Siebel Innovation Pack 19

Issue:- 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. 

Solution-

This has an impact on all the queries where we are querying LOVs on parent-child/hierarchial relationship directly from the siebel database. 

As all the queries consider below queries

Select * from S_LST_OF_VAL T1

left outer join S_LST_OF_VAL T2 on T1.PAR_ROW_ID = T2.ROW_ID   

But now  we have to consider the below query:

Select * from S_LST_OF_VAL T1

left outer join S_LST_OF_VAL T2 on T1.PAR_ROW_ID = T2.WS_SRC_ID