"Stock Number" vs Custom iProperty

[Andrew1307]

As the title says. Should I use the builtin Stock Number or use a custom iproperty MaterialStockCode. 

Linking over to my ERP system I need the raw material information in the part to be exported so the system can make line items of the parts they are the children of. ex sheet metal parts have a raw material stock code that is the sheet they are cut out of. structural shapes have a stock code that the part is cut out of. 

So unique parts have a unique part number and then a MaterialStockCode representing the raw material. Straigh cut to lenght parts with nothing else done to them have part numbers that are the same as the MaterialStockCode. 

But is there any reason to not use the built in "Stock Number" iProperty instead?

[rjay75]

I use the Stock Number exactly for this purpose. But it really depends on the terminalogy and how many numbers are assigned to your parts. Its just a matter of training what the number means for your company.

I also use the iProperties for ERP loading. The Part Number is the unique identifier and most important (typically matches the file name minus the extension but not required.) The Stock Number is the raw material identifier the part is made from. I have a seperate MAT_Qty iProperty to quantifies the raw stock material usage. If the Part Number and Stock Number are the same then the part represents raw material usage in a parent assembly. These are often material with a high degree of scrap or sized during assembly versus having an individual manufacturing step. (A good example would be adhesive insulation installed in process and not cut to length before hand.)

[Andrew1307]

That sounds very similar to my own workflow and confirms what I am doing. 

I use a custom iProperty MaterialQTY that I populate with iLogic as you have seen from my other thread.

Thank you.