Bookshelf Home | Contents | Index | PDF |
Siebel Product Administration Guide > Releasing Products and Other Versioned Objects > About Avoiding Duplicate Versioned Objects During Product Data MigrationStarting in Siebel 7.8, the import function for product data uses the object identifier to determine whether records being imported already exist in the target database. In earlier versions, the import function used a name-based identifier. The object identifier refers to the value in the OBJECT_NUM column of the versioned object table, S_VOD, for the corresponding versioned object. Object identifiers are initially set as the value of the row ID. They are always persistent and are referenced in other tables, including S_PROD_INT. For this reason, it is now absolutely mandatory to preserve the object identifiers of versioned objects across multiple environments in order to consistently export and import these object definitions across different environments. This behavior affects all versioned objects: Products, Classes, Attributes, Signals, and Variable Maps. Guidelines to Avoid Duplicate Versioned Object RecordsFollow these guidelines to avoid creating duplicate versioned object records:
How Duplicate Objects Are CreatedWhen 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 Table 43, and the target environment includes the product records shown in Table 44. After the data migration, the target application includes the records shown in Table 45. 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 Configurator will use the obsolete product definition based on the original Product B rather than the updated product definition of Product B (1-B). Possible Symptoms of Duplicate RecordsThe following symptoms probably mean you have duplicate records:
Name-Based ImportIf you have failed to create a master product database and you already have multiple databases with different object identifiers for the same objects, object identifier-based import fails. In this case, you can use name-based import. Name-based import is not recommended. Use it only as a last resort. Name-based import is done using the ISS Authoring Import Export business service. For more information, see Siebel Order Management Guide. |
Siebel Product Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |