Success Story · Harmonizing warehouse processes
ITT Cannon brought warehouse and inventory processes back to the SAP standard. Mobile UI5 dialogs make warehouse work easier, and the Mobile Builder follows.
ITT Cannon Read storyMobile Builder:
From problem to SAP Fiori app
You build Fiori apps by drag and drop directly in your SAP system, without middleware. This works on-premise, in the private cloud and in the SAP Public Cloud.
App designer
Drag and drop
No middleware
Directly in SAP
The starting point
The standard fits. Your process does not.
As soon as a process deviates from the SAP standard, the waiting begins: for IT, for budget approval, for the next release. Until then people make do with paper.
IT queue
Every process change becomes a project and lands behind twenty other tickets.
Paper as a stopgap
Lists, route cards and Excel sheets. What appears once often stays for years.
Knowledge silos
Three people know the special processes. If one is out, the process stops.
Expensive workarounds
Rebooking, double entry and troubleshooting. Nobody plans for these costs.
The solution
Digitize processes faster, without detours
The Mobile Builder runs as an ABAP application in your SAP system, with no middleware and no data leakage. Authorizations, documents and logs stay in the system.
100% SAP-native
Uses roles, authorizations and data models. Audit-ready and clean-core compliant.
Productive sooner
The first app is usually productive after a few days.
Clean core
Special processes stay outside the core. This helps with the move from ECC to S/4HANA.
One platform
Departments, IT and SAP experts work in the same tool.
How it works
Three steps to a productive app
You write no frontend code. The app runs on the devices you already have: scanner, industrial tablet or smartphone with scan grip.
1. Describe the process
You define what should happen at the workplace: fields, checks, postings.
2. Click the app together
Assemble building blocks by drag and drop, with AI support during setup.
3. Roll out and adjust
Live in the SAP system on any device. Changes take days instead of a release cycle.
Use cases
Where the Mobile Builder is strongest
You will find more on features and typical use cases on the Mobile Builder website.
Logistics and warehouse
Picking, packing tables and mobile warehouse processes.
Production
Confirmations, material consumption and shop floor dialogs.
Maintenance
Notifications, checklists and mobile data capture.
Quality and special processes
Inspection processes, documentation and individual workflows.
Devices
Runs on the devices you already have
The app opens in the browser. You do not have to install anything on the devices.
From practice
Mobile processes in the warehouse
Related
More around mobile processes
Fiori & UI5
A modern, role-based SAP interface for every device.
To Fiori & UI5UI5 Converter
Turns the mobile screens of SAP EWM and WM into responsive UI5 apps.
To UI5 ConverterEWM & MFS
Warehouse management for complex and automated warehouses.
To EWM & MFSWM & Stock Room Management
The basic functions of SAP WM in S/4HANA for simple warehouses.
To WM & Stock Room ManagementHPC.Warehouse Monitor
Real-time data, mobile processes and prioritized transport orders in the warehouse.
To HPC.Warehouse MonitorSAP Cloud ERP
Finance, procurement, supply chain and sales on one shared data basis.
To SAP Cloud ERP
Frequently asked questions
Mobile Builder: questions and answers
Answers to what companies ask us most often before they start.
What is the Mobile Builder?
The Mobile Builder is an SAP-native platform for building Fiori apps by drag and drop, with AI support, directly in the SAP system and without middleware. It is a product of HPC AG.
Does the Mobile Builder also run in the SAP Public Cloud?
Yes. It runs in S/4HANA on-premise, in the private cloud (RISE with SAP) and in the SAP Public Cloud. No middleware is needed, and no data leaves the system boundary.
How long does the first productive app take?
Usually a few days. Most of the work lies in clarifying the process, not in building the app.
Can departments build apps themselves?
Yes, within a framework set by IT. Authorizations, approved building blocks and transport routes stay under your control.
What happens during an S/4HANA upgrade?
The apps keep running because only released interfaces are used. Each release comes with a compatibility statement.
Which devices are supported?
Any device with a browser, without an extra app: industrial tablets, scanners and smartphones. A standard HTML5-capable browser is enough; SAP recommends Google Chrome.
Your next step
Talk to us about your processes
Whether as a start to process digitization or for a specific requirement: together we find out how the Mobile Builder supports you. Write directly to someone on the team or use our contact form for a free initial consultation.
Book a consultation
30 minutes, free of charge
