Mystery Orphan PO?

Kinetic ERP
1

I’ve got about 100 Orphan POs in our Generate PO Suggestion Log, some very recent. I can’t figure out why they are orphaned.

In checking a simple part:

  • The PO Release Job/Asm/Mtl qty matches the Job/Asm/Mtl qty.
  • PO is closed.
  • Material has the green checkbox on the job.
  • Job is open.

There is an entry in the Job change log where the original material seq# was deleted. Another material was added in the same spot. But then 3 days later the PO was cut; everything lines up currently…

Any ideas why it is still being seen as orphan? Thanks!

FYI I can’t find anything in Epicor help. Below best info I could find but doesn’t explain my issue…

2

I’m seeing that PORel.PORelOpen and PORel.OpenRelease sometimes don’t match. Anyone know the difference between the PORelOpen and OpenRelease columns?
Descriptions listed in Extended Properties Maintenance don’t help.
I have 164,000 lines where the two columns match, and ~1000 where they don’t (1 and 0 or 0 and 1).

If curious…

select t1.PORelOpen, t1.OpenRelease, * from POHeader t0
join PORel t1 on t1.Company = t0.Company and t1.PONum = t0.PONum
where t1.PORelOpen <> t1.OpenRelease

Edit - PORelOpen looks to be unused currently. It’s set to 1 on some old POs, but is set to 0 on all new POs, regardless of status.

3

Alright I think I got to the bottom of it. In addition to Open POs on Closed Jobs, I’m seeing these also count as orphan:

  • Open PO, Open Job, but Closed Order Release
  • Open PO, Partially Received, and PO is Past Due.