On the bridge between SAP and Kinaxis, the planning master data that the ERP lacks (hierarchies, mappings, rules, preferences) is maintained in a collaborative app, and every data gap the checks find is routed to its owner in a data-driven app before it stops the plan.
Up to 70 percent of a planning implementation's cost went into data integration and transformation, and data gaps were found in the planning system after the load.
Two apps sit on the bridge. A planning master data app, collaborative, with levels for planners, the centre of excellence and IT, maintains the hierarchies, mappings, rules and preferences the ERP has nowhere to keep. A data-quality remediation app, data-driven, receives every row that fails a check before the load, routes it to its owner with the fix options, writes the correction back through the ERP's interface and re-runs the check.
Catalogue entries that match the apps in this story.
The checks run before each load; each failing row is an instance owned by the steward of its domain; corrections are written back and the check re-runs within seconds; the board shows the plan's readiness by domain.
Data owners correct rows in the app with the check re-run at once.
Hierarchies, rules and preferences maintained with levels, versions and a log.
70 percent lower against the legacy approach; 8 to 10 weeks to first load.
Slot for the customer’s own words: supplied and approved by the reference contact before publication. The story above is written in Lima’s voice from the engagement material; the customer’s feedback goes here in theirs.
Route the gaps to owners from the first load; the remediation app is the difference between a planning system that is trusted and one that is worked around.
Under NDA, with the account owner's approval, we arrange a conversation with a customer whose processes resemble yours.
