The level-0 export, tuned and explained

Everything this catalog builds stands on one nightly file: the plan at leaf grain, in columns, on a schedule. Two routes exist, and the difference between them is measured in hours.

Note: In Planning, Oracle's module where budgets and forecasts are built, plan data lives in cubes, and getting it out nightly at the leaf grain is the foundation everything else on this catalog stands on. This page is the export done right, command by command.

The whole module is mapped on the Planning index.

RuleExport by DATAEXPORT at level 0, dynamic members off, columnar and relational, scheduled through exportData, and gated on landing.

Neverexport dynamic members by accident. The run slows drastically, and the numbers were computable from level 0 anyway.

◆ The two routes, the job command and the tuned rule, with the measured difference.

Route	What it is
Export Data job + exportData	Define an Export Data job in the application, then run epmautomate exportData JOB_NAME file.zip on a schedule, per Oracle's command reference. The file lands in the download location and the Inbox/Outbox. Simple, supported, and slow at scale.
DATAEXPORT in a rule	A business rule writes a delimited file to the Inbox/Outbox with full control over scope and options. A measured field case cut a one-hour-forty-five-minute job export to fifteen seconds with a tuned DATAEXPORT and a FIX. Control is the whole difference.

◆ The options block, line by line, level-0 blocks against members, dynamic off, and the columnar shape.

The options block that does the work, from the practitioner reference:

SET DATAEXPORTOPTIONS {
  DataExportLevel LEVEL0;
  DataExportDynamicCalc OFF;
  DataExportNonExistingBlocks OFF;
  DataExportColFormat ON;
  DataExportRelationalFile ON;
  DataExportOverwriteFile ON;
};
FIX (@Relative("Account",0), @Relative("Entity",0),
     "OEP_Working", {scenario}, {year})
  DATAEXPORT "File" "," "/u03/inbox/data/plan_level0.txt" "#";
ENDFIX

Three lines deserve explanation. DataExportLevel LEVEL0 exports level-0 blocks, not level-0 members: stored members in dense dimensions come along unless the FIX restricts to level 0 there too, which is the most common reason an export is bigger than expected. DataExportDynamicCalc OFF matters because exporting dynamic members drastically slows the run. And RelationalFile with ColFormat produces the columnar shape a warehouse loads directly, with Year and Period as plain columns, the resolution the time page requires.

THE USE CASE, SIMPLIFIED

The problem: The nightly export takes two hours, or fails quietly, or exports totals nobody can reload.

What we build: A tuned DATAEXPORT at level 0, dynamic members off, wired through EPM Automate on a schedule, landing gated in your warehouse.

What you get: A fifteen-minute nightly file at the leaf grain, reloadable, and every downstream report reads from it.

Nightly export measured in hours?

We tune the DATAEXPORT, wire the schedule, and gate the landing, and the file that everything reads arrives in minutes, every night.

Talk to us

Terms on this page

level-0 blocks: What LEVEL0 actually exports. FIX the dense dimensions too.
DataExportDynamicCalc OFF: Dynamic members recompute at export. Off, always.
RelationalFile: The columnar shape a warehouse loads directly.
exportData: The EPM Automate command that runs the defined job on schedule.