Technology Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 

Introduction: Currency Conversion in SAP

In SAP landscapes such as S/4HANA, SAP Datasphere, and SAP Analytics Cloud (SAC), handling multiple currencies is a fundamental requirement due to global operations and diverse organizational structures. Business transactions are usually posted in the local currency of the country where the transaction takes place, but reporting and analysis often require additional currency perspectives

SAP systems can support multiple organizational and reporting currencies, depending on system configuration and business requirements, such as:

Company Code Currency -  The legal reporting currency used for statutory and financial reporting.

Group (Global) Currency - Used for consolidation and group-level reporting across multiple company codes.

Profit Center Currency - Enables profitability analysis when a dedicated profit center currency is configured.

Cost Center Currency - Supports internal cost tracking and management accounting scenarios.

Transaction Currency - The currency in which the original business transaction is posted.

Controlling Area Currency - Used for management accounting and controlling across company codes.

Document Currency - The currency stored at the accounting document level for audit and traceability.

Functional Currency - Represents the primary currency of business operations, commonly used in management reporting.

To ensure accurate and comparable reporting across entities and regions, these currencies must be converted using well-defined exchange rates.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Currency conversion in SAP Datasphere plays a key role by:

  • Centralizing currency conversion logic
  • Enabling consistent currency handling across models
  • Providing harmonized financial data for analytics and planning in SAC

This makes SAP Datasphere the foundation for reliable multi-currency reporting in modern SAP analytics scenarios.

In SAP Datasphere, currency conversion can be implemented in Graphical Views, Analytical Models, and SQL Views, and can also be applied dynamically at runtime in SAP Analytics Cloud.

In the following post, I will be covering the currency conversion in graphical view with BW as a source system.

Prerequisite:

Based on the source system (BW, S4HANA etc) the ABAP connection should be configured from source to Datasphere system.

Step 1: Import TCUR* tables, views, data flows and remote tables into Datasphere Tenant

Go to Data Builder

Lokesh_Kumar_Pothapola_0-1770356286322.png

Select '+' symbol

Lokesh_Kumar_Pothapola_1-1770356286326.png

Select 'Currency Conversion Views'

Lokesh_Kumar_Pothapola_2-1770356286326.png

Note: In the Source drop down list, based on the type of source different artifacts will be created in Datasphere.

Manual - Local tables and views

SAP S/4 HANA Cloud / On Premise - Local tables, views and data flows will be imported
SAP ABAP connection - Local tables, views, data flows and remote tables will be imported.

Select Connection as ABAP

Lokesh_Kumar_Pothapola_3-1770356286327.png

By selecting ABAP as a source - Local tables, views, data flows and remote tables will be imported.

Lokesh_Kumar_Pothapola_4-1770356286328.png

Click on 'Create' - All the objects will be imported in to Datasphere tenant, localize the objects in a folder to use globally for different spaces.

Note: Naming convention as follows by default, option available to change Business Name

Remote tables - SAP.CURRENCY.RTABLE.TCUR*

Data Flows - SAP.CURRENCY.DATAFLOW.TCUR*

Tables - SAP.CURRENCY.TABLE.TCUR*

Views - SAP.CURRENCY.VIEW.TCUR*

Once you’ve created the currency conversion views and their supporting objects, you can share the TCUR* tables with other spaces. The spaces to which you share these tables will then see your space as an alternative source in the Source field above.

Step 2: Make TCUR* data available from BW to SAP Datasphere

Since the connection type is ABAP with BW, the existing source tables in the BW system must be mapped to their corresponding remote tables in SAP Datasphere.

Select the Remote table which are imported automatically in the system.

Example: For TCURR configuration, the same steps must be repeated for all imported TCUR* tables.

Go to 'Data Builder'

Lokesh_Kumar_Pothapola_5-1770356630740.png

Search 'SAP.CURRENCY.RTABLE.TCURR' table

Lokesh_Kumar_Pothapola_6-1770356630741.png

Open the table and set up the 'Remote' connection details (BW_ABAP : configured ABAP connection from BW to Datasphere)

Lokesh_Kumar_Pothapola_7-1770356630743.png

Note: There are different methods to replicate data into Remote table:

Start Data Replication: Fetches data from the source BW ABAP table (TCURR) into the corresponding remote table in SAP Datasphere and stages it. This step can be included in a task chain. (STAGED)

Enable Real-Time Replication: Reads data virtually from BW into SAP Datasphere on demand, without staging. (VIRTUAL)

Once this step is completed, go to 'Data Builder' -> search for data flow 'SAP.CURRENCY.DATAFLOW.TCURR' -> Select 'Run'

Lokesh_Kumar_Pothapola_8-1770356630744.png

Note: The data flow can be scheduled to run at regular intervals or included in a task chain for daily execution.

Once the data flow is completed (which can be monitored using the icon below), the data can be viewed in the currency view SAP.CURRENCY.VIEW.TCURR, a default SQL-based view provided by SAP

Lokesh_Kumar_Pothapola_9-1770356630744.png

SAP.CURRENCY.VIEW.TCURR (provided by SAP)

Lokesh_Kumar_Pothapola_10-1770356630745.png

 

Step3: Currency conversion in Datasphere views.

Go to 'Data Builder' (select space if applicable)

Lokesh_Kumar_Pothapola_12-1770357055415.png

Select 'New Graphical View' or select if any existing view available which requires currency conversion.

Lokesh_Kumar_Pothapola_13-1770357055416.png

There are three columns:

'Sale_Amount_CompCode' the measure contains amount to be converted

 'Company_Code_Currency' holds the source currency

 'Profit_Center_Currency' holds the target currency

Go to View -> Select the node where currency conversion need to apply -> Add 'fx' step

Lokesh_Kumar_Pothapola_14-1770357055418.png

Select 'fx' step -> Details -> select '+' -> select 'Currency Conversion Column'

Lokesh_Kumar_Pothapola_15-1770357055418.png

Set the Element Properties

Provide Business Name, Technical Name, Data type and Decimal changes

Lokesh_Kumar_Pothapola_16-1770357055420.png

Currency Properties

Lokesh_Kumar_Pothapola_17-1770357055421.png

Source Amount Column - Represents the column which requires conversion in this case 'Sale_Amount_CompCode''

Source Currency - Currency works as a source value  in this case 'Company_Code_Currency'

Target currency - Currency works as a target value in this case 'Profit_Center_Currency'

Reference Date - This is Year/Date to be used as a reference during conversion.

Steps: Different options available and one of the key element

Lokesh_Kumar_Pothapola_18-1770357055421.png

 

Shift

The amount is multiplied to remove decimals. Example 123.45 USD → 12345

Convert

The shifted amount is converted using the exchange rate. Example 12345 × exchange rate

Round

The converted value is rounded based on the target currency’s decimal rules.

Shift Back

The value is divided to restore the correct decimal places.

Note: For any simple currency conversion, recommended to select only 'Convert' and 'Round'

Lokesh_Kumar_Pothapola_19-1770357055422.png

Conversion properties

Lokesh_Kumar_Pothapola_20-1770357055422.png

Client - Client 000 is typically used for currency tables in SAP systems

Conversion Type - Exchange rate type maintained in TCURR (for example, M – Standard rate, P – Budget rate)

Error Handling - Defines the value to be generated if no valid exchange rate is found.

Advanced Properties

Lokesh_Kumar_Pothapola_21-1770357055423.png

Lookup: Regular and Reverse (to be selected if reverse exchange rate is maintained in the system)

Accuracy: Compatibility (Matches classic SAP (ECC/BW) currency results) and Highest (Provides maximum precision for accurate financial reporting)

Date Format: Auto Detect (Automatically picks the correct date format from source data and applies the right exchange rate)

All remaining views relevant to TCUR* will get auto populated by default, as its configured at beginning.

Activate and Deploy the view

Result Output:

Lokesh_Kumar_Pothapola_22-1770357055424.png

Exchange rate from AUD to GBP is maintained as 1.75 in BW system

Data From BW System:

Client

Exchange Type

From

To

Valid From

Exchange Rate

600

P

AUD

GBP

01.01.2025

/1.75

Values are converted using the applicable exchange rate and published in a new column called “Profit Center Amount.”

Conclusion: By centralizing currency conversion logic in SAP Datasphere, organizations can ensure consistent, auditable, and scalable multi-currency reporting across analytical and planning scenarios. This approach simplifies downstream consumption in SAP Analytics Cloud while maintaining alignment with SAP’s standard currency configuration.

 

Thank you for taking the time to read this article. I hope this overview helps you understand and implement currency conversion in SAP Datasphere more effectively. Your feedback, questions, and suggestions are welcome in the comments section.

 

Regards

Lokesh Kumar Pothapola

 

 

 

 

 

 

 

 

 

 

 

Labels in this area