- SAP on has made bizarre proposals regarding code pushdown (aka stored procedures) and Core Data Services.
- SAP explains Core Data Services as something innovative when SAP is just using new terminology to something quite old.
- As with Oracle, SAP is using CDSs to restrict the options of its customers to better lock them into buying SAP.
Introduction: How Truthful is SAP Being on Code Pushdown?
SAP has made a lot of noise about how important its code pushdown (aka stored procedures) in HANA are. However, an issue that has begun to arise in how SAP has begun to use the term to describe things that do not actually code pushdown. You will learn what is true regarding code pushdown.
What is Code Pushdown?
The first place to begin of course is “what is code pushdown.”
Code pushdown is an SAP term for putting code that was previously in the application layer into the database layer.
How SAP is Now Using the Term
As stated by a colleague.
“Code that was pushed down to the database becomes even more pushed down by “filter push down”, “limit push down” and “aggregation push down” This is plain old basic “anyDb” SQL wisdom. Reduce the amount of data as early as possible, especially before you join subqueries, that is at the “most inner” or “lowest” level of your SQL. “Filter push down”: filter each result set to be joined BEFORE you join them, do not join large sets and filter afterwards. I learned this in an “anyDb” administration and performance course about 15 years ago, and even then it wasn’t new.”
The first question that should arise when reading this is how is it that code has to be pushed down multiple levels in the database?
If the code is “pushed,” it is removed from the application layer and inserted into a table. Is there a level below a table? What is this quantum physics?
What SAP means is simply the reduction of data, not actually pushing code.
SAP on Core Data Services
SAP has published a document on ABAP Core Data Services of CDSs that can be found at this link.
But some of the things written in the document are required further elaboration.
For example, it states that Fiori apps are easy to create.
“Based on the OData exposure of CDS described above, it is then rather straightforward to create an SAP Fiori app using the development framework SAP WEB IDE (either locally or within SAP Cloud Platform). As depicted in Figure 4 the SAP Fiori User Interface connects to SAP Gateway using the OData services.”
The idea being the Fiori app will connect to the CDS view. The CDS is a database view with stored database functions that enable the retrieval of data. The idea is to improve on the limited ABAP dictionary views versus anyDatabaseViews have had for decades.
But instead of presenting CDSs as “catching up” with competing offerings, SAP decided to provide a deceptive explanation for the logic of CDSs. This is taken from the document ABAP Core Data Services on AnyDB.
“The CDS framework was introduced to leverage the computational power of HANA DB. Nevertheless, it can also be used with all other databases that support SAP NetWeaver (called anyDB in the following). This guide gives hands-on information on how to implement, run and optimize CDS based applications on anyDB.”
Reinventing the Wheel?
That makes it sound like SAP is bringing something that did not exist before — both for HANA and for AnyDB. The clear statement here is that other DBs can benefit from CDSs — making it appear as if CDSs are an innovation, not that they are bringing HANA to par (or attempting to do so) with AnyDB libraries.
That is one problem. The second is the phrasing that
“CDSs were designed to leverage the computation power of HANA, but nevertheless they can be used for other databases.”
This implies that other databases do not have HANA’s computational power. But let us leave that to the side for now.
The point we are emphasizing in is the presentation by SAP of CDSs as if other databases do not already have what CDSs offer. Clearly, it will take years for CDSs to reach parity with anyDatabaseViews.
Cost to Create Fiori Apps
Normally Fiori apps are extremely expensive to create, as was even pointed out in the Forrester study that SAP paid for, where Forrester states that Fiori apps should be used standard. This was addressed in the article What is Actually in the Fiori Box?
And we have numerous stories of the costs of making custom Fiori apps. Basically, this is not happening on projects to any significant degree. Customers that are sufficiently misinformed to customize Fiori apps normally soon run out of money. But these are custom Fiori apps with some complexity. Other Fiori apps are much easier to create than others, as observed by our colleague.
“A simple Fiori app consisting of a drill-down table (filterable, sortable, groupable) and navigation to a detail form is quite easy to build as long as you do not need anything extra. Fiori provides “SmartTables” and “SmartForms” widgets, their behavior can be controlled by annotations/properties in the metadata of OData services (e.g. filterable, sortable, label). These annotations can be defined at the level of the CDS View already (@Filterable, @Sortable, @Label) and are propagated to the OData service that can be generated from CDS Views by some SAP magic. This works quite well for Fiori Apps with almost no UI logic (especially drill down tables with detail views, no edit) that are built once and never touched again. However if you modify the data model you usually are best of when you rebuild your Fiori App from scratch.”
Laying Out Intelligent Fiori Usage
So if Fiori is laid out in terms of usage it is:
- Use the standard Fiori apps, although those Fiori apps are quite limited (See the article Strange Changes to the Number of Fiori Apps to find out how SAP has exploded and exaggerated the number of Fiori apps.
- Potentially use the SmartTable or SmartForm Fiori widgets to develop reporting apps.
- Do not customize any Fiori apps that have any complexity, so business logic, data complexity etc.
The vision being pitched is to use the CDS and then do what you want in Fiori. There is a big question as to whether that will actually happen. If SAP was happy with customers using an efficient non-SAP app development environment then maybe, but then, SAP will dissuade that from happening.
Secondly, another observation about the CDSs is from a colleague.
“This way offers you a clean layered application and the chance to write unit tests without database persistence. SAP are throwing away accepted architecture paradigms. CDS are OK to look at and analyze (join, aggregate, partly filter) data. That’s it. CDS is a framework, not new technology.”
This brings up the topic of whether CDS will ever really catch on, or if they will end up being just another item that SAP introduces that just falls to the wayside.
The Benefit to Stored Procedures / Code Pushdown
CDSs as with stored procedures are a form of code pushdown. However, overall, we are still lost as to why SPs are a good thing when the discussion of SPs is really about tradeoffs. This topic is actively debated among different with expertise in the area and there is not one clear answer. We keep pointing out that HANA is not addressing the hardware it runs on very well. So if you aren’t even addressing the hardware properly, why are we worried about SPs? Furthermore, SP’s bring up more portability overhead for different DBs. Also, if SP/CDSs are so effective, why won’t SAP publish any benchmarks on S/4HANA on ECC?
This gets into the topic if how most of SAP’s proposals, particularly since the introduction of HANA, where SAP took an abrupt turn from Netweaver as their primary marketing tentpole and transitioned to HANA, have been focused on making architecture arguments around performance. This is incongruous, as the performance was never an SAP selling point. Today the majority of SAP software performs worse in terms of speed and usability of that speed versus competing applications.
Previous points of emphasis on SAP were reliability and business process/functionality coverage. But first with Netweaver (which focused on integration) and then with HANA, SAP essentially changed its historical message and value proposition.
Restricting Stored Procedures for Competitive Reasons
In fact, SAP restricting SPs of S/4HANA is the primary limitation to being able to port S/4HANA to AnyDB. SAP is allowing the CDSs to be ported, but not other SPs.
Code that was taken from the application layer in ECC and was pushed into the SPs used to belong to the customer when they purchased the ECC license. But with S/4HANA that code did not transition to the customer. were taken from the application layer in ECC and were pushed into the SPs used to belong to the customer when they purchased the ECC license. But with S/4HANA that code did not transition to the customer.
SAP has proposed that this is all new code, but it could not be. Else, how did ECC do these things before?
The question that no one seems to be asking is why SAP has control over code that was previously in the application layer but was migrated to the DB layer as a stored procedure. These are codes that SAP supposes to deliver for their customers who paid for their software. This is code that the customer should be able to use as they wish under the license. That is they should not be restricted by code that is in SPs that SAP controls how is run.
The Proposed Logic of the Importance of the Code Pushdown
Now let us switch from one type of code pushdown (SPs) back to another type of code pushdown (CDSs)
Let’s look at SAP’s logic for the CDSs. Here was a recent argument made in favor of CDSs.
“Without CDS (labeled as “Classic Approach” in Figure 1), intensive calculations are done on the application layer avoiding costly computations in the database. This results in rather simple SQL queries between application and database layer. The drawback is however that lots of data need to be transferred back and forth between those two layers. Often, this is very time-consuming. “
Is it? With 2018 hardware? (or 2014 hardware as not all hardware is new).
What does SAP think its applications do? SAP does not compete in high-performance computing applications. These are not scientific applications, massively parallel scientific processing or even Big Data.
f there is a problem with transferring data between the two layers, then the entire application should be put in the database. Or most of it in the database. Is that such a good idea? We have software that performs much better than SAP on smaller hardware, and they do it with the standard division with application logic in the application layer and just storing data in the database.
SAP needs to police its use of the term pushdown or it will cease to have any meaning.
The evidence is how HANA has so vastly underperformed its performance hype as is covered in the article HANA as a Mismatch for S/4HANA and ERP.
SAP is not actually focused on performance, it is using performance to push out other database vendors. What SAP cares about is using the idea of performance to push customers down the rat maze in a way that benefits SAP the most. SAP can use arguments about performance to make them accept that logic of the lack of S/4HANA portability to different databases because SAP’s help restricts that portability. That is at least to the laymen — if SAP wanted, they could share the S/4HANA SPs with Oracle, IBM, and Microsoft, and all of these companies would pay the cost of performing the porting of the SPs to their respective databases. But the do not want to do this. They want to block out other vendors and restrict choice. And they are doing it retroactively because of the previous versions of their ERP system was portable to different databases, and that was the assumption under which it was purchased.
But SAP still will not release the SPs because they don’t want S/4AHANA ported, because they want to use S/4HANA as a wedge to get database sales that they would not otherwise get in an open competition. We cover SAP’s unwillingness to benchmark S/4HANA on HANA in the article The Hidden Issue with the SD HANA Benchmark.
Search Our Other HANA Content
Financial Bias Disclosure
Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.
The Real Story on ERP Book
How This Book is Structured
This book combines a meta-analysis of all of the academic research on the benefits of ERP, coupled with on project experience.
ERP has had a remarkable impact on most companies that implemented it. Unplanned expenses for customization, failed implementations, integration, and applications to meet the business requirements that ERP could not–have added up to a higher Total Cost of Ownership for ERP were all unexpected, and account control, on the part of ERP vendors — is now a significant issue affecting IT performance.
Break the Bank for ERP?
Many companies that have broken the bank to implement ERP projects have seen their KPIs go down— but the question is why this is the case. Major consulting companies are some of the largest promoters of ERP systems, but given the massive profits they make on ERP implementations — can they be trusted to provide the real story on ERP? Probably not, however, written by the Managing Editor of SCM Focus, Shaun Snapp — an author with many years of experience with ERP system. A supply chain software expert and well known for providing authentic information on the topics he covers, you can trust this book to provide all the detail that no consulting firm will.
By reading this book you will:
- Examine the high failure rates of ERP implementations.
- Demystify the convincing arguments ERP vendors use to sell ERP.
- See how ERP vendors take control of client accounts with ERP.
- Understand why single-instance ERP is not typically feasible.
- Calculate the total cost of ownership and return on investment for your ERP implementation.
- Understand the alternatives to ERP.
- Chapter 1: Introduction to ERP Software
- Chapter 2: The History of ERP
- Chapter 3: Logical Fallacies and the Logics Used to Sell ERP
- Chapter 4: The Best Practice Logic for ERP
- Chapter 5: The Integration Benefits Logic for ERP
- Chapter 6: Analyzing The Logic Used to Sell ERP
- Chapter 7: The High TCO and Low ROI of ERP
- Chapter 8: ERP and the Problem with Institutional Decision Making
- Chapter 9: How ERP Creates Redundant Systems
- Chapter 10: How ERP Distracts Companies from Implementing Better Functionality
- Chapter 11: Alternatives to ERP or Adjusting the Current ERP System
- Chapter 12: Conclusion