Can SAP Fiori Handle Warehouse Barcode Scanning Needs?

With SAP Fiori, SAP offers a design concept for unified and modern interfaces on desktop screens and, by its own admission, for mobile devices as well. In the context of mobile warehouse solutions, the question is: can flexible and high-performance scanner apps also be implemented with Fiori?

The Fiori approach includes universal design guidelines for the SAP ecosystem. On this basis, SAP offers ready-made standard apps for transactional or analytical applications. In principle, SAP users can also develop their own Fiori applications.

The Fiori Launchpad has been established as the central entry point for Fiori applications, serving as SAP's "start screen," so to speak. Users can access the Launchpad both in a desktop version and via the Launchpad app for Android and iOS. Its most important identifying feature is certainly the tiles used to launch individual applications. Companies can use Fiori as standard under SAP S/4HANA, and select Fiori apps are also available for older SAP versions.

But what are the actual requirements for mobile SAP solutions in intralogistics, and what characterizes Fiori in the context of MDE?

MDE Requirements in Intralogistics

• Warehouse employees without SAP expertise
• Small-format input displays
• Warehouse-optimized on-screen keyboards
• User-friendly, process-oriented operation
• Interruption handling (for connection drops)
• Handheld scanner solution suitable for offline operation
• Flexible use of all types of device peripherals
• Integration of third-party systems for process optimization

Fiori

• Designed for desktop input
• Requires a permanent data connection
• Transmits large data volumes
• Requires extra effort for functional interruption handling
• Compatible only with select device peripherals
• Suitable for: Office users, mobile devices with larger screens, and mapping simple standard processes

SAP does not offer ready-made Fiori apps for logistics processes in the warehouse and production that are specifically for use on handhelds. The apps that do exist in the SAP library for transactions like SAP goods receipt or transfers are designed for desktop input and, due to the sheer volume of data they present, are not optimized for small mobile screens. Furthermore, there are no plans to develop standard Fiori apps for SAP WM (or Stockroom Management under S/4HANA).

If a company is considering custom development of mobile MDE applications with Fiori, the corresponding time and financial costs should be calculated and potentially compared against a specialized mobile solution. Given the typically individual customizing of an SAP system, any scanner solution—whether built with Fiori or another technology—will always require company-specific adaptation.

Technical aspects will only be outlined here, as this is primarily a matter for the IT department: Fiori separates the user interface from the data—or more precisely, from the data service that enables communication with SAP. In the Fiori context, communication occurs via the OData interface technology, meaning that knowledge of OData within the company or among SAP consultants is required for mobile Fiori applications. Furthermore, Fiori interfaces are based on common web technologies like JavaScript, Cordova, etc., which an SAP application developer accustomed to ABAP may need to learn first. Last but not least, a warehouse app also needs a user-friendly, process-oriented design—making an understanding of mobile design principles essential.

The Fiori framework is not natively designed for the special requirements of mobile work in the warehouse and production. Processes in logistics and on the shop floor require the flexible use of device peripherals, such as barcode scanners, NFC, RFID, or cameras for OCR text recognition. While camera use is supported by Fiori, other device features relevant to intralogistics are not and must be individually implemented if needed. For example, the Fiori scan plug-in currently only supports the scan engine from the manufacturer Zebra—meaning mobile hardware from other manufacturers cannot be used.

A frequently cited drawback, and likely the most serious one in practice, is that Fiori transmits relatively large volumes of data when communicating between the client app and the SAP backend. This harms the performance of a scanner app and, ultimately, the acceptance among warehouse employees. These noticeable performance losses cause significant latencies, especially during a global rollout for plants that are located far from the SAP system. These performance issues are a primary reason why Fiori is often ruled out as a technology for MDE apps.

The acceptance of an SAP MDE solution depends heavily on its user-friendliness. Fiori is not a technology that was originally designed for use on handhelds. This becomes noticeable in the details when operating Fiori apps on MDE devices. For example, users report undesirable behavior from screen elements, such as the native Android keyboard popping up unintentionally. In contrast, specialized mobile applications use their own on-screen keyboards that are optimized for use on industrial handhelds in the warehouse.

Furthermore, Fiori as a technology offers no know-how or design standards for optimized user guidance on a mobile device. Fiori apps are often designed from the perspective of a desktop or office user. In the warehouse, however, employees need to make entries on small displays and are typically not SAP experts. Both of these factors require intuitive screens and the consistent omission of non-essential information.

As a native SAP technology, Fiori allows for communication almost exclusively with SAP. The integration of third-party systems into the mobile application—such as a document management system, a Manufacturing Execution System (MES), operational data collection (BDE), or a database, or the mobile integration of a lift system or scales—is only possible with an open software platform.

By default, Fiori apps are designed as browser-based applications. In the case of a logistics application in the warehouse, this means that a permanent data connection via WLAN or cellular must be available to retrieve data from and write back to SAP. However, brief connection interruptions are a part of daily life in a warehouse, and a warehouse application should at least provide interruption handling on the mobile device. This is possible with Fiori, but it involves additional effort. In contrast, those who need scanner solutions with extended or full offline capability will be better off with specialized software.

This brief overview makes it clear that Fiori is certainly suitable for mobile applications, especially when the applications map simple processes or are used on mobile devices with larger screens, and when performance plays a minor role. MDE solutions in SAP intralogistics are typically intended for very specific processes and users that are inadequately served by standard SAP technology. In these cases, it is worth examining alternative approaches.