Question Re: SAP Data Intelligence -- Data Replication & Approvals in Technology Q&A

SAP Data Intelligence -- Data Replication & Approvals

anujvahil — Mon, 26 Dec 2022 05:47:13 GMT

Hi All,

In SAP DI we have the concept of data pipelines and replication flows now. Does it have a governance mechanism to have approval workflows or change requests before the data is actually replicated to the target system. Without this functionally, there may not be a 'gate keeper' kind of functionality as to what is updated in DI and is going back to target system.

Regards,

Anuj

Re: SAP Data Intelligence -- Data Replication & Approvals

Cocquerel — Mon, 26 Dec 2022 22:03:36 GMT

With ABAP sources, you can control which table can be replicated. See details in note 2831756 - SAP Data Intelligence - ABAP Integration - Security Settings

Re: SAP Data Intelligence -- Data Replication & Approvals

anujvahil — Tue, 27 Dec 2022 04:15:12 GMT

Hi Michael

Thank for the prompt response, but my query is more in line with a user approving the change being done in DI before it goes to the target system so that there is a level of check involved before the data replicates. I could be a step before the replictaion is triggered as well.

Regards

Anuj

Re: SAP Data Intelligence -- Data Replication & Approvals

jimgiffin — Mon, 02 Jan 2023 15:48:46 GMT

Adding to the conversation - I think that in most scenarios, customers will have prod and non-prod environment for DI. This governance step should be applied in the migration of your objects from non-prod to prod. This can be done several ways (there are a few blogs about CI/CD and using git to manage artifacts). I compare it to the transports moving from Dev to QA and then to Prod in the ABAP stack, there is usually an review/approval process.

Re: SAP Data Intelligence -- Data Replication & Approvals

olafkexel — Tue, 03 Jan 2023 11:35:16 GMT

Hi Anuj,

are you talking about a "data replication process", which is typically happing in real-time or scheduled continuously over time or more a "data migration process", which is typically only happening once or manually triggered in low frequencies?

A workflow approval only makes sense for the second case...