cancel
Showing results for 
Search instead for 
Did you mean: 

Overpicking without Pick Point

amol2105
Explorer
0 Kudos
604

We have a scenario to pick only unit ( Quantity Classifier= U ) quantities from a bulk storage type. This picked quantity needs first to be transferred on a truck ( configured as a normal storage type ) and then moved to the repacking area where we need to repack a smaller quantity from the picked HU to be sent to other plant via a STO.

Configuration:

1. Source Storage type: Bulk Storage with rounding rule 4 ( round up to multiple of units )
2. Truck : a general storage type
3. Repacking storage type: Workcenter

LOSC 1: B401 to GI-ZONE with Intermediate TRUCK

LOSC2: TRUCK to Gi-ZONE with intermediate REPACKING AREA

We also use packspec with reocrd 0WHT so that with quantity classifier U onlu units are picked while task creation.

Issue is while i try to create my first task with a STO of suppose 4 KG and my unit quantity being 181 KG i get the error "warehouse request X: Line item X should not be overpicked"

Accepted Solutions (0)

Answers (2)

Answers (2)

schulte-bahrenberg
Contributor
0 Kudos

...for me the error message rather sounds like a wrong customizing for the pick-point. The process itself is a pick-point process so the full HU should be moved to the repack work-center and once the 4kg are re-packed moved back to stock I assume!?

So have you checked that pick-point settings in the storage types as well as LOSC are correct? Do you have a HU WT for the full HU and a waiting product WT for the 4kg?

Ajit_Routray
Active Contributor
0 Kudos

Hi amol2105

Did you try with Exception Code ? If not, please check the below KBA OSS as example.

2792780 - ODO is blocked after confirming a picking WT with exception code DIFS

Kind Regards

Ajit

amol2105
Explorer
0 Kudos

Hello Ajit,

Thanks for your suggestion. But the issue is my warehouse task is not getting created in the first place. The desire is even though STO quantity is 4KG suppose the task should be created with unit quantity of 181 KG as my round up rules at storage type level and quantity classifier in packaging specification are in picture.

Thanks & Regards,
AMOL PATIL

Ajit_Routray
Active Contributor
0 Kudos

Hi Amol

My apologies, missed the phrases in your question.

I think bulk means pick the whole quantity so rounding rule would be whole quantity (Guess 2). If you have different SKUs, then try to maintain different Storage type...so that it would be easy during picking and also adjust Warehouse Process type rounding rules accordingly.

Please let us know if further questions.

Kind Regards

Ajit

amol2105
Explorer
0 Kudos

Hello Ajit,

According to your suggestion with rounding rule 2 ( Round down WT to single unit ) the task is getting created for 4 KG itself. That's where the constraint is. Is there any that i can create task of 181 KG in the first place which is my Unit level ( first level ) quantity?
Physically there is no possibility that the user take 4 KG out 181 KG at the picking area itself. They have to take it repacking area which is far away from the picking bin and hence they need a truck in between.

Thanks & Regards,
AMOL PATIL

Ajit_Routray
Active Contributor
0 Kudos

Hi Amol,

Please maintain below if Quant is 181 KG.

In Storage type for Bulk- rounding rule 2 ( Round down WT to single unit )

In Warehouse Process type - rounding rule 5 ( Available Unit )

I guess WT would create 181 KG, could you please try and let us know outcome.

Kind Regards,

Ajit

amol2105
Explorer
0 Kudos

Hello Ajit,

The suggested change did not workout. System narrowed down on Quantity classifier U but the quantity chosen was full pallet quantity and not unit quantity. The basic issue still stayed the same we could not pick more than what is already there in warehouse request.

Thanks & Regards,
AMOL PATIL

Ajit_Routray
Active Contributor
0 Kudos

Hi Amol

As per my understanding, It seems you need BADI to manage this requirement since you dont want Pick Point and in the same time selective quants/stock have to pick to fulfill the requirement.

Kind Regards,

Ajit