Skip to main content

Transformation Hub in Views: Configuring the remaining object transformations

Setting up the remaining object transformations in the OCDM (Object Centric Data Model) is the final technical bridge that connects your raw data to the Transformation Hub.

This step is critical for three main reasons:

  • Ensures data consistency: By replacing generic join mappings with specific DATASOURCE references, you ensure that the Hub is pulling from the correct, validated "Writeback" tables rather than outdated placeholders.

  • Enables accurate KPI logging: The transformations for THActionBasedLog, THRateBasedLog, and THNonMonetaryLog are what allow Celonis to track your performance over time. Without these, you wouldn't be able to see the historical impact of your process improvements.

  • Activates the "Value" connection: These transformations link your Opportunities (the problems you want to fix) to your KPIs (how you measure success). This is what transforms the Hub from a simple dashboard into a tool that actually proves the financial or operational value of your work.

In short: this process moves your setup from a "static configuration" to a "live tracking system" that can actually report on the progress of your digital transformation.

Step 1: Updating global mappings

For the following transformations, you must replace the existing Join mappings with the DATASOURCE reference to ensure the Transformation Hub pulls from the correct writeback tables.

To do this, use the below steps and the table of information:

  1. Click Data - Objects and Events and open your Marketplace Installed Pool.

  2. Click Transformations.

  3. Open the transformation listed in the table below and repeat steps 4, 5, and 6 for each transformation listed.

    clicking_into_transformations.png

  4. Replace the Existing Mapping strings with the Replacement strings at the specified lines.

    For example, the THActionBasedLog - 1 transformation needs to be updated at lines 4 and 17:

    Existing Mapping strings:

    before_example.png

    Replacement strings:

    after_example.png

  5. For each of the four transformations, set the Data Source to KPI Logging - Combined Data Pool.

    data_source.png

  6. After updating each of the four transformations, click Save with validation.

    save_with_validation.png

Transformation mapping table

Transformation

Line number

Existing Mapping strings

Replacement strings

THActionBasedLog - 1

4

"${{JmTAcx_THWriteback}}"."OpportunityMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."OpportunityMapping"

17

"${{JmTAcx_THWriteback}}"."KPIMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."KPIMapping"

THRateBasedLog - 1

4

"${{JmTAcx_THWriteback}}"."OpportunityMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."OpportunityMapping"

13

"${{JmTAcx_THWriteback}}"."KPIMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."KPIMapping"

THNonMonetaryLog - 1

4 & 17

"${{JmTAcx_THWriteback}}"."OpportunityMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."OpportunityMapping"

THOpportunities - 1

8

"${{JmTAcx_THWriteback}}"."OpportunityMapping"

<%=DATASOURCE:TH_WRITEBACK%>;."OpportunityMapping"

Step 2: Updating the THLogEntry data source

Unlike the specific Action, Rate, or Non-Monetary logs, which aggregate data from external writeback tables,the THLogEntry acts as the "master index" or header for all log entries. It must remain within the core OCDM Schema to maintain referential integrity with the central Object-Centric Data Model. Using the Combined Data Pool here would break the relationship between the specialized logs and the primary process objects.

To update the THLogEntry data source:

  1. From the Transformation overview page, open the THLogEntry transformation.

  2. Click the Data Source drop down and select OCDM Schema.

    update_THLogEntry_-_1.png

  3. Click Save with Validation.

    save_with_validation.png

  4. Use this opportunity to ensure that all other transformations used the KPI Logging - Combined Data Pool data source.

    For example:

    data_source.png

Step 3: Enabling transformations, creating a version, and deploying

Once the mappings are updated, you must finalize the environment to push the changes live:

  1. Click Data - Objects and Events and select your Marketplace Installed Pool.

  2. Click Transformations and enable all transformations.

    enable_all_transformations.png

  3. Click Create version.

    create_version.png

  4. Select Open deployment after creating the version and click Create Version.

    create_version_window.png

    The data model version is created and the deployment window opens.

  5. Select the deployed version of the data model, choose the Development environment, and then click Deploy.

    select_version_and_then_deploy.png

    The data model is now deployed to the data pool.

  6. Click View Data Pool, opening your Marketplace Installed Pool.

    click_view_data_pool.png

  7. Click Data Jobs.

    select_data_jobs.png

  8. Locate the test data jobs and click Options - Execute Data Job.

    execute_data_jobs.png

  9. Select Full load and click Execute Selection.

    full_load.png

    The data jobs execute, updating the data available.

  10. From the data pool diagram, click Data Models and select your perspective.

    click_data_models.png

  11. Click Data loads and then Load Data Model.

    load_data_models.png

  12. Select Standard Query Engine and click Load data model.

    SQE_and_load.png

  13. Verify the load: Wait for the status to change to a green checkmark.

Next steps

With the object-centric data model (OCDM) and Action Flows established, the Admin Workbench acts as the final bridge to actionable insights. While the OCDM organizes the data, the workbench defines its impact by mapping snapshots to a structured Value Realized Journey. Proper configuration ensures that only verified, accurately calculated figures reach your Value Reports and executive dashboards.

See: Configuring the Admin workbench