Another post has been published on Pillir’s blog, this time with information on when and when not to use SAP Fiori apps. Pillar begins by describing SAP’s response to users who have demonstrated a need for additional functionality beyond the basic SAP ERP and SAP Business Suite offering. Research conducted by SAP revealed that the majority of SAP users use the SAP user interface to access common applications. As a result, SAP decided to create SAP Fiori apps for the most frequently used SAP GUI apps.
The SAP Fiori app library contains over 300 role-based, device-agnostic apps that support accounting, engineering, sales, customer service, fulfillment, and warehouse processes, among others. Additionally, Fiori transactional apps, fact sheets, and analytical apps use SAP user data to inform their design and provide only relevant information to users.
When an SAP Fiori application meets a user’s requirements, 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 an entirely different process more suited to their environment. SAP indicates that certain Fiori elements, such as adding, hiding or modifying a field, can be modified using the SAP Web IDE platform tool.
However, extensive customizations can be quite complicated. In addition to writing custom code in Fiori, users also need to consider the OData version they are using to login.
Pillir spoke to a developer who was unable to connect a custom Fiori app to an OData version provided by SAP that was no longer compatible. Differences between OData service versions 2.0 and 4.0 resulted in broken application functionality, additional development to connect custom fields, input parameter changes, and retesting of the entire application.
When SAP Fiori app development is required, there are many moving parts, and it’s important for users to understand that a customization decision requires full engagement. Once converted to a Fiori app, there will be no way back to the standard interface.
By using Pillir, users can bypass the hurdles developers face when customizing Fiori. Pillir’s integration with SAP is so robust that OData connectors are unnecessary; therefore, the work required to connect a Fiori app customization is eliminated. This low-code/no-code platform also allows users to deploy their app on any form factor, including devices with built-in apps from Zebra or Honeywell.
Pillir allows users to create “heavyweight” offline applications that work identically offline and online. For example, they can continue to generate SAP document numbers and use them to record equipment usage, locate and order parts, monitor time, and more. Then, once connectivity is restored, Pillir communicates data with SAP while synchronizing data, managing conflicts, and maintaining security.
For more information, please refer to the following URL: https://www.pillir.io/
Build ID: 89078749
If you detect any problems, problems or errors in the content of this press release, please contact [email protected] to let us know. We will respond and rectify the situation within the next 8 hours.