Object Numbering
This section describes various object numbering characteristics and differences betweenWindchill PDMLink and your ERP system.
Object Numbering and Attribute Field Length Differences
The minimum and maximum lengths of CN numbers and Reference Designators in Windchill versus Oracle Applications differ. This difference may cause failures when publishing CN Objects fromWindchill PDMLink to Oracle Applications. The differences in field lengths can be characterized for each object type (Parts, BOMs, operation labels, Resource numbers and CNs) handled by Windchill ESI, however, field length limitations need to be set for CN numbers and Reference Designators only, since the maximum field length for these fields in Oracle Applications is less than the Windchill maximum field length.
Object Type
Windchill Maximum Field Length
Oracle Applications Maximum Field Length
Part Number
40
18
Part Name/ Description
60
240
CN Number
32
10
CN Name
256
2000
Reference Designators
200
10
Operation Label
No limit
4
Resource Sequence Number
40
4
Department
No limit
10
Field Length Differences - Determining How to Compensate
The discrepancies for these field length differences can be compensated in Windchill. For default Windchill and Oracle Applications, the following lists where the information is located:
For information on how to limit field lengths in Windchill PDMLink, refer to the instructions in the Windchill Customizer’s Guide.
For information on how to set up auto-numbering in Windchill PDMLink, refer to the instructions in the Windchill Administrator’s Guide.
If Windchill PDMLink or your ERP system have been customized, these documents provide guidance on how to compensate for these field length differences.
The Object Numbering Property
The following traits exist for the property that controls object numbering in Windchill PDMLink:
The auto numbering properties are controlled by the Object Initialization Rules Administrator. There is a unique property that enables or disables auto numbering for each object type. Use the following as an example:
wt.enterprise.GeneratedIdentificationObject.ChangeOrderGenerator.number.format=WFN-ECN{GEN\:wt.enterprise.SequenceGenerator\
:WTCHANGEORDERID_seq\5\:0}
The auto numbering properties handle the following objects:
Parts
Documents
CAD documents
Managed baselines
Product configurations
Products
Change objects
Process plans
Resource groups
Process Materials
Skills
Tooling
Sequences
Enabling auto numbering allows the user to determine the starting number (change to Oracle Sequence), prepend the number with alpha characters, specify the number of characters, and specify the padding value.
The auto numbering properties are controlled at the site level.
The auto numbering property can be set on the Object Initialization Rules Administrator page off the Site menu.
Was this helpful?