SAP Fiori · S/4HANA · BTP Platform Enablement
Manufacturing SAP BTP SAP Fiori SAP Integration Suite
How a global building products manufacturer fixed its SAP order-entry app and stood up BTP
A global building products manufacturer Delivered 2024
Mindset fixed five distinct friction points in a global building products manufacturer's Guided Order Entry Fiori app, delivering faster and more accurate order creation, then expanded into BTP enablement, system integrations, and ongoing platform support.
By the numbers
-
13 weeks
Sprint 0 through hypercare delivery timeline
-
5
Distinct Fiori UX problems fixed in the order-entry app
-
2 sprints
Build cadence with 2-week iterations, daily stand-ups
Before
A functional app with real friction
- Order setup blocked until real line items existed, ZPSO orders required error-prone manual Plant entry.
- Critical fields resetting between edit and change modes, forcing repeated data entry.
- Redundant Delivery Group pop-ups and Detailed Tab rendering defects cluttering every order.
After
A clean, accurate order entry experience
- Orders can be set up early with a dummy line item, and Plant auto-populates for ZPSO orders.
- Fields persist across mode transitions, and display-to-change switching no longer requires a forced save.
- Rendering defects cleared, redundant pop-ups removed, and a governed BTP platform ready for what comes next.
Why this matters
A Fiori enhancement engagement that solved five specific, documented friction points for a live order desk, then became the starting point for a multi-phase BTP and integration program.
The challenge
A global manufacturer of high-performance insulation and building envelope products ran its sales order process through a custom Guided Order Entry (GOE) Fiori application. As the team worked to bring additional business units onto S/4HANA and improve the app, a set of specific problems kept slowing down the order desk.
Users couldn't start an order setup without real line items in hand, which created delays when orders needed to be initiated early. ZPSO order creation required manual Plant entry, a step that was error-prone and easy to get wrong. Critical fields like Plant weren't persisting when users moved between edit and change modes, so the same data had to be entered repeatedly. The Detailed Tab had rendering defects. And a redundant Delivery Group pop-up appeared every time it wasn't needed, cluttering the workflow.
The company needed all of this fixed precisely and without disrupting the order desk, while also planning a broader BTP foundation to support future integrations and a mobile-services program.
What we did
Mindset worked through each GOE problem in a structured, remote Scrum engagement: Sprint 0 for setup, two build sprints, UAT support, and hypercare, running over 13 weeks total with daily stand-ups, weekly cadence calls, and monthly leadership reviews.
For the dummy line item requirement, the team introduced a mechanism so users can open and set up an order before real line items exist, removing the wait. For ZPSO orders, Mindset auto-populated the Plant field and brought SAP Personas plant entry directly into the Fiori UI, so the correct plant is available without manual lookup. Data persistence was fixed so Plant and other fields carry through in both edit and change modes. A toggle was added so users can switch between display and change modes without being forced to save, matching how the order desk actually works. The Detailed Tab rendering defects were resolved and the Delivery Group pop-up was removed.
After the GOE work, the relationship expanded considerably. Mindset delivered a BTP Enablement and Fiori Activation program, a Planview and Adaptivework-to-S/4 integration, a Fiori and BTP advisory workshop, Mobile Services enablement, a Transportation Management integration with Integration Suite, and ongoing BTP advisory support into 2026.
The outcomes
Every GOE enhancement shipped on schedule within the 13-week plan. Order creation became faster for the team working ZPSO orders, manual entry errors dropped with the auto-populated Plant field, and the workflow cleared the redundant pop-up and mode-switch friction that had slowed users down.
The order desk gained an app that matched how they actually work: start an order early with a placeholder, fix errors less often, move through screens without forced saves. The UX improvements were delivered remotely with close collaboration between Mindset's team and the client's stakeholders.
The BTP enablement and integration work that followed the GOE phase gave the manufacturer a governed platform for system integrations, mobile services, and further Fiori development, with a consistent architecture lead across all phases.
If we built this today
Concept · not delivered scopeOrder entry that drafts itself.
This is a forward-looking concept, not the scope we delivered on this engagement. It is the build we would reach for now, grounded in SAP that ships today.
This team hand-built a custom Guided Order Entry Fiori app so sales orders went in faster and cleaner, the same friction a Joule sales-order agent is built to take off the rep's hands today.
The data product
Customer Intelligence
Grounds the agent in real order history, plant-to-customer patterns, and material availability so the drafted order matches how this customer actually buys. It gives the agent the business meaning behind a field instead of a blank box.
Intelligent Application on SAP Business Data Cloud
The Joule agent
Delivery Block Resolution
Reads the open sales order, the customer's plant assignments, and material availability, then drafts a clean order with the plant pre-filled so a rep can set it up before the real line items exist. It flags the blocks a person still needs to clear instead of forcing manual field entry.
SAP S/4HANA, SAP Fiori, SAP BTP · PROPOSE · Order processing time and order entry error rate
The Fiori app
Manage Sales Orders
The standard S/4HANA sales-order app with Joule in the launchpad, where a rep can ask for the order to be drafted, the plant defaulted, and fields validated before saving. It is the out-of-the-box home for the guided flow this engagement hand-built.
Embedded in the Fiori launchpad.
We would mine the real order-entry flow in SAP Signavio first, map the GOE app and its BTP touchpoints in SAP LeanIX, and let MIND accelerators carry the custom logic over to the standard app.
What we built
-
Order setup no longer blocked by missing line items
Dummy line item for early order setup
Introduced a mechanism so users can open and configure an order before real line items are available, removing the dependency that was blocking early order initiation.
-
Manual Plant entry error risk removed
Auto-populated Plant for ZPSO orders
Eliminated manual Plant entry for ZPSO orders by auto-populating the field and integrating SAP Personas plant entry directly into the Fiori UI.
-
No repeated data entry across mode transitions
Data persistence fix
Resolved the bug that caused Plant and other critical fields to reset when users moved between edit and change modes, so data entered once stays put.
-
Workflow matched to how the order desk operates
Display-to-change mode toggle
Added a toggle so users can switch between display and change modes without being forced to save, matching the actual order-desk workflow.
-
Cleaner interface, no rendering defects at UAT
Detailed Tab rendering fix and UI polish
Fixed the Detailed Tab rendering defects and removed the redundant Delivery Group pop-up, plus a UI polish pass across the full GOE application.
-
BTP platform operational for future phases
BTP enablement and Fiori activation
Stood up a governed SAP BTP foundation for the manufacturer's future integration and Fiori work, including Mobile Services enablement and advisory on Clean Core and platform governance.
-
Project data flowing between Planview and S/4HANA
Planview and S/4 integration
Built an integration between the manufacturer's Planview Adaptivework project management system and SAP S/4HANA as part of the broader integration program.
A look at the work