--- title: "SAP ECC 6.0 to Microsoft Fabric Case Study | Smart Data" url: https://www.smartdata.net/case-studies/sap-ecc-microsoft-fabric-industrial description: "Smart Data brought SAP ECC 6.0 data into Microsoft Fabric for the North American arm of a global industrial engineering group, within strict extraction rules." source: "Smart Data (smartdata.net). Markdown copy of the page; the HTML page is canonical." --- # SAP ECC 6.0 to Microsoft Fabric, inside corporate guardrails Smart Data brought SAP ECC 6.0 data into Microsoft Fabric for six operating entities sharing one SAP system, working within strict corporate rules on how data leaves SAP. Built on[Microsoft Fabric](https://www.smartdata.net/services/microsoft-fabric-consulting)[SAP](https://www.smartdata.net/services/enterprise-integrations) Industry Manufacturing Engagement Data Platform The North American arm of a global industrial engineering group needed its SAP data in the group's BI platform as a foundation for business reporting. Six operating entities shared a single SAP ECC 6.0 system, and the data had to stay protected between them while every site reported against the same definitions. Working alongside the client's SAP, IT and finance teams, Smart Data built a repeatable process for extracting SAP tables, loading them into Microsoft Fabric and validating the results against the source system, all within the group's corporate BI standards and ingestion framework. ## The challenge Getting SAP data into consolidated reporting meant working inside constraints the client had already set: - Six operating entities sharing one SAP ECC 6.0 system - Sensitive data, including wages and project financials, that could not be shared freely between entities - Strict rules on how data leaves SAP: no RFC bulk extraction, and files land as CSV through the corporate ingestion framework - An existing corporate Fabric platform and BI standards the solution had to fit - Consistent definitions needed across every site ## The solution We adapted the design to the corporate BI standards and ingestion framework as the engagement progressed. ### Key implementation highlights - SAP ECC connects through the Microsoft SAP connector and its ABAP add-on, over an on-premises data gateway - Extracts land as CSV, and the corporate ingestion framework loads them into the Bronze layer - The customer master was the first table through, validated with row counts, record spot checks and a closed-period comparison against SAP after SAP authorization issues were resolved with the client's SAP team - Since phase one, the full set of SAP master data tables has been brought in the same way - Each operating entity's raw and prepared data sits in its own workspaces, with workspace-level security protecting wages, project financials and other sensitive information - A shared Gold layer is designed for consolidated reporting in the next phase - Common master data, starting with customers, is loaded once and shared through OneLake shortcuts, so every site reports against the same definitions without keeping duplicate copies - Version control, a defined path from development to production and centralized environment settings - Architecture decisions documented and reviewed with the client's IT and finance owners ## The results A validated SAP-to-Fabric process, end to end in non-production: SAP data extracted, landed, loaded and checked against the source system Extraction the SAP side was comfortable with: the client's Basis and SAP teams found the process much easier than they expected An agreed architecture the team can reuse as more sites and SAP tables are added A clear path to production: the next phase moves the data flow into production, runs the first automated deployment and delivers the first project P&L reports ## Where this is going We bring SAP data into Microsoft Fabric for organizations that have to follow strict corporate rules on how data leaves SAP. If that is your situation, talk to us about scope. Client Manufacturing and industrial Platform and technology - [Microsoft Fabric](https://www.smartdata.net/services/microsoft-fabric-consulting) - [SAP Integration](https://www.smartdata.net/services/enterprise-integrations) - Lakehouse Architecture - ETL & Data Pipelines - Data Modeling - CI/CD How it fits together ## One SAP system, six secured entities, one set of definitions SAP ECC 6.0 One system shared by six operating entities Corporate rules - **No RFC** bulk extraction - **CSV** through the corporate ingestion framework Microsoft Fabric Own workspace per entity - Entity 1Bronze - Entity 2Bronze - Entity 3Bronze - Entity 4Bronze - Entity 5Bronze - Entity 6Bronze Phase one: loaded by the corporate framework and validated Gold Shared Gold layerNext phase Customer master loaded once, shared to every entity through OneLake shortcuts Consolidated reporting Every site on the same definitions Checked against SAP Row counts Record spot checks Closed-period comparison ## Working on something similar? Tell us what you are building and what it has to connect to. Here is what happens after you reach out. ### A short call about the work What runs today, what needs to change and the date you are working toward. ### An engineer looks at what’s running Scope comes from your systems as they are, before anything is priced. ### You get a written proposal Covering scope, team, approach and price. [info@smartdata.net](mailto:info@smartdata.net)[(937) 886-9166](tel:+19378869166)