Skip to main content

Celonis Product Documentation

Currency Conversions

The Procurement App makes use of the SAP Currency Conversion features. This feature makes use of the Run-time variables to define the ‘target currency’ in which the app is displayed from inside the app. The benefit here is that you can provide all regions of your business with their local currency, while only having to process 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.

  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 to create the value converted columns throughout the data jobs (e.g., PR_EBAN or PR_EKPO; already provided by default in the jobs)

  4. Create views of the currency tables (TCURR_CC, TCURF_CC and TCURX) in the Global PR 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.

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

FAQ - Open Purchase Requisition App

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 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 the local currencies never need to switch to those currencies. By not storing this mapping, the SAP system can operate with less data used for currency conversion mappings.

Because these mappings often do not exist between all local currencies, the PR 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.