I have a part “A” in inventory/stock. It is a purchased part. However, we would like to add a couple of materials to that part (“B” and “C”), without creating a new part. I’d like to raise a job for “A” which has the following materials “A”, “B” and “C”. Is it simply a case of raising a job for “A” and listing “A” as one of the materials? I want all materials to be backflushed.
Unfortunately, Epicor doesn’t treat part numbers that way. Epicor is expecting a new part number after something is done with it. Partially, it’s a cost thing. If you have 20 of part A at a cost of $20 each, then you do work to 10 of them, and add another $20 of cost, how does the system handle that?
Epicor will let you issue same part no. as material to itself at job level not at part level, however as @Banderson said your cost calculation and method traceability will be wrong, i.e beside the cost issue, when booking this job to stock again as ‘A’, how would you differentiate between the purchased ‘A’ and the manufactured ‘A’, even if you use lot tracked how would you know which one is which ?
Thanks for the replies guys, I understand the points you make. As the rework is low cost and low volume, I think I will do this outside the system. It is a one off and whilst I don’t like doing operations outside the system, sometimes needs must. Thanks for taking the time to reply anyway.
the issue is adding the same part no to itself, this is forbidden.
but if your reworked part has not got this issue, then it is a straightforward solution,
Create a blank ReWork method on Part level and approve it.
Create an NCR from stock, reject it to the DMR, then accept it to a the following rework Job
Create a job with _RW added to the created job no, choosing this method i.e. [Rework], engineer whatever you want on the job level including add material, notes, and/or operations.
book this job to stock using this Job no as lot no, thereby when users check stock they will know it is a reworked batch with a reworked method of manufacturing.
Note: this not suitable if your cost system set as last, or average unless you customize your reports and cost rollup to exclude these batches, but standard method will work ok.