Advanced Customization > Business Logic Customization > Data Exchange using Standards in Windchill > STEP Data Exchange using EXPRESS > AP242 XPX Mapping Guide > Mapping Table for Import of AP242 (non-Windchill data) to Windchill EXPRESS Entities > LocalId and Ufid Generation for Associations
  
LocalId and Ufid Generation for Associations
Mapping Table
As in the incoming data from non-WC system (w.r.t above snippet), there is no means by which localId/ufid can be extracted. So the general strategy for generation localId and ufid for associations would be as described in the table below.
AP242
Windchill
Notes
localId
( VersionToMaster association)
<linkType>-<parentPartNumber>-<parentPartName>-<ParentPartVersion>-<childPartNumber>-<childPartName>
e.g. 'wt.part.WTPartUsageLink-OCR0847312-VIS RLX M50,80-12 AUTOTAR SA1ND-001-7703026050--A-VIS RLX M50,80-12 AUTOTAR SA1ND'
OR
( VersionToVersion association)
<linkType>-<parentPartNumber>-<parentPartName>-<ParentPartVersion>-<childPartNumber>-<childPartName> -<childPartVersion>
e.g. ‘wt.part.WTPartDescribeLink-OCR0847312-VIS RLX M50,80-12 AUTOTAR SA1ND-001-7703026050--A-VIS RLX M50,80-12 AUTOTAR SA1ND-002'
OR
( WTPart, WTDocument, EPMDocument)
<Type>-<number>-<name>-<version> e.g.
‘wt.part.WTPart-0000000125-piston-A.1’
1. <linkType> would be a string value based on the type of association.
For PartUsageLink: linkType : STRING := 'wt.part.WTPartUsageLink'
For PartDescribeLink : linkType : STRING := ' wt.part.WTPartDescribeLink'
2. However <childPartVersion> would only be applicable in case WTPartDescribeLink.
ufid
( VersionToMaster association)
<linkType>-<parentPartNumber>-<parentPartName>-<ParentPartVersion>-<childPartNumber>-<childPartName>|<OriginatingSystem or lastKnownRepository>|<OriginatingSystem or lastKnownRepository>
OR
( VersionToVersion association)
<linkType>-<parentPartNumber>-<parentPartName>-<ParentPartVersion>-<childPartNumber>-<childPartName>-<childPartVersion>|<OriginatingSystem or lastKnownRepository>|<OriginatingSystem or lastKnownRepository>
OR
( WTPart, WTDocument, EPMDocument)
<Type>-<number>-<name>-<version>|<SYSTEM_GUI>|<SYSTEM_DOMAIN> e.g.
‘wt.part.WTPart-0000000125-piston-A.1| ptc.com|ptc.com’
masterUfid
( WTPart, WTDocument, EPMDocument)
<Type>-<number>-<name>|<SYSTEM_GUI>|<SYSTEM_DOMAIN> e.g.
‘wt.part.WTPartMaster-0000000125-piston| ptc.com|ptc.com’
externalTypeId
Windchill Objects (WTDocument, WTPart and EPMDocument) externalTypeId is formed by concatenating with the partTypes/documentTypes attribute from the Part/Document entity respectively if present.
For example : WCTYPE|wt.doc.WTDocument|3DR
Part 21 Representation
#3321= VIEWCONTEXT($,PROXYSTRING('VPLM_RN_PDT_OCR'),PROXYSTRING('FROZEN'));
#3326= PARTVIEW($,$,$,$,$,#3321,$);
#3361= PARTVERSION(IDENTIFIERSTRING('001'),CHARACTERSTRING(''),$,$,(#3326));
#3404= PART(IDENTIFIERSTRING('OCR0847312'),TRANSLATEDSTRINGSET((#3406,#3408))
,$,$,(#3325,#280),$,(#3361));
#3408= LOCALIZEDSTRING($,'VIS RLX M50,80-12 AUTOTAR SA1ND');
#3414= VIEWCONTEXT($,PROXYSTRING('VPLM_RN_PDT_IND'),PROXYSTRING('FROZEN'));
#3421= PARTVIEW($,$,$,$,$,#3414,$);
#3456= PARTVERSION(IDENTIFIERSTRING('002'),CHARACTERSTRING(''),$,$,(#3421));
#3499= PART(IDENTIFIERSTRING('7703026050--A'),TRANSLATEDSTRINGSET
((#3501,#3503))
,$,$,(#3420,#280),$,(#3456));
#3503= LOCALIZEDSTRING($,'VIS RLX M50,80-12 AUTOTAR SA1ND');