ADF failed to connect the SAP CDC table (ECC) by SAP CDC Connector

锐珂医疗-Hennie Ye 0 Reputation points
2026-07-30T08:02:27.4066667+00:00

Hello

Need support.

When I use ADF to load data from SAP CDC for example this table - it's error in "Preview ODP"as the screen shows. We confirm the table source "ZDDL_VBEP_BODS" is existing。

contact by email/teams ******@softwareone.com

Thanks

Hennie

Azure Data Factory
Azure Data Factory

An Azure service for ingesting, preparing, and transforming data at scale.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-07-30T08:02:54.08+00:00

    For an SAP CDC source that exists in ECC but fails in Preview ODP, the supported checks are:

    1. Verify the SAP system supports ODP 2.0 The SAP CDC connector requires the SAP ODP 2.0 framework. It is supported across many SAP ECC, SAP S/4HANA, SAP BW, BW/4HANA, and SLT releases, but the SAP release must meet the ODP requirements.
    2. Validate SAP user authorizations A common cause of preview failures is missing authorization for ODP RFC calls.
      • If the error is similar to DF-SAPODP-NoAuthForFunctionModule with RODPS_REPL_CONTEXT_GET_LIST, the recommendation is to add the required authorization profile to the SAP account according to SAP Note 460089.
      • For CDS-based extraction scenarios, missing SAP authorizations can also block extraction. The documented checks include reviewing the assigned SAP profile and paying attention to authorization objects such as S_RS_CDS_X and S_DHCDCCDS.
    3. Test extraction directly in SAP Run the SAP report RODPS_REPL_TEST for the same source object and same SAP user. This is the documented validation step for ODP setup and helps confirm whether the object can be extracted through ODP.
      • If the test fails, run transaction SU53 afterward to identify missing authorizations.
    4. Confirm the object is extractable through ODP If ZDDL_VBEP_BODS is a view, existence alone is not enough. Not all views are extractable by the SAP CDC connector.
      • Check table DDHEADANNO for the annotation ANALYTICS.DATAEXTRACTION.ENABLED.
      • If that annotation is missing, the documented guidance is to switch extraction to the SAP Table connector instead of SAP CDC.
    5. If SLT is used, verify the ODP queue/context configuration In SAP SLT transaction LTRC, the target system must be configured for:
      • RFC Connection
      • Scenario for RFC Communication = Operational Data Provisioning (ODP)
      • Queue Alias in the format SLT~<your queue alias>
    6. Check for SAP-side known issues Microsoft documentation lists SAP notes for known ODP extraction issues, including:
      • 2321589 for missing BAdI implementation for RSODP_ODATA subscriber type
      • 3038236 for CDS view extractions that fail to populate ODQ
      • 3076927 for unsupported callbacks when extracting from SAP BW or BW/4HANA
    7. Be aware of SAP Note 3255746 impact A recent SAP security patch can block incoming calls to the ODP RFC API from third-party clients, including the Azure Data Factory SAP CDC connector. This should be reviewed before or after SAP-side changes because it can directly affect connectivity and preview behavior.

    If the preview error specifically mentions SAP connection failure, also test connectivity from the machine hosting the integration runtime to the SAP server, for example with:

    Test-NetConnection <sap server> -port 3300
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.