Data extractions and transformations for object-centric process mining
The object-centric data model is system-agnostic and process-agnostic. Celonis EMS includes extractions and transformations to ingest business data for SAP ECC and Oracle EBS systems into the model. You can build your own extractions and transformations to use business data from other systems.
Extractions identify and ingest relevant business data from the tables in your source system.
Transformations create instances of objects, changes, events, and relationships based on the ingested data.
The supplied extractions and transformations get your business data into the Celonis object types, event types, and relationships. They cover the Accounts Payable, Accounts Receivable, Order Management, Procurement, and Inventory Management business processes.
For your custom object types and event types, and for custom properties and custom relationships that you've added to the Celonis object types, you’ll need to build SQL transformations using our editor, to transform the relevant data from your business system into objects and events.
Transformations
Transformations are where the data from your source system gets turned into objects and events. Here’s how they work:
A first set of transformations works with the raw data from your source system. These transformations map the business data into the object types. Their output is individual objects, with their properties and changes.
A second set of transformations works with these objects and their changes. They use the event types to identify the events that can be observed from the objects and changes. Their output is individual events, with their properties.
The OCPM Data Pool
The objects, events, changes, and relationships that are created from your data are stored in a database in the OCPM Data Pool.
Each object type and event type has a table where the specific objects and events are stored as rows - one row for each object or event.
Each object type table has an accompanying change table that stores the identified changes to objects of that type.
Object type tables and event type tables can also have accompanying relationship tables, which hold data about object to object relationships and event to object relationships.
When you customize Celonis object types, Celonis EMS extends those database tables to include your customizations. And when you create custom object types and custom event types, Celonis EMS automatically creates database tables for them.
Object-centric process mining database tables
Here's a reference for the tables that we use in the underlying object-centric process mining database in the OCPM Data Pool. You can manage all these using the visual editors we provide, and you don't need to edit them directly.
Each table name is made up of these components:
A prefix giving the table type.
The namespace for the table's content.
celonisis for object types, event types, and relationships prebuilt by Celonis, andcustomis for object types and event types that you've created.The name of the object type, event type, or relationship that the table holds data for.
Table | Table name prefix | Row contains |
|---|---|---|
Object type | o_ | One object and the current values of its properties |
Event type | e_ | One event and the current values of its properties |
Change table | c_ | One change to one row of the referenced table |
Object to object relationship table | r_o_ | One relationship between two objects |
Event to object relationship table | r_e_ | One relationship between one event and one object |