- SAP has told customers that they must use HANA CDSs.
- How accurate is SAP on this topic?
SAP has been communicating to customers that they should use HANA CDSs as a primary way to access SAP HANA data. And that CDS views are the way SAP will go forward in the future, which are available through OData interface.
- The OData interface is both problematic and not as flexible as SQL.
- SAP should not be defining how you consume of view the data. SAP offers CDSs. Customers can use them or not use them depending upon whether they find they fit their needs.
- Business logic cannot be published to the CDSs.
SAP has this way of presenting their options as if they are natural law. If the CDSs are good, a test will show this when compared to your alternative. The things that SAP are saying on this topic are adding up. We record false statements that are routinely made to customers. The idea inside of SAP is that customers have no real right to any truth, anything is said that simply supports whatever SAP wants the customer to do.
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 Risk Estimation Book
Better Managing Software Risk
The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.
Finding What Works and What Doesn’t
In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.
Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model