My client has an issue where they reuse a configured part number despite it being a different part. This creates many different jobs for this single part number. The part goes to outside processing, but when PO Suggestions runs it creates a single PO Line for all jobs. How can I prevent PO Suggestions from aggregating by part and create separate lines?
Would they be willing to add a unique field to the part number after configuration such as the Order Number and Line?
Have you tried messing with the lot sizing? Not sure if that would effect Sub-Con, and I don’t know if it would just make more releases.
I’m suggesting changes to the process now. But I thought there was some setting in the background (Supplier, Part, Site, etc.) that stopped the system from making a single PO from many demands.
I remember seeing that too, but I can’t remember where.
There is consolidated purchasing in part setup, but I need to refresh my memory on it.
That looks like multi company functionality.
Yeah, I knew it didn’t work like I thought it did. Last time I tested it I was trying to prevent what Jason is having an issue with.
That appears to be for multi-company (but the documentation is sparse). Either way, Lot Size is zero and Consolidated Purchasing is unchecked…
try max lot size of 1. Zero might just take it out of the equation.
Also days of supply of 1 will create a PO for each day. But that might not be granular or robust enough.
No luck. on the Max Lot or Days Supply. I am trying to convince them to use unique parts…
This is a little different because it’s subcontract operations. I would try changing the JobOper.Description field and adding different comments to that operation. Then re-running PO Suggestions and it may result in seperate PO Lines instead of one line with multiple releases.
Can you set the part to ‘make direct’? Then the PO suggestion should be for just that order line, and not affected by the other demand…