Skip to main content

Celonis Product Documentation

O2C and P2P process connector changes related to Replication Cockpit

In the new versions of “Order to cash” (3.1.0) and "Purchase to Pay" (3.3.0), the data jobs and schedules have been modified to enable the delta extractions and delta transformations in the Replication Cockpit.

Changes in the standard activity transformations
  1. There are several activity tables instead of a single one. To avoid potential transformation conflicts, all relevant source tables have separate activities tables now (e.g. _CEL_O2C_VBAP_Activities, _CEL_O2C_TABLENAME_Activities, etc.) the union of all separate activity tables is selected in a view and used for the Data Model (e.g. _CEL_O2C_Activities). This is done in theCreate Table: Activitiestransformation step.

  2. All Data Model table views have been converted to tables with this version (if not done earlier). This is necessary so that new records can be continuously integrated into the tables via Replication Cockpit.

Following use cases are available
Use Case 1: No Replication Cockpit

This has been a standardmethod for data extraction and transformation by executing data jobs.

In this approach, the process is executed by following data jobs:

  1. SAP O2C – Full Extraction

  2. SAP O2C - Daily Update – for transactional and non-transactional tables (note: enable the Extract Tables: SAP Connector (Delta Daily Without Replication Cockpit))

  3. SAP O2C – Full Transformation

Use Case 2: Replication Cockpit (Extractions + Transformations)

In this approach, the extractions and transformations are integrated (merged) continuously, within the Replication Cockpit. In this scenario, Data Jobs might be scheduled for the following purpose:

  • SAP O2C - Daily Update– for non-transactional tables (not updating frequently, data can be extracted/transformed by nightly data jobs as well, e.g. currency conversion)

  • Full Transformations– As good practice and for assurance reasons, having occasionally full transformation (drop and re-create) is recommended (e.g. weekly).

    Note: Execution times of the full transformation and Replication Cockpit should be synchronized to avoid conflicts (RC should be turned off while full transformation is running)

  • Data Model Load– Having extractions and transformations running continuously in the Replication Cockpit, usually in 15 min replication cycles, Data Model Load should be scheduled on an hourly basis.

Use Case 3: Replication Cockpit for Extractions only

In this approach, only the extractions are being continuously executed in the Replication Cockpit, while all transformations are executed by the scheduled Data Job. In this scenario, the following Data Jobs are required

  1. SAP O2C – Daily Update– with extractions and transformations of the non-transactional tables

  2. SAP O2C – Full Transformation– transformations of the transactional tables (for example once a day)