Another post was published on Pillir’s blog, this time with information on when to use SAP Fiori applications and when not to. Pillir begins by describing SAP’s response to users who have demonstrated a need for additional functionality beyond the core SAP ERP and SAP Business Suite offerings. Research conducted by SAP revealed that the majority of SAP users use the SAP user interface to access common applications. For this reason, SAP decided to create SAP Fiori apps for the most commonly used SAP GUI applications.
The SAP Fiori application library contains more than 300 role-based, device-independent apps that support accounting, engineering, sales, customer service, fulfillment and warehousing processes, among others. Additionally, Fiori transactional apps, factsheets, and analytics apps use SAP user data to inform their design and only provide users with relevant information.
When a SAP Fiori app meets a user’s needs, it’s often a great way to extend SAP functionality, save time, streamline processes, and increase productivity.
However, some users find that Fiori apps do not meet their needs. For example, some team members may want a different user interface, a display with less data to help them focus, a different screen order, or a completely different process that better suits their environment. SAP states that certain Fiori elements, such as adding, hiding or changing a field, can be modified using the SAP Web IDE platform tool.
However, extensive customization can be quite complicated. In addition to writing custom code in Fiori, users also need to consider the OData version they are using to connect.
Pillir spoke to a developer who was unable to connect a custom Fiori app to a SAP-provided OData version that was no longer compatible. The differences between OData service versions 2.0 and 4.0 resulted in broken app functionality, additional development to connect custom fields, changes…