Packaging material volume not considered in capacity check when putaway to non-HU storage type

[martinprokop]

Hello,

in EWM, the volume and weight capacity check is depending on T_331-HUOBL of the destination storage type (include /SCWM/LPUT_BIN_DETF81, form BIN_DETERMINATION_SINGLE, row 164 and on...).

This means: If the target storage type is without HU-management, but still we create HU-WT to putaway there, system checks the capacity in the target bin considering only /SCWM/HUHDR-N_VOLUME (load volume of HU), not the G_VOLUME (total volume of HU incl. packing material).

It seems not correct to me. I would expect this when planning putaway with product-WT's. In this case it is obvious, the capacity in destination bin will be occupied only by product itself, without packing material.

But in case of HU-WT I would always expect the destination capacity will be checked for the whole HU, including packing material. This should not be depending on HU-management in the destination storage type.

What do you mean?

Martin

[JuergenPitz]

Hi,

the perks of home office. And when other things do not work as they should...

OK, so you have a mixed pallet, but want no HU. You create a HU WT and have selected "Do not Put away HUs" in the destination? No, from what I understand you set "HU Requirement" to "Not allowed" - and I guess this is the trigger. Again, if a HU WT or product WT is not the issue, I would think. But you need to create a HU WT to keep the different products together.

Now when the HU is not arriving in the final bin (and that is why you are trying to tell the system by setting "do not put away HUs" or disallowing HUs) - how should the system then consider the HU dimensions. That does not make sense. Because for something like this we assume that the material is loose or is put into a kind of container which is in that bin (and is effectively the bin).

So I first wanted to write, that I agree, that you should open a ticket - but actually, no, I think the system can only work this way.

From the rest of what you are describing it seems that the real only issue in the process is that during picking the source HU can not be confirmed, yes? This should be manageable by setting up a specific verification profile. I have never tried it this way (usually the problem is the other way around, when there is a HU, you dont' want to confirm the bin), but that should work. Have you tried that? I guess this will only work as long as there is only one HU in the bin.

Brgds

Juergen

[martinprokop]

Hello Juergen,

I am afraid, your assumptions are not correct. In fact we don't have set "do not put away HUs" for the destination storage type.

We just have switched off the HU-Requirement there (HUOBL = Y - "Not allowed").

You may be right, it is probably not the optimal setup regarding HU's. Therefore I formulated it rather as a question, than an error. I just tried to understand it. Probably my understanding of the product-WT vs. HU-WT is different from the author of the concept...

If we decide it is urgent, there is a simple custom solution via Badi /SCWM/IF_EX_HU_BASICS_PRODUCT~CAPACITY

Regarding the HU-management in the storage type concerned:

Yes, I tried to switch it on. I tried to work with verification profiles as well. But especially in our case, when the HU contains multiple products, it brings lot of troubles.

For example during replenishment, we want to take just one single article in specified quantity from the source HU to replenish picking bin (e.g. we want to let the worker confirm only product and quantity at the removal step already). But the system always wanted to move and confirm the whole source HU, remove the required quantity and then to put the rest back away.

Best Regards

Martin

[JuergenPitz]

Hi,

*** I just see one thing: you are describing a problem with the volume - I only checked the weight. So there might be a bug. But otherwise I would expect everything I wrote below is true for volume as well***

"If the target storage type is without HU-management, but still we create HU-WT to putaway there, system checks the capacity in the target bin considering only N_VOLUME (load volume of HU), not the G_VOLUME (total volume of HU incl. packing material)."

First question: why would create a HU-WT? Or is that not the final storage type?

And at least in my quick check (target storage type has no HU requirement, but I create a HU-WT): the capacity check worked ok, the weight from the packed HU was used.

"would expect this when planning putaway with product-WT's. In this case it is obvious, the capacity in destination bin will be occupied only by product itself, without packing material."

Why should that be??? A product-WT does NOT mean that the product can not be packed. If the product is in a HU, the HU is also moved with a product-WT.

"What do you mean?"

Double-check and try ;.). I did not try to read the coding, but when testing the process it works in my system. If it does not in yours, I would check for notes or open a ticket...

Brgds

Juergen

---
Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[JuergenPitz]

Hi,

ok, I now I have tried with volume: and (as expected (or at least hopped)): the same result. The volume of the HU is considered, with HU or with product WTs.

Brgds

Juergen

[martinprokop]

Hello Juergen!

First of all: many thanks for your quick response! It is motivating! 🙂

To your questions: Our scenario is we have multiple products, packed on an Europallet. We want to move the pallet as a whole HU and find a destination bin according to its total volume. However, we do not want to keep the HU in the target storage type (/SCWM/T331-HUOBL = Y), as it has further consequences (system requires HU confirmation during removal, but the pallet label is not there anymore etc.). The pallet with its content will really be physically placed in the bin and occupies its total volume (G_VOLUME). First with removal of the last product from the pallet, also the Europallet will be removed from the bin an it remains empty.

I have tried this scenario many times very thoroughly and found a place in coding, where it is very clearly stated (concerning both volume and weight):

1. Include /SCWM/LPUT_BIN_DETF81 form BIN_DETERMINATION_SINGLE row 161:

- here the system decides about value for cs_ltap-movehu

- depending on LS_T331-HUOBL = Y the value movehu is re-set from A to B.

- For all other HUOBL values, the movehu remains = A

2. FM /SCWM/TO_HU_INT row 333: Determine moved capacity

- here the system decides depending on movehu value, if the capacity will be checked for product content only of for a whole HU:

--- in our case: movehu = B -> PERFORM prod_capa_determine2 - checks only the HUHDR-N_VOLUME

--- in case movehu = A -> PERFORM hu_capacity_determine - checks the total HU volume HUHDR-G_VOLUME

The fact, the WT is a HU-WT (flghuto = X) DOES NOT AFFECT the capacity check.

Best Regards

Martin