Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
giovani_quadros
Associate
Associate
1,912

MIRO invoices are like airplanes: there is a whole checklist of security items to ensure that everything is properly set up to prevent risks and ensure that you're good to go.

tumblr_m41eqfKKQV1qg8r34o1_500.gif

However, it would be particularly frustrating if a pilot were simply not able to take off if an unknown error message simply showed up, moments before taking off!

SAP clerks may also face a similar frustration when trying to post invoices in MIRO and a sudden error message M8889 shows up moments before posting the invoice, when everything looked so correct!
MIRO invoices are generally not the case of life and death like planes, but financial impacts may also be a significant concern if the invoice is not posted in time.

So far, I have processed 20+ cases with exactly that same situation.
The good news is that that situation always has the exact same solution.

Short answer: The explanation and solution can be found in this KBA:
3277397 - MIRO: error message M8889 "Account XXXXXX has been set as not relevant for tax" - SAP ERP ...

However, if that KBA is too technical for you, or you are too nervous to get into details, fasten your seat belts and let's understand what's going on.

tumblr_5682d7c29bb37164983b87bbf895ce6e_e3ff1f25_500.gif

Although both planes and software pass through thorough security inspections, new problems may still be detected throughout time, even though the engineers thought that everything was properly covered!

But things like these happen... And something like that happened recently when SAP Note 3109666 was released.

That note basically says that no errors were being returned when a G/L account was set as not relevant for tax, and yet a posting line had that account and a tax code at the same time.
You may not agree, but that is actually a problem from SAP software perspective!
To fix that problem, program code was edited to trigger M8889 when it should always have been triggered!

So, if you suddenly started facing that error message, your SAP system had most probably gone through an update that included SAP Note 3109666.
And there is also no need to worry, your system is safer!

You might be asking now: "But it was OK to post that kind of invoice in the past, I just want to keep posting invoices that way!"
Well, I just said that there's no need to worry: simply set M8889 as a warning message in transaction code OMRM and then you will be available to keep posting invoices that way. The only difference will be the warning message.

d1a55c5a9579a3ef5380a31e2f2a749d.gif

By the way, all these images are from Plane Crazy (1928), featuring Mickey Mouse's first appearance.
That cartoon is entering public domain in 2024, so I guess there are no copyright infringements.
If the question is now solved for you, you may grab a cup of coffee and enjoy the short film (and try to find a possible Felix the Cat appearing nearly the end!).