Native HANA Information Views on Source system S4/HANA.

[pushpam22]

Hello,

As per SAP recommendation for S/4 HANA as a Business Suite, for Operational and Analytics reporting, CDS Views is the way to go. CDS views will then be consumed by Fiori apps and Embedded analytics. 

Since we have BW/4HANA in place and all the operational reporting is done there through Native HANA Calculation views, is it feasible to use these models by export import in Source system data base? what are pros and cons of creating HANA Graphical CALC views (information Views) directly on Source system?

What are differences in terms of performance and ease of consuming ABAP CDS views Vs HANA Information Views? 

[ssurampally · Accepted solution]

Hi, You can do the native HANA development in ECC or S/4 HANA system, but object development directly in the database layer is not recommended. Initially, HANA live content of CVs was released directly on ECC tables, but later entire standard business content is getting delivered in ABAP cds views.

With that, the model development, security role configuration and analytics model consumptions in ui5/fiori are tightly integrated in ABAP layer services instead of database layer. Also, if you need to get the external data into s/4 for enterprise reporting scenarios, that is not feasible because s/4 is not a data warehouse.

for all your enterprise reporting scenarios, you can leverage objects of BW/4 HANA and Native HANA also the data sphere(cloud). 

[pushpam22 · Accepted solution]

Thanks for the reply, however we are not planning to integrate the external data in SAP ecosystem, instead integration will be done at EDP side. This requirement is just for operational reporting.

[ssurampally · Accepted solution]

Even for your operational reporting in S/4 HANA, ABAP cds views are the way to go solution. You get lot of business content, security, oData service layer consumption to ui etc. Always try to minimize the database stack exposure(Security, development) in S/4 HANA.