Analytics Catalog/Oracle EPM/Planning/Smart Lists & Text
Explore the catalogPlanningLevel-0 exportApproval statusData model
Oracle EPM Cloud · Planning · Export

The words in the plan, exported as words

A plan is not only numbers: cells hold choices from Smart Lists and typed commentary, and the standard exports return IDs for one and nothing for the other. Both have routes, and both belong in the nightly pipeline.

Note: In Planning, Oracle's module where budgets and forecasts are built, some cells hold choices and words, not numbers: Smart Lists and text. Standard exports return them as numeric IDs. This page is how to get the words out.

The whole module is mapped on the Planning index.

RuleExport the Smart List mappings beside the data and translate once in the warehouse, and run the documented textual route nightly for the words.
Neverhand a file of raw Smart List IDs to a reader. A 3 that means Delayed is worse than no answer, because it looks like one.
The two problems and their routes, IDs to labels, and the textual daily-maintenance procedure.
What comes out wrongThe route to the words
Smart List cells export as numbersThe standard exports return the internal ID, a 3 where the form says Delayed. The mapping from ID to label is application metadata: export it beside the data and translate in the warehouse, once, in one place.
Text cellsOracle's own best-practice list for these applications includes an Operations Guide procedure named exporting Smart List textual data during daily maintenance for incremental data import, per the best-practices index. The daily-maintenance route exists precisely because the standard data path does not carry the words.
The plan's narrativeJustifications and commentary typed into text cells are the part auditors ask for by name. Once the textual route runs nightly, the narrative survives outside the application, searchable, beside the numbers it explains.

The same discipline the reconciliation catalog applies to comments applies here: words are data, they export on their own route, and they join the numbers in the warehouse on the same keys.

THE USE CASE, SIMPLIFIED

The problem: The export shows 3 where the form says Delayed, and the commentary auditors want is not in any file.

What we build: The Smart List mappings export beside the data, and text values come out on the documented daily-maintenance route.

What you get: Files where choices read as words, and the plan's narrative survives outside the application.

Exports full of numbers that are secretly words?
We wire the mapping translation and the textual route into the nightly pipeline, and the plan's choices and commentary read as language everywhere downstream.
Talk to us
Terms on this page
Smart List
A pick-list cell. Stored as an ID, meant as a word.
the mapping
ID to label, exported beside the data, translated once.
the textual route
The documented daily-maintenance procedure for text.
narrative
The typed commentary auditors ask for by name.