3469992 - Database user on Space-level is not able to consume tables and all schemas in SAP Datasphere

When using a Database user on Space-level, tables (remote and local) are not available for consumption.

In HANA Explorer, all the schemas are not listed comparing when using a Database User on Tentant-Level (Extended Capabillities).

 SAP Datasphere

This is working as designed.

DB users on Space-level should only consume exposed views. Therefore, the tables and non-exposed views will not be listed.
As well for schemas, only the OpenSQL schema, Space schema (when Read Access (SQL) is enabled, when creating a DB user) and other a few technical spaces (SYS, SYS_BI, etc.) should appear, when using a DB User on Space-level.

NOTE
The only exception is when Space is defined as Monitoring Space. In this scenario, the DB User will have extended read capabilities for all schemas and tables. 
Only one space can be selected as Monitoring Space. Another monitoring space can be created, but the technical name must be SAP_ADMIN.

If a Database Space-level user was created while the Space was designated as a Monitoring Space, the user will retain access to all schemas, even if the Space is later reconfigured. To revoke this access, the Database Space-level user must be deleted and re-created.

• SAP Help Analyze Monitoring Data in a Space
• SAP Help Database Users

visibility, visible, could not find, search, monitoring, space user, access , KBA , DS-SM , Space Management , How To