Has anybody else using Requisitions seen their Req status not updating to “Ordered” after the 2024.1.15 update?
I ran a BAQ to see if I can see anything odd, but it appears that since Monday the 28th (following the .15 update) all of our Requisitions, even though they have PO records against them, are not updating to a Status of “Ordered”. They’re stuck as “Approved”.
This is becoming a nuisance as users are monitoring their requisitions and calling Purchasing to ask why their parts weren’t ordered. In fact, they HAVE, but the status is not updating.
Everything before 10/28 appeared fine. Everything after… stuck as “Approved”.
We don’t have a multi-step requisition process (multiple actions). As soon as it is dispatched, it is set to approved and sent to Purchasing and they either order or don’t.
Epicor has this bug as PRB0289589 and they’ve got a fix planned.
For us SaaS peeps: “The 2024.2.10 release is scheduled to be released in your pilot between 2/18 and 2/19, and to be released in your live environment the weekend of 2/22 and 2/23.”
Nice find. I was looking everywhere for the related PRB.
Appears the problem still exists in 2024.2.8 (I’m still in 2024.2.7). They say complete, but it would be nice if they included the update in which it will BE fixed.