2024 Aug 08 11:18 AM - edited 2024 Aug 11 3:52 PM
Dear Experts,
We are encountering an issue while following the process of canceling the Goods Issue (GI) of production orders using the HUCANC transaction and deleting the assignment to the production order using the COPAWA transaction. The process, which previously worked, is now failing, with the system returning the message: "No materials have been picked" (SAP message VHUMI 131).
I have attached screenshots of the error message, the Handling Unit (HU), and the production order for your reference. Could you please advise on how to resolve this issue? We are operating in an ECC environment.
Thank you for your assistance.
Hello @pradeepkumar21
I think your HU is not assigned to a production order anymore. Thus, you can't delete the assignment in COPAWA.
If the HU was picked, it would have status RESV, but it has statuses PHEX and WHSE.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @pradeepkumar21
Indeed, the value of 08 "Work Order for Components" in VEKP-VPOBJ indicates HU assignment to a production order. However, I'm not entirely sure how this field is updated when a HU is issued to a production order and when the goods issue is cancelled subsequently. It's quite possible that the value is not updated. Thus my assumption that the HU is not actually assigned to the production order anymore is still valid.
You can't delete the assignment in COPAWA as the assignment is not visible there. That again reconfirms my assumption that the HU is not assigned anymore.
To validate that I'd suggest to try to assign the HU to another production order with COPAWA. If that is allowed, it means you don't have any problem and that the HU is simply not assigned to the production order after the goods issue cancellation with HUCANC. If on the other hand, you get any issues with the HU assignment to another production order, e.g. a message that the HU is already assigned, then I'd suggest to rise an incident to SAP support as such an error message would indicate data inconsistency.
Best regards
Dominik Tylczynski
User | Count |
---|---|
88 | |
8 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.