SAP and Fabric: seamless controlling

For con­trol­ling with SAP and Fabric, the plat­form is only the start­ing point. In OneLake, SAP raw data arrives with cryptic table and column names—without KPIs, hi­er­ar­chies or plan-actual vari­anc­es. These only emerge in a technical model, and without one there is nothing to build reports on.

Bissantz closes this gap for SAP and Fabric with Bissantz ERP Solutions for SAP. Years of SAP project ex­pe­ri­ence are built into prebuilt modules that know exactly which SAP base tables to access. Con­trol­ling and finance get reliable figures without having to build the model themselves.

With Microsoft Fabric for SAP, com­pa­nies book subject modules from Bissantz in which trans­ac­tion data and KPIs are already modeled. Ac­count­ing covers the balance sheet and cost ac­count­ing, Sales covers multi-lev­el con­tri­bu­tion margin ac­count­ing, and Pro­duc­tion covers product costing. The Common Master Data module provides shared master data such as company codes and cur­ren­cies.

In Fabric, Bissantz builds a me­dal­lion ar­chi­tec­ture on this basis, all the way to the se­man­tic model. Hi­er­ar­chies are in place, and cu­mu­la­tive values and prior-year com­par­i­sons are prepared as cal­cu­la­tion groups. Con­trol­ling builds reports instead of writing DAX formulas – in DeltaMaster or Power BI.

Bissantz tailors SAP in­te­gra­tion with OneLake in Microsoft Fabric to your start­ing point. Operating model, data volume and refresh fre­quen­cy determine the ex­trac­tion method; a Bissantz as­sess­ment tool provides weighted rec­om­men­da­tions.

On-premises and private cloud systems connect the modules directly to SAP base tables, the public cloud uses CDS views. Bissantz has already mapped the old and new SAP worlds and identified the relevant ones among numerous, partly over­lap­ping CDS views.

Bissantz makes Microsoft Fabric for SAP im­me­di­ate­ly usable for con­trol­ling. In DeltaMaster, nav­i­ga­tion leads step by step from a variance to its root cause. An assistant suggests reports based on more than 600 rules, without an LLM. An AI model can be added if needed.

Planning follows the same model: enter and comment on values, allocate them according to seasonality, adopt the rolling forecast, and simulate assumptions with driver-based planning. Reporting and planning thus share a single database and a single cost accounting system.