3723407 - Expected schema/tables are not shown while importing Remote Tables from S/4HANA On-Premise - SAP Datasphere

Cloud Connector is selected for Data Provisioning Option under Remote Tables section of S/4HANA On-Premise connection to use the ABAP SQL service to federate data with remote tables.

When importing remote tables from SAP S/4HANA On-Premise system, expected schema/tables are not shown.

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

• SAP Datasphere
• SAP S/4HANA On-Premise

1. Data Builder -> Import -> Import Remote Tables.
2. Select S/4HANA On-Premise connection, click "Next Step".
3. Observe that only "Dbc2AbapTest" and "SYS" schemas are shown here.

Possible cause 1: Missing configurations of Service Definition and Service Binding in ABAP Development Tools, which are required to expose CDS view entities using the SQL service.  

• Note: In the Remote Table scenario where SCC is used as Data Provisioning Option, Datasphere displays the SQL schema name when importing remote tables, NOT other schemas (e.g., not database schema).  

Possible cause 2: Insufficient authorization to access the SQL service for privileged access to the CDS view entities. 

Solution for possible cause 1:

To expose CDS view entities using the SQL service, an SAP S/4HANA business user has created a service definition and a corresponding service binding of type SQL1 in the ABAP Development Tools.

• The service definition lists the set of CDS view entities that shall be exposed
• The service binding of type SQL for that service definition enables their exposure via the ABAP SQL Service.

For more information, see Creating a Service Definition and an SQL-Typed Service Binding in the ABAP Platform documentation for your SAP S/4HANA system.

To expose the SQL service to get privileged access to the CDS view entities with a communication user, a role is required. For more information, see Creating a Role for Privileged Access in the ABAP Platform documentation for your SAP S/4HANA system. 

• Authorization Object S_SQL_VIEW and S_START are required to expose the SQL service to get privileged access to the CDS view entities.
  
  
  • Authorization Object S_SQL_VIEW:
    

    Authorization Field	Values
    SQL_SCHEMA	The name of the service binding (exposed as a schema) that you want to grant access to
    SQL_VIEW	Comma-separated list of all CDS view entities to which you want to grant access or * (if you want to allow access to all CDS view entities in the service definition)
    SQL_VIEWOP	Choose SELECT (Datasphere only supports federation in this scenario): SELECT: SELECT grants read access to the specified CDS view entities.

  • For the authorization object S_START, the authorizations are already predefined; there's no need to change anything here.

• Using ABAP SQL Services for Accessing Data from SAP S/4HANA | SAP Help Portal
• SAP S/4HANA On-Premise Connections | SAP Help Portal

remote tables, S_SQL_VIEW, S_SQL_PROC, SQL_SCHEMA, authorization object, SAP S/4HANA, ABAP SQL service, service definition, service binding, schema access, CDS view entities, privileged access, remote table import issues, unable to access, not shown, invisible, not visible , KBA , DS-DI-RT , Remote Tables , Problem