Enterprise SCM & Sales Reporting

We unified chaotic SAP BW queries and manual Excel mappings into a scalable Power BI framework for a global Tier-1 automotive supplier — giving plant managers a single source of truth for daily run-rates, margins, and order books.

The mess

Operations was drowning in data silos. Supply chain and sales teams tracked daily run-rates, margins, and order books using disjointed SAP BW queries — specifically the P9A system — taped together with manual Excel mappings. Every stakeholder wanted a different view. Top management needed plant summaries. SCM wanted real-time order books. Business development needed loss-maker analysis. Nobody agreed on the numbers because everyone pulled from different extracts at different times.

The end-of-month cycle was brutal. Someone spent three days manually reconciling SAP exports in Excel to produce a report already outdated by the time it landed.

What we did

We didn’t just build a dashboard — we built a reporting framework. Started with requirement gathering across three stakeholder groups (top management, SCM, business development) who each had conflicting priorities and different metric definitions.

Then we engineered a pipeline that married SAP BW data with complex offline mapping rules that previously lived in someone’s personal Excel files. Those mapping files were the bottleneck — undocumented, version-confused, maintained by one person who happened to know where they were saved.

We moved the mapping logic into the pipeline, version-controlled and testable. Built a Power BI suite on top: daily sales tracking, real-time order book monitoring, margin analysis, loss-maker reports.

The result

Single source of truth. Monthly Excel grind eliminated. Daily tracking on autopilot. Margin anomalies caught the same day instead of three weeks later.

The turning point of the project was finally locating the “master mapping logic” that governed the global supply chain. It wasn’t in SAP. It was a 40MB file named Mapping_Final_v6_DO_NOT_TOUCH.xlsx sitting on the local desktop of a controller who was going on a three-week vacation. Moving that fragile file into a version-controlled, automated pipeline wasn’t just a technical upgrade — it was a rescue mission.