Warehouse Task Update after Aborting Confirmation

[former_member740704]

I have a requirement where I need to update the destination bin of the Warehouse Task after failing a certain check and aborting the confirmation.

I am doing the check and preparing the update in /SCWM/EX_CORE_CO_IMPORT, and then doing the check and aborting the confirmation in /SCWM/EX_CORE_CO_CHECK_CONF with an error message.

After aborting the confirmation, I can see that the change to the destination bin is not updated in the Warehouse Task yet. I also see that only by CONFIRM+SAVE and without erroring out the confirmation does the changes get updated to the Warehouse Task.

My question is: is there a way to update the Warehouse Task with my changes after failing the first confirmation so that the user can simply press confirm again a second time and pass the confirmation as the destination bin should now be updated for the Warehouse Task and thus passing the check? We need this all be done in the background (that is why I'm using the CO_IMPORT BADI), so no foreground manual manipulation of the Warehouse Task is allowed.

[Daniil]

Hi Kevin, there is always a way 🙂

Wont it be bettor instead of error and pressing second time to show user hint (Pop-up message) that it is not possible to confirm as is and ask if he would like to change destination bin, and to change it with exception code for example (if this is possible in your badi).

I guess it is done in the /scwm/TO_CONF transaction. I guess standard does rollback in case when WT confirmation fails, and therefore your changes are not saved.

[former_member740704]

Like I mentioned, the user is not suppose to change the destination bin. It should automatically have changed after the failure of the first confirmation try.

I agree that it would be better to have the user change it themselves, but this requirement is passed to me to implement so I have no say in the process unless I can convince them their original requirement is impossible with how SAP has implemented WT confirmation.

[Daniil]

Hi Kevin, I meant that you have an option to interact with user. So you can show him pop-up "Confirmation to the required bin is not possible", and buttons "cancel", "use other bin". and with other bin you update ct_conf and/or ct_conf_exc with exception code and you update the bin. No need in this case to update WT in the database before confirmation. Or you can 'remember' failed WT numbers when user tried first time and you can add exception code for such WTs with a confirm + save.

[former_member740704]

For the first method, I'm not sure how to have buttons enhanced for WT confirmation. Also, additionally this will be mainly through the RF gun so is it possible to have the button if it's done through the RF gun?

For the second method, I don't think I am allowed to create a Z table to remember the failed WT.

[Daniil]

Hi Kevin, I meant an internal table, and not database table. If ti is from RF, you can do everything, you can replace standard FM with your own and implement needed logic.