SAP Knowledge Base Article - Public

3482783 - ODP SAPI extractor not available in Replication Flow - SAP Datasphere

Symptom

When creating Replication Flow in SAP Datasphere, cannot find any folder under ODP_SAPI container.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

Environment

SAP Datasphere

Reproducing the Issue

  1. In app Data Builder, create new Replication Flow.
  2. Select connection.
  3. Select ODP_SAPI container.
  4. In "Select Source Object" part, cannot find any ODP_API sources.

Cause

  • Cause 1:
    Program error. Code correction missing in source system.

  • Cause 2:
    Communication user does not have sufficient authorizations.

  • Cause 3:
    The required hierarchy with the application component is not available in ABAP-based source system.

  • Cause 4:
    The extractors/DataSources are not released for ODP.

Resolution

  • Resolution 1:

    Make sure source system contains all the SAP notes needed to work properly with SAP Datasphere.
    1. Install the Note Analyzer (from SAP Note 3016862) needs to be installed in ABAP Source system of SAP Datasphere.

      SAP Note 3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/SAP S/4HANA)

    2. Run transaction code CNV_NA_DI and make sure all the listed SAP Notes are installed in system.
      
  • Resolution 2:

    Make sure the maintained credentials (USER on the ABAP source system) in the connection has sufficient authorizations according to SAP Note 3100673 - SAP Data Intelligence / SAP Datasphere - ABAP Integration - Security Settings.

    Also, below method can be used to find the missing authorizations:
    1. Change the user type from system to dialog type.
    2. Log into source system with this USER.
    3. Validate the connection on SAP Datasphere side until the warning message appears.
    4. Use SU53 on the source system to display the missing privileges of the USER.
      
  • Resolution 3:

    Transfer component hierarchy according to KBA 2205577 - Application component does not exist when activating DataSource in RSA5: Error R8418.
    Basically, steps are as follows:
    1. Run transaction code RSA9 in the ABAP-based source system
    2. Answer the popup window "Do you want the content application Transfer Component Hierarchy?" with "Yes".
      
  • Resolution 4:

    Release the extractors/DataSource to ODP via program BS_ANLY_DS_RELEASE_ODP according to SAP Note 2232584 - Release of SAP extractors for ODP replication (ODP SAPI).

    For detail information, see KBA 3489773 - ODP SAPI Source does not appear in SAP Datasphere for Replication Flows.

See Also

  • KBA 2205577 - Application component does not exist when activating DataSource in RSA5: Error R8418
  • KBA 3489773 - ODP SAPI Source does not appear in SAP Datasphere for Replication Flows
  • SAP Note 3016862 - DMIS Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology (DMIS2011/DMIS2018/DMIS2020/SAP S/4HANA)
  • SAP Note 3100673 - SAP Data Intelligence / SAP Datasphere - ABAP Integration - Security Settings
  • SAP Note 2232584 - Release of SAP extractors for ODP replication (ODP SAPI)

Keywords

ODP_SAPI, disappear, Datasphere, authorization , KBA , DS-DI-RF , Replication Flows , BC-BW-ODP , Operational Data Provisioning (ODP) and Delta Queue (ODQ) , BC-BW , BW Service API , Problem

Product

SAP Datasphere all versions