Skip to Content
0

LS26 has two different lines

Mar 21, 2017 at 08:22 AM

61

avatar image

Hi All,

Please check screenshot below from LS26. I have created outbound TO against delivery for 18 PC.

Negative stock removal is allowed and material is fixed bin.

Can you explain why different line with negative quant is created eventhough stock was there in first line?

Thanks

ls26.jpg (38.5 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Manish Kumar Mar 21, 2017 at 08:47 AM
0

Please share the Transfer order detail for the bin using T-code LT26

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

lt26.txt

Hi,

Please find attached LT26 list for new example with same bin below.

lt26.txt (68.2 kB)
ls26.jpg (44.7 kB)
0
Manish Kumar Mar 21, 2017 at 10:53 AM
0

Can you please attach the LT26 result once again, I am unable to read the file (lt26.txt) which you have uploaded it is better if you can capture the screen and share rather then .txt file

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

Hi,

Please check if it is visible now? I have attached again.

lt26.txt (68.2 kB)
0
Manish Kumar Mar 21, 2017 at 11:04 AM
0

I am getting the below attach screen image when I open the txt. As requested earlier please share the SAP screen


arpvs.png (8.4 kB)
Show 2 Share
10 |10000 characters needed characters left characters exceeded

Date is huge. So uploading recent TO information. Please check and let me know if this is sufficient.

lt-1.jpg (96.0 kB)
lt-2.jpg (89.0 kB)
lt-3.jpg (77.5 kB)
0

Hi Suresh,

Purpose for asking the LT26 is to compare how much you received in storage type 100 and How much got dispatched out from storage type 100, either you can perform this activity at your end which will answer your query the reason for negative

or

Could you please filter the report output at Batch (batch number shared earlier where you have negative quantity 0000031615) level and check the size of output record and if possible please share

0
Jürgen L
Mar 21, 2017 at 11:52 AM
0

I don't see any matching data to your initial screenshot, which had storage bin 04-114-1 and your second screenshot has 05-098-2 as storage bin. Also the batch number is different.

If you want to know why you have 2 lines in your initial screenshot then best you compare both records technically in transaction SE16N at table LQUA

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

Hi Jurgan,

Please refer below screen shot.

LS26:

LQUA: I am unable to find out reason why different quants are created at same time.

ls26.jpg (44.7 kB)
lqua-1.jpg (71.8 kB)
lqua-2.jpg (64.8 kB)
0

So far I cannot really see a root cause for having these records next to each other, can just do some wild guesses or ask further questions.

What I see and what confuses me is that all items have the very same delivery number

I also do not really understand why it is storage type 100 when you use deliveries, with deliveries I would expect 916 as storage type.

Can you share a screenshot from your delivery showing these items 150 to 230?

Can you also share a screenshot from document flow of one of these delivery items?

0

Delivery lines:

Document flow for 2 items:

delivery.jpg (51.1 kB)
line-150.jpg (22.2 kB)
line-230.jpg (22.5 kB)
0

the most important information from the document flow is missing: the status column

0

status is completed.

capture.jpg (31.2 kB)
0

one last request: a screenshot from MB51 showing all movements for the material batch combination

0

MB51 for material and batch

mb51-1.jpg (171.3 kB)
mb51-2.jpg (173.4 kB)
mb51-3.jpg (170.5 kB)
mb51-4.jpg (178.5 kB)
mb51-5.jpg (172.7 kB)
mb51-6.jpg (151.8 kB)
0
Show more comments

Just addition to what Jurgen mentioned I see that your system is linked with SUBSYSTEM so you need to look that parameter also is there any mismatch in between the data you supply to subsystem and while receiving back are you receiving any different batch or the code perspective also are you using standard SAP approach to confirm this TO once you receive data from subsystem

0