Skip to Content
0

Is destination HU required while repacking a product with multiple units of measure?

Mar 12 at 06:17 AM

125

avatar image

In the SAP EWM /scwm/pack transaction, I try to repack a product from one storage bin to another. There are 2 scenarios, one where the product has just one unit of measure, and the other where the product also has an alternate unit of measure.
In the Repack Product tab, the details about Src HU/Bin, Product, Quantity and Storage bin are filled. Upon execution, the product with a single unit of measure gets repacked without any issue. But for the product that has 2 units of measure, an error is raised about initial input in case of destination HU. Why does this happen? Is the destination HU check necessary for repacking a product which is being repacked from one storage bin to another?

inputs.png (23.7 kB)
erroroninput.png (2.8 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

shailesh mishra Mar 12 at 01:07 PM
0

Hello,

It might be possible that when repacking the product with alternate UOM, system is rounding up the quantities and hence source Stock HU is not equal to destination Stock HU, so quantity difference. Please share the UOM conversion maintained in product master whether they are in decimals??

Best regards

Shailesh Mishra

Show 2 Share
10 |10000 characters needed characters left characters exceeded

The quantity conversion and related checks all happen AFTER the check for the destination HU. The crux of the issue is why the destination HU is checked in the first place. Because the repacking is from one storage bin to another, and there is no HU involved.

0
Former Member

Hi Deshpande,

Just out of curiosity I am asking this question,

If you are moving product from one bin to another why are you using /SCWM/PACK. This transaction is to repack product or HU in another HU isn't it? If you want to simply move the product from bin to bin is it not preferable to use internal movements with /SCWM/ADPROD transaction?

Please pardon if my understanding is not correct.

Thanks & Regards,

Aswatha Narayana

0
Ajit Routray Mar 13 at 09:03 AM
0

Hi Awantee,

It might be the cause of Pack spec or pack material or consolidation group etc.. etc...not sure the exact reason.I guess the default class/method execute to find the destination HU (Class: /SCWM/CL_EI_WRKC_UI Method: /SCWM/IF_EX_WRKC_UI_DET_HU~FIND_DEST_HU) .

BADI: /SCWM/EX_WRKC_UI_DETERMINE_HU

Kind Regards,

Ajit

Show 3 Share
10 |10000 characters needed characters left characters exceeded

But if there is no HU involved in the repack process, why does the check happen when there are 2 UoM, but not when there is just one?

0
Awantee Deshpande

Hi Awantee,

Sorry, never checked without HU, need to check in my system .It seems the process of unpack is having some converting issue from Alternative to Base UOM.

-> Did you maintain preferred UOM in Product Master?

-> Did you try in RePACK HU Tab ?

Kind Regards,

Ajit

0

Hi,

Sorry for the delayed response.
Yes, everything pertaining to the UoM has been maintained. And I am using the Repack HU tab.

There is another issue that comes into picture with the involvement of the pack material.
The scenario involves having more than one UoM with
1. Neither pack material nor destination HU specified
2. Pack material is mentioned but destination HU is not

At least one of these situations leads to the 'Input parameters initial. Cannot read any HUs' error every time.
Is packing supposed to be allowed in both cases? Because with a single unit of measure, there is no issue.

0
avatar image
Former Member Mar 25 at 05:19 AM
0

Hi Awantee,

I am stuck on the same issue. Are you able to find the answer to this question?

Regards,

Pooja

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi, I found out that if the product is relevant for stock specific unit of measure, then the destination HU is checked for quant conversion compatibility. However, this check is not required if destination HU is not involved, so that part of the code can be skipped, and the issue is resolved.

0