If you plan to expose your SAP Data (Table or Query Data) to external environment like UI5/Fiori or HANA, then you need to push your data in a form of API. By API we mean, using OData. OData will generate a service link that can be accessed via internet and can be used to perform CRUD operations
We will create tiles to integrate our SAP Screen Personas Flavors directly into the Fiori launchpad. This allows our users to access both new applications (i.e. Fiori apps) as well as the modernized classic SAP transactions (Screen Personas Flavors) all from one unified entry point. To begin, we navigate to the Fiori Designer web address. This allows us to create Catalogs, Groups, and new tiles for the content we would like to appear on the Fiori Launchpad.
A viewport in SAP Screen Personas is a view on part of your Adaptive Flavor. You can use viewports to break complex screens into multiple parts, which improves the performance and loading time of the flavor, and gives the end user a modernized UI while requiring a minimal level of effort.
Adaptive Flavors implemented in conjunction with the use of the Slipstream engine provide users a modernized UI while requiring a minimal level of effort. Adaptive Flavors allow one initial Flavor to be reused to customize different classes of mobile devices, providing a user a UI experience that seems personalized and efficient for their needs
The SAP Screen Personas Slipstream Engine is a UI5 application that runs in a browser. Unlike Web GUI, the Slipstream Engine was engineered to run on mobile devices, with the expectation that one of the main screen interactions will be touch. So, SAP Screen Personas flavors look like mobile apps when you run them on a tablet or phone.
SAP Fiori can mean different things within a variety of contexts. Fiori can mean a series of specific design guidelines, and it can mean a collection of substantive apps. The most critical point is that SAP Fiori is driving the evolution of user interface, and it is now the forward face of SAP S/4 applications.