Standard Signal or Variable Map ( S_VOD table ) Shows Inconsistent Versions after the Siebel Upgrade (Doc ID 561149.1)

Symptoms

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= ‘<Row Id>'.

Changes

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

Cause

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