** TEAM FPM ** A new UI Concept for the SADL based Application Creation Tool
The Floorplan Manager (FPM) framework contains a number of app wizards to create various types of FPM applications. There is a wizard for creating FPM apps based on Service Adaptation Definition Language (SADL) entities. With SADL, it is possible to push down queries directly to the database itself, thereby improving response cycle times, and, with suitable databases, very large amounts of data (millions of records) can be retrieved and displayed tremendously quickly.
Being inspired by the SAP App Gyver visual programming environment, the FPM and UR team have invested into the UI Concept of the SAP FPM Application Creation Tool to the strengthen the Low-Code/No-Code (LCNC) capabilities of the Floorplan Manager UI Framework. The improved user interface will be available with SAP_UI 757 (ABAP Platform 2022).
Imagine you want to display data from, for example, a CDS view or a DDIC table or a BOPF model with a web application, or you even want to create new data sets with this web application. You have no backend or UI developers available and need the web application immediately. You don’t want to make any concessions to the standards yourself, which means the web application should be secure and easy to use, it should display large amounts of data with high performance and have a beautiful user interface. In this case, the Floorplan Manager’s SADL-based Application Creation Tools (ACT) are the right choice for you
In the following example we demonstrate how this can be done in a few minutes. Just follow the step-by-step instructions below.
The ACTs can be accessed with the Floorplan Manager Workbench (transaction FPM_WB), in the section Wizards for Creating Application there are two links
- Wizard for Creating FPM Apps Based on Business Entities
- Wizard for Creating FPM Apps on Business Entities (CRUD)
The first tool can build apps to read data from a database, the second one can build app to create, read, update and delete (CRUD) items on a database.
If you are building an app to read data from a database, then first select a suitable data source, you have at least the following choices:
- BOPF Business Object
- Core Data Services
- Data Dictionary
- Enterprise Procurement Model (EPM) Entity Provider with Runtime Adapter
For demo purposes you may select the fourth option.
and decide for the business entity EPM Address Header data.
In the fourth step you can define the structure of the user interface. For instance, you may add a filter page and a chart that counts and visualizes the different countries of the address data.
On the right is an embedded preview. Here you can check how your app looks and how it works. In addition, you can run the preview in a separate session by using the function External Preview.
Almost there! In the fifth step, you only have to find a suitable namespace for the objects to be created, where Z is the default value. In addition, technical names (application and configurations) can be adjusted.
In the sixth and final step, you can (if necessary) specify a package and transport request, and use the Save function to build the web application.
On the confirmation screen you will find two links
- Edit Configuration (FLUID): This allows further adjustments (texts, visibilities, sequences, semantic colors) to be made.
- Execute Application: Hereby you start the new app … live and in color!
Done The new web application is here. By the way, you have just tried out the new Horizon theme Have fun with it!
The Search Page
The Filter Page