Building and publishing a hierarchy

Create the parent values in the natural account value set, create the tree and a tree version, then add nodes and drag the detail values under their parents. Run the audit and watch it fail on a duplicate node first, fix it, and re-run. Then activate, publish to the cube, and verify by running an account inquiry that rolls up. Audit errors are your friend. Read them literally — they name the node and the problem, and the temptation to skim past them is what turns a five-minute fix into an afternoon. Publishing takes real time on a large hierarchy, so plan for it in the cutover schedule rather than discovering it at two in the morning. And the one that belongs in the client's month-end checklist rather than in your memory: every new account added after go-live must be added to the hierarchy, or it silently vanishes from reports.…

In this module: Module 4 · Chart of Accounts and Ledger Design

1. 1What we're building
2. 2The decision you can't undo
3. 3Anatomy of a chart of accounts
4. 4Segment labels and qualifiers
5. 5Running the design workshop
6. 6Sizing segments: the arithmetic
7. 7Building value sets
8. 8Structure, instance, deployment
9. 9Loading account values
10. 10Account hierarchies and why reporting needs them
11. 11Building and publishing a hierarchy
12. 12Accounting calendars
13. 13Currency and conversion rate types
14. 14Primary, secondary, reporting: the decision tree
15. 15Building the primary ledger
16. 16Ledger options and completing the definition
17. 17Cross-validation and segment value security
18. 18What breaks
19. 19Lab briefing: Meridian Trading