Name Based Siebel XML Import Issue (Doc ID 2146133.1)

Last updated on JUNE 03, 2016

Applies to:

Siebel Product Configurator - Version 8.1.1.10 [23021] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.10 [23021] version, Order Management

Siebel was upgraded from 7.5 to 8.1 in July 2014. We have different Product Row Id’s in different environments and hence was advised by Oracle to use "Name Based" instead of "Object based" XML import method.

ACTUAL BEHAVIOR
---------------
Exported Siebel XML is referring to Row Id of the Root Product instead of Product Name and as this Row Id is not in target environment, it is not associating the Root Product to the script event. BUT if we bundle all 5 Root Products in 1 XML and deploy, then Siebel resolves the Row Id conflict and associates the Root Product correctly to the script definitions in target environments,

EXPECTED BEHAVIOR
-----------------------
'Name Based XML import' method is consistent for product with a standard design.

STEPS
-----------------------

While importing a product using Name Based XML import method from one environment to another, the association of Root Product with a script event defined in the imported product is getting removed.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Business is unable to launch new trading offers and is affecting the revenue badly.

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