Advanced Customization > Business Logic Customization > Data Exchange using Standards in Windchill > Product Lifecycle Management Services, Version 2.0 > PLM Mapping Information > Details of the Mapping between Windchill and PLM Services > Windchill Elements and Attributes Mapping for Supported Windchill Objects
  
Windchill Elements and Attributes Mapping for Supported Windchill Objects
The tables below explains the mapping between elements and attributes for some of the key Windchill objects which are supported.
WTPart
Object Type = WTPart
PLM Root Element = Item
Windchill Attribute Name
PLM Element
Description
number
Id
ObjectID/ufid
Item_version/uid
original value will be stored as key-value pair
masterUfid
uid
original value will be stored as key-value pair
name
Name
versionInfo/versionId
Item_version/Id
concatenate as A.2
versionInfo/iterationId
BusinessFields/BusinessField
String_value or Numerical_value
See BusinessFields / BusinessField section for element specific mapping for exact mapping.
Use Item_version/Design_discipline_item_definition/Simple_property_association/ Specified_value to build relationship with String_Value/Numeric_Value
contentItem
Digital_file
Use Document_assignment to build relationship with Item
endItem
defaultTraceCode
genericType
partType
folderPath
lifecycleInfo/lifecycleTemplateName
versionInfo/versionLevel
domainName
lifecycleInfo/lifecycleState
externalTypeId
String_value
Use Item_version/Design_discipline_item_definition/Simple_property_association/Specified_value to build relationship with item. The value is stored as a key-value pair, as following:
<Property_value
xsi:type="String_value">
<Value_name>
endItem</Value_name>
<Value_specification>false
</Value_specification>
</Property_value>
EPMDocument
Object Type = EPMDocument
PLM Root Element = Item
Windchill Attribute Name
PLM Element
Description
number
Id
ObjectID/ufid
Item_version/uid
orginal value will be stored as key-value pair
name
Name
CADName
Item_version/Design_discipline_item_definition/Item_instance/Id
versionInfo/versionId
Item_version/Id
concat as A.2
versionInfo/iterationId
BusinessFields/BusinessField
String_value or Numerical_value
SeeBusinessFields / BusinessField section for element specific mapping for exact mapping.
Use Item_version/Design_discipline_item_definition/Simple_property_association/ Specified_value to build relationship with String_Value/Numeric_Value
contentItem
Digital_file
Use Item_version/Design_discipline_item_definition/Document_assignment to build relationship with item for secondary content. Use Item_shape to build relationship with item for primary content.
masterUfid
authoringApplication
epmDocType
derived
domainName
folderPath
lifecycleInfo/lifecycleTemplateName
lifecycleInfo/lifecycleState
versionInfo/versionLevel
epmDocSubType
externalTypeId
String_ value
Use Item_version/Design_discipline_item_definition/Simple_property_association/Specified_value to build relationship with item. The value is stored as a key-value pair, as following:
<Property_value
xsi:type="String_ value">
<Value_name>
derived
</Value_name>
<Value_specification>
false
</Value_specification>
</Property_value>
EPMMemberLink
Object Type = EPMMemberLink
PLM Root Element = Next_higher_assembly
Windchill Attribute Name
PLM Element
Description
BusinessFields/BusinessField
String_value or Numerical_value
See BusinessFields / BusinessField section for element specific mapping for exact mapping.
Use Simple_property_association/Specified_value to build relationship with String_Value/Numeric_Value
ObjectID/localId
uid
Original value will be stored as key-value pair
uses/ObjectReference/ufid
Related
transform/matrix4d/m0*
Direction
Use Placement/Model_placement/Axis1 to build relationship with Next_higher_assembly.
transform/matrix4d/m0*
Direction
Use Placement/Model_placement/Axis2 to build relationship with Next_higher_assembly.
transform/matrix4d/m2*
Direction
Use Placement/Model_placement/Axis3 to build relationship with Next_higher_assembly.
transform/matrix4d/m3*
Cartesian_point
Use Placement/Model_placement/Local_origin to build relationship with Next_higher_assembly.
occurences/attribute
name
isAnnotated
asStoredChildName
depType
isPlaced
isRequired
externalTypeId
String_value
Use Simple_property_association/Specified_value to build relationship with item. The value is stored as a key-value pair, as following:
<Property_value
xsi:type="String_ value">
<Value_name>
isAnnotated
</Value_name>
<Value_specification>
false<
/Value_specification>
</Property_value>
BusinessFields / BusinessField
Object Type = BusinessFields/BusinessField
PLM Root Element = String_Value / Numeric_Value depending upon datatype
Windchill Attribute Name
PLM Element
Description
datatype
General_property/Property_type
Creates an element Genaral_Property and associates respective values. Use Property_value_representation/ Definition to build relationship with General_property.
datatypeQualifier
General_property/Description
value
Value_component, Significant_digits, Unit_component/ Unit_name
Gets split into value, unit and significant digits and gets assigned to Value_component, Significant_digits, Unit_component respectively.