Replacement for SAP QUERY ?

[Former Member]

Hello

We operate a huge HR systems.

SAP Query is a very often use toolset in HR-Administration,Shared HR Service Center, Reporting etc. etc.

BUT the runtime of our SAP Query reports are very long, often longer than 3h.

Is it possible to replace SAP Query (inside the HR System) with a SAP HANA based solution ?

Kind regards

Gerald Eder

[Vitaliy-R · Accepted solution]

Hi Gerlad,

Are you looking for replacing your current SAP QUERY solution with BusinessObjects BI based data marts with SAP HANA in the back-end, or for the solution where you are still running you SAP QUERIES in ABAP, but queries are processed in HANA database?

Cheers,

-Vitaliy

[Former Member]

Hello Vitaliy

I don't need a replacment for SAP Query just a "boost" for executing SAP Query.

If it's possible to run SAP Queries in ABAP but they are processed in HANA, this will be fine.

Regards

Gerald

[Vitaliy-R]

That's the idea behind some of the new SAP apps - ABAP programs are writing data to both traditional database and to SAP HANA db (HDB), and then ABAP-based reports make calls to HANA db as another logical database using new DBSL connector for HDB in NetWeaver. I haven't done this myself yet, so can only tell you about the idea, but not about how-to do this. Good luck. -Vitaliy

[Former Member]

Hello ,

In HANA/In memory database, you can write SQL script procdures which are similar to stored procedures. Once yo have them defined in ana, you can call them via secondary database connection from ABAP or via calling a rfc to an external program (eg. java) which can make an ODBC/JDBC call and get the data from HANA.

Secondary connection would be my best bet for your requirement.

Regards

Pranav

[lbreddemann]

Hello Gerald,

to directly access HANA tables via standard NetWeaver transactions like SAPQUERY there are some requirements that aren't fullfilled yet:

- a DBSL connect to a NewDB/HANA instance must be availble (will be as of Kernel 7.20_EXT)

- the ABAP coding needs to make use of the secondary db connect (as long as HANA is not the system database for your NetWeaver - and this is likely to take some more months...)

So - right now, today, there is no easy one-step-way to speed up your SAPqueries with HANA.

What you nevertheless might be worth a look for you is the delivered ECC content for HANA that consists of several re-implementations of important ECC reports.

best regards,

Lars

[christian_koch3]

Hello Gerald,
> 
> to directly access HANA tables via standard NetWeaver transactions like SAPQUERY there are some requirements that aren't fullfilled yet:
>  - a DBSL connect to a NewDB/HANA instance must be availble (will be as of Kernel 7.20_EXT)
>  - the ABAP coding needs to make use of the secondary db connect (as long as HANA is not the system database for your NetWeaver - and this is likely to take some more months...)
> 
> So - right now, today, there is no easy one-step-way to speed up your SAPqueries with HANA.
> What you nevertheless might be worth a look for you is the delivered ECC content for HANA that consists of several re-implementations of important ECC reports.
> 
> best regards,
> Lars

@ Lars: Do you now if there will be some trainings (how to set up necessary infrastructure within an existing SAP landscape and and how to write HANA-related abap-code) as soon as these 2 options will be available? I think a lot of problems regarding performance could be resolved with this...actually we have huge performance problems e.g. doing dome checks against duplicate and blacklists in some online transactions with CRM - using this kind of db access could solve these problems...

Rgds

Christian

[lbreddemann]

Hello Christian,

the actual usage of the secondary database connection to a HANA database is not different than the usage of any other secondary database connection.

Check sap note [323151 - Several DB connections with Native SQL|https://service.sap.com/sap/support/notes/323151] to get a head start for this.

For the installation part, please check [1597627 - HANA connection|https://service.sap.com/sap/support/notes/1597627].

best regards,

Lars