MB5B - Incorrect initial stock value

[moisesteixeira]

Dear all,

I have been browsing SCN, and OSS for information regarding MB5B, and nothing helped me to find a solution so far. Therefore, if possible, I would really like to have some advice on this issue I am facing.

When executing MB5B report without restraining any date on selection screen, the initial stock value is not correct.

I have searched OSS notes, and even though many are related with this issue, I’ve found none which is pertinent to this scenario.

Examples:

201327 - Values in Inventory Controlling

456106 - Standard analyses: Display of values

1772782 - MB5B: Detailed information about opening and closing stock

209629 - MB5B: Start date amount not equal to zero, zero qty

In debug mode I can see that no documents related with price changes are being selected, and I believe that’s the problem.

I’ve compared two different systems (ECC SAP_APPL 600 SAPKH60025 vs ECC SAP_APPL SAPKH60606 ) and I’ve found that the most recent one makes the selection of price change documents via table BSIM.

The system on ECC 600 SAP_APPL SAPKH60025, does not select any documents from BSIM (because BSIM is empty…).

Scenario 1 ECC SAP_APPL 600  SAPKH60025 => NOT OK

The following document is causing the difference and is not being caught in the report:

Scenario 2 ECC SAP_APPL SAPKH60606 => OK

Also and finally, MR51 returns no documents in ECC SAP_APPL 600  SAPKH60025.

Questions:

Would you have any ideas of why is this happening?

Is there other way of having Price Change documents being considered in MB5B rather via table BSIM?

Do you believe the problem is not on BSIM table being empty?

p.s. Summarization of accounting documents is not active in any of the systems: 201039 - Missing accounting documents in MB5B and MR51

Thanks in advance for your time!

Regards,

Moisés Edgar Teixeira

[Prasoon · Accepted solution]

Hi,

   Please refer the note:  1278202 - MB5B Valuated Stock mode: Open Stock = 0 and Open Value <> 0

Regards,

AKPT

[moisesteixeira · Accepted solution]

Hi,

Thanks for the reply, but that's not the case here, the summarization is not active. I don't know if you saw the update I did on the question:

(...)

p.s. Summarization of accounting documents is not active in any of the systems:

201039 - Missing accounting documents in MB5B and MR51

Regards,

Moisés Edgar Teixeira

[Former Member · Accepted solution]

Not sure if this is helpful or not but this KB clearly states that MB5B looks at BSIM in its calculations for all releases:

2000331 - MB5B shows different results for the same data even when checking closed periods

[moisesteixeira · Accepted solution]

Hi,

The problem mentioned is that no records are being updated at all in table BSIM.

I have already read the KB article mentioned, and it helped me to understand the logic behind MB5B.

So, this KB is helpful to understand, but doesn't solve this problem.

Regards,

Moisés Edgar Teixeira

[Former Member · Accepted solution]

Hi,

Do also refer the below OSS Note, which explains the table updation of BSIM and corresponding details of MB5B report with solution...

497992 - XXX MB5B : Composite SAP Note for Release >= 4.0B 05/2002

[moisesteixeira · Accepted solution]

Dear Mallinath,

I have read the note before, and again now after your suggestion, but I do not see where in this note its explained how to get BSIM populated.

The comments made on BSIM are referring a different scenario:

(...)

If the Customizing settings are incorrect, FI documents, whose amounts were not however posted to the respective material stock accounts, may appear in the list. The relevant item in the FI document does not the account key "BSX".

(...)

In this case, the BSX account key is in the financial document:

Could you detail a little bit more, about the necessary settings to get BSIM updated?

Thanks,

Moisés Edgar Teixeira

[former_member373041]

Hi guys,

Logic to put to BSIM consists of 2 conditions:

1. Posting key 89/99

2. Transaction key BSX (as normal configure to posting key 89/99)

Please check your configure first and hope it is still helpful for you.

Regards,

Ryan