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

Last updated on MAY 19, 2017

Applies to:

Siebel eConfigurator - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.
***Checked for relevance on 10-Sep-2013***

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= ‘04-FMOFZ’.

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:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms