PO Receipt Error - No PO releases found to process within mass receipts

I’m testing out how to do Mass Receipt within Receipt Entry and receive this error although the items are open items. I’m guessing it is something simple that I’m missing. Maybe it is Thanksgiving Hangover and I haven’t recovered yet. lol

If it’s like mass issue it won’t work on lot tracked parts.
Also make sure you are in the correct site maybe?

Hi Mark,

I’ve read that, but it seems to be a hit and miss. I’ve got parts where they work and I can do next lots and it prompts for just the heat numbers for the parts that are on those lines.

Then other POs I get that error. Not sure why it hits on some and not others.

All parts are set as lot tracked.

I appreciate the feedback. I’ll dig further. Maybe they are not all lot tracked as a I thought and that is why some are working.

Thanks again,
Randy

Did you ever figure this out @rholndoner ? We started getting this error for a bunch of POs just last week, apparently had not seen it before.

Hi Adam,

We never found out what was causing it. I couldn’t find how it was a lot issue because all parts were lot tracked, although all documentation pointed to that, along with what Mark said above.

We have not gone back to find a resolution. Not enough resources to spend the time on it, unfortunately. I wish I had a better answer. :frowning:

@rholndoner - I found a KB article on EpicCare that mentioned getting the error consistently if you have a Job in your system with a blank Job Number (i.e. JobHead.JobNum = '' ). I ran a quick query and sure enough, that’s what we had going on!

Requested the data fix, which renames the job so we can actually open it in Job Entry and delete it out of the system, and now we’re back in business being able to do Mass Receipts!

Here is the KB Article on EpicCare: KB0132484

And our Case Number just in case someone else needs to reference this: CS0005075991

2 Likes

Oh Wow! Nice! I’ll have to look at that and see if we are running into the same problem. Thanks for the update, Adam!