cancel
Showing results for 
Search instead for 
Did you mean: 

Different stock view in LX03 for picking TO

sahana_ps
Participant
0 Kudos

For a sales order with stock quantity 10, I created a partial delivery for quantity 3.

Initially the stock in LX03 :

Stock Available Stock Put away stock Pick Quantity

10 10 0 0

1st Case: After Creating a Transfer order (which is not confirmed yet), in LX03, there are 2 lines

2nd Case: After Creating Transfer order (which is not confirmed yet), in LX03, the same line is updated with the stock quantity.

The difference what I can only notice is the storage type and bin in both the cases.

Can you please help me to understand that due to exactly what configuration we have different view in LX03.

Accepted Solutions (0)

Answers (3)

Answers (3)

raghug
Active Contributor

I think for the first one (ST2) you have bulk storage turned on - that would be the putaway strategy 'B' against the storage type. When you do that, it does not hard allocate the material from an SU. The LX03 display is from table LQUA. If you want to see the requested pick quantities against the bin, use table LQUAB, you will see your material / quantity request with no batch in the table LQUAB.

The second is a more standard scenario where the pick quantity is immediately assigned to be picked from a specific SU. I am guessing you don't have a bulk strategy for this ST1 storage type.

raghug
Active Contributor
0 Kudos

It is because of the putaway strategy, not the picking strategy (A little confusing, I know).

The advantage of using the bulk strategy is that the TO only directs you to a bin, not to pick the exact quant. This way, you are allowed to change the SU or Batch of the material you are picking and just tell SAP during the confirmation. The idea is that in Bulk locations, there is a lot of material and it will not be possible (or efficient for the user) for SAP to direct the user to pick a particular SU and Batch.

If the putaway strategy is not bulk, the assumption is that SAP has enough information to direct the user to pick an exact batch from an exact SU.

In this case, you have to base put away strategy being bulk or not, on your requirements for picking.

If your requirement is to just show the pick requirements in LX03... you will have to create some sort of custom report with multiple levels. For example, you can run into this scenario...

  • Bin A
  • Pick Requirement = 3
  • SU 1 - Qty = 10, Batch = 123
  • SU 2 - Qty = 5, Batch = 123
  • SU 2 - Qty = 5, Batch = 456

In this case, you don't know which SU or batch the user is going to pick - so it is not possible to have a single line describing the pick. The user can pick from either SU1 or SU2, and if from SU2 they can chose either Batch 123 or 456.

In your ST1 scenario, the TO may already say pick 3 from SU 2, Batch 456 and you have no way to override.

sahana_ps
Participant
0 Kudos

Hi Raghu,

Thanks for your reply.

Yes. You are correct. In ST2 Putaway strategy is Bulk storage.

But still I have a question. We are picking the stock from ST2 so picking strategy will be considered. And for both the storage type F is the picking strategy.

So due to which config we see this change. If it is due to putaway strategy, then can you please explain more.

In both the transfer order, the destination storage type is dynamic bin ( Delivery no.).

Can you please help.