SAP Integration Suite · HANA · BTP Governance
Manufacturing Cloud Connector Cloud Foundry SAP BTP
A global plumbing products manufacturer builds a single source of truth for employee data on SAP BTP
A Global Plumbing Products Manufacturer Delivered 2025
Mindset ran a 14-week data harmonization initiative on SAP Integration Suite, establishing standardized employee data in a centralized HANA repository, eliminating manual reconciliation, and migrating the company off a legacy NEO tenant with near-zero downtime.
By the numbers
-
14 weeks
Discovery through hypercare, end to end
-
0
Downtime on the NEO to Cloud Foundry cut-over
-
1 repository
Single HANA source of truth replacing multiple inconsistent systems
-
2 tracks
Data harmonization and BTP governance delivered in parallel
Before
Fragmented data, ungoverned BTP landscape
- Employee records split across multiple source systems with different field names, naming conventions, and completeness.
- Manual reconciliation required to align data across systems, with no single trusted source.
- BTP landscape with unused services running, unreviewed admin roles, and no centralized cost tracking.
After
Harmonized data, governed platform
- Standardized employee data in a centralized SAP HANA repository, with automated sync pipelines replacing manual reconciliation.
- Integration Suite on Cloud Foundry replacing the legacy NEO tenant, with cut-over completed at minimal downtime.
- Tighter BTP governance: unused services deactivated, admin roles reviewed, and cost tracking active.
Why this matters
Two problems solved in one engagement: a data quality issue that was undermining operational trust, and a platform governance gap that was letting costs and access drift. Running both tracks in parallel made the 14-week timeline possible.
The challenge
Employee data at this manufacturer was spread across multiple source systems, each with different field names, naming conventions, and levels of completeness. Reconciling records across those systems was a manual job, and the inconsistencies made it hard to trust what any single system was telling you.
At the same time, the company's SAP BTP environment had grown without consistent governance. Platform costs were not tracked centrally, unused services were running, and administrative roles had not been reviewed against least-privilege principles. The combination of a data quality problem and a platform governance gap made it a natural candidate for a combined initiative.
What we did
Mindset ran the engagement in two tracks delivered in parallel over 14 weeks using two-week Scrum sprints.
The data harmonization track started with a field-by-field definition of employee data standards, worked out with business and IT stakeholders across the first three weeks. From there, the team built reusable transformation logic in SAP Integration Suite on Cloud Foundry to cleanse and normalize both current and historical employee records. Harmonized data was landed in standardized SAP HANA tables as the single source of truth. Automated sync pipelines with validation, reconciliation, and error-handling were built on top, and the HRDATA application was re-developed to the new field standards. Migration from the legacy NEO tenant to Integration Suite on Cloud Foundry was executed as a phased cut-over with minimal downtime.
The BTP governance track ran alongside. Mindset created a Shared Services subaccount in the BTP landscape, migrated the HDB and IAS platform services into it, tightened subaccount administrator roles to reduce unnecessary access, and de-activated unused services to reduce cost. Mindset's Resource Consumption Tracking Tool was installed to give the team ongoing visibility into platform spend.
Delivery used daily stand-ups, weekly cadence calls, and monthly leadership reviews, tracked in Jira with documentation in Confluence and SharePoint.
The outcomes
The company finished the engagement with a single, trusted employee data repository in SAP HANA. Cross-system inconsistencies that had required manual reconciliation were resolved by the transformation logic, and automated pipelines now keep records current without human intervention.
The migration from legacy NEO to Integration Suite on Cloud Foundry completed with minimal to zero downtime. Downstream integrations that previously had to navigate inconsistent source data can now point at the standardized HANA tables, reducing the complexity of future integration work.
On the platform side, the BTP landscape is more tightly governed: unused services are off, administrative access is tighter, and the team has cost tracking in place from the Mindset tooling installed during the engagement.
If we built this today
Concept · not delivered scopeOne trusted source for employee data.
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.
When employee records live in several systems with different field names and uneven completeness, reconciling them by hand burns time and erodes trust, so this is the kind of harmonization work a Joule agent could carry now.
The data product
Harmonized Employee data product
A governed employee data product on SAP Business Data Cloud, modeled to the field-by-field standard the team defined with stakeholders. It grounds the agent in agreed meaning so harmonization stays consistent as new domains get added.
Data product on Business Data Cloud
The Joule agent
Employee Data Harmonizer
Reads inbound employee records from each source system, maps fields against a governed standard in the SAP Knowledge Graph, flags mismatched names, formats, and gaps, then proposes cleansed, normalized records for the single source of truth before they land in HANA. Built in Joule Studio, connected through A2A, with source access scoped via MCP servers.
SAP Integration Suite, SAP BTP, SAP HANA, Cloud Foundry, Cloud Connector · PROPOSE · Manual reconciliation hours and cross-system data inconsistencies
The Fiori app
SAP Integration Suite Flow Builder with Joule
This is a BTP and Integration Suite job, not an S/4HANA Fiori app, so we are honest about that. Joule rides inside the Flow Builder to draft and document the iFlows that move and transform employee data, and an iFlow Health Watcher pattern keeps an eye on the running integrations.
Lives in SAP Integration Suite on Cloud Foundry, not the Fiori launchpad.
We would mine the current reconciliation flow in SAP Signavio first, map the source systems and BTP dependencies in SAP LeanIX, then let MIND accelerators carry the old NEO logic over to the new harmonization standard.
What we built
-
Standardized employee data fields across all source systems
Employee data harmonization pipeline
Field-by-field employee data standards defined with stakeholders, then reusable transformation logic built in SAP Integration Suite to cleanse and normalize current and historical records.
-
One trusted employee data source replacing multiple inconsistent systems
Centralized HANA data repository
Harmonized employee data landed in standardized SAP HANA tables as a single source of truth, with automated sync, validation, reconciliation, and error-handling.
-
Application aligned to the new data model from day one
HRDATA application re-development
The existing HRDATA application rebuilt to the new harmonization standards so it reads from and writes to the standardized data model.
-
Cut-over completed with minimal to zero downtime
NEO to Cloud Foundry cut-over
Phased migration from the legacy NEO Integration Suite tenant to Cloud Foundry, with parallel operation and validation at each phase before the legacy tenant was retired.
-
Cleaner BTP landscape with least-privilege admin access
BTP Shared Services subaccount
A governance-aligned Shared Services subaccount created in the BTP landscape, with HDB and IAS platform services migrated into it and administrative roles tightened.
-
Platform cost visibility from go-live
Resource Consumption Tracking Tool
Mindset's BTP cost and consumption visibility tooling deployed into the landscape, giving the team ongoing platform spend tracking.