Scroll Top

Scrum: Hand-Written Notes In The Digital Age?

Scrum: Hand-Written Notes In The Digital Age?

TAKE NOTE (Insights into SAP solutions and Emerging Technology)

Nowadays it is important to minimize the time span required for a new software to be introduced to the market. Notably, SAP projects are far too complex for producing an all-encompassing performance specification.

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
The cause of these problems lies in the models themselves that define how to proceed; they are too inflexible and bureaucratic, unnecessarily strapping the whole team into a tight corset of constraints.

Scrum in SAP

Scrum is based on a very simple process. Only three roles are involved in a scrum process. The Product Owner submits the subject-specialist requirements, the Scrum Master’s role corresponds to that of a project manager, and the scrum team develops the product.


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.
Below is a very basic example of an AMDP method. This method simply selects the 200 records from database table SNWD_SO, with no selection conditions. There are a few features to pay particular attention to, which have been highlighted and numbered



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…

On-premises Tailored Data Center Integration is for companies that want to install and run HANA on their own hardware and networking infrastructure.
Infrastructure as a Service (IaaS) refers to platforms such as Amazon Web Services (AWS) and Microsoft Azure. You only manage the HANA software in these scenarios, while the hardware is managed via the IaaS system.
Managed hosting means the infrastructure and infrastructure management work are outsourced to a service provider. Usually, this doesn’t mean that the service provider really does all of the infrastructure work, so it is usually a good idea to keep expertise in your organization. But much of the day-to-day management of the system can be handled by the provider. SAP provides this type of service for HANA via its HANA Enterprise Cloud and SAP HANA Cloud Platform.
The choice of which option fits your business depends on the features available at each level, as well as the cost to your business of maintaining the expertise to support the deployment option you have chosen.

Pin It on Pinterest

Share This

If you enjoyed this post, why not share it with your friends!