Analytics Legends The knowledge platform for SAP Analytics
Academy module

Currency Conversion & Units

Currency and unit conversion architecture: source systems, reference rates, one foundation conversion view per combination, consumers — architecture diagram for Currency Conversion & Units, Analytics Legends Academy module M009

As of 2026-08-16

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

4 conversion methods (date · period-end · average · custom). Senior pattern: 1 conversion view per (source × target × method) in foundation space, reused everywhere. NEVER hardcode rates. Read from TCURR-replicated table. Index rate table; partition fact by date if conversion is dominant cost.

What you will learn

  • Understand the core concepts behind currency conversion & units
  • Apply Currency in a typical SAP analytics engagement
  • Recognize the 3-5 common mistakes and how to avoid them
  • Position this skill in your personal brand and rate conversation

Module overview

Currency conversion = the operation that turns "€5M French sales + £3M UK sales + $7M US sales" into "consolidated EUR revenue". Get this wrong and the CFO finds out at month-end close — every time. Datasphere supports 4 conversion methods; senior consultants pick per use case and document.

The 4 methods.

  1. Date-based rate — convert at the transaction's posting date (revenue recognition standard, IFRS / US GAAP).
  2. Period-end rate — convert at month-end (balance sheet standard).
  3. Average rate — month/quarter/year average (income statement consolidation).
  4. Custom rate — corporate plan rate, historical rate, hedged rate (planning + budgeting).

The senior pattern. Define ONE conversion view per (source × target × method) combination in the foundation space. Reuse across all consumers. Never let two consumer views convert independently — drift WILL happen.

Unit conversion follows the same logic: ONE conversion view per (unit × method). UoM tables in S/4HANA (T006) are authoritative; reflect them in the foundation space, not in each consumer.

Prerequisites

  • Review core concepts first: C008, C012, C006

Outcomes

  • Understand the core concepts behind currency conversion & units
  • Apply Currency in a typical SAP analytics engagement
  • Explain the core architecture and decision points for Currency Conversion & Units
  • Apply a repeatable implementation pattern in a 15-minute lab format

Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.

Open in the app →

Next in this track