Symptom
- Error while fetching CDS data in Datasphere during Replication Flow setup.
- When adding a CDS Object, a popup shows error message "Getting dataset definition failed …"
Environment
- SAP Datasphere
- SAP S/4HANA
Reproducing the Issue
- Create a Replication Flow.
- Select the SAP S/4HANA On Premise as the Source Connection.
- Choose CDS_EXTRACTION as the Source Container.
- Search and select the target CDS view.
- Click Next and Add Selection, an error occurs while fetching the dataset definition.
Cause
- Connection validation fails. For example, when validating the connection, the following error popup:
-
Replication Flows: Cause: ABAP connector(Axino) ABAP connection check FAILED: request failed: rc=1, msg="Message: Opening connection to backend failed: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount \"xxx\" and SCC location ID, with default value, that is empty string or simply not configured. Check the configuration on SCC and cloud side.\nCode: RFC_COMMUNICATION_FAILURE"
-
- Missing code correction which can be checked by running Note analyzer - transaction CNV_NA_DI
Resolution
- Validate the Datasphere ABAP connection. If it reports the subaccount or Location ID related issue, please check KBA 3440815.
- In the ABAP source system, run transaction CNV_NA_DI and implement all missing notes as the central SAP Note 3016862.
- For TCI-based notes, download and upload the required TCI SAR package(s) and implement the TCI. Refer to KBA 2543372.
Keywords
datasphere, replication flow, cds extraction, getting dataset definition failed, getDisConnectionChildren, getDisConnectionDetails, rfc_communication_failure, cloud connector, scc, abap connector, cnv_na_di, tci, transport-based correction instructions , KBA , DS-DI-RF , Replication Flow Runtime , Problem
SAP Knowledge Base Article - Public