SAP applications are around for quite some time now and so is the option and need to extend them. SAP took care of this and offered many extension mechanisms within the underlying ABAP technology stack. In addition, the ABAP platform itself served as a strong workhorse to build custom-specific functionality and apps collocated to the SAP core system. Unfortunately, this came at a price
ABAP for HANA
SAP envisions BW/4HANA as an unrestricted data warehouse solution for the modern enterprise-level organization. Data warehousing is a consolidation of corporate and extra-corporate data than can be analyzed for decision-making and innovative new products. Look for future releases to integrate more tightly with Hadoop and provide big data lakes, machine learning, and intelligent data analysis.
SAP S/4 Hana Past upgrades include the 1511, 1610, 1709, 1809 and recently the 1909 releases. These upgrades are centered on machine learning and automation. In the SAP S/4HANA 1909 release, SAP went a step further and embedded these capabilities into the platform’s core. SAP calls this the digital core.
As you prepare to migrate your business warehouse (BW) from ECC to SAP HANA, you will need to consider various aspects of the planning process for a successful migration. While this post may be a bit short to list every element to contemplate, the focus is on those key aspects to ensure the smoothest migration possible.
SAP Business Warehouse (BW) powered by HANA also known as BW on HANA (BWoH) is SAP’s data modeling, warehousing, and reporting tool built on the HANA database. SAP BW on HANA (BWoH) runs on the HANA database and therefore it is simpler and faster.
When correctly implemented, SAP HANA conveys outstanding results and performance, analytic intelligence, integration capabilities, data processing, and improved ROIs of the SAP landscape with swift time-to-value. Planning and executing a successful transition to the SAP HANA platform is crucial, and this article provides a detailed overview of ten tips that will help mitigate risks during your business’s migration to SAP HANA.
AMDPs provide powerful abstractions that enable ABAP developers to combine the benefits of the high-speed in-memory execution of SAP HANA with the well-established ABAP runtime and lifecycle model. Along with CDS Views, CDS Table Functions, and OPEN SQL, allow ABAP developers to renovate their existing assets and create new and innovative applications for SAP Business Suite on SAP HANA without losing the platform-independence of ABAP.
Core Data Services, or CDS, is a “semantically rich” Data Definition Language (or DDL) created by SAP. It provides an easy to understand and reusable tool that ABAP developers can utilize to execute the “code pushdown” paradigm. CDS has evolved into different variants, but the ABAP developer should chiefly be concerned with two specific ones…The lesser used option is HANA CDS, the database language that can be used to create tables, views, and structures on the HANA database itself. Views created in HANA can be consumed from the Netweaver AS using Native SQL. The second and most important variant of CDS that should concern ABAPers is the ABAP CDS. While significant differences have evolved between the two variants — for example, SAP HANA-based CDS obviously operates on SAP HANA, while ABAP-based CDS operates on most major database platforms as well as SAP HANA, and each has a different type of repository for development objects — both variants pursue the same goal: to represent central data definitions as a common basis for application development of all kinds.
Chances are that if you work with SAP ABAP, you have heard of SAP HANA by now. You’ve probably heard that it’s “the future” and a “game changer.”