With more businesses looking to unlock the full potential of ABAP in Platform 1809, the optimization of ABAP becomes crucial. The current implementation of ABAP brings a lot of improvements to the forefront to help companies with their app development. Indeed, Platform 1809 presents a slew of development improvements for ABAP users and lays the foundation for both SAP HANA and SAP S/4HANA users. However, to truly leverage the power that these improvements in code offer, we need to explore how we can optimize the ABAP platform. This article intends to explore three optimizations that are present in Platform 1809.
Optimization 1: Machine-to-Machine (M2M) Communication
SAP’s solution for IoT device interface uses the Message Queuing Telemetry Transport (MQTT). This protocol is developed as a means of supporting industrial IoT device deployment. It achieves this through a lightweight system that allows servers to publish their presence and devices to subscribe to the relevant streams of data. ABAP 1809 offers a programmable MQTT interface that can relay messages and collect event-driven data as an MQTT broker.
By doing this, ABAP gets direct access to devices, allowing developers to leverage the machine learning capabilities that SAP has implemented. What’s more, a direct interface with ABAP will enable developers to tap into real-time analytics processing and increase the responsivity of devices through intelligent use of EDGE connections.
Optimization 2: Hierarchy and Abstraction
SAP HANA has become famous in coding circles for its ability to have hierarchies built into its databases. Now, ABAP 1809 brings further functionality by allowing developers to operate entirely within SAP HANA. In the past, one of the prerequisites for developing an ABAP application was ensuring that there was compatibility between SAP’s database and other external databases. However, SQL would not work well with SAP’s hierarchies, and it required some clever workarounds to attain compatibility.
Previously, ABAP applications handled hierarchies on the server level, using makeshift SQL tables to ensure compatibility between different databases. Now, ABAP 1809 brings a new way to deal with this directly within the application itself. The two keywords, DEFINE HIERARCHY and DEFINE ABSTRACT ENTITY, offer developers the chance to manipulate date directly using ABAP SQL. This version of SQL is developed as an SAP-specific implementation of the Open SQL standard and was created to deal with ABAP applications’ specific needs.
Optimization 3: Custom Code Adaptation
If like Dermani Medspa, you’re planning a migration from SAP Business Suite to SAP S/4 HANA, you will need to migrate your custom code as well. ABAP Test Cockpit is where users can start with their code migration. It offers coders a robust analysis utility for figuring out the incompatibilities between Business Suite custom code and SAP S/4HANA. Even though it can quickly highlight these errors, it doesn’t fix them automatically.
ABAP Test Cockpit 1809 presents an upgrade, in that it offers users a few quick fixes for commonly encountered errors. The feature is akin to other development environments like Visual Studio.
In addition to these quick fixes, ABAP Test Cockpit 1809 also offers some graphical reporting applications that are SAP Fiori based. These can make visualization of errors much more straightforward and help developers work out where problems exist.