SAP MM Consignment Process: Troubleshooting Consignment Settlement in MRKOIf you've ever found yourself scratching your head while trying to settle a consignment in SAP MM using MRKO, you're not alone. One common error message that many SAP users encounter is:"Consignmnt settlement: No message was found for partner 123/company code 1000."Let's unpack this issue and walk through a fix that's not only straightforward but also makes you feel like a configuration wizard by the end. Understanding the Consignment Process in SAP MMBefore diving into the fix, it helps to understand what's going on under the hood. In SAP MM (Materials Management), consignment involves materials being stored at your premises but remaining the property of the vendor until you consume them. The consignment settlement process — done via Transaction MRKO — essentially tells SAP, "Hey, I've used these materials, now let's pay the vendor."But sometimes, SAP throws a curveball — like the error about the missing message for your vendor/company code combo. Root Cause: Missing Output Condition for ConsignmentThat cryptic error usually means SAP can't find a message output type (i.e., how to process the settlement) tied to your vendor and company code. Here’s where transaction MRM1 comes in. MRM1 is the gateway to setting up condition records for message types related to invoice verification.Step-by-Step Fix: Setting the KONS Condition Type1. Go to Transaction Code MRM1This is where you define the message output for consignment settlements.2. Enter the following:
3. Important:
4. Save the condition record.Now, go back to MRKO and retry your consignment settlement.Outcome: Successful Settlement and Invoice CreationIf everything’s set correctly, MRKO should now run like a charm. You'll be able to settle your consignment, and — even better — an invoice document gets created, which can be viewed in the standard SAP invoice history.Pro Tip:Always check if a message condition exists before running MRKO — it saves time and avoids that frustrating error.Real-World Scenario: From Error to SuccessIn a recent case, a user was stuck with the same error message in MRKO. After setting up the KONS condition type in MRM1 (without specifying the vendor), they were able to process the settlement flawlessly. An invoice was generated, and the error was a thing of the past.It’s a small config tweak, but it makes a big difference. Bonus Tip: Monitor Message Outputs via NACEIf you're into fine-tuning or debugging further, use Transaction NACE to explore and configure output types, forms, and processing routines for MM messages — including consignment.Final ThoughtsThe SAP MM consignment settlement process is powerful but picky. That’s why tiny oversights, like a missing message condition, can bring it to a screeching halt. Thankfully, tools like MRM1 give you the control you need to resolve the issue quickly.Next time you see that "No message was found" error, you’ll know exactly what to do — and maybe even impress a few colleagues along the way. Frequently Asked Questions (FAQs)1. What is the purpose of the KONS condition type in SAP MM?KONS is used to define message output types for consignment settlements in MRKO.2. Why should I not enter the vendor/partner number in MRM1?Leaving the vendor blank allows SAP to apply the message condition universally for all vendors in that company code.3. Can I create different KONS records for multiple company codes?Absolutely. Just change the company code in MRM1 and repeat the setup.4. How can I verify if the invoice was created post-settlement?Use transactions like MIR4 or review the PO history tab to see the invoice document.5. Is MRKO the only way to settle consignment?Yes, MRKO is the standard transaction for consignment settlement in SAP MM.Fast links:
Get help for your SAP MM problems
SAP MM Books
SAP Material Management Tips
Best regards,
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|