I asked a similar question some time ago, still looking for an elegant solution:
Context:
Currently we do all the extraction within one Data pool, that does also contain the OCPM objects and events. Since we start to connect additional systems, we want to use the approach “1 dedicated Data pool per system, 1 common Data pool for all OCPM objects and events data”
Problem:
I hoped to simply rebuild the existing extractions in a new Data pool and then switch the Data source within the OCPM-transformations to the new Data pool. This works totally fine for custom objects, but for Celonis objects the Data source is read-only:
What is the most “elegant” solution?
One approach would be to create a view for each table: view in the old data source pointing to the underlaying table of the new data pool. ...quite a lot of (maintenance) effort and not sure whether this would work.
Another approach is to create full overwrites of all transformations. But by this you loose the connection to the official catalog with its updates.
What would you do? Or do have Celonis Admins the possibility to change the Data Source (in some “God-mode”)?