sherenegladysj - Monday, May 10, 2010 7:44 AM:
Hello all,
I want to have Part Naming Convention in the part Item Number field. The Naming Convention as follows...
DF_PN_X_XXX (All Part Number should follow this pattern)
DF_PN -- Code
X ----- Type (P-Part / A- Assembly/ M- Mechanical/ E-Electrical...)
XXX ----- Base Number (000 - assembly, 001, 002,003 for subassembly & Parts)
How to achieve this? I think Sequence does not help me on this case...
Thanks & REgards,
Sherene
RobMcAveney - Thursday, May 13, 2010 2:05 PM:
The use of "intelligent" part numbers like this is not suggested. There are many shortcomings to this approach, and most experts will advise you to change your part numbering scheme to sequential numbering. Here are a couple of examples of problems with "intelligent" numbering:
- You design a part for one product and later use it on a different product. Do you a) change the part number to a different code, b) copy the part and have the same part with 2 different numbers, or c) leave the part number alone and have a BOM with multiple codes in it? If c) then what was the point of the code to begin with?
- You design a complex part and give it a number like DF_PN_P_123. Later you decide the part is too hard to manufacture as one piece, so you redesign it as a subassembly. What do you do with the part number?
- Your company merges with another company. Both companies use "intelligent" numbering schemes, but the formats are different Do you a) change all of one company's part numbers to match the other scheme, or b) leave the part numbers alone and teach the engineers to use both schemes? In either case, what happens after the third or fourth merger?
After reading the above, hopefully you are convinced to change your part numbering scheme instead of automating it. However, since this is the Developers Forum I will give you the technical answer to your question: you will need to write code to set the part number. The first 8 characters would be set based on other properties of the Part (I assume). The last 3 digits could either come from a Sequence (you would need one Sequence per code group) or you could just search for the highest existing number in that code group and increment it yourself.
kapil - Friday, May 14, 2010 1:55 AM:
I too certainly agree upon that part number should not be intelligent.It should be just a unique code to identify the part. here is a nice article on disadvantage of intelligent part numbering system
If you still decide to achieve this. You can create list of all possible selections and display them as dropdown box in Part form.
Open Part Item type and go to the Server Event tab. Add new Method with onBeforeAdd Event. You can write the logic to combine those selections and set value for item_number
Regards,
Kapil
jonasach - Thursday, May 13, 2010 3:48 PM:
Should be called "Informative" part number, and less "intelligent".
Assuming you have other systems (even industry standard values) that already reference these values, could innovator have the non-intelligent part numbers, and a cross reference field(s) for the other system(s).
Simple search capability would get you either value.
Early designs would not have to reserve the formatted number until approved.
aravinth_r - Thursday, March 1, 2012 9:00 AM:
Hello Kapil,
I am not able to see the onBeforeAdd server event in the ARAS PLM system. I am only able to see the following events which contains *onBefore*.
onBeforeAddAlias
onBeforeAddReadProperty
onBeforeAddSequence
onBeforeAddUpdateLocated
onBeforeAddUpdateSavedSearch
onBeforeAddVariable
onBeforeLockFMEA
onBeforeUpdateVariable
Can you tell me among the above which one I should use for writing the method you have given? Please let me know
Thanks, Aravinth
