Skip to main content

Celonis Product Documentation

Variable Configuration

To start with the variable configuration, please go to the Knowledge Model (KM).

Go through the variables section in the view mode and validate whether the input used for the variables is correct for your business needs. To view all variables in use, you can navigate to the variables section of the KM.

For the apps, only non-auto-generated configurations are used, so you can disable the auto-generated definitions. In some cases, variables are used for storing values (strings, integers, etc.) that are used inside of KPIs and inefficiencies, such as the Planned Lead Time, for storing target and benchmark values of KPIs and frequently used activity names like the “Goods Issue” activity.

Some variables are more important than others to update, in the sense that the business logic of the app will not work if they are not set correctly. An example are the variables that reference different fields and activity names, e.g. the ‘Record Goods Receipt' activity.

On the other hand, all variables are set with a default value and, in some cases, the app will still function properly if they are not updated, e.g. the ‘Desired Service Level’. If you identify some variables that need to be adjusted, you can easily update them directly inside of the variable part of the KM visual editor.

Other variables are stored in the plain text variables section of the package settings. These variables can also be changed if needed and are only affecting the package in which they are defined.

Note

Note on Knowledge Model Updates in a Dependency setting:

The Knowledge Model contained in the package of a fresh installation of MDI will only contain a reference to the Master Knowledge Model in the Starter Kit as well references to standard actions or naming conventions relevant for MDI.

Out of the box, any PQL queries will always be held in the Master Knowledge Model.

Logic created inside the local package Knowledge Model will only be applied to MDI and not the Starter Kit or other connected apps.

To make customizations made in the MDI Knowledge Model available in other apps using the IM Master Knowledge Model, copy and paste the changes to the Master Knowledge Model, publish the IM Starter Kit, and update the dependencies of any connected apps.

Important Variables to Validate and Update

Below you find a list of variables that should be validated during the app configuration. These variables can only be updated from the runtime variable editor or KM editor with ANALYST or ADMIN permissions.

Variable ID

Type of variable

Variable name/ description

toCurrency

Runtime variable

Currency to be displayed in app

fromCurrency

Runtime variable

Original currency

currencyConversionType

Runtime variable

Currency conversion type

PARAMETER_RECOMMENDATIONS_NUMBER_OF_MONTHS_PAST

KM

Number of past months (excl. current month) considered for parameter recommendations.

Default: 12

PARAMETER_RECOMMENDATIONS_NUMBER_OF_MONTHS_FUTURE

KM

Number of future months (excl. current month) considered for parameter recommendations.

Default: 4

PARAMETER_TOLERANCE_MASTER_DATA_RECOMMENDATION

KM

Tolerance used for highlighting and prioritizing parameter recommendations.

Default: 0.2

Note

Runtime variables not listed here are inherited from the IM Starter Kit and do not need to be reconfigured for MDI.