Skip to main content

Celonis Product Documentation

2. Adjusting the Knowledge Model to fit your Data Model
2.1 Making adjustments in the Knowledge Model

In the Knowledge Model, we use variables and formulas to provide better maintainability as well as permit the bulk change of values. During the first setup of the App, you need to check both the variables and formulas. You should start by validating and adjusting the variables and then validating and adjusting the formulas.

  1. To perform the validation, align with your customer’s SAP IT Business Partner and Process Owner. They have knowledge about the data structure and are aware of customizations that might need to be included.

  2. To validate the PQL statements of the variable/formula, use analysis in the same Data Model, copy and paste the PQL statements into it and validate the results with your SAP IT Business Partner.

  3. If required, adjust the variable/formula in the Knowledge Model by:

    1. Copying relevant code in View mode.

    2. Entering Edit mode and pasting your selection.

    3. Adjusting the formula/KPI according to your preferences/needs.

For more information about how to make the adjustment in the Knowledge Model, watch this video.

 

Note

Links to the formula/KPI from dependent areas, such as filters for tasks and views, flags for execution gaps or KPI definitions, are automatically updated.

Although it uses many new studio components, all calculations (such as Filters, KPIs, Variables, Charts and Tables) are still based on PQL within the Knowledge Model. If you get any error messages, you can narrow them down to the respective PQL-statement and test your code in an analysis or view to check if you have any syntax errors.

2.2 Reviewing and adjusting variables

Note

If you have never worked with Knowledge Model variables before, you can find the documentation here. Currently, the App comes with:

  • Mandatory variables thatmustbe adjusted and reviewed.

  • Optional variables thatmayneed to be adjusted and reviewed.

Mandatory variables

Important

The VARIABLE_OPEN_ORDERS and VARIABLE_ORDER_TYPES are used for the global filters (i.e. FILTER_OPEN_ORDERS and FILTER_ORDER_TYPES) within the App and will be applied to all components using the Knowledge Model. If you get an error in your setup, you should start by checking they are working properly.

Variable Name

Description

Importance

ToDo

VARIABLE_ACTIVITY_

RECORD_GOODS_ISSUE

Defines the activity name for the goods issue.

Orders that have a goods issue are considered not open anymore.

Enter the String of how your activity for the goods issue is called within your event log.

Default value:

Record Goods Issue

VARIABLE_ACTIVITY_

CREATE_INVOICE

Defines the activity name for creating the invoice.

Orders that have an invoice created are considered not open anymore.

Enter the String of how your activity for creating the invoice is called within your event log.

It is important to only take customer invoices into account and no pro-forma invoices, credit/debit memos or inter-company invoices.

Default value:

Create Invoice

VARIABLE_OPEN_

ORDERS

Filters on only the open sales orders.

Acts as a global filter on the entire App.

Enter the PQL Statement/Condition of how you define an open order.

Reuses the activity for goods issue and invoice creation but also the Order Status.

Default value:

 

OR

(

PROCESS NOT EQUALS ('${VARIABLE_ACTIVITY_CREATE_INVOICE}','${VARIABLE_ACTIVITY_RECORD_GOODS_ISSUE}') AND PU_LAST(VBAK,VBUK.GBSTK) = 'C')

VARIABLE_ORDER_TYPES

Selects the Order types in scope.

Acts as a global filter on the entire App.

You may want to exclude some orders (e.g. by document type, order type or sales organization) from the Data Model.

Enter the PQL Statement/Condition of the order types in scope.

Default value:

VBAK.VBTYP NOT IN ('B')

VARIABLE_KNOWLEDGE_

MODEL_KEY

Enter the Knowledge Model key including the package key.

Necessary to map tasks and augmented attributes to the relevant knowledge model.

Enter the KM key copied from your Studio package. See the recording above of how this is done.

Default value:

order-management-execution-app-store.knowledge-model

Optional variables

Variable Name

Description

Default Value/Example

VARIABLE_ACTIVITY_CHANGE_CONFIRMED_DELIVERY_DATE

Defines the activity name for changing the confirmed delivery date.

Change Confirmed Delivery Date

VARIABLE_ACTIVITY_CREATE_DELIVERY

Defines the activity name for creating a delivery.

Create Delivery

VARIABLE_DATE_DELIVERY_DATE

Defines the deadline of the App, i.e. relevant how the order priority is calculated but also how tasks and execution gaps for overdue orders are classified.

PU_MIN(VBAP, VBEP.EDATU ,"VBEP"."BMENG">0 AND VBAP.ABGRU IS NULL)

VARIABLE_NET_ORDER_VALUE_CONVERTED

Defines the columns for sales order items where the converted value can be found.

VBAP.NETWR_CONVERTED

VARIABLE_WORKING_DAYS

Defines the working days. Important as considered for the deadline and how long it takes until orders are due.

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY

VARIABLE_TASK_ASSIGNMENT

Defines who tasks should be assigned to.

CASE WHEN VBAK.VKORG = '001' THEN 'a.person@celonis.com' ELSE 'order-management@celonis.com' END

VARIABLE_TASK_ASSIGNMENT_FALLBACK

Defines the fallback assignment (i.e. if the first user assignment was unsuccessful)

Best would be to assign one person by sales group or sales organization.

CASE WHEN VBAK.VKORG = '001' THEN 'a.person@celonis.com' ELSE 'order-management@celonis.com' END

2.3 Reviewing and adjusting formulas

If you have never worked with Knowledge Model KPIs before, you can find the documentation here.

Currently, the App comes with these formulas (see technical documentation here).Similarly as for variables, follow the guide to validate and adjust the formulas.