Question

Open Orders stopped going into Fulfillment workbench

  • 16 April 2024
  • 3 replies
  • 44 views

  • Participating Frequently
  • 9 replies

We have had this happen twice in approx six months.  Fulfillment workbench will be empty, previously thru the day orders will be going thru populating the workbench, however there came a time when the next time a user checked, it was empty.  No changes to the system or processes that we are aware of, we are Epicor cloud kinetic environment.  We check, and we have orders that should be in the fulfillment workbench, ready to fulfill is checked, etc.  We aren’t doing anything different then when everything is working.

Then after some time, this time it was less than an hour, but the first time (six months ago) it was a few hours, it will let new orders that are entered, they will show up in the workbench.  Previous Open orders (that are still open) are not showing up in the workbench.

The only way we have found to get them into the workbench, was to change the shipby date, save (we do change it back and click save again just to keep the order information correct), and then the order will show up in the workbench. 

Whatever is happening, it does affect open SO, open PO, open transfer orders, so it is a huge impact, and takes us a while to get it all straighten out.  Thankfully this has only happened twice, but i am trying to be proactive to prevent, but have no idea why it happens in the first place. 

Epicor Support doesn’t have any ideas why or what would stop the workbench from getting orders that are ready to go into the workbench, we haven’t been able to get support into the environment before the initial issue goes away.

I am curious is anyone else has had something like this happen before? and if so, did you happen to figure out what the catalyst was to start the whole thing.

Thanks for any insight anyone can provide.
Have a great day.


3 replies

Hi - Do you run MRP?  If you have it defined, what is your unfirmed job prefix?

 

@connie.peters Yes we have schedule for MRP, and it runs the same settings it has for a few years.  And this particular “freeze” happened approx 1-2 hours after the last MRP ran. 

We did run a manual MRP after noticing this freeze, thinking maybe something had a hiccup in the process, but no change.

We had a similar issue several years ago but this doesn’t sound the same.  I’ll share our issue with you just in case it helps.  For us, MRP stopped running and we found that it was due to the prefix on our unfirmed jobs.  Our Prefix was “UXXXXX” and had been for a couple of years.  The change was that we entered a new customer that started with “U” and for some reason the conflict between the two “U’s” caused MRP to stop running.  We changed our unfirmed job prefix to “UNFXXXX” ran MRP and our jobs generated in the fulfillment workbench as expected.  Hope you find answers soon!

Reply