WTPart Number Same as CAD Document Number During Auto Associate
Aug 01, 2012
10:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Aug 01, 2012
10:28 AM
WTPart Number Same as CAD Document Number During Auto Associate
I'm on 10.1 M010 and I thought there was a preference to make the WTPart Number equal the CAD Document Number upon Auto Associate but I cannot find it. Does anyone know what it is?
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CD6FD0.636F4650]
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CD6FD0.636F4650]
Labels:
- Labels:
-
Other
4 REPLIES 4
Aug 01, 2012
11:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Aug 01, 2012
11:31 AM
Preferences:
Operation > Auto Associate > Auto Associate Numbering Parameter
Operation > Auto Associate > Auto Associate Naming Parameter
The manual Using Creo with Windchill provides related information.
HTH
Swamy Senthil
Swasen Inc.
Operation > Auto Associate > Auto Associate Numbering Parameter
Operation > Auto Associate > Auto Associate Naming Parameter
The manual Using Creo with Windchill provides related information.
HTH
Swamy Senthil
Swasen Inc.
Aug 02, 2012
10:05 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Aug 02, 2012
10:05 AM
Ok so you got this functionality to work? Here's what I want:
1. CAD Document Number generated from EPM_SEQ
2. WTPart
a. Number equals CAD Document when created through Auto Associate
b. Number generated from EPM_SEQ when created through Windchill. Using this sequence should prevent collisions with WTParts created through Auto Associate.
To accomplish this I have done the following:
1. Product Level EPM Document OIR uses EPM_SEQ
2. Product Level WTPart OIR uses EPM_SEQ
3. Org Level Auto Associate Numbering Parameter: number
4. Org Level Auto Associate Truncate Name File Extension: Yes
5. Org Level Auto Associate Truncate Number File Extension: Yes
6. Org Level Force Autonumbered Part Creation: Yes
Here is what happens when I create a new CAD Document:
1. The CAD Document receives a new auto number
[cid:image002.png@01CD7096.5936A090]
2. I check in and auto associate and the WTPart is created with the next number in the EPM_SEQ
[cid:image003.png@01CD7096.5936A090]
This obviously isn't what I want so what am I doing wrong with my configuration?
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image004.jpg@01CD7096.5936A090]
1. CAD Document Number generated from EPM_SEQ
2. WTPart
a. Number equals CAD Document when created through Auto Associate
b. Number generated from EPM_SEQ when created through Windchill. Using this sequence should prevent collisions with WTParts created through Auto Associate.
To accomplish this I have done the following:
1. Product Level EPM Document OIR uses EPM_SEQ
2. Product Level WTPart OIR uses EPM_SEQ
3. Org Level Auto Associate Numbering Parameter: number
4. Org Level Auto Associate Truncate Name File Extension: Yes
5. Org Level Auto Associate Truncate Number File Extension: Yes
6. Org Level Force Autonumbered Part Creation: Yes
Here is what happens when I create a new CAD Document:
1. The CAD Document receives a new auto number
[cid:image002.png@01CD7096.5936A090]
2. I check in and auto associate and the WTPart is created with the next number in the EPM_SEQ
[cid:image003.png@01CD7096.5936A090]
This obviously isn't what I want so what am I doing wrong with my configuration?
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image004.jpg@01CD7096.5936A090]
Aug 03, 2012
06:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Aug 03, 2012
06:58 AM
Patrick
We use 9.1 not sure if this is relavant for 10
Toenable "CAD centric" appraoch (CAD created first then part automatically created from it)
1/A part type requiredwith OIR without autonumber (falling back toCAD number/filename driven numbering in preferences) for CAD centric
2/ A part type required with OIR enablingautonumbering for Part centric(overriding preferences)
We therefore had to create a soft type of part. Onetype forCAD centric and one for Part centric. In 9.1 OOTB autoassociate always uses the root type of WTpart to the soft type has be type which uses the OIR with autonumber switched on.
Darren
Aug 03, 2012
03:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Aug 03, 2012
03:12 PM
Darren,
I am finding out what you obviously found out in 9.1. Did you ever think about implementing a custom logic algorithm to be used in the WTPart OIR as a possible alternate solution? This is possible per the "Specialized Administration Guide" on page 142.
Custom Rule Allgorriitthms
To create custom algorithms, PTC provides the RuleAlgorithm interface upon
which all out-of-the-box algorithms have been built. For details on how to use this
interface to create custom algorithms, see the Javadoc associated with this
interface.
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CD718A.5F11F3D0]
I am finding out what you obviously found out in 9.1. Did you ever think about implementing a custom logic algorithm to be used in the WTPart OIR as a possible alternate solution? This is possible per the "Specialized Administration Guide" on page 142.
Custom Rule Allgorriitthms
To create custom algorithms, PTC provides the RuleAlgorithm interface upon
which all out-of-the-box algorithms have been built. For details on how to use this
interface to create custom algorithms, see the Javadoc associated with this
interface.
Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image001.jpg@01CD718A.5F11F3D0]
