Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Thanks for your help!
The condition record didn't have a printer assigned. That's what was causing the error.
--- On Fri, 8/6/10, ha_tran via sap-log-mm <sap-log-mm@Groups.ITtoolbox.com> wrote:
From: ha_tran via sap-log-mm <sap-log-mm@Groups.ITtoolbox.com>
Subject: RE:[sap-log-mm] ERS Settlement: No message found (works correctly for other co codes)
To: "Keith Hyams" email@removed
Date: Friday, August 6, 2010, 4:19 AM
Posted by ha_tran (Senior SAP Supply Chain Business Analyst)
on Aug 6 at 4:21 AM Mark as helpful
Hi,
The message indicates that the condition record for ERS message type was not defined for your partner xxxx and company code xxxx combination. Therefore, what you should do is to go to Transaction MRM1 and maintain related condition record before running MRRL again.
Cheers,
HT
---------------Original Message---------------
From: Keith Hyams
Sent: Thursday, August 05, 2010 8:55 PM
Subject: ERS Settlement: No message found (works correctly for other co codes)
> Hi ,
>
> We recently added a new co code in development and have been unable to run MRRL successfully.
>
> The transaction finds the appropriate POs and Receipts, but we get the following error message:
>
> (ERS settlement: No message was found for partner xxxx/company code xxxx)
> Message no. M8446
>
> We do not get the message when we run MRRL for other co codes using the same vendor. I've checked the purchasing info record for the material and the No ERS box is un-checked.
>
> Any help is definitely appreciated.
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Related Content White Papers
In the Spotlight  _.____.__ |
Mark as helpful
