Last updated on MAY 19, 2017
Applies to:Siebel eConfigurator - Version 8.0 SIA  and later
Information in this document applies to any platform.
***Checked for relevance on 10-Sep-2013***
If there is standard Signal or Variable Map (S_VOD table) which has a custom active version (S_VOD_VER table, CURR_VER_FLG = Y), the following problem is noticed after the upgrade:
-there will be two active versions-old custom one and a new standard one with CURR_VER_FLG = Y
Example: Variable Map- ‘Default Pricing Variable Map – Context’ ROW_ID= ‘04-FMOFZ’.
After a Siebel upgrade process, inconsistencies in the vanilla Signals and Variable Maps (Versioned Object Definition) were discovered, where they were modified on the prior Siebel version prior to the upgrade.
As a consequence, these objects are left corrupt. Some of the inconsistencies are:
- More than one released version is left active for the object
- More than one record is marked as workspace
- The contents between the workspace and last version are different – a developer can release a modification without knowing that other changes, not made by him, are being released at the same time
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms