Customizations based on LOV table S_LST_OF_VAL joins no longer working after upgrading to IP17
(Doc ID 2433063.1)
Last updated on AUGUST 08, 2018
Applies to:Siebel Life Sciences CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.
We have observed that after every full migration from lower environment to higher environment, row_ids of LOVs are getting changed.
This is impacting our few functionalities where we have LOVs referred as joins & child tables have join specification based on old row_ids.
Is this expected behavior with IP18?
In previous Siebel versions (before IP17) the LOV from s_lst_of_val were joined on row_id
In current Siebel version (IP17) this join has changed from row_id to ws_row_id joined with par_row_id, ws_id and we have customization created on row_id join (before ip17)
note: In IP17, the vanilla BC are working but we have issues with our custom BC. We need to understand the new mechanism of joining LOV's.
- How are the new joins created in IP17 so we can modify our customization and not have issues?
After changing the customization as per vanilla BC, customization is not working. Is there some internal mechanism (in Siebel code) that is performing some additional steps in order to make this work for vanilla BC ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!