The Account dimension, and where your members survive

Four prebuilt account trees ship with the module processes, and Oracle can rewrite their formulas in updates. Where you hang custom members decides whether an update is routine or an incident.

Note: In Planning, Oracle's budgeting and forecasting module, the Account dimension is the chart the plan is written in: revenue and expense lines, drivers, and statistics. This page is how that dimension is organized and where custom members belong.

The whole module is mapped on the Planning index.

RuleCustom members in custom branches, drivers exported with the plan, and prefixed trees treated as Oracle's property.

Nevercustomize inside a prefixed rollup. Content updates overwrite Oracle's trees without checking what you added to them.

◆ Where accounts live, and whose they are, the prefixed trees, the custom branches, the drivers.

What lives where	The operating rule
Prebuilt module accounts (OFS_ Financials, OWP_ Workforce, OCX_ Capital, OPF_ Projects, OEP_ shared framework)	Each process ships its account tree, per the module reference. Treat prefixed members as Oracle's: updates can rewrite their formulas, and any customization has to be re-applied by hand afterward.
Custom members	Hang them in your own branches, never inside prefixed rollups, and never named with a reserved prefix: Oracle's naming restrictions forbid starting any object name with OEP_, OFS_, OCX_, OWP_, or OPF_. An update that rewrites OWP_ formulas has no way to know your member depended on them.
Drivers and statistics	Headcount, rates, units: non-currency accounts that feed the currency ones. Keep them in the plan, and export them with it; a driver that never leaves the cube cannot explain a variance.

In the sixty-entity world the account tree carries revenue budget 842.0M and opex 512.6M, and the drivers underneath them are what the driver report reads. The dimension design choice that matters most is not here at all: it is whether parents are stored or dynamic, and that lives on Aggregation strategy.

THE USE CASE, SIMPLIFIED

The problem: A content update rewrites prefixed formulas, and a custom member that depended on them breaks quietly.

What we build: We inventory the account tree, separate your members from Oracle's, and export the drivers nightly with the plan.

What you get: Updates stop breaking things you built, and every variance arrives with its driver beside it.

Account tree grown wild over five budget cycles?

We inventory the dimension, separate yours from Oracle's, and the next content update stops being a risk event.

Talk to us

Terms on this page

OFS_ / OWP_ / OCX_ / OPF_: Financials, Workforce, Capital, Projects prefixes. Oracle's trees.
driver: A non-currency account that feeds currency ones. Export it.
statistic: Headcount, units, rates. The explanation layer of a plan.
content update: When Oracle rewrites prefixed formulas. Plan for it.