Building SAP Fiori Apps can be mundane and boring work. Having to repeatedly code common interaction patterns and functionality for every application is a mindless task where time could be better spent improving the efficiency of the user and making their life a little more enjoyable (in the world of interacting with SAP).
Michael Golz, Chief Information Officer at SAP Americas, made a profound statement at the Newtown Square, headquarters of SAP America, for the SAP Cloud Platform & Design Innovation Customer Forum, when he said, “Take the work out of work”.
At the time Golz was giving a keynote on the SAP Intelligent Enterprise and how the SAP Cloud Platform (SCP) plays an integral part. However, as he clarified his meaning, it was immediately obvious that our IQX AppBuilder development platform does exactly that. It takes the mundane and boring work out of creating Fiori Applications for SAP.
Today, starting from scratch is unnecessary, slow and mundane. Low code, drag and drop capable development platforms with deep SAP integration are available and should be utilized. What they save in time, cost and coding frees teams up to focus on what is really valuable – business process efficiency, user experience and compliance. Or if using the latest buzz words, true ‘Digitalization’.
So, let’s take an example of building a basic Fiori app that stores some non-SAP data and needs the ability to attach some documents. Here are 5 basic tasks you need to perform before you even get started on the real functionality of the application. Included are also examples of where you could be saving time and costs by using the IQX AppBuilder for SAP Fiori development platform.
- Create Tables for Data Storage
- Create OData services for CRUD operations
- Create OData services for search helps (F4)
- Create OData services for server-side actions (e.g. Validation)
- Build pages (MVC) using XML or WebIDE layout designer
4. Create OData Services for Server-Side Actions (e.g. Validation)
As explained previously, any interaction between the web front end and SAP is done through OData services. We’ve covered the reading and writing of application data but that doesn’t include any other server-side functionality that needs to be implemented in ABAP such as simulating a Sales Order before posting.