08-07-2014 3:56 AM
I understand from SAP mentor that there are some facts that are incorrect in the below blog and it was rejected. Not able to post a question to him to understand those. But i am really curious to know what are incorrect and understand those. If any of know, can you pls highlight / share your thoughts / ideas ?
The objective of this blog is to enable the IT team to map the FIORI apps to their existing applications. Hope,
this gives a quick overview on how FIORI is different and what is common between existing Business
Packages that they access through portal and FIORI app. Both FIORI and the Business packages enable the
business applications on web by consuming the back end calls which remains the same in both the cases.
Before Fiori was launched | After Fiori was launched |
---|---|
Business applications were enabled on Web browser through Business package implementations or through custom development | Business applications are enabled on multiple channels (desktops/laptops / smart phones / any handheld devices) through FIORI Apps. |
There are standard business packages for each module in SAP | Standard Fiori apps are being launched / developed for various modules within SAP |
Standard Business packages were based on WebDynpro framework | FIORI apps are based on SAP UI5 framework |
Custom configurations were made to standard business packages to meet different customer requirements | Standard Fiori apps can also be configured to meet customer requriements |
Custom WebDynpro applications were built if the customer requirements were not met by the standard business package | Custom UI5 applications can be developed to meet the customer requirements that are not available as part of standard business package |
Business packages based on WebDynpro were integrated on to Portal and accessed via portal while it can be accessed as separate url as well | FIORI applications can be launched via Portal as well. FIORI launch pad can be integrated on to Portal and Fiori apps can be launched from the launch pad. Fiori apps can also be accessed via FIORI login, if it is not needed to be accessed via portal |
Though Business packages can be accessed from browser on mobile, the look & feel of the screen will be distorted or the user experience to fill the fields will not be good. This is because, WebDynpro doesn't follow response design concep | FIORI apps are based on SAP UI5 which follows the responsive design concept. Hence, when Fiori Apps are accessed on any device, the screen layout will adjust according to the screen size and hence user experience while using the application is good. |
Business package based on WebDynpro were invoking the RFCs / BAPIs directly from the back end system, int order to display the data or to perform any CRUD operations | FIORI apps consumes the ODATA Services of respective back end RFCs from NW Gateway server, to display the data or to perform any CRUD operations |
WebDynpro framework is not very fast in lower bandwidth. | Standard / Custom Fiori apps are recommended to business, if the application is to be accessed in a lower band width. |
Run once, deploy once and run anywhere is not applicable here | Create a UI5 app, deploy it once and it can be accessed from any channel. There are no different set of codes for different devices. |
08-07-2014 10:31 AM
Hello Rukmani,
Actually, it was me. And I appologize that you have had no chance to get in touch with me directly.
In fact, I was leaving a note with the decline and was assuming you would see not only the note but also my contact details to get in touch with me. It seems this is not the case. Some lesson for me to learn for next time: get in touch with the person directly and leave the note empty...
I will send you a private mail so that we can work together on your list.
All the best,
JJ