Siebel Business Process & Functionality (MOSC)

MOSC Banner

Standard Signal or Variable Maps show inconsistent versions after Siebel upgrade

edited Dec 16, 2016 12:09AM in Siebel Business Process & Functionality (MOSC) 2 comments

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 (

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center