Celonis Product Documentation

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: Runtime variables present in the IM Starter Kit but not in MDI are stored as regular Knowledge Model variables in the latter. 

The business logic is packaged into formulae (KM KPIs) to reuse in the different parts of the app or inside of other KPIs/formulae to make the setup more concise.

These PQL-statements define the calculations of KPIs, filter statements on your data, and inefficiencies. Hence they are one of the most important parts of the app.

To give you an example, the formula KPI_MATERIAL_CALC_ACTUAL_PURCHASE_LEAD_TIME is used both for evaluating purchase orders as well as for computing related planning parameters (e.g., Recommended Purchase Lead Time, Recommended Safety Stock, etc.). So by adjusting the underlying business logic in that one place, you adjust the business logic for all KPIs and related definitions at once.

This list is not exhaustive and should be checked inside of the Knowledge Model. Make sure to also check nested formulas that might be used within the listed KPIs below. You can identify by the prefix whether it’s defined as KPI or formula.

In case you update the underlying business logic or used variables, please make sure to also update the documentation for the business users in the Documentation folder.