How to Ensure GR is Valuated at the Exchange Rate Defined in the PO (SAP) 

Introduction

Let’s be honest—there’s nothing more frustrating than carefully setting up a purchase order (PO) in SAP with a specific exchange rate, only to have your Goods Receipt (GR) and subsequent Invoice Receipt (IR) reflect something entirely different. Imagine negotiating with a vendor at 1 USD = 40 INR, and by the time the invoice gets posted, SAP decides it’s 43 INR instead. Not good. In global procurement, exchange rate mismatches can mean accounting headaches, vendor disputes, and even audit red flags. So, how do we lock in the exchange rate from PO all the way through to invoice verification? The answer lies in understanding the right SAP configurations, how exchange rate types work, and when to use the "Exchange Rate Fixed" indicator. Let’s walk through it.

Understanding Exchange Rates in SAP

An exchange rate in SAP determines how the system converts one currency into another. These rates are stored in transaction OB08 and are usually maintained based on exchange rate types like "M" (average rate), "B" (bank buying rate), "G" (bank selling rate), or custom ones like "PP" (for purchasing processes). By default, SAP pulls the exchange rate from the standard type "M" unless told otherwise. This rate is updated periodically and can fluctuate, which is great for real-time data, but not ideal when you want consistency between your PO and your final invoice.

Where Exchange Rates Matter: PO, GR, and IR

There are three major points in SAP procurement where the exchange rate comes into play: 
1. PO (Purchase Order - ME21N/ME22N): You can manually enter or let the system fetch the exchange rate from OB08. If left unchecked, this value can change later. 
2. GR (Goods Receipt - MIGO): The system usually uses the rate type tied to the GR document type. But if your PO has a fixed rate, it should carry over. 
3. IR (Invoice Receipt - MIRO): If the exchange rate wasn't fixed earlier, this is where discrepancies often show up. 
Each step depends heavily on how the exchange rate is configured in the PO.

Fixing the Exchange Rate at the PO Level

Here’s the golden rule: If you want the same exchange rate to be used across PO, GR, and MIRO, fix it at the PO stage. While creating or editing a purchase order in ME21N or ME22N, go to the Header section and tick the checkbox for “Exchange Rate Fixed.” Once this is done and the PO is saved, that rate is locked. It cannot be changed during Goods Receipt or Invoice Verification. This is especially useful when working under contract terms that guarantee a specific rate. Think of this checkbox like freezing a moment in time. You're telling SAP, “No matter what the market rate is later, use this one.”

OB08 Configuration: Defining Exchange Rates

The OB08 transaction is where the magic begins. Here, you can define exchange rates for different currency pairs, valid from and to specific dates, using various exchange rate types. Let’s say you want 1 USD = 40 INR starting from 01.08.2008. You enter this into OB08 under the rate type "PP" (assuming that's your purchasing-specific rate type). However, here’s the catch: if your PO is defaulting to rate type "M" and you haven’t manually selected "PP", then SAP will continue to use whatever rate is defined under "M". Another common mistake is not aligning the validity period in OB08 with the document date of your PO. Always double-check the dates to ensure your desired rate is active.

Common Mistakes in Exchange Rate Handling

Here are the top missteps we see SAP users make: 
  • Forgetting to tick “Exchange Rate Fixed” in the PO.
  • Expecting the rate to auto-correct later in MIGO or MIRO. 
  • Using the wrong exchange rate type without realizing what the default is. 
  • Posting GR before correcting the PO, then getting stuck with the wrong valuation. 
  • Assuming exchange rates will be consistent across document types without configuration. 
Avoiding these common errors can save hours of rework and potential reversals.

Step-by-Step Guide: PO to GR to MIRO with Fixed Rate

Here’s how you make sure your exchange rate stays fixed from start to finish: 
1. Create the PO in ME21N. 
2. Enter the desired exchange rate manually or let it pull from OB08. 
3. Tick the “Exchange Rate Fixed” checkbox in the header. 
4. Save the PO. 
5. Post the Goods Receipt via MIGO. The system will use the PO's exchange rate if it was fixed. 
6. Post the Invoice via MIRO. The rate will remain unchanged if the checkbox was selected earlier. 
Voila! You’ve just locked in your procurement exchange rate like a pro.

Advanced Tip: Reversing GR to Correct Exchange Rate

Made a mistake? Don’t worry—it happens to the best of us. If the Goods Receipt has already been posted with the wrong exchange rate, and the PO was not fixed, here’s what you can do: 
  • Reverse the GR using MIGO. 
  • Edit the PO in ME22N, enter the correct rate, and fix it. 
  • Repost the GR with MIGO. 
  • Then proceed with MIRO. 
It’s a bit of backtracking, but it works.

How Exchange Rate Type Impacts GR and MIRO

Here’s the thing: the exchange rate type used during GR often depends on the configuration of the GR document type. If that document type is set to use “M”, it will always fetch the current OB08 rate for “M” unless overridden by a fixed PO rate. Same applies for MIRO. If the PO doesn’t have a fixed rate, MIRO uses the current OB08 rate of the configured type, which may be different than what you wanted. Bottom line: Use fixed rates in PO if consistency is your goal.

Case Study: USD to INR Procurement Flow

Let’s say you maintained the following in OB08: 
  • Exchange Rate Type: PP
  • Currency Pair: USD → INR - Rate: 1 USD = 40 INR 
  • Valid From: 01.08.2008 But your PO is using exchange rate type “M”, and the system shows 1 USD = 43 INR. 
Unless you manually change the rate in the PO and tick “Fixed,” your downstream GR and MIRO will default to the new 43 INR. This is why configuration and awareness at the PO level are so critical.

When Not to Fix Exchange Rate

There are situations where fixing the exchange rate might actually be counterproductive. For instance: 
  • If you want the most current market rate to apply at time of invoice. 
  • If your vendor agreements allow flexible pricing based on currency fluctuations. 
  • For low-value transactions where the gain/loss isn’t material. 
In those cases, leaving the rate unfixed and letting the system auto-update via OB08 might be smarter.

Exchange Rate in Framework Orders and Contracts

Framework orders and long-term contracts present their own challenges. Since these can span months or years, fixing an exchange rate early could lock you into a disadvantageous rate. In such scenarios: 
  • Define rate validity intervals. 
  • Consider multiple condition records. 
  • Or set dynamic pricing rules based on agreed-upon ranges. 
Talk to your finance team before locking anything down.

Troubleshooting Exchange Rate Discrepancies

Here’s a quick checklist when the exchange rate seems off in GR or MIRO: 
  • Was the “Fixed Exchange Rate” box selected in the PO? 
  • Is the correct rate type maintained in OB08? 
  • Are the document and rate validity dates aligned? 
  • Is the GR document type configured to use the expected rate type? 
Most exchange rate issues trace back to one of these.

Important SAP Transactions Involved

Here are the key transactions to keep in your toolkit: 
  • OB08: Maintain currency exchange rates 
  • ME21N / ME22N: Create or edit purchase orders 
  • MIGO: Post goods receipt 
  • MIRO: Enter incoming invoice 
Knowing when and where to act makes all the difference.

Expert Best Practices for SAP Procurement Teams

Here are a few battle-tested tips from experienced SAP professionals: 
  • Always review exchange rate during PO approval. 
  • Use custom exchange rate types if business requires. 
  • Train your buyers on OB08 implications. 
  • Document currency rules with vendors in contracts. 
  • Use PO printouts or SAP messages to confirm fixed rates with stakeholders. 
These small steps save big headaches.

Conclusion

Ensuring your Goods Receipt is valuated at the same exchange rate defined in your Purchase Order isn’t rocket science—but it does require a bit of upfront diligence. By understanding how exchange rates work in SAP, fixing them appropriately in your PO, and aligning your document types, you can maintain consistency, compliance, and financial accuracy. Just remember: it all starts at the PO.

Frequently Asked Questions (FAQs)

1. What happens if I don’t fix the exchange rate in the PO?
SAP will use the latest rate from OB08 during GR and MIRO, which may cause mismatches.

2. Can I change the exchange rate after GR?
Not directly. You’ll need to reverse the GR, update the PO, and re-post it.

3. Why does MIRO pick a different rate than PO?
Because the PO didn’t have a fixed rate, and MIRO is pulling the latest from OB08.

4. What is the best exchange rate type for purchasing?
“PP” is often used for purchasing-specific rates. But it depends on your organization’s policy.

5. How do I know if GR used the correct rate?
Check the accounting document generated during MIGO. It will show the valuation rate.

Get help for your SAP MM problems
SAP MM Forums - Do you have a SAP MM Question?

SAP MM Books
SAP Material Management Certification, Interview and Configuration Reference Books

SAP Material Management Tips
SAP MM Configuration Tips and Materials Management Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.