# SAP MM Error Messages List: Reading Codes and Changing Message Severity > Source: https://netray.co/erp-help/sap-mm-error-messages-list > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SAP messages are identified by class and number, for example M7 021 or ME 172. No official complete list fits every release, so the reliable method is SE91: enter the class and number to get the exact text, long text and where used. The class prefix tells you the area (M7 inventory management, M8 invoice verification, ME and MEPO purchasing), and many messages can be downgraded from error to warning in customizing. ## Kind error ## System sap ## Erp SAP ECC / S/4HANA ## Module MM / Message Control and Customizing ## Query sap mm error messages list ## Alternate Queries - m8147 error in sap mm - me172 sap mm error - sap mm error message configuration - error sap m7036 - error sap me154 ## Applies To SAP ECC 6.0 and S/4HANA on-premise MM. Message texts vary by release and language. ## Steps ### How to find the meaning and fix of any MM message **Items:** - Copy the full message including class and number from the status bar (the message in the log shows it as 'M7 021' or similar) or press F1 and open the technical information. - Open SE91, enter the class (for example M7) and the number. Read the short text, the long text and the where used list. - Use the class to identify the process: M7 is inventory management and goods movements (MIGO), M8 is logistics invoice verification (MIRO), ME is purchasing documents and MEPO is the PO enjoy transaction messages (ME21N, ME22N, ME23N). - Reproduce the situation in a test client, with the same plant, material, movement type and posting date, to confirm the trigger. - Fix the cause (master data, stock, period, authorization or customizing), not the single document. - If the message is a configurable one, you can decide whether it should be an error, warning, information or switched off, as described below. ## Sections ### What the codes in your list refer to **Body:** M7 021 is 'deficit of stock' on goods issue, covered at sap-m7-021-deficit-of-stock-error. M7 053 is the 'posting only possible in periods' message, covered at sap-migo-m7-053-posting-only-possible-in-periods. These are the two in this family that are well documented and safe to describe from memory. For others such as M7001, M7036, M8147, M8443, ME154, ME172, MEPO823, MA550, 06280 and 06855, the same short number can have different text per release and per language, and some belong to other classes than you may expect (class 06 and MA are not purchasing or inventory classes in the usual sense). We do not list a guessed meaning for them here. Look each one up in SE91, read the long text, and use the where used list to find the program. A good habit is to keep your own internal list of messages your users hit, with the fix that worked, in the same form: class, number, text, cause, fix, owner. ### Changing message severity in customizing **Body:** Some MM messages are configurable. In the IMG you find 'Set Up Attributes of System Messages' (transaction OMT4 for materials management; OBA5 is the equivalent used for FI messages). You enter the application area, the message class and number, and choose the standard type, or a user specific type, such as error to warning. The settings are stored in table T160M and are checked at runtime. Only messages that SAP prepared for this have an entry in the check. Others cannot be changed in customizing without a modification or an enhancement, and we do not recommend that. Changing an error to a warning removes a control, so involve the process owner and auditors. **Code:** - SE91 Message class + number -> text, long text, where used - OMT4 MM: attributes of system messages (stored in T160M) - OBA5 FI: message control (FI messages) ### Building your own list for support **Body:** Export the messages your support desk sees. Many sites log them in SLG1 or in user tickets. A table with message, count per month, process and fix makes a good knowledge base and shows where master data quality is poor. Pair it with a search by message class and number, not by text, since text is translated and can change after an upgrade. ## Pitfalls - Trusting a blog's message text instead of reading SE91 on your own release. - Downgrading an error to a warning to make a user's problem go away, with no process owner approval. - Assuming the class prefix tells you the module for every message; it usually does, but not always. - Searching by the message text in one language and missing tickets in another. - Using OBA5 for an MM message or OMT4 for an FI one; the entries are separate. ## Ai Angle An assistant grounded in your SAP system (ERPray, read-only, role-aware, can run on-prem) can look up the message in the message tables for your release, find the document the user was posting and show the stock, period or master data facts that triggered it. That turns 'what does this mean' into 'here is the cause on this document'. The customizing change is yours to approve. ## Faq ### Where can I see all SAP MM error messages? **Answer:** In SE91 (Message Maintenance). Enter the message class and number to see the text, long text and where used list. Each class can be browsed. There is no single official PDF that matches every release. ### What does the class in an SAP message mean? **Answer:** The class groups messages by application area. M7 is mostly inventory management, M8 invoice verification, ME and MEPO purchasing. The two part code is class plus number, and the number alone is not unique. ### Can I change an SAP error message to a warning? **Answer:** Only for messages SAP made configurable. Use OMT4 for MM or OBA5 for FI messages in customizing. The settings are stored in T160M for MM. Get process owner approval, since it removes a control. ### Why does the same message number show different text? **Answer:** Texts are translated and can differ between releases and support packages. Always check SE91 on your own system, in the logon language you use. ## Search terms sap mm error messages list, sap mm common errors, sap mm error message configuration, m8147 error in sap mm, me172 sap mm error, sap m7036 error, sap me154 error, sap mepo823 error, sap se91 message class, sap omt4 message control --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json