Pick Task Error

We have multiple pick tasks that failed with the error “Already Fulfilled/Commitment Changed.” The error was generated when the task was attempting to be done and the SO does show the line item is picked and committed. The SO has since been billed and marked fulfilled, but this was after the failure message was generated.

We made sure the bin putaway was run as I know a lot of pick task errors result from this. Anyone have any insight?

Edit: One thing I thought of was that the pick task is occurring from multiple bins. So if they need to pick 1000, there may be bin A with 333 qty, bin B with 333 qty, and bin C with 334 qty. I’m not sure if that’s causing the issue.

Rookie Asked on December 8, 2023 in Order Management.
Add Comment
1 Answer(s)

You may have solved this already, but if the failure states “already fulfilled/Commitment Changed,” open the wave and a corresponding pick task. Hit “Retry Updates” and it should move to “Done” status. Refresh the WAVE and it should show as “Complete.” I had this similar issue last week with some backorder and approval issues, but after doing these steps the WAVE failures went away.

Rookie Answered on March 12, 2024.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.
  • This site made possible by our sponsors:   Tipalti   Celigo   Become a Sponsor   Become a Sponsor