Introduction
Ever tried to run a consignment settlement in SAP using MRKO
and got hit with the dreaded "No tax information found" error (Message
no. M8 732)? You're not alone—and yes, it's frustrating. But don’t
worry, this guide will walk you through why this happens and how to fix
it like a pro.
What Is SAP Error M8 732?
Error M8 732 pops up when SAP can’t find the necessary
tax information during a consignment settlement. In simpler terms: the
system doesn't know what tax rules to apply, so it just stops you in your
tracks. This usually means that something’s off in the purchasing info
record or plant-to-purchasing org assignments.
Common Reasons Behind the Error
1. No Purchasing Org Assigned to Plant
If Plant XX doesn’t have any purchasing organization assigned,
the system has no path to retrieve tax data.
2. Multiple Purchasing Orgs Without a Standard
If your plant is linked to more than one purchasing organization
and there’s no default set, SAP won’t know which one to pick.
3. Missing Tax Code in Info Record
The vendor-material-plant-purchasing org combo doesn’t
have a tax code maintained in the consignment/pipeline info record.
Step-by-Step Fix
Step 1: Validate Plant Assignments
-
Go to transaction OX17.
-
Check the assignments under:
-
Plant -> Purchasing Organization
-
Plant -> Standard Purchasing Organization
Step 2: Check Info Record in ME13
-
Use ME13 to display the info record.
-
Verify if the tax code is populated for the consignment vendor
and material.
Step 3: Create or Update Info Record in ME11
-
If the info record doesn’t exist, create it using ME11.
-
Ensure the Control Data section includes a valid Tax
Code.
Step 4: Activate Consignment in OMEV
-
Go to transaction OMEV.
-
Confirm that consignment processing is active.
Step 5: Rerun MRKO With Specific Selection
-
Instead of running MRKO broadly, narrow down the selection:
-
Use Material Document or Consignment Material.
-
Avoid using only Company Code and Plant as this triggers
the error across all records.
Pro Tip: Understanding the System Logic
Here’s the thing: If multiple info records exist and even
one lacks a tax code, the system fails the entire consignment settlement—even
if other records are correctly maintained. SAP evaluates line items collectively.
Helpful SAP Notes for Deeper Reference
-
SAP Note 140675 – Tax Code Determination in Consignment
-
SAP Note 350450 – MRKO List Display Behavior
-
SAP Note 139792 – Tax Indicator Logic in Info Records (as
of 4.0)
Final Thoughts
Fixing SAP’s consignment settlement issues can be a pain,
but once you understand the logic, it's totally manageable. Just think
of it like setting the GPS right before your trip—once you’ve got the
right directions (purchasing orgs, tax codes, and info records), the journey
becomes smooth.
FAQs
1. What is a consignment info record in SAP?
It's a purchasing info record specific to consignment materials,
storing data like pricing and tax codes between vendor and material.
2. Can I have multiple purchasing organizations for one plant?
Yes, but make sure one of them is set as the standard,
or SAP won’t know which one to use.
3. Why does MRKO fail even when tax code is maintained?
If any info record related to the selection lacks
a tax code, the error triggers for all items.
4. What if no info record exists?
You must create one using ME11—this is mandatory
for settlement.
5. Is this error specific to any SAP version?
It mostly appears in older ECC systems but can still occur
in S/4HANA depending on configurations. |
SAP MM Tips
|