If you’ve ever dealt with SAP consignment processing
and bumped into cryptic error messages like FS217 or M8443 while using
Transaction MRKO, you're not alone. Vendor settlement errors can be maddening—especially
when they seem to appear out of nowhere and block your month-end close.
But here’s the good news: There’s a reliable, step-by-step
way to troubleshoot this—and I’m going to walk you through it like
we’re solving this together over coffee.
1. First Things First: Set Up Output Condition Type KONS
Here’s the deal: One of the foundational steps that often
gets missed is setting up the Output Type correctly—specifically, type
KONS. In SAP lingo, an Output Type defines the format
and method of communication—whether it’s a printed form, a system email,
or something else. For consignment settlement, KONS is critical.
Here’s how you do it:
-
Use Transaction Code: V/30
-
Click New Entries
-
Enter your data to define output type KONS
-
Save it
Think of this like setting up the rules for how SAP communicates
with the vendor during settlement. If this is missing or misconfigured,
the whole process can break down.
2. Link Output Conditions with Transaction MRM1
Once your Output Type is created, it’s time to assign the
right conditions to it using MRM1. Why this matters:
SAP needs to know when and for whom to trigger the KONS output. This is
like telling SAP, "Only send this message when you're dealing with Vendor
X under Company Code Y." Steps:
-
Go to Transaction MRM1
-
Click Key Combination
-
You’ll see Create Condition Records (Consignment): Fast
Entry
-
Define your Company Code, Partner, and any other necessary
fields
-
Hit Save
Now SAP knows when to apply the KONS output—and that’s
one major roadblock removed.
3. Tax Code Setup in the Info Record (Transaction ME12)
Now, this next part is a gotcha moment for many. In
consignment, SAP still expects a valid Tax Code in the info record—even
if it's exempt. Steps:
-
Go to Transaction ME12
-
Make sure the Info Category is set to Consignment
-
Press Enter until you reach Purch. Org. Data 1
-
Hit Enter again to get to the screen where Tax Code appears
-
Set it to I0 (exempt)
This might feel like a small detail, but trust me—it’s
one of those “little things” that can throw a wrench in your settlement.
4. Fix the Tax Category in the G/L Account (Transaction FS00)
Now, let’s talk about your G/L Account settings, which
might be causing those nasty error messages like FS217. Use
Transaction FS00 and do this:
-
Look for the Tax Category field
-
Use the dropdown to pick “-” Only Input Tax Allowed
-
Save
This aligns your tax settings with what’s expected during
MRKO processing. If your G/L account doesn’t allow the right tax settings,
SAP will throw an error—and it usually doesn’t tell you why clearly.
5. Run Compatibility Check Between Movement Type and G/L
Account
This next step is gold—and so many teams skip it.
Here’s where we check if SAP’s Movement Type 291K is
playing nicely with the G/L Account field selection. Use
this trick:
-
Go to Transaction SE38
-
Enter program name: RM07CUFA
-
Hit Execute
-
Enter Movement Type: 291K
-
Run it
What you’ll see next is a side-by-side comparison:
-
Mvt type vs G/L Account field status
Look for mismatches like:
-
Movement Type requires a field (+) but the G/L account suppresses
it (-)
-
Or vice versa
These inconsistencies can directly trigger MRKO settlement
errors. Fixing them usually clears the way forward.
6. Execute Transaction MRKO for Settlement
Now that we’ve laid the foundation, it’s time to go back
to the main task—settling vendors. Steps:
-
Go to Transaction MRKO
-
You'll see a list of unsettled or pending transactions and
recent goods receipts
-
Go back to the previous screen and press the “Settle”
tab
-
Execute again
If everything else has been configured correctly, SAP should
now be able to process the vendor settlement without throwing any more
errors. And yes—your vendors get paid, your books are clean, and you
finally get to move on.
7. If Errors Still Show: Turn Messages from Error to Warning
(Transaction OMRM)
So, you’ve followed everything and SAP still throws an
error? Here’s a workaround: Go to Transaction OMRM.
This is where you can change how SAP handles certain messages—from hard
errors to soft warnings. Important: Only do this if
you’re absolutely sure the root cause isn’t data-related, and you just
want to proceed with caution. Locate the specific
error message (like FS217 or M8443), and switch it from “E” (error)
to “W” (warning). Save and retry the MRKO process.
8. Review Error Logs in SE31 for Deeper Diagnostics
Still no luck? Then it’s time to get into the weeds.
Go to Transaction SE31. Here you can analyze SAP table structures,
forms, and even message logs to understand why something is failing.
Look up message class FS and message number 217 (or whichever
message you’re getting) to find the root cause. It might lead you to
something you missed—like a missing condition, a misconfigured movement
type, or a mismatch in your plant settings.
Bonus Tip: When in Doubt, Cross-Reference with OSS Notes
or SAP Launchpad
Sometimes these errors are related to version-specific bugs
or patches. Don’t forget to search SAP Notes or the SAP Launchpad for
your error code. You’d be surprised how many of these issues have known
fixes.
Conclusion: Simplify Your SAP MRKO Troubleshooting Once and
for All
Troubleshooting MRKO vendor settlement errors can feel like
decoding ancient scrolls—but once you know where to look, it’s actually
pretty methodical. From setting up the right output type (KONS), to aligning
tax codes, G/L settings, and movement type compatibility, each piece of
the puzzle matters. The good news? Once you’ve got
this process locked in, it becomes repeatable—and that means fewer errors,
faster closings, and smoother vendor relationships.
Frequently Asked Questions (FAQs)
Q1: What does error FS217 mean in SAP MRKO?
A: FS217 typically indicates a mismatch in tax-related configuration
between the G/L account and the document posting logic. It’s often tied
to tax category settings in FS00.
Q2: How do I fix error M8443 during consignment settlement?
A: M8443 usually points to missing condition records or output
types. Ensure that Output Type KONS is properly configured and linked via
MRM1.
Q3: Can I bypass MRKO errors by converting them to warnings?
A: Yes, using Transaction OMRM, you can change certain error
messages to warnings—but only if you're sure it won’t cause downstream
issues.
Q4: What is the purpose of Movement Type 291K?
A: Movement Type 291K is used for goods issue transactions
related to consignment. Compatibility with G/L account field status is
crucial.
Q5: Do I need to update the tax code in all Info Records
for consignment?
A: Yes. Even if the tax is exempt, SAP expects a valid tax
code like I0. This must be maintained in ME12 under consignment info category. |
SAP MM Tips
|