Standard Signal or Variable Maps show inconsistent versions after Siebel upgrade
Hi
I would like to bring up an issue we recently saw with Siebel upgrades. This can happen on all Siebel versions:
After the Upgrade we can find standard Signals or Variable Maps, which have two active versions-old custom one and a new standard one with CURR_VER_FLG = Y
This can generate a lot of weird behavior and errors on functions like
- pricing
- eligibility/compatibility
- eConfigurator
- ...
We strongly recommend to check the status of signals and variable maps after an upgrade.
Please see following entry under My Oracle Support:
Standard Signal or Variable Map (S_VOD table) show inconsistent versions after the Siebel upgrade (