msc mobile emerging technologies blog

---

The purpose of this tutorial is to suggest how to detect any change a user could do in a Web form and more specifically within an SAP UI5 Form that is binded to a JSONModel. Indeed, unlike the oData model (sap.ui.model.odata.ODataModel), the JSON model (sap.ui.model.JSONModel) doesn’t offer a native “hasChanges” method. Yet, as we are about to demonstrate, there exists an easy alternative that consists in creating a Binding Model linked to the JSON model context and then listening to the “change” event of this binding Model.

---

There are a number of technologies that are becoming more and more important in the SAP world. Next to SAP's new flagship HANA we are talking about OData and SAP UI5. Therefore it is no surprise that SAP enabled their SQL Anywhere database to speak OData as well.

This blog will show how to enable the SQL Anywhere database to become an OData provider and how to consume this service from a locally installed WebIDE.

---

This blog explains in 5 steps the technical approach we follow when transforming an ABAP based Web Dynpro solution into a Fiori like application built with SAP UI5. 

---

Travel Management is around in the SAP ERP system since the late 1980s. This blog shows a brief history of the user interface of the travel management in the last 35 years.

The SQL Anywhere middleware database of SMP 2.3 tends to gow over time. This is using up a lot of discspace and can cause issues. This blog shows step by step how to shrink the database size.

---

We discussed the synchronization of high data volumes for offline availability before. SAP has used a similar architecture with MobiLink, the Exchange Framework and SAP UI5 in what they called the SAAP - SAP Always Available Platform. Breck Carter has written a great blog post about it - SAAP Is Built On SQL Anywhere.  

---

In a maintenance and customer service process, there are obvious domains to utilize checklists in order to fulfill the following purpose:

• Standardize maintenance checks based on predefined steps in order to ensure consistency and quality. As an example, we can examine a car inspection scenario which could consist of steps like:
  • Check wheels
  • Check engine
  • Check gears
• Capture condition of equipments
  • Qualitative: e.g. general condition like “good” or “bad”
  • Quantitative e.g. air pressure, operating hours or temperature
• Capture standardized error codes and causes like “outworn”, “overheated” or “leaking” for further analysis

This information could be used internally for documentation or data analysis. In addition, it could be shared with customers (for instance on a service report or inspection certificate).

---

SAP offers more and more business processes that are running out of the box on mobile devices. This is done by rolling out a growing number of so called Fiori Apps. But also on the technology side SAP is catching up by introducing mobile friendly technologies like UI5, Gateway/Odata, SAP Mobile Platform and HCP Mobile Services.

These applications and technologies are great to mobilize 95% of all online and offline use cases, but there are exceptions where they are not enough. This includes:

1. Offline applications with a very high data volume (Millions of records or GB of data)
2. Offline applications which require a synchronization that is sub-second
3. Applications with an ultra-fast user interface

SAP has another technologies that they acquired together with Sybase and Syclo – MobiLink and the Exchange Framework. This blog will give an introduction an architecture consisting of the Exchange Framework, MobiLink and Apache Cordova. It will explain how they can be utilized to create solutions that can meet the three previous mentioned attributes.

---

Within an implementation of the SAP SRM UI AddOn we recently had to add a Custom Annotation to an existing Gateway Service. In this blog we want to share how this is done. 

As described in an earlier blog post, we implemented the new SAP UI5 based SRM UI at one of our customers. Following up on this, we want get more into the implementation details with this post and show more of how we created the custom user interface.