01 / Inside the engagement
Situation
An enterprise ERP program put the SAP HANA reporting environment under a change freeze. Existing reports would keep running, but no model could change and nothing new could be built at the source. Factory dashboards, finance tracking and downstream Power BI and Power Apps all depended on those models.
Before
- SAP HANA models
- Change freeze
- Existing reports still running
After
- Critical HANA models
- Databricks daily refresh
- Changeable reporting
Simplified workflow. The case text describes the contribution, delivery stage and evidence.
Explore the full conceptual diagram
02 / Inside the engagement
What UTIS did
- Before the freeze, identified the 30 business-critical HANA models out of 50.
- Enabled them in Databricks with automated daily refresh, and automated a manual inbound-delivery lookup-and-notify workflow along the way.
- A second UTIS engineer delivered a separate report change ahead of the freeze date, avoiding the change-board delay.
03 / Inside the engagement
Results
- 30 of 50 models live in Databricks and refreshing daily.
- The business kept modifying and extending its reporting throughout the freeze instead of waiting a year.
Why it matters to you
A source-system freeze does not have to freeze the business. A refreshed reporting layer with a clear boundary around the models it covers keeps the essential reporting moving while the ERP program runs.
Stack
How we measured it: model count and refresh status on the platform.