Need some ideas: PCIDs on jobs with coparts/keeping PCID connected to job. 2022.2.8

Great minds,

We have a process where a job is created to make x number of the same part. A custom application contains a record for each part and processes it through report quantity and job receipt to inventory in Epicor functions.

When these parts are manufactured, they might not meet the specifications for a “prime” part and are downgraded to a different part number. We add a copart and do the report quantity and job receipt to inventory with that part number. Works great.

So, we wanted to use PCIDs and bolted on an application to add a PCID with the build/split/merge BO after the job receipt to inventory. That works fine, too.

But we lose connection to the job from the PCID detail record because the PCID transaction isn’t associated with job. The job number is empty. Up the chain we go.

Epicor recently gave us the capability to report quantity with a PCID and send it to WIP and then do a PCID receipt to inventory. We added the capability at the report quantity point in our function. Works great.

BUT. If we add a copart to the job, it won’t work. In MES, the PCID controls are disabled when the copart is added. Epicare says coparts and PCID are not compatible. In my function, the business object throws an exception once I add the copart.

SO. How might I get what I want in a different way? Anyone have suggestions?

Thanks,

Joe

1 Like

Update:

I got around this by doing my normal report quantity and receive to stock without a PCID, and moving the stock to the previously created PCID with Build/Split/Merge, and then:

Widget: GetByID on the PCID record
Code: set the job number on the detail SupplyJobNum
Widget: Update

It seems to work so far, in that the PCID detail record retains the supply job number. We’ll see what issues it causes, I suppose.

Joe

2 Likes