Problem in Stock Report

Question

Dear Sir,
I am facing problem in MB5B, two months before i use this TCode and report are like this
Opening Stock              27,179.437  MT                59,705,114.71  INR
total value of Receipts 65,473.815  MT               132,382,668.98  INR
total value of Issues    53,774.361- MT               108,659,912.15- INR
Closing stock               38,878.891  MT                83,427,871.54  INR
and now again today i am checking the report are changed, the report are like this
Opening Stock              27,179.437  MT                60,007,580.64  INR
total value of Receipts 65,473.815  MT               132,382,668.98  INR
total value of Issues    53,774.361- MT               108,659,912.15- INR
Closing stock               38,878.891  MT                83,730,337.47  INR
Why the value changed, i am not able to getting it where does the problem. I am new to MM field. Anybody any idea about this. I want to sort out this issues as soon as possible.
Please help.

Answer 1

some problems can only be solved with OSS notes. if you someone who has to solve SAP issues, then you need access to OSS yourself, or you need one in your organisation who can lookup and implement SAP notes for you.
Ask your basis team, they can grant you access to SAP Marketplace to search for OSS notes.
In general you should differentiate with data that is audit relevant and non-audit relevant data like statistical data.
MC.9 is statistical data, certainly not that important like audit relevant data in MB5B.
if you see a difference, then just assume that the audit relevant data is okay, and the statistic may be wrong.
Do not assume that the statistic has the right information and you need to adjust the audit relevant data, as this is certainly a wrong approach.
when you post a movement then you create audit relevant and statistic relevant data. this does not happen in the same LUW, it is decoupled. if something is wrong and the audit relevant data cannot be posted to the database, then the whole data is rolled back and nothing is posted to any table.
but if something is wrong with the statistic data, then the statistic data posting fails, but the audit relevant part is not rolled back, hence you get this kind of inconsistencies.
(this is just one example how such inconsistencies can arise, there are more reasons which you can learn by reading OSS notes)