Period and Years, steered by variables

Two dimensions carry time so a rolling forecast can roll. The member names matter less than the substitution variables that point at them, because the variables are what everything reads.

Note: In Planning, Oracle's budgeting and forecasting module, time is split across two dimensions, Period and Years, and steered by substitution variables. This page is how the split works and why the variables matter more than the members.

The whole module is mapped on the Planning index.

RuleVariables everywhere time appears, a written month-roll checklist, and exports that resolve variables into plain Year and Period columns.

Neverhard-code a year in a form or rule. It works until the year changes, then someone spends a morning finding it.

◆ The split and the steering wheel, years, periods, variables, and the month roll.

Time splits across two dimensions: Years holds FY25, FY26, FY27, and Period holds the months and quarters inside a year. The split is what makes a rolling forecast possible, and substitution variables steer it: Oracle's own Workforce doc has rules reading &CurYr and &CurMnth to know where now is, per the synchronize doc. Change the variable and every form, rule, and report that references it moves together. Hard-code a year anywhere and that object breaks when the year changes.

The habit	Why
Variables in every form and rule	One place moves the whole application forward a month.
The month-roll checklist	Update the variables, run the copies, verify one form. The June forecast update in the sample world, landing at 851.4M, is exactly this checklist and nothing more.
Exports carry Year and Period as columns	The warehouse does not know what &CurMnth means; the export resolves it, per the level-0 export page.

THE USE CASE, SIMPLIFIED

The problem: The month roll depends on one administrator's memory, and exports break when the variables move.

What we build: We script the roll, and the export resolves substitution variables into literal Year and Period columns before landing.

What you get: The first Tuesday of the month takes minutes, and your warehouse never sees a variable name.

Month-roll still a ritual only one admin knows?

We script the roll, wire the export to resolve the variables, and the first Tuesday of the month stops depending on one person's memory.

Talk to us

Terms on this page

&CurYr / &CurMnth: The variables Oracle's own rules read for now.
the split: Years for FY, Period for months. Rolling needs both.
month roll: Variables, copies, one verification form. Scripted.
resolution: Exports turn variables into literal columns.