SAP Datasphere - How to handle ERP connection mapping (DIX → QIX) when transporting Replication Flow

[tungx]

Hello Experts,

I’m working on a transport scenario for SAP Datasphere using SAP Cloud Transport Management (CTMS) between two BTP subaccounts:

• DEV subaccount → contains SAP Datasphere connected to ERP DEV system (connection name: DIX)

• QAS subaccount → contains SAP Datasphere connected to ERP QAS system (connection name: QIX)

In the DEV environment, I created a Replication Flow that extracts data from an ABAP CDS View in ERP DEV via the connection DIX.

When I export this Replication Flow from Datasphere DEV (using CTMS), the exported package seems to include the connection reference as well.
However, when I import the same transport package into the Datasphere QAS environment, I’m not sure how Datasphere handles the source connection — because in QAS, the ERP connection should point to QIX (ERP QAS), not DIX (ERP DEV).
My questions:

1. Does SAP Datasphere automatically detect and remap the connection from DIX → QIX during import?
   (I assume no — since Datasphere does not have a logical system mapping concept like SAP BW.)

2. If not, is there any connection mapping mechanism similar to BDLS (logical system mapping) in SAP BW?

3. Is it possible to maintain a mapping configuration file (e.g., JSON) for connection replacement during import via CTMS?

4. What is the best practice for naming and managing ERP connections across DEV / QAS / PROD systems to ensure smooth transports?

Any documentation link or official guidance on connection mapping for Replication Flows in Datasphere would be highly appreciated.

Thank you!

[virgonitul]

Hi,

I think Best practice is to have the same connection name for all environments.

Thank you,

Nitul

[tungx]

Thank you, Nitul I will try it