SAP Power BI Integration
SAP Power BI Integration: One Reporting Layer for Finance, Sales and Production
A multi-plant manufacturer running SAP S/4HANA needed management reporting its people would actually use. Finance lived in Excel exports, sales waited for weekly PDFs, and production data from the shop floor never reached an SAP report at all. Natura Systems designed and delivered an SAP Power BI integration that connects S/4HANA, SAP BW and shop-floor systems to one governed Power BI semantic model — with SAP authorizations enforced, no additional load on the ERP, and data refreshed every 15 minutes where the business needed it.
Why Power BI — and Why Not Only SAP Analytics Cloud
Natura Systems delivers both SAP BW and SAP Analytics Cloud and Power BI. We recommend based on the client’s landscape, not our preference. In this case three factors pointed to Power BI:
- Licences already existed. The group was paying for Power BI Pro through Microsoft 365 and using none of it.
- Non-SAP data mattered. Around 30 % of the required KPIs came from the shop-floor historian, a CRM and a logistics provider — Power BI’s connector breadth made blending these straightforward.
- The users were already in Teams and Excel every day. Embedding reports where people work beat asking them to learn a new portal.
SAP Power BI Integration Architecture
The architecture separates the layers cleanly so that each one can change without breaking the others. Business logic stays in SAP; Power BI consumes curated, authorised data.
SAP Power BI integration architecture: SAP S/4HANA, SAP BW, on-premises gateway, semantic model and reports
Rather than exposing raw tables, we built the reporting logic inside SAP where it can be tested, transported and governed. For S/4HANA that meant analytical CDS views (extending SAP’s standard Virtual Data Model where possible) published as OData services through SAP Gateway. For finance history we reused existing BW queries. Where sub-second performance on large volumes was required, HANA calculation views did the heavy lifting.
All SAP traffic passed through a clustered on-premises data gateway with the SAP .NET connector and HANA ODBC driver installed on every node — the single most common cause of failed SAP Power BI projects is a gateway set up on one laptop. The semantic model was built as a star schema with conformed dimensions (material, customer, plant, calendar) shared across finance, sales and production so that a filter on one report means the same thing on every other.
Row-level security was derived from SAP, not maintained twice: authorisation objects for company code, plant and sales organisation were extracted nightly into a security table, and Power BI RLS roles read from it. A user who cannot see Plant 2 in SAP cannot see Plant 2 in Power BI either.
This is where an SAP consultancy with industrial automation experience makes a difference. Machine counters, downtime codes and OEE from the PLC/SCADA historian were loaded into the staging layer and joined to SAP production orders on order number and confirmation timestamp. Plant managers now see planned versus actual output, scrap by reason code and OEE per line next to the SAP order — in one report, with one definition.
- SAP first. The logic lives in CDS views, BW queries and HANA views built by SAP consultants — not reverse-engineered from tables in Power Query.
- Automation and SAP together. We connect PLC, SCADA and MES data to SAP every week; putting it next to SAP figures in Power BI is a natural extension.
- Authorisations respected. Row-level security is derived from SAP roles, so security is maintained once.
- SAP Quality Award Grand Winner. Delivery discipline recognised by SAP, applied to analytics projects.
- Türkiye and Central Asia. Local presence, English, Turkish and Russian speaking teams, and long-term ERP and BI support after go-live.
If your teams are exporting SAP data to Excel every week, or your Power BI reports run on tables nobody fully understands, we can help. Contact Natura Systems for a landscape review: we look at your SAP modules, existing BW content, Microsoft licences and shop-floor sources, and propose an integration architecture with a realistic timeline.