EWM - Print labels and pick-HUs

[former_member524593]

Dear EWM Gurus

Client requirement is to print production staging labels.

We have developed a custom form we trigger from PPF PRWO6 every time a task with a certain WPT dedicated for production is completed.

Label is triggered and printed correctly each production wpt tasks is completed via a copy of WO_MULTIPLE action definition.

Nevertheless, in the scenario where user confirms warehouse task while using pick-HU, system generates two separate tasks :

· - One for source bin

· - One for destination bin

Therefore, the initial task triggers 2 actions definitions and thus, is printing two identical labels for a single item.

Do you have in mind a way to solve this issue by restricting/limiting this “sub-task” creation (keep one task for source & destination bin) for example or something else.

Thank you again for your valuable support

[former_member788724]

Hello

That's a real problem when you have WO print by WO_MULTIPLE action definition.

Everything will work fine when you confirm by warehouse monitor 🙂

When you confirm in RF then you will always get this double print issue. It will be even more interesting when we have multiple WT's in a WO and with HU's. RF normally adds one new sub task when we confirm the WT that is normally to put stock from resource to destination storage bin.

and yes- this sub task creation can't be stopped in RF.

What we did in our project was- we had stopped this sub task print in BADI used for printing.

Now I don't remember exactly what logic we had put to add missing data like destination bin etc. in the main task , as destination bin details are available in the sub task only. so you need to find a logic to map main task with sub tasks and delete sub tasks later from print buffer. Our developer used one BADI(SAP standard) where he was able to manipulate all these data.

For our project, we triggered the print when all tasks of the WO were confirmed. This was also controlled at program level (I don't remember this very well now 🙂 But we had issues sometimes that even if all tasks were not confirmed , we used to get print.) We had explored the logical condition to print only when WO is confirmed, but somehow it was not working for us at that time. Now I suggests to go paperless only for all warehouse activities 🙂

Regards

ASLAM

[Daniil]

Hi gcourregesz,

it should be one WHO, and you can use WHO conditions and not RF conditions for this.

RF Conditions are usually for Print Function code (explicit), still I would expect to have two different steps of you say about confirmation of the second WT. Maybe it is printed two times for confirmation and for WT creation? Should be visible from the timestamp or you can see how many printouts do you have after you confirm first step. If both printouts are coming from the first step you can try to use second step (if it fits, it be only one wt for pick HU).

And/Or you can try to limit amount of actions in Customizing. But I would suggest to switch to SAPWO001 table.

You can try as well Logical conditions, but I guess it wont help, If I remember right system uses first wt of the who.

And it is a badi available to suppress printing if I am not mistaken.