I just re-ran PO suggestions for a specific purchased part that we stock, and PO suggestions is giving me two new PO suggestion lines for the same part with different quantities, with the same due date on each of them. Any idea what would case that? Not sure why it’s not combining them into the same suggestion line. Existing PO’s with unreceived lines for this same item have their quantities and dates locked.
Because Epicor goes with the path of least resistance. With PO Suggestions, some companies may want to dual source their purchased parts and if they were combined, it would be more difficult to split it. You can easily create 1 PO from 2 suggestions.
Does Time Phase show anything different in the Source column for the two lines?
Check comments on the POs. If they are different, it is probably creating multiple lines.
I hear what you’re saying, but we only buy it from one supplier, who it is suggesting us to buy it from. None of the other 10 or so New PO Suggestions (for this same supplier and part class) are split out like this.
Nope, the source is exactly the same for both. “Suggestion for Warehouse”
If you posted screen shots of the suggestions, that would probably help a lot, instead of having everyone guess which of the numerous set up flags it could be.
Before you mess up the guessing with screen shots I am going to for part class split PO Line for 1000.
Split PO Line
Indicates that purchase suggestions for part records with unique Purchasing comments should generate a different purchase order line for each part entry.
Example: Part DSS-1000 is requested by two different operation lines on a job. If this check box is selected and the Purchasing comments are different for each operation line, the parts are kept as two different purchase order suggestions. If the check box is cleared, the parts would be combined into a single purchase order suggestion.
None of our part classes have the “Split PO Line” checkbox checked. By ‘Purchasing Comments’, assuming you are referring to JobMtl.PurComment on the material line for this purchased product on the jobs with this item, those are all blank.
I guess the next step is to run suggestions for this part only and see what the log says and maybe post some screen shots so we can possibly spot something. have you downloaded logs from the cloud before? I have no idea how to do that.
Do you have Days of Supply set on the part? Maybe it’s splitting the demand into 2 suggestions because it’s for 2 different jobs and Days of Supply is at 0?
Epicor development is taking a look at this. Appears to be some sort of bug. PO suggestions are not only doubling up for the same item/supplier/due date in some instances, but also suggesting wildly high (seemingly random) quantities that would take us well above the max. Seems to be disregarding the existing PO’s already in place, which are showing in time phase. Curious if anyone else is seeing the same?
Not sure if this is the end all solution, could be part though. We use Allow Consumption of Minimum Qty ( Site Maintenance/Planning tab) to keep from suggestions from being created if items below min level.
Update - I removed the lock date from the release level (but kept qty locked), and now it’s giving correct suggestions for New PO’s. Previously, with the date locked, new PO suggestions was ignoring any existing PO’s, and suggesting we place new PO’s with due dates AFTER the existing PO’s were due. Now, with only the qty locked, it’s just giving Change PO Suggestions, to expedite existing PO’s.