OB08 — Maintain Exchange Rates
OB08 is used to maintain exchange rates by rate type, currency pair and validity date for financial and logistics conversion. It is most useful when period-end rates, daily rates or missing currency conversions must be entered or validated. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains OB08 — Maintain Exchange Rates — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 617 words
Esta página aún no está disponible en español.
Purpose
maintain exchange rates by rate type, currency pair and validity date for financial and logistics conversion. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
OB08 is typically used when period-end rates, daily rates or missing currency conversions must be entered or validated. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Confirm the rate type required by the business process.
- Check whether an existing rate already covers the date.
- Maintain the approved market/treasury rate with correct quotation direction.
- Validate factors for currencies with non-1:1 scaling.
- Test a representative posting or valuation.
Key data objects
These are the fields and business objects that usually explain the result in OB08. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- rate type — verify the exact value, validity/date context and source of derivation.
- from/to currency — verify the exact value, validity/date context and source of derivation.
- valid-from date — verify the exact value, validity/date context and source of derivation.
- direct/indirect quotation — verify the exact value, validity/date context and source of derivation.
- translation factors — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
OB08 remains relevant on S/4HANA for exchange-rate maintenance; many enterprises feed rates automatically, so manual entries should follow Treasury governance. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Entering the inverse rate in the wrong quotation direction. Reconcile the exact document and period before making a configuration change.
- Using today's rate to fix a historical document. Reconcile the exact document and period before making a configuration change.
- Maintaining a rate manually when an automated feed should be corrected upstream. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ob08ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.