Tuesday, 28 March 2017

Exporting Product Lines in Siebel


As we know we can export Products, Product classes, Attributes etc., using workspaces. 

But can we export Product Lines also using workspace??? No. This cannot be done using product workspace. 

Reason being, Product line is not a versioned object. You can add/delete product from a product lines as and when required and there is no track for that.

Hence exporting and importing Product Lines doesn’t work in same way. 

See the below snapshot where you cannot find the Type of Versioned Object.

Here comes the question of how do we export product lines? The answer is through ADM (Application Deployment Manager)


  • We need to go through ADM process, we need to follow following process
  • Navigate to Application Deployment Manager --> Deployment Projects
  • Create a New Record and make sure Export to File is selected
  • Create a New Record in Project Items with below details
    • Data Type Name=ProdFeature
    • Deployment Mode=Synchronize or Upsert (as per Business customization)
    • It is recommended to always have one master environment, hence in that case it would be Synchronize
    • Save the record
  • Now there will be a child for ProdFeature with Data Type Name as “ProdLine”
  • Provide a Filter against ProdLine as “[Name]='<Product Line>'
  • Click on Validate Filter Button
  • Once Validated, navigate to Deployment Sessions
  • Create a New Record
  • Select the project Created
  • Click on Save
  • You should be able to see the status as Filter Validated under Session Transactions
  • Click on Deploy
  • System will prompt for Server Path, Provide the same
  • Once Export is done, Status will be changed to Export Completed


Snapshot showing Project Items with Deployment mode as “Upsert”



Importing Product Lines

  • Navigate to Application Deployment Manager --> Deployment Sessions
  • Go to Menu and Select Deploy from Local File
  • Click Browse and select the XML file, import the same


Note: Make sure Organization Id in XML is as per Target Environment, if not, you need to change in XML, else import will be successful but Organization will not be mapped, hence you might face Visibility issues