Skip to main content

Celonis Product Documentation

Troubleshooting views and analyses

Here's troubleshooting tips for using object-centric perspectives with views, analyses, and other assets in Studio. The main documentation is at Using objects and events for process mining.

Troubleshooting object-centric process mining lists all the troubleshooting topics to help you create object-centric data models.

I am using an analysis in Studio, and getting the error message “Invalid PQL.CURRENCY_CONVERT: FROM_CURRENCY [ABC] not found in the conversion rates table [o_celonis_CurrencyConversion]”

This error message means that you are using the PQL formula CURRENCY_CONVERT and that you are passing the formula a value for the from_currency parameter that does not exist in the o_celonis_CurrencyConversion object type table.

There are several possible causes of this problem, including extraction filters on the input tables and incorrect source data. However, the most common cause for SAP data is that the Celonis-supplied transformation for the CurrencyConversion object applies a filter based on the column “TCURR”.”KURST'' and the parameter ExchangeRateType. The default value for the ExchangeRateType parameter is 'EURX', but that might not be the correct value for your SAP instance. Check the source system data to determine which value would be correct here. If that’s the issue, update the value of the local parameter ExchangeRateType for the CurrencyConversion transformation to the correct value, then publish your changes.

octrouble_dx_15.png
I want to adjust or localize the object and event names that are displayed in a view, analysis or other frontend asset in Studio

The object and event names displayed in views, analyses, and other frontend assets in Studio use the object type names and event type names for the Celonis and custom types in your object-centric data model. You might want to adjust the names for display purposes - for example, to add spaces - or to match the language settings of the current user.

You can change the display names using a table name mapping. To help you decide if your desired changes are worth the effort, note that you’ll need to upload your table name mapping for all the perspectives for which you want to make this change, including both the development and production versions. You’ll also need to maintain the table name mapping for all object types and event types going forward. Using a custom table name mapping will override the implicit translation that happens by default.

If you want to define your own table name mapping, go to the perspective’s data model in the OCPM Data Pool, and locate the Name mapping tab. Click on Download Current Mapping at the top right. The downloaded file is an Excel template that you can adjust to meet your needs. For example, to rename an event, add a suitable value in the TRANSLATION column for the event type table. For details on defining a table name mapping, see Name Mapping From File.