Helper objects

Helper objects are technical components of the Celonis object-centric data model designed to support calculations, logic reuse, and performance optimization. They are not intended for direct business consumption, but serve as foundational building blocks for KPIs, filters, and analyses. By centralizing complex logic, helper objects improve model maintainability, reduce duplication, and help ensure reliable, scalable insights across dashboards and use cases.

Helper objects are created during data modeling and analysis development in Celonis. Depending on their purpose, they may be implemented as:

Helper tables in the Data Model (e.g. via transformations or views).
Helper columns as calculated fields in tables.
Helper KPIs defined using PQL.
Helper views using PQL functions or pre-aggregations

When to use helper objects

Helper objects should be used when:

The same logic is required in multiple KPIs, filters, or analyses.
Calculations are complex, performance-intensive, or difficult to maintain inline.
The result is an intermediate value rather than a business metric.
Multiple analyses depend on a shared technical definition.

When not to use helper objects

Helper objects shouldn't be used when:

Logic is simple or used only once.
The object represents a business-facing metric or dimension.
There is no clear consumer (KPI, analysis, or table).
The object adds unnecessary complexity without performance or reuse benefits.

Examples of helper objects with PQL

The following examples can be used to illustrate when to use helper objects with PQL:

Example one: Helper table – Case duration

Used to pre-calculate case cycle time once and reuse it across multiple KPIs. This is good for when you're looking to track average cycle time KPIs, SLA compliance checks, or trend analyses

TABLE _HELP_CASE_DURATION AS
SELECT
  CASE_KEY,
  MIN(EVENT_TIME) AS CASE_START,
  MAX(EVENT_TIME) AS CASE_END,
  DATEDIFF('day', MIN(EVENT_TIME), MAX(EVENT_TIME)) AS CASE_DURATION_DAYS
FROM EVENT_LOG
GROUP BY CASE_KEY

Example two: Helper column – Rework flag

Used to simplify repeated logic in KPIs and filters.

CASE
  WHEN COUNT_TABLE(EVENT_LOG.ACTIVITY = 'Rework') > 0
  THEN 1
  ELSE 0
END

PQL operators that use reference tables

These PQL operators use reference tables that you can include as helper objects:

FACTORY_CALENDAR - uses a calendar table with columns for the identifier, start date, and end date.
WEEKDAY_CALENDAR - uses a calendar table with columns for the identifier, weekday, shift start time, and shift end time.
WORKDAY_CALENDAR - uses SAP’s TFACS table.
QUANTITY_CONVERT - uses a quantity conversion rates table with columns for the conversion rate identifier, from unit, to unit, and conversion rate.
CURRENCY_CONVERT - uses a currency conversion rates table with columns for the from currency, to currency, conversion rate, from date, to date, exchange rate type, and source system identifier.
CURRENCY_CONVERT_SAP - uses SAP’s TCURR, TCURF and TCURX tables.

You can also create helper objects to look up long lists of values, such as match lists for the IN operator.