Scrum: Hand-Written Notes In The Digital Age?
TAKE NOTE (Insights into SAP solutions and Emerging Technology)
Thus the flaws of the “Classic” Software Development LifeCycle (SDLC) are as follows:
- Development steps taken are too big – if the project fails or goes off into the wrong direction, this is often noticed
- Silo-thinking – the subject-specialist department and the development department scarcely have any direct contact
- Losses of efficiency – bureaucracy and the administrative workload obstruct productivity
- Communication problems – misunderstandings or unclear requirements are noticed too late
UNDER DEVELOPMENT (Information for ABAP Developers)
ntroduction to ABAP Managed Data Procedures (AMDP)
As we described in a prior blog The ABAP Developer Road Map to SAP HANA, with the advent of SAP HANA, there has been a paradigm shift in the way business applications are developed. The rule-of-thumb is simple: Do as much as you can in the database to get the best performance. This was coined as “Code Pushdown” by SAP. So far we have looked at CDS Views as a way to achieve Code-Pushdown in the blog Don’t Try Coding ABAP Core Data Services Without Reading This First. In this blog, we will continue to examine Code-Pushdown Patterns, specifically ABAP Managed Data Procedures (AMDP).
AMDPs are implemented as an addition to traditional ABAP Object-Oriented programming. A user creates a class just like any other class, but to implement the AMDP they must execute two important steps:
Let’s look at the steps:
Step#1: First, they must ensure that the class implements the interface IF_AMDP_MARKER_HDB. Implementing this interface does not add any interface methods, but simply flags the code as an AMDP class.
Step#2: The Method that actually implements the AMDP procedure code must have some specialized method additions to identify itself as an AMDP. These additions also provide some information about the database and language the method should be implemented.
The Method Additions are described below:
- BY DATABASE PROCEDURE – Identifies this method as an AMDP
- FOR HDB – The HDB part identifies this is a procedure for HANA. This is the only option for AMDP available as of now
- LANGUAGE SQLSCRIPT – This identifies the language that will be used inside the method. SQLSCRIPT is the language that the HANA DB uses, and it is the language that must be used with the AMDP method.
Q&A (Post your questions and get the answers you need)
Q. I have been reading so many articles on SAP HANA, its confusing when they refer to on-premises vs. cloud. How do the cloud and on-premises SAP HANA deployment options differ?
A. SAP HANA deployment options range from those in which you have to manage everything from the metal on up, to those with push-button upgrades. No solution yet exists that makes the system a fully managed platform as a service (PaaS), where upgrades are transparent and the system always remains on the latest version (SAP’s HANA Cloud Platform HCP is the closest)
Let’s look at the different options…