Skip to main content

Celonis Product Documentation

Currency conversion tables
General set up and overview

The Inventory Management App makes use of the SAP Currency Conversion feature. This allows for you to define the ‘target currency’ that the app should be displayed in on the fly inside of the app, by making use of the Run-time variables. The power here is that you can provide all regions of your business with their local currency, whilst only having to process this in the data model once.

In order to configure this correctly in the data pool, you will need to do the following:

  1. Ensure that you have defined these data pool parameters:

    1. Exchange-rate-type :This parameter should store the exchange rate type that you use for currency conversion. Oftentimes this is M or EURX.

    2. Currency:This parameter should store the target currency that you wish to convert to in the data transformations. Note: you will still need to define the package variables in the app set up. Specifically, the package variable ‘from-currency’ should equal the data pool parameter ‘currency’, and the package variable ‘currency-conversion-type’ should equal the data pool parameter ‘exchange-rate-type’.

  2. Create the currency tables TCURR_CC, TCURF_CC and TCURX in the local data job/s (already provided by default in the jobs).

  3. Use those tables in creating the value converted columns throughout the data jobs (eg. VALU_SALK3_CON in the Stock_history table; already provided by default in the jobs).

  4. Create views of the currency tables (TCURR_CC, TCURF_CC and TCURX) in the Global MM jobs (already provided by default)

    1. If you used multiple source systems in your local jobs, you should also union the tables together and add a source system ID, as explained in Multiple SAP Source Systems.

  5. Ensure that the three global views are available in the data model, with the aliases defined such that they’re named: TCURR, TCURX and TCURF.

FAQs about currency conversion tables

Why should I convert the columns to a single currency in the data jobs, and then convert back in PQL to all other currencies?

The currency conversion is set up this way because oftentimes the SAP system does not store the mappings between all possible currencies in the system. For example, there might not be a mapping between Indian Rupees (INR) and Swedish Krona (SEK), simply because those local currencies never need to switch to those currencies. By not storing this mapping, the SAP system can operate with less data tied up in currency conversion mappings.

Because these mappings often do not exist between all local currencies, the IM Connector first converts all currencies to a common currency that is mapped (eg. EUR, USD, GBP), and then allows you to convert back to other local currencies within the application. Essentially like a join n:1:n, OR local currency 1: common currency: local currency 2.