Skip to main content

Celonis Product Documentation

Data Model Best Practices

General Best Practices
  • Whenever possible, name tables after their names in the source system.

  • Connect tables as you joined them in the transformations.

  • Only join the case table and the master data for activities to the activity table.

  • For memory footprint reasons, use tables for data representation with complex logic instead of views.

  • For performance reasons, only use views of master data tables.

  • Keep the data model as simple as possible.

Foreign Key Relationships

When connecting tables via foreign keys in a data model, consider:

  1. Tables with a 1:n relationship are correctly joined automatically.

  2. For tables with a 1:1 relationship, the join direction has to be considered for pull functions to work properly. You can only pull from the fact to the dimension table. In the example below, you could only pull from BSEG to LFB1, e.g. PU_COUNT(LFB1, BSEG.LIFNR).

50727017.png

To check the cardinality between tables, go to any workspace in the EMS and click on the data model icon (marked in red below).

50727018.png

A screen similar to the following will open and cardinalities can be inspected by hovering your cursor over the connection.

50727019.png