The best practice development. We should use the view instead of connect to database directly (SAPSR3). In order to increase the performance of reporting by column view and segregation of HR data. In that case, , we must connect to view(system-local.bw.bw2hana) instead of database schema SAPSR3. Please see how to do it below.

ADSO

1. On HANA Studio, at ADSO general tab, mark "External SAP HANA View".
   
   
   

2. The view will created on schema _SYS_BIC with "system-local.bw.bw2hana"
   

DSO

1. At BW (SAP GUI), right click at the DSO and select change and then mark "External SAP 
   
2. The view will created on schema _SYS_BIC with "system-local.bw.bw2hana" same as ADSO

Composite Provider

1. On HANA Studio, at Composite provider general tab, mark "External SAP HANA View".
   
2. The view will created on schema _SYS_BIC with "system-local.bw.bw2hana" same as ADSO
   
   

Master data

1. On HANA Studio, at info object general tab, mark "External SAP HANA View for reporting".
   
2. The view will created on schema _SYS_BIC with "system-local.bw.bw2hana" same as ADSOQuery

Query

Prerequisites

• The InfoProviders that the query is defined on must be of type DataStore object (advanced) or CompositeProvider.
• The External SAP HANA View flag must be set for the InfoProvider on which the query is defined.
• To use a hierarchy: A SAP HANA view must have already been defined for the InfoObject, on which a hierarchy is defined.
• The CompositeProvider must not have any ambiguous joins.

1. On HANA Studio, at info object general tab, mark "External SAP HANA View".
   
2. The view will created on schema _SYS_BIC with "system-local.bw.bw2hana" same as ADSO