Inconsistency in Material Management Inventory Management: Erp SCM Goods Movements

5/4/2016 Inconsistency in Material Management Inventory Management ERP SCM SCN Wiki
Getting Started Newsletters Store
Welcome, Guest Login Register Search the Community

Products Services & Support About SCN Downloads
Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
ERP SCM / … / * Goods Movements
Inconsistency in Material Management Inventory Management
Created by Polly Gan, last modified on Aug 20, 2015
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 MMIMGFINC 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)
https://wiki.scn.sap.com/wiki/display/ERPSCM/Inconsistency+in+Material+Management++Inventory+Management 1/12
Missing FI Document/Missing MM document
Description:
Goods movement is considered valuated(MSEGDMBTR 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 userexit 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 userexit and BAdI
Documentations:
1284654 Caution with implementations of the BAdI: MB_DOCUMENT_BADI
968812 MM/FI Difference for material stocks
Back to top
Wrong Update of MBEW
Description:
Goods movement, invoice verification or price change postings fail to update valuated stock(MBEWLBKUM) or Value of Total Valuated Stock(MBEWSALK3).
Root cause:
1. Program error caused by note 1946956
2. Modification in customer report which updates MBEW
Detection:
1. During goods movement, error M7314 happens
2. If Material Ledger is activated, error C+048 happens
3. In MB5B (valuated stock option) , situation that opening stock <> 0 or opening value <> 0 happens
4. in MB5K, difference between valuated stock and storage location stock happens
5. In MB5L, variance between MM and FI happens
Solution:
1. Implement the corrections of the note 2025493 Severe Inconsistencies after Material Price Change or MR22
Existing Data inconsistencies should be corrected by SAP support
2. Review customer report and remove the command which updates standard table MBEW
Back to top
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:
1913754 MM/FI differences due to manual postings: Check report
968812 MM/FI Difference for material stocks
Back to top
Change of Account Determination
Description:
The MMFI comparison report (MB5L) shows a difference between MMFI 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 plusminus 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 MMFI inconsistency existing on this case. To solve the plusminus difference in MB5L, it is necessary to perform manual FI posting.
Documentations:
2008455 Change of account determination when stock is not zero
Back to top
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:
1846376 MM/FI difference occurs in transaction MB5L and report RM07MMFI for current year
Back to top
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:
1. Program error caused by note 1557108
2. 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:
1. Apply note 1930161 and note 1935699
2. 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:
1248511 Differences between storage location stock and batch stock
Back to top
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:
1. 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.
2. We generally recommend that you change the value and/or quantity update for new material types only.
Documentations:
1396442 Changing the quantity/value update un the material type
2010127 Inappropriate customizing change of material type may cause stock inconsistency
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 (MSSAKZBWS in sales order stock or MSSQKZBWS in project stock) is
different to the valuation entered from the sales order (VBAPKZBWS) or project (PSPRKZBWS). 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:
1. Check the relevant sales order stock(project stock) if it's zero in MMBE
2. 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)
3. Use report MBMSSACO (for sales order stock) or report MBMSSQCO (for project stock) to correct the valuation indicator for example MSSAKZBWS from VBAPKZBWS
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:
547277 FAQ: Requirements in SD and in the delivery
661856 Correction of valuation indicator KZBWS with 0 stock
Back to top
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
600 SAPKH60022
602 SAPKH60211
603 SAPKH60310
604 SAPKH60411
605 SAPKH60507
606 SAPKH60602
Detection:
1. SE16 check table MKPF entries were deleted during archiving
2. SE16 check table MSEG entries still remain
Solution:
1. Apply note 1702011
2. 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
3. Mark the affected archive files as corrupt/delete
4. Perform a fresh archiving
Documentations:
1761611 MM_MATBEL:Correction Report to reload archives
Back to top
Inconsistency in Previous Period
Description:
MM stock inconsistency happens in previous period.
Root cause:
1. Missing note 1636844, note 1647160 and note 2059141(invoice processing)
2. Unexpected operation which initialized period by MMPI
3. 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"
1. The period in the stock table and the period in the corresponding history table are identical.
(e.g. MBEWLFMON = MBEWHLFMON and MBEWLFGJA = MBEWHLFGJA which however should not happen)
The stock in the current period is correct; however, the stock is not correct in the previous period.
2. SE16 check table MARVCD
If there's inappropriate period initialization, there will be record in the table indicating that
3. MB51 to list material documents and find the target posting which was posted near the period closing
Solution:
1. Apply note 1636844, note 1647160 and note 2059141 (invoice processing)
2. 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)
3. 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 yearend 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:
487381 RMMMINIT: Protection Against Unintended Execution
520010 FAQ: Inconsistencies in inventory management
Back to top
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 userdependent 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:
935755 Negative stock even though this is not permitted in Customizing
369518 Transfer stock not reached if posted with BAPI
Back to top
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:
1. go to MM03 transaction and check the price in Accounting 1 view.
2. 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.
3. 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:
1708261 Error 'M7 308' is raised when trying to post a goods movement
Back to top
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:
612132 FAQ: Stock consistency between serial numbers and MMIM
Back to top
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:
48815 Checking possible inconsistencies between MM and QM
Back to top
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:
535043 Stock comparison with LX23: Difference between WM and IM
Back to top
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:
1. Correction needs to be done by SAP support under component COPCACT
2. Follow the steps in note 1020077 to suppress C+048 error to avoid very high situation
Documentations:
1020077 Operational block due to error message C+ 048
364368 Material ledger help desk
Back to top
Index by Error Message
M7201
M7308
M7309
M7310
M7314
M7242
C+048
IO231
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
mm_tsg mm_gm mm_inc
Contact Us SAP Help Portal
Privacy Terms of Use Legal Disclosure Copyright Follow SCN

Inconsistency in Material Management Inventory Management: Erp SCM Goods Movements

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Inconsistency in Material Management Inventory Management: Erp SCM Goods Movements

Загружено:

Авторское право:

Доступные форматы

5/4/2016 Inconsistency in Material Management Inventory Management ERP SCM SCN Wiki

Getting Started Newsletters Store

Welcome, Guest Login Register Search the Community

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Вам также может понравиться

Inconsistency in Material Management Inventory Management: Erp SCM Goods Movements

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Inconsistency in Material Management Inventory Management: Erp SCM Goods Movements

Загружено:

Авторское право:

Доступные форматы

5/4/2016 Inconsistency in Material Management ­ Inventory Management ­ ERP SCM ­ SCN Wiki

Getting Started Newsletters Store

Welcome, Guest Login Register Search the Community

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Вам также может понравиться

5/4/2016 Inconsistency in Material Management Inventory Management ERP SCM SCN Wiki