SAP Knowledge Base Article - Public

3467820 - CDS Views not found in CDS_EXTRACTION container when using Replication Flow in SAP Datasphere

Symptom

When creating a new Replication Flow in Datasphere, upon opening the Source tab and expanding the SAP S/4HANA On-Premise Connections or SAP ABAP Connections or SAP S/4HANA Cloud Connections, the CDS view is not displayed in the list.

Environment

SAP Datasphere

Reproducing the Issue

  1. Create replication flow
  2. Select S/4HANA On-Premise or ABAP or S/4HANA Cloud connection
  3. Select CDS_EXTRACTION container
  4. Cannot find CDS View

Cause

Cause 1:

The CDS View does not meet the required conditions (extraction-enabled and C1-released).

Cause 2:

In some cases, for SAP S/4HANA On-Premise or ABAP connections, missing SAP Notes in source system may also lead to the issue.

Cause 3:

For S/4HANA Cloud connection:

  • Incorrect authorization for extracting CDS views from S4HANA Cloud into Datasphere
  • Authorization Group set for communication arrangement: SAP_COM_0532 is not correctly defined.

Resolution

Solution for Cause 1:

Only ABAP CDS Views that meet both of the following conditions are available for access or replication in SAP Datasphere:

  1. Extraction-enabled: The CDS view is annotated with @Analytics.dataextraction.enabled: true.

  2. C1-released: The CDS view has been C1-released.

For more information, see:

When adding source objects in replication flows, such CDS Views can be found in the CDS_EXTRACTION container.

Limitations:

Sometimes, even if a CDS View is visible in the CDS_EXTRACTION container, it may not be fully supported in all scenarios. The following restrictions apply:

  • Delta replication not possible: CDS Views without "dataExtraction" and "changeDataCapture" annotations.
  • Parameterized CDS Views: Not supported.
  • CDS Views with table functions: Only initial load is possible; delta replication is not supported.
  • Client field issues: CDS Views that include tables with a client field as key but are not client-dependent (e.g. T000).
  • Large result sets: CDS Views returning more than 2 billion records will fail due to HANA memory limits.

For more information see "Not supported CDS Views" part in SAP Note 2890171 - SAP Datasphere / SAP Intelligence - ABAP Integration.

Solution for Cause 2:

For S/4HANA On-Premise and ABAP connections, if the above conditions are fulfilled and the CDS Views are still missing from the CDS_EXTRACTION container, the issue may be due to an incomplete SAP Note implementation.

Please follow KBA 3643099 - How to check Note Analyzer in On-premise ABAP-based systems for Datasphere Data Flows and Replication Flows to implement all missing SAP Notes in source system.

Solution for Cause 3:

For S/4HANA Cloud connection scenario:

Please refer KBA 3118974 to maintain Authorization Group.

  • 3118974 - Communication arrangement creation fails due to error "Authorization Group must be maintained"

More information, please refer Integrating CDS Views Using SAP Datasphere | SAP Help Portal

"You have created at least one authorization group ID with a CDS view allowlist. (To do so, proceed as follows: In your configuration environment, use the search function to open the following activity: Define Allowlists for CDS View Extraction. For more information, see Configuration Environment of SAP S/4HANA Cloud. When creating the communication arrangement, the communication user is assigned to an authorization group. CDS views that are not part of this authorization group will not be visible in in the CDS_EXTRACTION folder (the folder that is used to add source objects to a replication flow)."

See Also

Keywords

cds view, no visible, abap, extraction, Too complex for automatic CDC delta, extension views , KBA , DS-DI-RF , Replication Flow Runtime , DS-DI-CON , Connections , DS-DI-ABA , Data Flow / Replication Flow with ABAP as data source , Problem

Product

SAP Datasphere all versions