Product Names appended with Row Id

With respect to Products in Siebel, sometimes, you might have encountered with a situation where product name will be appended with ROW_ID of the product.

Here we will discuss on Issue, Reason, and Possible Solution for this Problem

One basic thing everyone has to remember about products is, they come in to exists only once the products are released, which means only when a versioned object reference of that product are created.

Scenarios of Observation:

 You might have observed this issue in different situations like

• During Products addition in Workspace
• When products are imported in Target System

Possible reasons:

1. This happens generally when OBJECT_NUM reference of VOD table doesn't match with that of ROW_ID of S_PROD_INT

Initially OBJECT_NUM value will be set to that of ROW_ID of S_PROD_INT.

These values are preserved and referenced/used in many other tables.

Now, lets see why the values are changed with following Example

Consider following are the details of a Product in two different environments

	Product Name	ROW_ID	CFG_MODEL_ID	OBJECT_NUM	VOD_NAME
Env1	Test	1-1A	1-1A	1-1A	Test
Env2	Test	1-1B	1-1B	1-1B	Test

Now, when you import the product Export from Env1 to Env2, This might either fail or if it gets success a new record will be created in New Environment. And final structure looks like this

	Product Name	ROW_ID	CFG_MODEL_ID	OBJECT_NUM	VOD_NAME
Env1	Test	1-1A	1-1A	1-1A	Test
Env2	Test	1-1B	1-1B	1-1B	Test
Env2	Test {1-1A}	1-1A	1-1A	1-1A	Test {1-1A}

Where an Extra record is created in Target Environment Env2.

Remember, CFG_MODEL_ID stores the versioned object Identifier

Scenarios you might encounter when Duplicate products Exists

• During Customization, we might get an error saying object Identifier not found
• Product Name appended with RowId
• Duplicate Class and attribute records in Target Environment

Possible Solutions

Following solutions are not tested by me but might work

• Use Name based Import using ISS Authoring Import Export business service as suggested by Oracle
• Rename older product NAME  in S_PROD_INT and VOD_NAME in  S_VOD and try to import

Best Practices

• Never Create products with same name in two different Environments
• Never Create Attributes, Classes and any other information in other environments
• Maintain single product  master environment for configuring the products from Scratch