Hello CETEC Support Team,
We are looking to generate PRC codes with 1-Character Alpha (currently PRC accepts only 3-character Alpha) codes so as to simplify our current Part nomenclature on Cetec without affecting our overall Engineering Part Numbering Logic.
Our current MFG Part#s as setup as smart Alpha-Num PN#s in the following format:
A-NNNN-NN
Is there a way CETEC can customize the PRC Code field to accept 1 character alphabetical codes?
If you are worried about your part nomenclature, I would recommend naming your part name as fully A-NNNN-NN, but just using the normal PRC codes and dropping the PRC code from any invoices. However, our PRC code needs to be 3 characters .
Cetec ERP Support Team
Hi @cetecerp31 Yes, this is our Part nomenclature already as A-NNNN-NN, but it is super confusing/ non-value-add to our engineering and production teams to include the PRC code as a 3 alpha-char prefix to our existing alpha-num Part#.
It would be great if the PRC code were customized to a 1-Alpha character so that we may move our Part numbering towards a âNNNN-NNâ format.
Can this absolutely not be done? What is the reasoning behind this?
Thank you.
After double checking with engineering, you can set the PRC code as âAlpha_Space_Spaceâ and it shouldnât cause any problems. You may need to use the old version of PRC List to do that: PRC List
However, do NOT Start your PRC with a Space, as it will cause issues.
Let me know if that works for you.
Cetec ERP Support Team
@cetecerp31
Yes, This would theoretically work.
How would we upload an âImportâ file with the âprcâ and 'partnumbâ modified, as the template requires âprcpartâ to be a required field.
Will BOM associations to the Part whose PRC is being modified remain unaffected?
I think that you would have to upload a entirely new set of PrcParts.
They would have to be on the form A_ _ -NNNN-NN.
After that you would have to merge all your old parts that are on the form PRT**-NNNN-NN** with the new one.
That way you would be abel to keep the Bom associations for all your parts.
However you will loose information in the description field and OEM part and Tech description if you have any.
That can of course be uploaded again after. But make sure you have exported all that information before you do the merge.
Also make sure you have that information sorted so that it aligns with the new parts so that you can easily just swap out the prcPart in the list to the new one.
With that said I would not do this if you have a lot of parts.
The merge operation is quite time consuming and requires you to stay focused to avoid making any misstakes. it is also a lot of keyboard interaction to get this done.
I would have put your part nomenclature A-NNNN-NN in the description field so that it is searchable like that and left the PrcPart as is. Unless of course we are talking about less than 50 parts then it might be worth it.
My two cents
//H
That is a good response, thank you @sisyfos . Part merges can be dangerous because they are permanent, so I pulled a backup of your environment in case anything goes awry.
Another possible issue with this is the data gets scrubbed when being imported, which means it might drop spaces on the ends. A decent workaround would be to use dashes instead of space, so A-- NNNN-NN.
That is a good workaround that would be less time consuming and still searchable.
Thanks,
Cetec ERP Support Team
