Improved demand planning process and seamless back-end migration
A live o9 Demand Planning solution transitioned from JDA source data to SAP, with a modernized cloud integration and enhanced reporting — without disrupting ongoing planning operations.
The Challenge
The organization was moving away from its legacy planning-analytics and JDA source systems as part of a broader technology transformation, which meant Demand Planning in o9 needed to shift to receiving source data from SAP instead — including a full change in leaf-level IDs for Item, Location, and Customer, while the existing o9 tenant continued to run on JDA-based data.
Our Approach
- 01
Remap master data to SAP IDs
Retained existing file structures, data mappings, and hierarchy levels while remapping master data values in o9 to SAP-aligned values across Item, Location, Key Customer, and Collaboration ID dimensions.
- 02
Modernize the integration layer
Replaced the legacy SFTP-based integration with a scalable GCP/GCS bucket-based pipeline for inbound data.
- 03
Build new dbt transformation interfaces
Introduced new inbound extracts and transformation interfaces through dbt (data build tool), loading the transformed data into GCP.
- 04
Enhance the planning UI
Added three new reports — Key Customer, Collaboration ID, and History Control — with action buttons to streamline data maintenance for planners.
The Results
Seamless JDA-to-SAP transition
Migrated critical planning master data from JDA to SAP with no disruption to ongoing planning operations.
Modernized cloud integration
Replaced legacy SFTP processes with a scalable GCP/GCS-based data pipeline.
A better planner experience
Enhanced reports and UI actions made day-to-day data maintenance faster and clearer.
Business continuity preserved
Existing planning structures and processes were preserved throughout the transition, protecting daily and weekly planning batches.