Different results for the same action in MI10

[Former Member]

hi gurus!

im new in this module and im having an issue with MI10 transaction, there are some materials where the difference get posted, but others where the total ammount gets postes.

for example:

Material 005 has -100 units

Material 006 has -100 units

if i use MI10 to post 10 units each i get as a result:

Material 005 has 10 units

Material 006 has -90 units.

why do i get this difference?

Regards!!!

[JL23 · Accepted solution]

from where did you take the "book quantity" and when?

How long time passed by between this and posting MI10?

I can only imagine 2 reasons:

- there were movements between you looked up the book stock and posted MI10 or between MI10 and you checked the stock again.

- you did not hit the same stock (different batch/different stock type) that you saw initially for the first item, so you just created stock equally to your count.

I would suggest to check in MB51 if there were some movements.

Find your inventory document in table IKPF and ISEG and lookup the book quantity and counted quantity  and see if the book quantity really matches with the book quantity you mentioned before

[Former Member · Accepted solution]

i dont belive thats the issue, im checking the new inventory as soon as i run MI10 (also as im working on testing right now i have the whole system just for me lol)

[JL23 · Accepted solution]

what shall I say, your screen shots do not really equal to what you wrote before and are inconsistent in itself

why should a MBEW stock (which is minus)  increasse by 101 if you just post 10 ?

you do a physical count at storage location level, so it would be better to check MARD table before and after instead of MBEW.

search the 701 movements with SE16 in table MSEG. Field MSEG-LBKUM has the quantity before posting and field MSEG-MENGE the posted quantity.

do they match with your MBEW screen shots?

regarding MI20 you just executed with standard settings, which covers only the execution before posting the difference. Please click the boxex  for status selection and execute.

you get 2 pop-ups (one after the other), make sure that you have all boxes flagged to not miss anything.

[Former Member · Accepted solution]

thats what i mean... it seems totally random.... (im sure it not... but i still cant figure out why)

mard and mbew doent match at all...

i have a new screenshot with the MI20 executed as you told me (BTB thanks for that.... as i wrote before, im new to this module and transactions and they are a little confusing to me...)

thanks a lot!

[JL23 · Accepted solution]

as you see MI20 and MARD equal.

you still did not give any evidence from MB51 and we do not know about the general stock situation from MMBE. 

the total of all MARD records should be equal to the quantity in MBEW, precondition that all your material is valuated.

So you should see a bigger negative stock in MMBE as evidence to your table values, otherwise I would say you have an inconsistency.

Still an inconsistency would be consistent inconsistent  if you just post 1 movement. it would not explain a difference of 101 if you just post 10.

[Former Member · Accepted solution]

ive just talked to a functional, it seems it is an inconsistency from an old custom development that was not tested correctly and it was messing with the stock.....

thanks a lot Jurguen and Dev for your help and patience! you guys rock!

[former_member197616]

Hi,

Through MI10 you are trying to enter the counted number for that material and post  . system will calculate whather the posted quantity is more or less of the book inventory and post the accountings as per that .

Regards,

[former_member183424]

Check MI20 with the physical inventory document.Analysis these fields

Book Quantity

Qty Counted

Different Qty.

You will find the reason.

[Former Member]

mmmm.... im sorry... i still dont get it

[former_member183424]

Post the screen shot of MI20 for the physical document number.

[Former Member]

here is the before and after MI10 execution + the MI20 (it comes up empty....)