Skip to Content
0
Jun 13, 2016 at 06:38 AM

Can not access _SYS_BIC schema of BW on HANA using Smart Data Access (SDA)

711 Views

Hi,

We have 2 HANA databases. HANA Runtime (BW on HANA) (102.5) and HANA Reporting database (102.03). We have created few calculation views on HANA Runtime database and would want to access them using SDA from the HANA Reporting Database but we dont see any objects under "_SYS_BIC" when accessed using SDA

We can access the objects from all the other schemas like "PUBLIC", "_SYS_BIC", "BW Schema of remote HANA database" for which access has been provided to the technical User "MODELER" which was used to create the SDA connection but we cannot see a thing for "_SYS_BIC"

1) Created the SDA in HANA Reporting Database with HANA Runtime as a remote source with technical User "MODELER"

The MODELER has below authorizations in HANA Runtime Database

Object Privileges:

- Select and Grant access to Schemas "_SYS_BIC", "_SYS_BI", "_SYS_REPO" with grantable "No"

- Execute access on REPOSITORY_REST (SYS) with grantable "No"

- Select access on _SYS_BIC for user _SYS_REPO

System Privilege:

- "CATALOG READ" without grantable option

- CREATE REMOTE SOURCE

- REPO.* (All REPO priviliges)

Granted Roles:

- ABAP_ADMIN

- ABAP_DEV

- ABAP_READ

- ABAP_SYS_REPO

- bw2hana/SAPHBD- SAP_BW_MODEL_GENERATIC

- MODELING

- MONITORING

- PUBLIC

- TABLE_REDISTRIBUTION

Package Privileges:

- Root Package

2) the User in HANA Reporting database has below access

Object Privileges:

- Execute access on REPOSITORY_REST (SYS) with grantable "No"

- Full priviliges for SDA_BW_HANA (Name of Remote Source connection)

System Privilege:

- "CATALOG READ" without grantable option

- CREATE REMOTE SOURCE without grantable option

- REPO.* (All REPO priviliges) without grantable option

Granted Roles:

- MODELING without grantable option

- MONITORING without grantable option

- PUBLIC without grantable option

Package Privileges:

- Root Package without grantable option

Can anyone please provide some insights on this

Regards,

Ashok O.