Reviewing, loading and rolling back

Review the configuration summary, load it, monitor the process, and verify object by object against a checklist. Then deliberately load a flawed configuration, roll it back, and look at what the rollback does and does not remove. Then load a corrected version. Rollback is the configurator's best feature and it has limits. It will not remove objects that have since been used. So: roll back early, or not at all. Seeing what a partial rollback leaves behind is what stops you ever assuming it is a clean undo. Verify manually every time. Process success is not structural correctness — the same distinction as a green deploy that shipped the wrong build. And never run this against an environment with worker data. Plainly, without qualification.

In this module: Module 8 · Enterprise Structures Configurator

1. 1Why we built it manually first
2. 2The configurator flow
3. 3Creating legal entities and business units in ESC
4. 4Reference data sets in ESC
5. 5Reviewing, loading and rolling back
6. 6What breaks
7. 7Lab: build it fast, then find the gaps