Stock Inconsistency | ERP软件技术分享

Community

Topics

Groups

Answers

Blogs

Events

Programs

Resources

What's New

Home

Community

Blogs

Ask a Question

Write a Blog Post

Former Member

January 30, 2015 4 minute read

Stock Inconsistency

51635,615

Introduction:

Very often we get issues like stock shown in Material Master record with Stock available in MMBE . At the same time, valuated stock will not match with codes/reports like MCBE, MC.9, MB53. It is very important in Inventory Management to check that the stocks are properly maintained for their correctness in terms of quantity and value. These type of inconsistencies cause instability of system in terms of incorrect reporting, false stock statements and incorrect decisions.

This document deals with possible causes of stock inconsistencies and the analysis required for finding the same and taking corrective measures.

Possible Reasons for Stock Inconsistency:

Prolonged usage of inventory management transactions like MIGO, MB1B for stock posting.

Archiving of documents.

Wrong postings with negative stock\

History tables MBEWH, MARDH, MSEG, MKPF not updated properly

Errors during Inventory Transactions:

Whatever may be the reason, system would become inconsistent which may provide error message like any of the following :

M7 308 ‘Stock value and qty are unrealistic: & / &

M7 309 ‘Stock value is negative: &

M7 310 ‘Valuated stock is negative: &

M7 314 ‘Valuated stock becomes negative: &

The possible reason is, there exist no actual stock in the system, though MMBE shows some stock. Most of the time this could be the reason for error messages.

Transactions where we can check the stocks:

Various transactions which are used to find stocks in SAP are :

MMBE – Stock Overview Report

MM03 – Accounting view of material master fetches data from MBEW (table for valuated stock)

MB53 – Plant Stock Availability

MB52 – Warehouse Stock Availability

Possible causes of inconsistency and their solution:

1. Difference between storage location stock and batch stock

Sometimes, the sum of all batch stocks from MCHB table for a particular material differ from storage location stock available from table MARD. This is not applicable to spacial stock like Sales Order stock or Project Stock.

The possible reason for this inconsistency could be when you use a modification for batch number assignment. One batch is assigned several times (e.g. use of a dummy batch number or the actual date)

Solution:

Check your modification in batch number assignment, in particular in Function Module VB_NEXT_BATCH_NUMBER.

A second option to find whether the inconsistency is a result of such a modification is to call transaction MSC3N for the relevant batch and display the change documents. If there there several change documents with the content “Batch created”, this usually hints to a modification in batch number assignment.

To avoid further inconsistencies, delete your modifications. Implement Notes 1035372 and 1062164 and set the parameter ALLOW_EXISTING_BATCH in the existing user exit EXIT_SAPLV01Z_002 to make postings to the existing batch. If the system now issues the error message M3 204 ‘Batch & already exissts in plant &’ or M# 556 ‘Batch & already exists for material &’ , you must repopulate the batch number in the user exit EXIT_SAPMM07M_010.

2. Wrong Goods Receipt

In your system, there is a GR for PO, in which an item in the material document contains the material number of the previous purchase order item.

3. A material has inconsistent data

The stock in Accounting View (Table MBEW) does not correspond to the stock in the Stock Overview. You have own programs which cary out an update on MBEW.

Cause and Prerequisites:

Table MBEW contains valuation data of material , for example the total stock and total value. These fields are updated with every goods movement. With these frequent changes in the table, each updatem which doesnot lock the table correctly, can cause data inconsistency.

Solution:

Do not use your own programs to change fields LBKUM, SALK3, SALKV, VKSAL, STPRS, VERPR, VPRSV of table MBEW.

If you use own programs which changes other fields of table MBEW, always use the addition SET. Thus, on the database only, fields specified with command SET are changed. Stock postings which may be carried out at the same time remains unaffected.

4. Non-generation of Accounting Document in MIGO

When Goods Movement is posted, a material document is generated. However, no update on the dependent stock tables, such as MARD and MBEW are carried out. In addition, no accounting document gets generated.

Causes and Prerequisites

Following procedure causes incorrect update.

i. You post goods movement with transaction MB11 or MB1A

ii. You enter movement type, plant and storage location in initial screen and choose Enter

iii. You enter material number in the following overview screen and confirm your entry by choosing Enter.

iv. Since you did not fill the field quantity, you reach the detail field automatically. Your system generates warning message M7 129 ‘Enter a quantity’.

v. You display the movable quantity using Key combination Shift + F5, and exit the dialog box (F12).

vi. Enter the entry quantity in the following detail screen and confirm it by choosing Enter.

vii. Then press cancel (F12)

viii. You reach the Overview screen again and post goods movement (F11)

5. Due to Period Closing Issues

In period closing for material master (MMPV), goods movement are done during the interval between Last Day of the Old Period and First Day of the New Period.

It is recommended not to post any documents whilst the period closing programs are running. Before the period closing program runs, check in transaction SM13 whether outstanding update terminations of goods movement are still displayed. These must be cleared and closed before the period closing program runs.

Useful Reports to Analyze Inconsistencies:

RM07SHUP – Shows updates recorded in table mminkon_up.

MBANEKBE – Display of a purchase order history

MBCKBSEG – This report checks Materials having balance in FI with no entry in MBEW, Materials with wrong valuation class in MBEW as a result of which account determination gets different account as in BSEG , Materials which have a different actual value in MBEW as in BSEG, Manual Postings or with posting key not equal to BSX for stock accounts

MBCKBSIM – This report checks whether for all BSEG entries, a BSIM entry exists

MBTRAMEW – This report will try to find inconsistencies caused by Stock Transfer Orders with active ingredient batches. This report also allows posting the correction using transaction MWBE

RM07HIST – routine to read history stock from history tables.

MBUPDATE – This report allows modification of MM-IM table fields. Updated values are stored in table MMINKON_UP

MBLABST – Shows general information and Stocks for a specified material in a specified plant.

MBMSSQCR – Using this report, user may change the content of field MSSQ-KZBWS (special stock valuation indicator) when the special stock is 0.

Conclusion:

Although there are many reasons for stock inconsistencies, some of possible reasons and there solutions have been discussed. Finding out inconsistencies and their corrections will improve the stock management thereby, reducing the inventory costs.

FollowLikeRSS Feed

Alert Moderator

Assigned Tags

MM (Materials Management)

goods movement error

goods movements

inventory controlling

inventory management

stock inconsistencies

Community Wiki

Spaces

Help

Configure

Dashboard

…

* Goods Movements

Skip to end of banner

Go to start of banner

Inconsistency in Material Management - Inventory Management

Skip to end of metadata

Created by Polly Gan on Aug 20, 2015

Go to start of metadata

The following wiki page is meant to give an overview of all types of inconsistencies you may find in an SAP ERP system in the Materials Managements - Inventory Management area. The information on this page is aiming to provide you with all the necessary information to proactively avoid inconsistencies. In case the inconsistencies have already happened this wiki will also help you identifying them and finding the right ways to fix them.

Inconsistency types

Inconsistencies in inventory management

MM/FI Differences

Missing FI Document/Missing MM document

Wrong Update of MBEW

Manual Postings from FI

Change of Account Determination

Missing Balancing Carry Forward

MM Stock Discrepancies

Discrepancy between storage location stock and batch stock

Changing "value update" indicator for material type when stock <> 0

Special Stock Inconsistencies

Missing Header Table MKPF/Missing Item Table MSEG

Inconsistency in Previous Period

Others

Negative Stocks

Unrealistic stock

Serial Number Stock Inconsistency

Inconsistency between QM and MM stock

Inconsistency between WM and MM stock

Inconsistency between ML and MM

Index by Error Message

Hot News Note Must Be Implemented to Avoid Inconsistency

2025493 Severe Inconsistencies after Material Price Change or MR22

1935699 QA11: Stock inconsistency after status change in batch stock

1930161 Stock inconsistencies in table MCHB for batches

Based on the principles described in note 32236, SAP Support will only provide help and corrections for inconsistencies that occurred in live productive systems. Incidents opened for development or test systems will be closed without investigation. In case you have located an inconsistency in your productive system, which cannot be cleared with the methods and techniques explained in this wiki page, please go through the following checklist:

Open the remote connection to your productive system and maintain the secure area with valid logon credentials as per note 508140

Declare a contact person for application and remote connection related questions

Make sure that the correction reports mentioned in note 32236 have been implemented in your system

Once these prerequisites are fulfilled you can open an incident at the component MM-IM-GF-INC where you provide the following information in the problem description:

Are you using an industry solution? If "YES", which one, and since when?

When was a release upgrade performed and from which SAP release?

Have you carried out SLO conversion programs in the past (for example, change of chart of accounts, company code deletion or company code combination)?

Affected company code(s)?

Affected plant(s)?

Affected material number(s)?

For inconsistency analysis and correction, please provide necessary authorizations as mentioned in note 32236: To be able to process and analyze the data inconsistencies promptly, our support team requires a user master record with sufficient authorization. The reports listed above can usually only be started by users that have debugging authorization (object 'S_DEVELOP', object type 'DEBUG' and activity '03'). In addition, Debug&Replace authorization is required as well as authorization for all transactions in package MB and SM*/SE* system transactions.

Inconsistencies in inventory management

MM/FI Differences

Generally MM/FI difference can be detected in transaction MB5L(report RM07MMFI)

Missing FI Document/Missing MM document

Description: Goods movement is considered valuated(MSEG-DMBTR contains value), however no corresponding FI document is generated. Or vice verse FI document is generated but source document in materials management is missing.

Root cause: Inappropriate COMMIT WORK/ROLLBACK command in user-exit or BAdI: e.g. Enhancement MB_CF001: EXIT_SAPLMBMB_001 Enhancement MCB10001: EXIT_SAPLMCB1_001 BAdI MB_DOCUMENT_BADI which destroys SAP LUW.

Detection: MIGO - display the posted material document

MIGO - go to Doc.info tab and click on 'FI document' button

Solution: Check and remove the inappropriate COMMIT WORK or ROLLBACK in user-exit and BAdI

Documentations:

Wrong Update of MBEW

Description: Goods movement, invoice verification or price change postings fail to update valuated stock(MBEW-LBKUM) or Value of Total Valuated Stock(MBEW-SALK3).

Root cause:

Program error caused by note 1946956

Modification in customer report which updates MBEW

Detection:

During goods movement, error M7314 happens

If Material Ledger is activated, error C+048 happens

In MB5B (valuated stock option) , situation that opening stock <> 0 or opening value <> 0 happens

in MB5K, difference between valuated stock and storage location stock happens

In MB5L, variance between MM and FI happens

Solution:

Implement the corrections of the note 2025493 - Severe Inconsistencies after Material Price Change or MR22 Existing Data inconsistencies should be corrected by SAP support

Review customer report and remove the command which updates standard table MBEW

Manual Postings from FI

Description: In MB5L, variance between MM and FI happens.

Root cause: The difference is caused by manual posting from FI side to stock account(BSX). 'Post automatically only' indicator (XINTB) in the account master (FS00) was once unselected, and FI manual postings were made to stock account even it shouldn't.

Detection: In MB5L, variance between MM and FI happens. Report ZSHOW_MAN_FI_DOCS_ON_STOCK_ACC in note 1913754 detects manual postings.

Solution: Cancel FI manual postings and then set 'Post automatically only' indicator (XINTB) in the account master.

Documentations:

Change of Account Determination

Description: The MM-FI comparison report (MB5L) shows a difference between MM-FI for two accounts. The same value appears on one account with a minus sign and on the other account with a plus sign. The total difference is zero. Root cause: The "Material Crcy" of MB5L reads the stock value(SALK3) of table MBEW, meanwhile the "Stock Account Crcy" of MB5L reads the value of FI G/L account (stock account). The cause of the plus-minus difference for two accounts shown in MB5L is due to the account determination of transaction BSX (Inventory Posting) has been changed when the stock quantity of the material which belongs to the corresponding valuation class is not zero. Detection: In transaction MB5L, minus/plus constellation happens

Solution: There is no real MM-FI inconsistency existing on this case. To solve the plus-minus difference in MB5L, it is necessary to perform manual FI posting.

Documentations:

Missing Balancing Carry Forward

Description: Discrepancy between MM and FI happens.

Root cause: A balance of a specific stock account form the previous year has not been carried forward to the current year.

Detection: MB5L Discrepancy between MM and FI happens. FS10N A balance of a specific stock account form the previous year has not been carried forward to the current year.

Solution: Execute the carry forward.

Documentations:

MM Stock Discrepancies

Discrepancy between storage location stock and batch stock

Description: There's inconsistency between storage location stock(MARD) and the total of batch stock(MCHB)

Root cause:

Program error caused by note 1557108

Modification in batch number assignment, in particular in the function module VB_NEXT_BATCH_NUMBER

Detection: Transaction MB5K enter material number and plant See error 500 Actual qty not equal to total of stocks

Solution:

Apply note 1930161 and note 1935699

Remove the modification and implement the Notes 1035372 and 1062164 and set the parameter ALLOW_EXISTING_BATCH in the existing user exit EXIT_SAPLV01Z_002 to make postings to the existing batch.

Documentations:

Changing "value update" indicator for material type when stock <> 0

Description: There's inconsistency between storage location stock(MARD) and total valuated stock(MBEW)

Root cause: "Value update" indicator is changed for material type when stock <> 0 in customizing OMS2

Detection: Transaction MB5K enter material number and plant See error 500 Actual qty not equal to total of stocks Solution:

If you want to change the value and/or quantity update of the material types, you have to book out the existing stocks in advance. Ensure that you book out existing stocks in your productive system before you transport the Customizing changes.

We generally recommend that you change the value and/or quantity update for new material types only.

Documentations:

Special Stock Inconsistencies

Description: During goods movement for special stock(sales order stock E or project stock Q), error M7242 happens even it's set as warning message in customizing OMCQ.

Root cause: There are special stocks with an incorrect valuation indicator (KZBWS). In these stocks, the valuation in the material master (MSSA-KZBWS in sales order stock or MSSQ-KZBWS in project stock) is different to the valuation entered from the sales order (VBAP-KZBWS) or project (PSPR-KZBWS). The system always issues message M7 242 as an error during goods movements for the production order, purchase order, or transfer posting. This is to prevent inconsistencies. MSSA entry or MSSQ entry is created with the relevant valuation control (via the sales order/project) at the time of the first goods receipt for the special stock, so if the requirement type/requirements class (for the sales order stock) or control of the project stock (for the project) is changed, it will lead to inconsistency between KZBWS in master data and in sales order(or project) (see also Note 547277, question 15).

Detection: MIGO - goods receipt reference to purchase order

SE16 view table MSSA:

SE16 view table VBAP:

VA03 check sales order item change log - Requirement type has been changed OVZH check the linking requirement class to changed requirement type

OVZG check the valuation indicator KZBWS in requirement class: valuation indicator has been changed to M

Solution: Follow the steps in note 661856:

Check the relevant sales order stock(project stock) if it's zero in MMBE

If it's not zero, then use movement type 501 E(Q) or 561 E(Q) to book out the sales order stock(project stock)(message M7242 needs to be set as warning in customizing OMCQ)

Use report MBMSSACO (for sales order stock) or report MBMSSQCO (for project stock) to correct the valuation indicator for example MSSA-KZBWS from VBAP-KZBWS These reports only work when the relevant special stock is 0, so step 1 and step 2 need to be done prior.

In future, when business requires to change the requirement type in sales order item, refer to note 547277 question 15. and consider to

a) Complete all items that contain the requirements class to be changed (reject, deliver, delete). Then you can change the requirements class. b) Create a new requirements class and use it for new items.

Documentations:

Missing Header Table MKPF/Missing Item Table MSEG

Description: After archiving using archiving object MM_MATBEL for material document, only MKPF table entries are deleted but not MSEG entries.

Root cause: Program error caused by note 1624064 or 1685464 or the contained support packages

Detection:

SE16 check table MKPF - entries were deleted during archiving

SE16 check table MSEG - entries still remain

Solution:

Apply note 1702011

Implement the correction report "Z_MM_MATBEL_RELOAD" attached with note 1761611 to reload the objects from the corrupted archive file back to the tables MKPF and MSEG

Mark the affected archive files as corrupt/delete

Perform a fresh archiving

Documentations:

Inconsistency in Previous Period

Description: MM stock inconsistency happens in previous period.

Root cause:

Missing note 1636844, note 1647160 and note 2059141(invoice processing)

Unexpected operation which initialized period by MMPI

A rare case that causes a large amount of data inconsistencies. During the period closing program run, the processing of a small MM document overtakes the processing a large MM document. - In Customizing for materials management OMJI, "Late Lock" is activated. - In period closing for the material master (transaction MMPV), periods are closed during the interval between the last day of the old period and the first day of the new period.

Detection: MB5K enter material and plant and choose checking period "Stocks at End of Prev. Month" MB5L enter company code and choose period "Select Balance, Previous Perio"

The period in the stock table and the period in the corresponding history table are identical. (e.g. MBEW-LFMON = MBEWH-LFMON and MBEW-LFGJA = MBEWH-LFGJA which however should not happen) The stock in the current period is correct; however, the stock is not correct in the previous period.

SE16 check table MARVCD If there's inappropriate period initialization, there will be record in the table indicating that

MB51 to list material documents and find the target posting which was posted near the period closing

Solution:

Apply note 1636844, note 1647160 and note 2059141 (invoice processing)

Follow the steps in note 487381 if it's necessary to initialize the period. (User has to take the risk to carry out the initialization, and the inconsistency caused by MMPI needs to be corrected via chargeable service)

Check note 520010 question 6 and avoid live postings during period closing.

Generally it's not necessary to correct history tables especially the back posting is not allowed for the concerned company code. Check note 34440 part below:

4. As of Release 4.5A, stocks and stock values of past periods are stored in history tables. These tables solely serve for the analysis of stock inconsistencies in the current period by SAP Support. If further material documents were posted in subsequent periods after a stock inconsistency occurred, the history tables created after the inconsistency also contain incorrect stocks or stock values for the relevant material. However, these history tables are not repaired since they are not required for your SAP system to function.

Exceptions:

1) History tables of the previous year are required for the year-end closing. 2) History tables of the previous period, if posting to the previous period is not possible due to an incorrect history table. Thus, analyzing history tables using customer reports is not supported.

Documentations:

Others

Listed situations might be relevant to inconsistency, but not real inconsistency in the sense of SAP Note 32236.

Negative Stocks

Description: The valuated stock of a material is negative even though negative stocks are not permitted in Customizing. Another scenario involves negative stock in transfer at plant or storage location level. In a two-step stock transfer process (for example, 303/305 or 313/315), the goods receipt quantity exceeds the goods issue quantity.

Root cause: This situation may occur due to a delayed update. A check to determine whether the stock becomes negative, and whether this is permitted, takes place in the dialog when you enter the document. However, this check does not take place during the update. Therefore, if sufficient stock exists when you enter the document, but the document is updated only at a later stage after additional goods issues take place in the meantime (after the deletion of the lock entries), there may be negative stocks.

Negative stock in transfer (without a purchase order reference) may also occur if, for the goods receipt from the stock in transit (movement type 305 or 315), the BAPI BAPI_GOODSMVT_CREATE is called several times within the roll area.

Detection: Transaction OMJ1 - Validate negative stock settings

Transaction MMBE - Validate current stock levels Transaction MB51 - Locate the duplicate posting

Solution: The negative stock can be eliminated by reversing the "duplicate" goods issue or by posting a new goods receipt.

In the example scenario above this would mean: A) Reversing material document 4900013449 B) Posting a goods receipt for 850 PC For this, system messages M7 309 and M7 310 must, at least temporarily, be set to "No Message" in Customizing (transaction OMCQ), which can also be done on a user-dependent basis. Alternatively, you can also allow negative stocks temporarily (in Customizing and in the material master). To avoid situations such as this, you should NEVER manually delete the lock entries that come from the update in SM12. To resolve this negative stock in transfer caused by the same roll area postings, adjust the call for BAPI_GOODSMVT_CREATE in your own program as described in consulting note 369518.

Documentations:

Unrealistic stock

Description: During goods movement, error M7308 happens.

Root cause: There's unrealistic stock situation e.g. total stock = 0 while total valuated stock value <> 0

Detection: MM03 check material master accounting view:

Solution: Refer to KBA 1708261 and execute following steps:

go to MM03 transaction and check the price in Accounting 1 view.

then, go to MR21 transaction and post a price change by increasing the price in 0,01. For example, if price is 100,00 EUR change to 100,01 EUR.

open MR21 transaction once again and then post a price change by reducing the price in 0,01. For example, from 100,01 EUR to 100,00 EUR.

Once these price changes have been posted the total value on stock will be adjusted and then you should be able to make any necessary goods movements for this material.

Documentations:

Serial Number Stock Inconsistency

Description: Even though serial number profiles are set up correctly in your customizing the system has allowed the multiple use of a single serial number, which has led to inconsistent serial number statuses.

Root cause: Incorrect customizing settings at the time of postings or customizing changes

Detection: SE38 execute report RIMMSF00 and find the difference between serial number stock and MM stock

Error IO231 happens during goods movement indicating the serial number stock is not matching the movement to be proceeded.

Solution: Run a complete physical inventory for example MI10.

Documentations:

Inconsistency between QM and MM stock

Description: Stock inconsistency between inspection stock in materials management and inspection stocks managed in inspection lots happens. MM stock correct based on material documents posted.

Root cause: This is caused by incorrect inventory management in inspection lots.

Detection: Report ZQEVAC20 attached with note 48815 detects the difference between QM and MM stock.

Solution: Use report ZQEVAC20 attached with note 48815 to adjust the QM stock.

Documentations:

Inconsistency between WM and MM stock

Description: Stock inconsistency between inspection stock in materials management and warehouse management. MM stock correct based on material documents posted.

Detection: A stock comparison using Transaction LX23 displays stock differences between Inventory Management and Warehouse Management.

Solution: Follow note 535043 and clear the difference using LX23:

The stock comparison report first reads all IM stocks and all special stocks. In the second step the WM stocks are read and summed up. If a difference then results when a comparison is carried out between the two internal tables, the individual stocks are listed and the difference calculated. A comparison is only carried out if you select the 'Clear differences' check box. The program then creates a batch input session for Transaction MI10. An automatic physical inventory is carried out during the processing of the BI session in the inventory management that adjusts the IM stocks to the WM stocks. If the stock situation is that the stocks in the inventory management are correct and the WM stocks are incorrect, then this situation can only be corrected using standard means by the differences being cleared in a first step, that is the IM stocks are adjusted to the WM stock, and in a second step in the WM the stocks being corrected by physical inventory count.

Documentations:

Inconsistency between ML and MM

Description: During goods movement error C+048 happens and goods movement for the material is no longer possible. Material management is consistent with FI.

Root cause: There's inconsistency between material ledger and material management.

Detection: CKMC check between ML and MM

Press Data Comparison button

Solution:

Correction needs to be done by SAP support under component CO-PC-ACT

Follow the steps in note 1020077 to suppress C+048 error to avoid very high situation

Documentations:

Index by Error Message

Hot News Note Must Be Implemented to Avoid Inconsistency

mm_tsg

mm_gm

mm_inc

rm07mmfi

fb5l

Privacy

Legal Disclosure

Trademark

1284654	Caution with implementations of the BAdI: MB_DOCUMENT_BADI
968812	MM/FI Difference for material stocks

1913754	MM/FI differences due to manual postings: Check report
968812	MM/FI Difference for material stocks

2008455	Change of account determination when stock is not zero

1846376	MM/FI difference occurs in transaction MB5L and report RM07MMFI for current year

1248511	Differences between storage location stock and batch stock

1396442	Changing the quantity/value update un the material type
2010127	Inappropriate customizing change of material type may cause stock inconsistency

547277	FAQ: Requirements in SD and in the delivery
661856	Correction of valuation indicator KZBWS with 0 stock

600	SAPKH60022
602	SAPKH60211
603	SAPKH60310
604	SAPKH60411
605	SAPKH60507
606	SAPKH60602

1761611	MM_MATBEL:Correction Report to reload archives

487381	RMMMINIT: Protection Against Unintended Execution
520010	FAQ: Inconsistencies in inventory management

935755	Negative stock even though this is not permitted in Customizing
369518	Transfer stock not reached if posted with BAPI

1708261	Error 'M7 308' is raised when trying to post a goods movement

612132	FAQ: Stock consistency between serial numbers and MM-IM

48815	Checking possible inconsistencies between MM and QM

535043	Stock comparison with LX23: Difference between WM and IM

1020077	Operational block due to error message C+ 048
364368	Material ledger help desk

M7201
M7308
M7309
M7310
M7314
M7242
C+048
IO231

2025493 Severe Inconsistencies after Material Price Change or MR22
1935699 QA11: Stock inconsistency after status change in batch stock
1930161 Stock inconsistencies in table MCHB for batches