3482783 - ODP_SAPI Sources or folders Not Found in SAP Datasphere Replication Flow

When creating a Replication Flow in SAP Datasphere, ODP_SAPI sources or specific folders cannot be found under the ODP_SAPI container, or the container itself does not appear.
In some cases, the following error may be displayed:

• Error in getDisConnectionChildren. Failed to get container children for /ODP_SAPI.
  ODP context SAPI is not a valid ODP context. Code: 99999

• SAP Datasphere
• ABAP-based source systems (SAP ECC, SAP S/4HANA)
• SAP BW/4HANA

1. Go to Data Builder in SAP Datasphere.
2. Create a New Replication Flow.
3. Select the source connection.
4. Open the container ODP_SAPI – ODP Context:SAPI.
5. In Select Source Object, no ODP_SAPI sources are visible. Or specific folders are missing. Or the ODP_SAPI container itself is not available.

Cause 1:

The source system is SAP BW/4HANA, where ODP_SAPI context is not supported.

• ODP_SAPI is not supported in SAP BW/4HANA system.
• For more details, see SAP Note 2443863 - BW4SL - S-API DataSources (SAP BW/4HANA as Source)

Cause 2:

In the source ABAP-based (ECC/S/4HANA) system, required code corrections are missing.

Cause 3:

The communication user used in the connection lacks sufficient authorizations.

Cause 4:

The DataSource exists but is not released to ODP.

Cause 5:

The application component hierarchy is missing in the source system. 

Resolution for Cause 1:

• For SAP BW/4HANA InfoProviders, it is recommended using ODP_BW context instead.
• For other tables residing on SAP BW/4HANA system, the recommended approach is to use a standalone SAP LT Replication Server, either
  • SAP LT Replication Server for SAP S/4HANA 1.0 (add-on DMIS 2020), or
  • SAP LT Replication Server 3.0 (add-on DMIS 2018).
• See 2443863 - BW4SL - S-API DataSources (SAP BW/4HANA as Source)

Resolution for Cause 2:

• 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.
• Additionally, please make sure the following SAP Notes are implemented in the system if the system meets the software component prerequisites specified in those notes: 
  3596322 - Data Integration ABAP - Enable ODP metadata filtering  
  3487859 - SAP Datasphere - ABAP Integration - ODP Context SAPI is shown even though it is hidden in BW/4HANA  
  (Please notice that after implementing Note 3596322, the Replication Flow source-object selection panel will display a flat list of ODP objects instead of folders. This is expected behavior.)

Resolution for Cause 3:

• Make sure the maintained credentials (USER on the ABAP source system) in the connection have 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. 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 for Cause 4:

• Function Module RODPS_REPL_ODP_GET_LIST can be used to check if extractors/DataSources are released to ODP or not.
  I_SUBSCRIBER_TYPE            HANA_SDI
  I_CONTEXT                          <SAPI>
  I_SEARCH_PATTERN             <search patten>
• Also, table ROOSOURCE can be used to check if DataSource is active, table ROOSATTR can be used to check if DataSource is released for ODP.
• If extractors/DataSource cannot be found in FM RODPS_REPL_ODP_GET_LIST result, open a support case under BC-BW-ODP component.

For details, please see below KBA:

• 2232584 - Release of SAP extractors for ODP replication (ODP SAPI)
• 3198662 - Supplement of SAP Note 2232584 DataSource Release for ODP

Resolution for Cause 5:

1. Run transaction RSA9.
2. In the popup “Do you want to transfer component hierarchy?”, choose Yes.

See KBA 2205577 - Application component does not exist when activating DataSource in RSA5: Error R8418.

• 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)

ODP_SAPI, disappear, Datasphere, authorization, odp sapi, extractor, exposed, not found, data source, ODP_SAPI, disappear, Datasphere, not found, not visible, missing, not visible, data source, No valid application component hierarchy exists  , KBA , DS-DI-RF , Replication Flow Runtime , BC-BW-ODP , Operational Data Provisioning (ODP) and Delta Queue (ODQ) , BC-BW , BW Service API , Problem