Another post was published on Pillir’s blog, this time with information about when and when not to use SAP Fiori applications. Pillir begins by describing SAP’s response to users who demonstrated a need for additional functionality beyond what core SAP ERP and SAP Business Suite offer. Research conducted by SAP revealed that the majority of SAP users utilised 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 applications.

The SAP Fiori applications library contains more than 300 role-based, device-agnostic apps that support accounting, engineering, sales, customer service, fulfilment, and warehouse processes, among others. In addition, Fiori transactional apps, fact sheets, and analytical apps utilise SAP user data to inform their design and deliver only pertinent information to users.

When a SAP Fiori app meets a user’s requirements, it is often a good way to extend SAP functionality, save time, streamline processes, and boost productivity.

However, some users find that Fiori apps do not meet their requirements. 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 that is more suited to their environment. SAP states that certain Fiori elements, like adding, hiding, or changing a field, can be modified using the SAP Web IDE platform tool.

However, extensive customisations can be quite complicated. In addition to writing custom code in Fiori, users must also consider the OData version they are using to connect.

Pillir spoke with 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, modification of input parameters, and retesting of the entire app.

When SAP Fiori app development is required, there are many moving parts, and it’s important for users to understand that a decision to customise requires total commitment. Once converted to a Fiori app, there will be no way to return to the standard interface.

Using Pillir, users can circumvent the obstacles that developers face when customising Fiori. Pillir’s integration with SAP is so robust that OData connectors are unnecessary; therefore, the work required to connect a Fiori app customisation is eliminated. This low-code/no-code platform also enables users to deploy their application on any form factor, including devices with embedded applications from Zebra or Honeywell.

Pillir allows users to create “heavyweight” offline applications that function identically offline and online. For instance, 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 has been restored, Pillir communicates data with SAP while synchronising data, managing conflicts, and maintaining security.

To find out more please see the following URL: https://www.pillir.io/

3133 West Frye Road

United States

comtex tracking



Source link

By admin

Leave a Reply

Your email address will not be published. Required fields are marked *