Scribd
Upload
140 views1 page

ABAP For HANA and "Code Push-Down" SAP Blogs

Uploaded by

Karan Nagar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
140 views1 page

ABAP For HANA and "Code Push-Down" SAP Blogs

Uploaded by

Karan Nagar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Community

Ask a Question Write a Blog Post Login / Sign

Jens Weiler
February 3, 2014 | 2 minute read

ABAP for HANA and “Code Push-


Down”

! 15 " 48 # 66,315

With the brand new NW AS ABAP 7.4 SP5 we are adding a


new possibility for ABAP Developers to leverage HANA
capabilities ( New ABAP for HANA features in SAP NW 7.4
SP5 ).

The whole ABAP for HANA story began last year with our
!rst release of NW AS ABAP 7.4 introducing a new coding
paradigm (at least for ABAP): “code pushdown”.

So what does this mean?

Code pushdown means delegating data intense calculations


to the database layer. It does not mean push ALL
calculations to the database, but only those that make
sense. An easy example is if you want to calculate the
amount of all positions of invoices. You should not select all
positions of those invoices and calculate the sum in a loop.
This can be easily done by using an aggregation function
(here SUM()) on the database.

However, pre ABAP 7.4 releases only provided very limited


support for such an approach. In the 7.4 SP2 release we did
our !rst step to overcome this limitation. We introduced new
ABAP artifacts to consume HANA views and procedures in
ABAP: The “Bottom-Up approach”.

Only use this in needed cases

Sounds perfect? Yes, but unfortunately it has some


drawbacks. First of all, as a developer, you have to work in
both worlds (HANA and ABAP). This requires a database
user, which alone is quiet tricky in some enterprise
environments. You also have to keep the HANA and ABAP
artifacts in sync and take care of the lifecycle management.

With the new SP5 release we are taking the next step to
enabling code pushdown with ABAP for SAP HANA: The
“Top-Down approach”. It is based on your feedback and our
own experience using ABAP for SAP HANA. It enables
developers to continue working in their ABAP environment
and still have similar possibilities to leverage the power of
SAP HANA.

Recommended approach

This approach comes with a huge bag of goodies, like writing


SQL Script or being able to create database views with new
join and aggregation capabilities directly in ABAP. We will
describe these features in detail in more blogs that will
follow soon.

By the way: this does not mean you do not need the Bottom-
Up approach anymore. There are still special cases which
you won’t be able to tackle with these new “Top-down”-
features. But we are continuing to enrich the ABAP
possibilities with every SP. Stay tuned.

If you are interested in those new features there is are


already great videos available in our YouTube Channel: ABAP
for SAP HANA – YouTube

Cheers

Jens

Follow " Like $ RSS Feed

Alert Moderator

Assigned Tags

ABAP Development

SAP NetWeaver Application Server

abap

abap for hana

abap4hana

abap7.4

abapforhana

View more... %

Similar Blog Posts &


Simple Program
By Former Member Sep 26, 2013

Code-to-Data Paradigm in ABAP with SAP HANA


By Srinivas Gadilli Mar 14, 2020

Code Push Down for HANA Starts with ABAP Open SQL
By Sundaresan Krishnamurthy Sep 26, 2014

Related Questions &


Code Pushdown in ABAP on HANA
By Pravvu Daisy Jul 26, 2020

Push button (urgent)


By Former Member Jan 15, 2008

Prob with Push Buttons in the selection screen


By Former Member Apr 12, 2007

Join the Conversation &


SAP TechEd
Tune in for tech talk. Stay for inspiration. Upskill
your future.

SAP BTP Learning Group


SAP Business Technology Platform Learning
Journeys.

Co"ee Corner
Join the new Co!ee Corner Discussion Group.

15 Comments

You must be Logged on to comment or reply to a


post.

Abdul Hakim
February 3, 2014 at 8:45 am

Jens - Thanks for sharing this info with the ABAP


Community..Glad to know that ABAP is getting better in every
release..Just a thought..is there any plan to come up with
"Open SQLScript" similar to "Open SQL" so that the
SQLScript also will be database independent..

Thanks

Hakim

Like 0 | Share

Jens Weiler | Blog Post Author


February 3, 2014 at 9:31 am

Hi Abdul,

valid question, but sorry: at the moment we have no


activities planned in this direction. Current focus is to get
the best out of ABAP and HANA and there is still a lot to do
for us.

Cheers

Jens

Like 0 | Share

Abdul Hakim
February 3, 2014 at 9:59 am

Thanks for the clari"cation.

Like 0 | Share

Vikas Singh
February 12, 2014 at 11:15 pm

Thanks - very useful post. CDS and AMDP de"nitely make


things easier as getting the dB user is not easy sometimes.

Like 0 | Share

Yogesh Vijay
March 11, 2014 at 4:22 am

Very useful post. Thanks Jens Weiler

Like 0 | Share

Hyuk Joo Lee


January 7, 2015 at 7:40 am

Thanks - very useful and helpful post,

BTW, can I get some explicit special cases regarding what you
mentioned?

By the way: this does not mean you do not need the
Bottom-Up approach anymore. There are still special
cases which you won't be able to tackle with these new
"Top-down"-features.

Cause, I know why I should use CDS View and AMDP, but I'm
not sure why we still have to use Bottom-Up approach...
although it is drawbacks...

Thank you in advance,

BR

Hyukjoo

Like 0 | Share

Jasmin Gruschke
January 7, 2015 at 8:28 am

Hi Hyukjoo,
you should in almost all cases prefer the top-down
approach. What Jens refers to by "special cases" are e.g.
cases where you have an SAP-delivered (or partner-
deliverd) database procedure or column view, which you
would like to consume. In such a case, you might just wrap
the delivered content with an external view / database
procedure proxy. Or you might be in the unlucky situation
to "just have ABAP 7.4 SP2 at hand", which does not
include AMDPs and only limited capabilities in CDS views.

But to repeat the above advice, you should stick to the top-
down approach and only use in special (rare) cases the
bottom-up approach.

Cheers,

Jasmin

Like 0 | Share

Hyuk Joo Lee


January 8, 2015 at 1:02 am

Thanks a lot Jasmin,

Now I'm very clear on this topic~!

BR,

Hyukjoo

Like 0 | Share

Shakul Jugran
March 16, 2015 at 4:35 am

Thanks for another useful post, Jens

Like 0 | Share

Former Member
October 21, 2015 at 7:52 am

Really a helpful information .. Thank you Jens..


Looking forward to have such quality post in coming days..

Like 0 | Share

Apoorv Sirohi
April 19, 2016 at 1:44 pm

So much informative... Thanks for sharing

Like 0 | Share

Prince JOSHI
October 18, 2016 at 10:40 am

Nice Blog.

Could you please explain a little bit when to go for ADVANCE


OPEN SQL(ABAP 7.4 or ABAP 7.5) instead of ABAP CDS?

Also, little more about SQL script?

Like 0 | Share

Ramesh Vodela
December 6, 2017 at 6:32 pm

I have looked at some of your Teched sessions such as


SH109 and SH140 - is there any chance that I can access the
demo code -

Thanks

Ramesh

Like 0 | Share

Manish Gupta
May 11, 2018 at 8:25 am

Hi Jens,

Are there any guidelines available which can help in decision


making on when to do code push down and when to use open
SQL?

I am asking it speci"cally with regards to Open SQL and


AMDP.

Like 0 | Share

Ranganath Muddeerappa
November 15, 2021 at 6:57 am

Thanks for useful information.

Regards,

Ranganath

Like 0 | Share

Find us on

Privacy Terms of Use

Legal Disclosure Copyright

Trademark Cookie Preferences

Newsletter Support

You might also like