Mystery source for PO Suggestion Operation

Kinetic ERP
1

So I noticed today we have about 100 PO suggestions for Operations from 2019 with no apparent demand. Job number and order number is blank in SugPoDtl.
They are coming from somewhere, as when we regen each night, they are found and added to the table.
Any ideas?

There is an old, closed job that has the parts and operations on it, but they are completed, with POs cut and received. In our test database I reopened the job. Changing quantities on the parts in the job doesn’t affect the PO suggestion demand. If I add a new line to that job with the same part number, that demand will also be added. So I don’t think the demand is coming from the job…

I searched our whole database for the part number in question, it has to be coming from here right?
So long as it isn’t buried in some unsearchable data chunk…

image
image603×823 14.5 KB

Anyone see the culprit?

image
image1523×144 5 KB

Maybe it has something to do with CoParts… the items in PO Suggestions are listed in CoParts, while there are other items on the original job that aren’t in the CoPart table and aren’t on the suggestions… not sure what to do if this is the problem.

image
image1403×101 4.4 KB

2

That last image looks like it is a co-part of itself. Both PartNum and CoPart fields are the same.

And it’s purchased AND a CoPart?

I’m guessing that you use it’s “parent” in an assembly, but only need part of it. So you put the unused portion into inventory via CoPart. That sound right?

3

Hey thanks for thinking about this with me.

THB I’m not familiar with CoParts. No co-parts are listed on the Job Closing Co-Part tab. So I’m not sure this is the issue.

Yes the part number and copart number are the same.
The part is manufactured, on the job as an assembly with operations.
Are you seeing that it is purchased somewhere? The suggestions are for Operations on the part, not the part itself…

I’m not seeing any inventory entry for a CoPart, just Part.

4

Is there anything in the PO regen log file for the part?

5

Yeah, I focused on the “PO Suggestion” part and kind of missed the “Operation”. And I’ve no experience with po operations.

Sorry about that.

6

Thanks for thought. No not in the basic log, though there are a bunch of unrelated orphaned POs I need to look into as well.

I’ll try running Generate PO Suggestions with full logging, see if anything hints from that…

7

So it is in the log, but I don’t see how to diagnose… no differences.

Bad suggestion:

14:14:30 Processing Part:153-802. Attribute Set: ''. V600
14:14:30 Processing Part:153-802 Attribute Set: '' Site:MfgSys Contract:.
14:14:30 Parameters: Receive Time -> 0; Planning Fence -> 0; Delta In -> 0; Delta Out -> 0; Lead Time CutOff -> , Use Dynamic DOS -> True, Allow Consume Min -> True
14:14:30 Deleting suggestions
14:14:30 Processing non-stock transactions for Part:153-802, Attribute Set: ''.
14:14:30 ProcessJobPOs
14:14:30 Creating new PO suggestion for Part:153-802, Attribute Set: '', Date: 7/23/2019 12:00:00 AM, Quantity: 1.00000000 Number: 0
14:14:30 Done with New Suggestion transaction
14:14:30 ProcessJobPOs
14:14:30 Creating new PO suggestion for Part:153-802, Attribute Set: '', Date: 7/26/2019 12:00:00 AM, Quantity: 1.00000000 Number: 0
14:14:30 Done with New Suggestion transaction
14:14:30 Processing stock transactions for Part:153-802. Attribute Set: ''.
14:14:30 Beginning Balance 0
14:14:30 Done with Part 153-802. Attribute Set ''.
14:14:30 Done with Part 153-802.

Valid suggestion:

13:50:31 Processing Part:149-352. Attribute Set: ''. V600
13:50:31 Processing Part:149-352 Attribute Set: '' Site:MfgSys Contract:.
13:50:31 Parameters: Receive Time -> 0; Planning Fence -> 0; Delta In -> 0; Delta Out -> 0; Lead Time CutOff -> , Use Dynamic DOS -> True, Allow Consume Min -> True
13:50:31 Deleting suggestions
13:50:31 Processing non-stock transactions for Part:149-352, Attribute Set: ''.
13:50:31 ProcessJobPOs
13:50:31 Creating new PO suggestion for Part:149-352, Attribute Set: '', Date: 6/15/2022 12:00:00 AM, Quantity: 1.00000000 Number: 0
13:50:31 Done with New Suggestion transaction
13:50:31 ProcessJobPOs
13:50:31 ProcessJobPOs
13:50:31 Creating new PO suggestion for Part:149-352, Attribute Set: '', Date: 7/6/2022 12:00:00 AM, Quantity: 1.00000000 Number: 0
13:50:31 Done with New Suggestion transaction
13:50:31 ProcessJobPOs
13:50:31 Processing stock transactions for Part:149-352. Attribute Set: ''.
13:50:31 Beginning Balance 0
13:50:31 Done with Part 149-352. Attribute Set ''.
13:50:31 Done with Part 149-352.

image
image1643×323 38.9 KB

8

As far as I know ProcessJobPOs are for buy direct items. We don’t use them, but when I checked my regen log I had over 150 direct suggestions, so thanks for helping me find them. Have you thought about running the refresh quantities process in test to see if it has the part and fixes it.

https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=6b40d7be1be4b348e596a79b2d4bcb1b&table=kb_knowledge

9

Yes actually I just ran the Refresh Quantities and Allocations report for that a couple hours ago, it found several items, but not these bad suggestions. I am going to run update at EOB today.

I did find the source of the bad suggestions - they are from bad PartDtl records. In my case the PartDtl records point to the wrong (nonexistant) assembly sequence on a job. Looks like this ends up as blanks on SugPoDtl.

There are lots of posts here about corrupt PartDtl rows, and how Epicor has various datafixes for them. I’ve sent in a request to get one.