Dimension lists in Workday Adaptive Planning grow messy over time. Values get added twice under slightly different names, parents are removed and leave orphans, and whole dimensions sit empty. Nobody notices until a report breaks, and checking each dimension by hand means opening every one in turn.

Name a dimension, or leave it blank to cover all of them, and it lists the dimensions in Workday Adaptive Planning and pulls the values for each. It flags empty dimensions, values that repeat a name or code, values whose parent is not in the same dimension, and values missing a short name or description that their siblings have. Nothing is changed. It recommends each fix instead of applying it, and it tells you when a result may have been cut short.

You get a clear list of the dimension values that need cleaning up, with nothing changed in the planning model.

Checking currency setup in Workday Adaptive Planning means comparing the currencies defined for the instance against the ones set on each organisation level, usually across two screens. A level pointing at the wrong currency, or two currencies marked as reporting, is easy to miss by eye.

Optionally name a company, and it reads the currencies defined in Workday Adaptive Planning and the currency on every level. It identifies the corporate and reporting currencies, then flags a missing or duplicate corporate or reporting currency, levels using an undefined currency, defined currencies no level uses, and unusual precision. You get a table of currencies with the levels using each one. If either read comes back empty it stops and says so rather than guessing, and it changes nothing.

Currency inconsistencies across the entity tree are listed in one report, with no guessing and no changes to the model.

Adaptive Planning returns organisation levels as flat lists with parent links, so reconstructing the entity tree means piecing it together by hand. Along the way a child with a different currency than its parent, or an elimination level in the wrong place, slips through.

Name a root level, or leave it blank for the whole tree, and it reads the levels from Workday Adaptive Planning and builds the hierarchy from the parent links. It flags currency changes between parent and child, where elimination levels sit, workflow status that differs from siblings, parents that are missing from the results, and duplicate names or codes. It stops if the root is ambiguous, never infers links the data does not show, and changes nothing.

You see the entity tree and its structural problems in one report, built only from links the data actually contains.

Analysts scroll the Workday Adaptive Planning chart of accounts by hand looking for duplicates and inconsistent settings, and they miss them. Two accounts share a code, a child differs from its siblings on balance type or rollup, and nobody sees it until a plan does not add up.

Optionally narrow by account type or part of a name, and it pulls the matching accounts from Workday Adaptive Planning. It lists the top-level accounts, then flags duplicate names or codes, empty account groups, balance type or subtype that differs from siblings, differing entry and rollup settings, and intercompany accounts. It reports only what the data shows, says if the list may be truncated, and changes nothing in the model.

Misconfigured accounts are listed with a recommended fix for each issue type, without anyone scrolling the chart by hand or touching the model.