We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re:RE:[sap-log-mm] Error MIRO

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by nesta_kettyfunz
on Oct 10 at 9:28 AM
Mark this reply as helpfulMark as helpful
Hi,Skandios
According to your problem, I suppose your company use the Standard price as the price indicator.
To solve this problem, you need to do
At frist, make sure that's account in UMB (You can find the UMB in T-code: OBYC)

Secound, make sure this account which assign to UMB set a tax category.

After then, I think your problem will be resolved.


------------------ Original ------------------
From: "ha_tran via sap-log-mm"email@removed;
Date: 2010?10?10?(???) ??12:47
To: "nesta_kettyfunz"email@removed;
Subject: RE:[sap-log-mm] Error MIRO


Posted by ha_tran (Senior SAP Supply Chain Business Analyst)
on Oct 10 at 1:38 AM Mark as helpful
Hi,

Did you get the same problem when posting LIV invoice with reference to PO in MIRO Transaction?. Did you make any setting under IMG ---> Material Management ---> Logistics Invoice Verification ---> Incoming Invoice ---> Maintain Default Values for Tax Codes? What was the error message number?

Cheers,
HT

---------------Original Message---------------
From: skandios
Sent: Friday, October 08, 2010 6:06 AM
Subject: Error MIRO

Hi all,
I'm facing a problem during MIRO registration. When I simulate the registration some account items do not have the tax code assigned. That blocks the MIRO posting because the document type requests a tax code.
The lines involved are those of UMB procedure (revenue/loss for revaluation)
Any advice?
Skandios
__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
Most Popular White Papers

In the Spotlight
Assess and overcome obstacles to realize the benefits of cloud. Join the IBM virtual discussion Oct. 14 @ 2 pm ET
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language