Just after returning from SAP Teched held at Bangalore recently, with packed back to back sessions and demo pod areas on HANA (specifically in the area of ABAP for HANA), the learning has been awesome. It promises another exciting year ahead. We already have good blogs in this area, but I tried to put in my understanding about how SAP HANA can be leveraged to accelerate existing ABAP applications in ERP.
In this blog, I have tried to summarize different approaches that can be followed to make existing ABAP applications accelerate by leveraging the optimization techniques through SAP HANA.
For both the above approaches, we could use a side-by-side car approach where in HANA is used as a secondary database, data is replicated from ERP to HANA through SAP LT replication server as shown below.
A beta shipment for this is planned for end 2012. Ramp-Up is planned for 2013. Lets try not to include features of AS ABAP 7.4 in this blog as the focus is here on current General Available HANA system(AS ABAP 7.x)
Some of the techniques that we could use to accelerate our existing ABAP applications are as follows.
Scenarios are specified by defining the context in which data is to be read from the SAP HANA database.
Context Definition – This can be done at Tables / DB Views , or Main program or Batch job name level. This can be done by creating an entry in RDA_CONFIG table. This table can also be maintained by RDA_MAINTAIN report that uses a scenario (Scenarios are specified by defining the context in which data is to be read from the SAP HANA database. – this is in the form of an .xml file ) with a table name and program name, use the “Upload scenario” option. This is an easy mechanism to enable the application to read data from HANA database instead of the classical database.
Once an entry is created in the above table, the “Connection Decider” decides to read data either from secondary database (HANA database here) or from the Primary database as shown below.
Instrumented application server needs the following steps to be done
2. ADBC (ABAP Database Connectivity) - ADBC is an API for the Native SQL interface of the AS ABAP that is based on ABAP Objects. With ADBC, we can do the following:
Class CL_SQL_CONNECTION offers methods like Create, update, insert etc to work with the underlying database. It is suggested to use ADBC as it works faster than the open SQL.
3. Code Pushdown – Calculation logic in applications can be pushed down from the Application server to the Database server. This can be done easily through SQL script (procedural extension of SQL). SQL script procedures may contain SQL statements and call other procedures. It is used to write procedural orchestration logic and to define complex data flows. . The SQL script procedure can be created easily as shown below:
Stored procedures can be created in SQL script editor of HANA studio or can be created in ABAP program. Same can be consumed through ADBC and has been proved that SAP script procedures works faster that simple open SQL statements.
Some of the blogs on SCN that can help to accelerate SAP ECC Applications.
Accelerating SAP ECC Applications – Part 1
Accelerating SAP ECC Applications – Part 2
What is the future of ABAPer ? Is there anything new coming up? has been one of the major questions lingering in most of the ABAPer’s minds , I could find that the answer indeed was Adapt to the changing SAP scenarios, improve your zest to learn new Technologies Learn the required skill sets for the same – ABAP for HANA, SQL scripts etc, experiment the learning and move on …
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
3 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 |