How Duplicate Objects Are Created

When you migrate customizable product (CP) data using product export and import or Application Deployment Manager (ADM) and the joint workspace data type, you can create duplicate records in the destination environment database when the CPs in the two environments have the same name but have different object identifiers. The S_PROD_INT.CFG_MODEL_ID column stores the versioned object identifier.

For example, assume that the source environment includes the product records shown in the following table.

Product Name	Row ID	CFG_MODEL_ID
Product A	1-A	1-A
Product B	1-B	1-B

The target environment, including the product records, is shown in the following table.

Product Name	Row ID	CFG_MODEL_ID
Product A	1-A	1-A
Product B	1-C	1-C

After the data migration, the target application includes the records shown in the following table.

Product Name	Row ID	CFG_MODEL_ID
Product A	1-A	1-A
Product B	1-C	1-C
Product B (1-B)	1-B	1-B

Product A is imported correctly to the target environment, because it has the same identification number in both environments.

Product B has different identification numbers in the two environments. Therefore, when it is imported, a duplicate product with the name Product B (1-B) is created. Product B (1-B) contains the latest changes of the product that were made in the source environment, while the original Product B in the target environment is unchanged.

Note: All run-time data, such as quote line items, order line items, and assets, still refer to the original Product B. If a user customizes the product, Siebel Product Configurator will use the obsolete product definition based on the original Product B rather than the updated product definition of Product B (1-B).