Loading Parts and Part Relationships
Your Site Administrator can load suppliers, supplier parts, and part relationships in a bulk process. Objects to be loaded are defined in XML files and loaded using the LoadFileSet or LoadFromFile utility.
The following table lists the object types can be loaded in Windchill Supplier Management:
|
Object Type
|
Description
|
|---|---|
|
Organizations
|
Creates WTOrganizations that represent suppliers.
|
|
Manufacturers and vendors
|
Creates suppliers of the manufacturer or vendor type.
|
|
Contacts
|
Adds contacts for a manufacturer or vendor.
|
|
Documents
|
Adds documents to a manufacturer or vendor.
|
|
Manufacturer parts
|
Creates manufacturer parts as a subclass of WTPart.
|
|
Vendor parts
|
Creates vendor parts as a subclass of WTPart.
|
|
OEM parts
|
Creates OEM parts that are associated with supplier parts.
|
|
Sourcing contexts
|
Creates sourcing contexts. A default sourcing context is assigned to each organization container.
|
 |
• Make sure manufacturer parts, vendor parts, OEM parts, and sourcing contexts already exist in the system before loading AML/AVL entries.
• If sourcing contexts are not required for your implementation, use the default sourcing context when loading entries into the AML/AVL.
|
 |
• The entries in the AML/AVL create associations between manufacturer or vendor parts and the corresponding the OEM part within a specific sourcing context. Each entry can also contain the assigned sourcing status.
|
The following flow diagram illustrates the sequence of steps in the loading process.
| | When creating WTOrganizations, the target container must be Site. When creating suppliers, adding contacts, and adding related documents, the target container must be the container to which the supplier belongs. |
For more information on the DTD and its elements, see DTD Files for Loading and Importing Supplier Data.