Joint WorkSpace Export and Import via ADM (Doc ID 538388.1)

Last updated on FEBRUARY 24, 2016

Applies to:

Siebel System Software - Version 7.8.2 SIA [19213] and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Database: Oracle 10g
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8



***Checked for relevance on 22-Aug-2013***

Symptoms

While exporting and importing Joint Workspaces using Application Deployment Manager (ADM), the standard columns (description, product line) were not deployed from the source to target environment.

This statement was located:
"after you have completed ADM for Joint WorkSpace, follow the same process for another ADM object of ProductData. This time you need to specify the searchspec for the product, instead of 'my_joint_workspace_name'."

Thus, ''my_joint_workspace_name'' will migrate the header information (id, name, vendor, org) and versioned content (structure/rule/ui) for those products inside the joint workspace.

The second product data object will migrate non-versioned information (description, price type, partnum). This second object (ProductData) cannot be imported without importing the first object (Workspace Projects); otherwise, a no insert error is thrown.

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