3 weeks ago
We have a business requirement to print HU labels after picking and packing. We want to print the label after the material has been committed to the Handling Unit (not at HU creation).
Looking at OPD, I don't see an available option to represent this. It looks like there is a flag for 'HU Task exists'. This should work, as when the material is committed to the HU, it also creates the drop off HU Task. However, this doesn't seem to trigger our outputs.
Is there an OPD trigger for Handling Unit output type to trigger HU label creation at product WT confirmation?
Request clarification before answering.
Hi @Markas ,
since you want to print during warehouse task confirmation, have you already tried to work with warehouse order documents? I would assume, this form also has all the information you need and you can adjust the form layout as needed. The printing should be called also during warehouse task confirmation.
Best regards,
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are right, that the print is generally for the warehouse order but since the warehouse tasks are a child of the warehouse order, the printing is also triggered during warehouse task confirmation.
If you set up the OPD to print for warehouse order status "D", then printing should be triggered for the confirmation WT 1-49, if you additionally set up to print for status "C", then printing should also be triggered for the confirmation of WT 50.
For the confirmation of WT 1-49, the form data provider will pass all open warehouse task. So for example, when confirming WT 1, the open warehouse tasks 2-50 will be passed to the form. To my understanding when confirming WT 1 you want to print for WT 1 - which is exactly the WT which is not passed to the form. To achieve this you can implement BAdI /SCWM/EX4_OM_WHO_EXTEND_WT to read the confirmed warehouse tasks for that warehouse order from CDS view I_EWM_WarehouseTask_2. For WT 1 the logic would be easy, because there is then only one confirmed WT. To make sure the logic also works for WT 2-50, it is probably easiest to sort the confirmed warehouse task descending by ConfirmationUTCDateTime.
I hope this helps.
Best regards,
Christian
@Christian_Ries yes, this is exactly the strategy we are doing in our new design of sorting descending after reading confirmations too, and the one extra step is to remove tasks by other users because in our case we may have multiple pickers working on the same WO.
User | Count |
---|---|
5 | |
3 | |
3 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.