cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with manually entering batch split in delivery (system message LB 046)

Former Member
0 Kudos

Dear forum

We have a delivery in which the batch determination for a material is already performed.

However, we are not happy with the batch determination for the material, so  we go into the batch determination (in transaction VL02n) for that material (by pressing the Batch Split button for the selected line item in the delivery).

Then we enter the batch split details screen and press the "New Batch Determination" button.

Then the Batch Determination SD: Select Batches screen appears and we manually start to enter quantities for the batches we would like to include in the batch split. All the batches are available in stock.

And now comes the problem:

For Material A we have a batch 24084 which has a batch split quantity of  8547 EA (this quantity has been determined by our batch determination-the batch search selection criterias)

.

When we manually try to change this value to a lower value (becuase we do not simply want to ship the 8547 EA, instead we want to ship 4356 EA of this batch to our customer), the system sets it back to the 8547 (the higher number) with the system message:

"The available quantity of batch 24084 was corrected to 8.547,000 EA

Message no. LB046"

Why is the system forcing back our manually entered value to the original values?

Brgds,

Lars

Accepted Solutions (1)

Accepted Solutions (1)

Lakshmipathi
Active Contributor
0 Kudos

Check whether the following note helps you:-

  1. Note 1167139 - Batch deter underconf during deliv creation; wrong TQAs
  2. Note 1644718 - Error message LB046 during quantity change in batch split

G. Lakshmipathi

Former Member
0 Kudos

Hello G Lakshmipathi the Note 1644718 solved our problem.


Thanks!

Lakshmipathi
Active Contributor
0 Kudos

Happy to note that your issue is solved.  By the way, please close this thread as "Answered".

G. Lakshmipathi

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Lars,

Have you checked if the "change allowed" indicator is set in your batch search strategy (Transaction VCH3)?