If you are OK with setting up the library in SAS metadata you could just register the non-hier tables so those would be the only ones that showed. However using a LIBNAME statement would bypass this.
Discuss your issue with your SAP DBA as they could probably setup a special schema that hides these.
The goal is that every single user will connect from SAS Eguide to SAP HANA with his own user so we will have to set security only at the SAP HANA platform.
So registering the library in metadata would mean we would have to do it for every user, and update (new) tables regularly.
Is it possible to create a metadata library which uses something like &metapassword?
@Filipvdr - A library set up in SAS metadata only needs to be defined once and then shared with all EG users. If SAP HANA can authenticate against OS user accounts that would be ideal as you don't need to supply a user and password any more. An alternative would be to use token-based authentication where all SAP HANA libraries share the same user account for connection purposes.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.