If you have built any Object-Centric Data Models (OCDM) recently, you know the pain of handling tables that use composite primary keys.
Previously, Celonis only allowed a single string ID as the primary key. If you were pulling tables from SAP (like VBAP), you had to write custom SQL transformations to concatenate keys (like VBELN and POSNR) into a single string ID just to make joins work.
With the June 15, 2026 release, Celonis natively supports composite primary keys. You can now select multiple columns directly in the Objects and Events UI to form your primary key, completely bypassing the old SQL concatenation step.
This change fixes three major issues.
First, you don't have to write redundant CONCAT SQL code in your data jobs anymore. Your SQL transformations stay clean.
Second, database joins run faster on raw composite columns than on concatenated string columns, especially when you are querying millions of rows.
Third, your Celonis data model now matches your source ERP schema exactly, which makes data validation and tracking much easier.
If you are building new OCPM models, try selecting multiple key columns in the UI instead of writing concatenation transformations. It saves a lot of time.