Siebel Business Process & Functionality (MOSC)

MOSC Banner

Product objects tables with corrupted data

edited Dec 16, 2016 12:14AM in Siebel Business Process & Functionality (MOSC) 1 commentAnswered
  Hi experts,
I'll try to explain shortly our problem: our customer have implemented all OM processes and Product Admin , respecting v.8.1.1.3 standard flows and configuration mechanims; now they are facing a product deploy problem when try to import product data on preproduction enviroment.

Analyzing the problem, we noticed that in Preprod env are already present some product/class/attribute  (manually created) that via Workspace Project are trying to import and that these product/class/attribute have different IDs (ROW_ID on S_PROD_INT, OBJECT_NUM on S_VOD ...) or version start/end date (S_VOD_VER.START_DT on target env is bigger than on source env) between two enviroments that does not allow to load updated information. On this scenario are generated different import exception:

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