S/4HANA UX · Salesforce Integration · Clean Core
Manufacturing SAP BTP SAP Fiori SAP Integration Suite
Building the Fiori and Salesforce UX for a precision manufacturer’s JD Edwards-to-S/4HANA migration
A precision component manufacturer Delivered 2026
Mindset validated an embedded-Fiori-in-Salesforce model through a rapid proof of concept, then stood up a full S/4HANA UX program to carry that model into production across sales and service workflows.
By the numbers
-
1 login
Single sign-on across Fiori and Salesforce
-
8 sprints
Three-week development cycles across UX workstreams
-
5 functions
S/4HANA functions surfaced natively inside Salesforce
Before
A migration risk: users split across systems
- Sales and service teams worked across Salesforce, Fiori, and other tools with no unified experience.
- Standard Fiori apps required users to leave Salesforce and open a separate SAP interface.
- Custom part numbers and multilingual material descriptions had no consistent path into the new system.
After
S/4HANA data inside the tools people already use
- SAP Fiori embedded inside Salesforce via a Canvas app, with OAuth single sign-on.
- Order entry, availability checks, and material lookup accessible without leaving Salesforce.
- Clean-core part number display and multilingual descriptions reconciled across both interfaces.
Why this matters
The hardest part of any ERP migration is user adoption. This program tackled that directly, building the UX bridge between SAP and Salesforce before go-live, with a clean-core approach that won't create upgrade debt.
The challenge
The manufacturer was moving its ERP from JD Edwards to SAP S/4HANA, and its technology stack ran well beyond SAP. Salesforce, Salsify, Shopify, Aras, and Google Cloud Platform all played active roles, which meant sales and service teams worked across multiple systems every day.
For the migration to land well, users had to be able to reach SAP data and actions from inside the tools they already knew. A Fiori-first approach that asked people to leave Salesforce and open a separate SAP window was a real adoption risk. At the same time, any customization needed to stay clean-core, so it wouldn't create drag on future SAP upgrades.
The company also carried a catalog of part numbers and multilingual material descriptions tied to its Japan headquarters that had to be surfaced correctly in both Fiori and Salesforce.
What we did
Mindset started with a tightly scoped feasibility proof of concept to answer one question: could a SAP Fiori app be embedded inside Salesforce as a Canvas app and actually feel natural, with OAuth-based single sign-on so users never hit a second login screen?
The POC ran against a Salesforce sandbox and a Dev S/4HANA and BTP instance, testing a standard Fiori order management app rendering inside Salesforce. It validated the model and fed directly into a full S/4HANA UX Program.
The larger program runs across three workstreams. The first surfaces Fiori UI and S/4HANA data inside Salesforce via SAP Integration Suite and Salesforce Connect, covering order entry, availability checks, and material lookup. The second handles clean-core customization, including the manufacturer's own part number display and selection, coordinated with both the client and their system integrator on the classification data model. The third reconciles alternative-language material descriptions against the Japan headquarters feed.
Delivery follows Mindset's onshore-led, India-augmented model with a dedicated delivery lead acting as Scrum Master, running eight three-week development sprints against the client's own S/4HANA procurement schedule.
The outcomes
The proof of concept confirmed the embedded-Fiori-in-Salesforce architecture before the larger program commitment was made. That validation gave the team and the client confidence in the approach and a working technical foundation to build from.
The full UX program is active. When complete, sales and service users will access SAP order data and actions from inside Salesforce with a single sign-on, part number selection integrated directly into the Fiori and Salesforce interfaces, and material descriptions accurate in multiple languages.
If we built this today
Concept · not delivered scopeOrder management that lives where reps work.
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 engagement set out to surface S/4HANA order processes cleanly inside Salesforce so sales and service users would actually adopt the new system, and today that same embedded order experience can carry a Joule agent that drafts the fix for a blocked order in place.
The data product
Customer Intelligence
Pulls order, fulfillment, and account signals from S/4HANA into one governed view so the agent reasons over real customer and order meaning, not a stale copy. The Knowledge Graph keeps the business semantics honest across the connected stack.
Intelligent Application on SAP Business Data Cloud
The Joule agent
Delivery Block Resolution
Reads sales orders, credit holds, ATP shortfalls, and the cross-system context from Salesforce and the S/4HANA order book, then proposes the cleanest path to clear a stuck order and surfaces it right where the rep is already working. The human approves before anything moves.
SAP S/4HANA, SAP BTP, SAP Integration Suite, SAP Fiori · PROPOSE · Order-to-fulfillment cycle time and blocked-order backlog
The Fiori app
Manage Sales Orders / Sales Order Fulfillment
The standard S/4HANA order app, the same one the team validated inside a Salesforce Canvas frame, now ships with Joule embedded so a rep can ask why an order is blocked and get a drafted fix without leaving the record. The delivery-block resolution view rolls up every issue holding an order back.
Embedded in the Fiori launchpad, and renders inside Salesforce via Canvas
We'd still mine the real order-to-cash flow in SAP Signavio first, map the connected stack in SAP LeanIX, and lean on MIND accelerators to carry the proven embedded-Fiori pattern from the old build into the new one.
What we built
-
Validated the embedded architecture before full program commitment
Fiori-in-Salesforce proof of concept
A feasibility POC embedding a standard SAP Fiori order management app inside Salesforce as a Canvas app, using OAuth-based authentication to eliminate a second login.
-
8 development sprints across sales and service UX
S/4HANA UX Program
A structured, ~12-month engagement tracking the client's S/4HANA procurement schedule across design and architecture, eight three-week development sprints, testing and deployment, and hypercare.
-
5 primary sales and service functions surfaced inside Salesforce
Salesforce UI/UX integration
SAP Integration Suite and Salesforce Connect wiring to expose Fiori UI and S/4HANA order data inside Salesforce, covering order entry, availability checks, and material lookup.
-
Part number selection available in both interfaces without custom code risk
Clean-core part number display
Custom part number display and selection built to clean-core standards, integrated through a classification characteristic into both Fiori and Salesforce, coordinated with the client's broader classification data model.
-
Material descriptions consistent across language variants and interfaces
Multilingual material description reconciliation
Alignment of alternative-language display material descriptions against the Japan headquarters data feed, ensuring correct display across both Fiori and Salesforce.
-
Sprints aligned to client ERP procurement timeline
Onshore-led agile delivery model
A Mindset delivery lead acting as Scrum Master, with onshore architecture and India-augmented development, running against the client's own S/4HANA go-live schedule.