9.4Overview of Possible Architectures

This last section is based on the basic principles of the previous chapters and describes the two basic architectures to add analytical functionality to transactional, ABAP-based systems:

When doing so, we’ll focus only on the operational level for reporting and data analysis while assuming that SAP HANA is used as the primary database. In some cases, however, the two approaches can also be used if SAP HANA is implemented as a secondary database.

9.4.1Direct Access to Analytical Functionality in SAP HANA

Direct access to analytical functionality in SAP HANA refers to data analysis via SAP BusinessObjects tools without using an AS ABAP. Moreover, this also includes the provisioning of analytical functionality via SAP HANA Extended Application Services (SAP HANA XS Engine, which is described in Chapter 1, Section 1.1.4).

The architecture for direct access to analytical functions in SAP HANA is displayed in Figure 9.11. In this architecture, end users communicate with the SAP HANA database either directly or via the SAP BusinessObjects portfolio but without using the ABAP AS.

Direct Access to SAP HANA

Figure 9.11Direct Access to SAP HANA

[»]SAP HANA Live

One scenario for direct access to SAP HANA for operational reporting is the implementation of SAP HANA Live (previously SAP HANA Analytics Foundation). Put simply, SAP HANA Live provides a virtual, multilevel data model (Virtual Data Model) consisting of SAP HANA views based on the database tables of the SAP Business Suite.

SAP HANA Live can be accessed using the SAP BusinessObjects tools or using special HTML5 applications based on SAP HANA XS. You can use SAP HANA Live both with a primary and a secondary SAP HANA database.

The advantages and disadvantages of analytical functions in SAP HANA are obvious:

9.4.2Access via SAP NetWeaver AS ABAP

Instead of using the SAP BusinessObjects portfolio or the SAP HANA XS Engine to access SAP HANA directly, you can provide analytical functions via AS ABAP. In addition to the SAP BusinessObjects tools, you can use further options to add analytical functions to transactional applications when choosing this approach. A central infrastructure component of this approach is the Analytic Engine we mentioned earlier.

The architecture for accessing analytical functions via AS ABAP is shown in Figure 9.12. With this architecture, the application server is used for all communications with the SAP HANA database.

Access to Analytical Functions via AS ABAP

Figure 9.12Access to Analytical Functions via AS ABAP

Access to SAP HANA via AS ABAP and using the Analytic Engine provides some important advantages over direct access to SAP HANA to integrate analytical functionality in transactional applications.

First, in contrast to direct access to SAP HANA, you can maintain and administer users and authorizations in a single system when accessing analytical functionality via the Analytic Engine. End users need only one user account for AS ABAP. As described in Chapter 3, communication with the SAP HANA database is done via a technical database user. In addition, you might have to create users in the SAP BusinessObjects BI server.

Second, when using the Analytic Engine, you benefit from some additional functions that SAP HANA doesn’t currently provide:

Third, the infrastructure of AS ABAP provides some interesting approaches for integrating analytical functions with transactional applications. Although we can’t describe them in detail here, we’ll mention them briefly:

These approaches that go beyond the tools of the SAP BusinessObjects portfolio are particularly suitable to extending existing applications easily and without risk, such as by providing analytical side panels in the SAP Business Client for your end users.

Many of the technologies and tools mentioned in this chapter were only described very briefly, but this information will help you with some ideas for adding analytical functions to transactional, ABAP-based applications.