SAP BTP / Master Data Automation
Energy and Utilities SAP BTP SAP CS SAP DMS
How Mindset automated manual SAP master data creation for a global filtration manufacturer
A Global Industrial Filtration Manufacturer Delivered 2024
Mindset automated the manual creation and modification of SAP part numbers, bills of material, and document info records for a global manufacturer, cutting the time and error rate that came with doing it by hand.
By the numbers
-
3 transaction types
Part numbers, BOMs, and document info records automated
-
~90%
Of the company's master data needs covered by the solution
-
Global rollout
Multilingual solution ready for all facilities
Before
Manual entry, limited by the central instance
- Part numbers, BOMs, and document info records created and modified manually in SAP transactions, slow and error-prone.
- Engineering time spent on data entry rather than engineering work.
- A centrally controlled SAP instance that limits local changes, making a traditional configuration-based fix difficult.
After
Automated master data, globally deployable
- Automated creation and modification of part numbers, BOMs, and document info records on SAP BTP.
- Works within the constraints of the central instance and requires no local SAP changes.
- Multilingual support built in, ready to roll out across the global manufacturing footprint.
Why this matters
A manufacturer constrained by a centrally controlled SAP instance needed a way to automate master data creation without touching the core system. Mindset reused a proven BTP accelerator and built a globally deployable solution from the ground up.
The challenge
Engineering teams at this Minnesota-based filtration manufacturer were spending too much time on a process that should have been fast: creating and modifying part numbers, bills of material, and document info records in SAP.
The MM01/02/03, CS01/02/03, and CV01N/02N/03N transactions all required manual data entry. Each one was time-consuming and error-prone, and the volume of work kept adding up. What made the problem harder was the SAP environment: the company's instance is controlled out of Germany, which limits what the local team can change. Any solution had to work within those constraints and had to be multilingual so it could roll out globally.
What we did
Mindset had already built a BTP-based master data automation solution for a different manufacturing client facing the same problem. After a discovery session where the team demoed that solution, it was clear it covered roughly 90% of what this company needed.
The team built a Master Data Upload automation on SAP BTP that handles part number creation and modification, bill-of-material creation and modification, and document info record creation and modification. The solution was designed to work within the constraints of the centrally controlled SAP instance and built with multilingual support from the start. Delivery ran over roughly five months with an offshore developer and an onshore technical architect. A follow-on change order extended the work to complete the full scope.
The outcomes
Engineering teams no longer have to create and modify SAP master data records by hand. The automation handles part numbers, BOMs, and document info records through a single process, reducing the time required and removing the risk of manual entry errors.
Because the solution was built on SAP BTP and designed around the constraints of the centrally controlled SAP instance, the company can roll it out globally without needing local SAP instance changes at each location.
If we built this today
Concept · not delivered scopeMaster data that builds 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 filtration manufacturer's engineers were hand-keying part numbers, bills of material, and document info records across MM, BOM, and DMS, slow work that an agent can now draft for them.
The data product
Cloud ERP Intelligence
It grounds the agent in the governed material, BOM, and document semantics from S/4HANA through the SAP Knowledge Graph, so proposed records match how this manufacturer actually models its parts. That keeps the drafts multilingual and consistent across a global rollout.
Intelligent Application on SAP Business Data Cloud
The Joule agent
Production Master Data Readiness Agent
It reads the engineering inputs, existing material records, and BOM and document structures, then proposes ready-to-post material masters, bills of material, and document info records with the right plant, view, and language data filled in. A person reviews and approves before anything is created.
SAP S/4HANA, SAP MM, SAP DMS, SAP BTP · PROPOSE · Engineering hours per part number, BOM, and DIR created
The Fiori app
Material and BOM maintenance apps with embedded Joule
The standard S/4HANA apps for maintaining material masters, bills of material, and document info records, with Joule sitting inside them to draft entries and catch missing fields before posting. We name the category honestly here rather than a single app, since the master-data work spans several maintenance apps.
Embedded in the Fiori launchpad
We'd mine the real MM01, CS01, and CV01N steps in SAP Signavio first, map the system constraints in SAP LeanIX, and let MIND accelerators carry the proven BTP automation pattern from the old build into the new one.
What we built
-
Manual data entry for part number creation eliminated
Part number automation (MM01/02/03)
Automated creation and modification of SAP material master records, replacing manual MM transaction entry.
-
BOM creation and modification automated end to end
Bill of material automation (CS01/02/03)
Automated creation and modification of SAP bills of material, handling the CS transaction flow without manual input.
-
DMS record creation automated alongside material and BOM flows
Document info record automation (CV01N/02N/03N)
Automated creation and modification of SAP document info records in the Document Management System.
-
No changes to the centrally controlled SAP instance required
Centrally controlled instance compatibility
Built to work within the constraints of an SAP environment controlled from a separate geography, without requiring local instance changes.
-
Deployable across the global operation
Multilingual and globally deployable design
The solution was built with multilingual support from the start so it can be rolled out to facilities across the company's global footprint.