Platform: Workday Financial Management and Workday Adaptive Planning
Scope: the level hierarchy load for one reporting structure
The business problem
The loader that builds the level hierarchy in Workday Adaptive Planning stopped with an error. The message said a parent node was missing for one top level. Until the hierarchy loads, new organisations do not appear in planning, and actuals for them have nowhere to land.
Existing architecture
Levels come from Workday through a data source. A union table combines the source rows. A custom SQL column works out the parent of each level, and the loader maps that column to the parent field.
Why it happened
The named top level already existed in the model, directly under the root. So the level itself was not missing. The problem was its parent reference.
The custom SQL column gave two top levels a hardcoded parent ID. That ID did not exist among the source levels, so the loader could not resolve it. The same SQL also compared a level code against a level name, so that condition never matched the record it was written for.
Design decision
We removed the hardcoded parent. A level that sits directly under the root gets an empty parent, and every other level keeps the parent that the source gives it. We did not create a placeholder parent, because that adds a level nobody owns.
Implementation approach
1. Read the loader log and note the exact level named in the error.
2. Check whether that level exists in the model and where it sits.
3. Export the source rows and look for the parent ID the loader is asking for.
4. Read the SQL in the custom column that builds the parent.
5. Correct the SQL in a development tenant and run the loader manually.
Controls and validation
The development loader completed without errors or warnings and recorded both newly created and updated hierarchy members. We treated task success as the first control, not the final sign-off: the hierarchy, attributes, currency and version behavior still needed independent comparison with the intended model.
Outcome
The parent-reference correction restored the loader in the development environment. The available record did not establish final hierarchy acceptance or a production promotion.
Lessons learned
- A missing parent error is often about the parent reference, not the level named in the message.
- Hardcoded IDs in integration SQL break when the source structure changes.
- Take a level export before the run. An export taken after the run cannot show what the run changed.
