Creating Enterprise Data and Plant-specific Functional Data from Loader
For each part, you can create multiple view-specific enterprise data objects of different types but only one common enterprise data object. Also, for each view-specific enterprise data object, you can create multiple plant-specific functional data objects of the same type or of different types. The preference set for enterprise data is applied when creating these objects. For more information on preferences, see
Preferences in MPMLink.
|
|
Only users with Windchill Administrator privileges can create enterprise data and plant-specific functional data objects.
|
Before you begin, ensure that you have read the assumptions that apply when creating enterprise data and plant-specific functional data objects using the loader. For more information, see
Assumptions for Loading Objects.
Configuring the Load File
The structure of the load file and the corresponding high-level steps to configure the file for creating data objects are as follows:
1. Disable automatic creation of plant-specific functional data objects. Uses the element DisableAutoCreationOfPFD.
If automatic creation of plant-specific functional data objects is not disabled, the value set for the preference Automatically Create Plant-specific Functional Data is considered. To ignore the preference value when creating the objects, you need to disable automatic creation irrespective of the value set for the preference. This action does not modify the preference value.
This step applies only when you want to create view-specific enterprise data objects and plant-specific functional data objects using a load file. Skip this step if you want to create plant-specific functional data objects for an existing view-specific enterprise data object.
2. Search for the part. Uses the element BeginSearchPart.
Specify details of the part for which you want to create the enterprise data objects and plant-specific functional data objects. When the load file is parsed, the relevant part is identified in the system based on the following attributes:
◦ Part number
◦ Organization name
◦ Version
◦ Iteration
◦ View
◦ Variation
3. Create an enterprise data object. Uses the element BeginEnterpriseData.
◦ Specify any of the following details for the common or view-specific enterprise object that you want to create:
▪ Version
▪ Iteration
▪ View. Specify view details only when creating a view-specific enterprise data object.
▪ Life cycle
▪ Life cycle state
|
|
Objects are created or iterated based on the version or iteration specified in the load file and the checkout status specified in the wt.properties.xconf file. For more information, see Checkout Flags for Loading Objects. |
◦ Specify whether the view-specific enterprise object should be designated as a phantom object. Uses the element csvphantom.
The values True, yes, or 1 indicate a phantom attribute.
◦ Specify attributes for the enterprise data object. Uses the elements ExtAddEffData and IBAValue.
You can define multiple default as well as custom attributes. Additionally, you can set multiple effectivities, such as date, lot, and serial number, on the object. If the attribute already exists, the attribute values get updated with the values you provide here.
4. Create a plant-specific functional data object in the context of a view-specific enterprise data object. Uses the element BeginPlantFunctionalData.
◦ Specify any of the following details for creating a plant-specific functional data object:
▪ Version
▪ Iteration
▪ Life cycle
▪ Life cycle state
▪ Type: Specify the internal name of the soft type.
|
|
Objects are created or iterated based on the version or iteration specified in the load file and the checkout status specified in the wt.properties.xconf file. For more information, see Checkout Flags for Loading Objects. |
◦ Specify attributes for the plant-specific functional data object. Uses the elements ExtAddEffData and IBAValue.
You can define multiple default as well as custom attributes. Additionally, you can set multiple effectivities, such as date, lot, and serial number, on the object. If the attribute already exists, the attribute values get updated with the values you provide here.
◦ Specify a unique set of common attribute values when creating multiple plant-specific functional data objects of the same type for the same instance of view-specific enterprise data object. Uses the elements csvalternate1, csvalternate2, and csvcategory. Out of the box, these elements represent the attributes supply chain, location, and category, respectively.
5. Enable automatic creation of plant-specific functional data objects. Uses the element EnableAutoCreationOfPFD.
The automatic creation of plant-specific functional data objects can now be enabled to start creating the objects based on the details provided in the load file. This step does not modify the value set for the preference Automatically Create Plant-specific Functional Data.
|
|
It is recommended that the default Java heap size for method server be set to 8 GB. The size of each load file should not exceed 300 MB.
|
Uploading the Load File
After creating the load file, you can upload it to Windchill using the command: windchill wt.load.LoadFromFile -u<admin user name>-p<admin password>-d<location of the load file>-CONT_PATH<“container path, product container”>
For example, windchill wt.load.LoadFromFile -uwcadmin-pwcadmin-d/vagrant/temp/Sample/SampleLoadWTPart.xml-CONT_PATH“/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=TestProduct”
The method server displays a log of all the objects that were loaded successfully. Issues encountered during loading, if any, are also displayed.
The attributes that uniquely identify a plant-specific functional data object are displayed in this sequence: view, object type, supply chain, location, category. For example: PlantMfg, Purchasing, 003, 001, Quality.
