Automatic Pack in Inbound process

[Former Member]

Hi,

While working with pack specification I encountered with one error in inbound process.

Process scenario is as followed.

The each of product is packed into a packaging material which creates a HU(small box).

subsequently each 10 PCS of above HU's are packed into another HU(Pallet).

packaging specification is maintained with two levels.

ERP system I have created inbound delivery of 12 quantity and distributed to eWM system.

in eWM system according to packaging specification system has generated two HU's.

first top HU - 1000 contains ten low level HU's and second top HU 1001 contains two low level HU's.(worked as expected)

after confirmation of unloading task goods are available at staging area and new 2 tasks are generated.

source is staging area and destination is final bin.

Here system has created two new HU's for two tasks. ( do not know why this was happened?). Ideally the source and destination HU should be 1000 and 1001 for individual task.

when I check any one of the new HU system is taking to me HU details screen and I can see that

top HU is 1001 and low level HU's are new Handling Units.

when I tried to confirm the final putaway task system is throwing error as HU xxxxxxxxxx has a reserved quantity; HU withdrawl not possible

and from monitor when I click on HU details I have my own HU's 1000 and 1001. 1000 HU is with 10 low level HU's and 1001 is

with two low level HU's.

thanks for your time and valuable inputs..

[Former Member]

Hi Steve

Check  at source and destination storage type.

HU Picking Control

The HU Picking Ctrl indicator controls how the HU should be affected if a full

homogeneous pallet (i.e., containing only a single quant with the entire quantity

having the same stock data) will be removed from the bin. Options include:

>>Adopt Source HU with Lower-Level HUs into Pick-HU The source HU is adopted as a lower level HU onto the destination pick HU during

the task confirmation.

>> Propose Source HU as Destination HU The source HU is adopted as the destination HU during the task confirmation.

>> Warehouse Process Type Controls Proposal for Destination HU The settings in the storage process control the proposal for the destination HU. The storage process control settings can be accessed in the IMG by following the menu path Extended Warehouse Management • Cross-Process Settings • Warehouse Task • Define Warehouse Process Type. For the assigned storage

process of the warehouse task, the Control for HU Pick indicator is used to determine the destination HU proposal.

>> Only Adopt Contents (Prod. and Lower-Level HUs) into Pick-HU Only the contents (the products or the lower level HUs) of the source HU are adopted to the destination pick HU.

I hope you issue will resolve with this setting...

Your reply is awaited.

Regards

Suraj

[Former Member]

Hi Suraj,

If we consider the case 3

>> Only Adopt Contents (Prod. and Lower-Level HUs) into Pick-HU Only the contents (the products or the lower level HUs) of the source HU are adopted to the destination pick HU.

After creation of picking task only low level HU's will be copied to PICK HU.

If the source HU is a nested HU we need to provide the low level HU manually. - correct me if I am wrong.

How exactly this is integrated to outbound process? TOP HU is pallet contains 10 low level HU's of cartoon. Each cartoon contains 4 pcs.

Now I would like to pick 2 cartoons from the pallet as always selling unit is cartoon.

I created delivery for 2 cartoons and distributed to eWM. when I created a task , only one task is generated for 2 cartoons. I created PICK HU for picking 2 cartoons.

As it was only one task for 2 cartoons I cannot provide the 2 low level HU details in confirmation screen.

Thanks for your time and help..

[Former Member]

Hi  Nicoleq,

>> Only Adopt Contents (Prod. and Lower-Level HUs) into Pick-HU Only the contents (the products or the lower level HUs) of the source HU are adopted to the destination pick HU.

After creation of picking task only low level HU's will be copied to PICK HU.

If the source HU is a nested HU we need to provide the low level HU manually. - correct me if I am wrong. >>>Correct  As per SAP.

Second case need to check whats happening...

Regards

Suraj