Skip to main content

Perspectives and event logs

In Object-Centric Process Mining (OCPM), a perspective is essentially a specific view of your process data. Perspectives define which object types (like Purchase Orders, Vendors), event types (like “Order Created,” “Invoice Paid”), and the relationships between them you want to analyze. Using perspectives allows you to focus on the part of your process that matters for a particular analysis without changing the underlying data model. This makes it easier to explore, visualize, and analyze complex, multi-object processes from the angle that’s most relevant for your question.

Celonis provides prebuilt perspectives for these key business processes:

  • Accounts payable

  • Accounts receivable

  • Inventory management

  • Order management

  • Procurement

When you enable one of these processes, Celonis automatically applies the corresponding perspective, providing the object types, event types, and relationships needed for analysis. You can extend these perspectives by adding more objects, events, or relationships, or build fully custom perspectives from scratch using the perspective builder.

Event logs created from perspectives

Some Celonis apps, like the Supply Chain Network Visibility App and object-centric Starter Kits, work directly with perspectives. Other apps, such as Process Explorer, Process Adherence Manager, and case-centric Starter Kits, use event logs created from perspectives. Event logs organize your objects and events into a format that tracks all events for a single object throughout its lifecycle.

When using event logs:

  • Celonis automatically generates event logs for each object in a perspective (prefixed el_), which you can use as-is or create additional custom event logs (prefixed el__) for extended or complex analyses.

  • You can set any object as the lead object and have multiple event logs per object.

  • Event logs let you subset events by attributes, with _ActivityDetails columns for detailed analysis.

  • For apps or features that require a single event log, you must create a custom event log and mark it as the default. Automatically generated logs cannot be set as the default.

  • Event logs feed activity tables in Studio, which can be analyzed via views, PQL, or dynamically with CREATE_EVENTLOG.