Inconsistency in Material Management - Inventory Management
目录
- Description
- Root cause
- Inappropriate COMMIT WORK/ROLLBACK command in user-exit or BAdI
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- Solution
- Description
- Root cause
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- Solution
- Documentations
- Description
- Root cause
- Detection
- SE16 view table MSSA
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
Back to top
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
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
Back to top
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
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
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
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
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
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
...
