XSA - Access _sys_bic column view from HDI container

[nuno_melo]

Hi,

I need to access a column view in schema _SYS_BIC from the HDI container using flowgraphs. I now have the right authorizations in place but when the view is queried it returns no data once it requires the session client. I cannot give that directly in Hana Studio to the OO user. How can I fix this?

Thanks in advance.

NM

[jan_zwickel]

Hi Nuno,

if you go for the connection specific setting in Database Explorer you could add a new HDI container connection and select the already existing container in the dialog. While adding it as a new connection you can modify the Advanced Options.

Best,

Jan

[nuno_melo]

Hi Jan,

many thanks for your valuable feedback. Once the view is maintained by external team, I think I have to go with the first option (user specific or session specific).

For a session specific, how can I set the CLIENT= 100 in the advanced options? When I choose "Open HDI Container" from Development view, I creates a connection but I cannot change the advanced options (it's greyed out). How can I add the CLIENT = 100? Is it in the MTA file?

Many Many thanks.

Kind regards,

NM

[jan_zwickel]

Hi Nuno,

the actual calling user is relevant for the session client. Thus it depends on how you execute the flowgraph. If you execute it directly from Web IDE a ...._RT user will be used.

To set the client you basically have two options (user specific or session specific):

user specific: alter the user client as you tried for OO but for the executing user

session specific: set the client when establishing your connection. For example, if you connect from Database Explorer there is an option "Advanced Options". If you enter here something like CLIENT=100 the client value 100 will be taken when executing through this connection.

Given the complexity of changing the client of the executing user or when creating the connection, I am wondering whether it would not be a better solution to filter directly on the column instead of relying on the "implicit" client filtering. For example, you could set your view to "Cross Client" so that no client filtering occurs anymore and explicitly define a filter on the client column.

Best,

Jan