Introduction
The Next Generation Outline Extractor reads the outline of an Oracle Essbase cube (or an EPM Cloud/PBCS plan type) and writes it out in whichever format you need - a delimited load file for rebuilding another outline, a documentation-style spreadsheet, relational tables, or a handful of other formats described below.
Internally, every extractor reads its source into one shared, source-neutral model (the Common Outline Format) and every writer consumes that same model - so any extractor can be paired with any writer. Extracting from Essbase and writing to relational tables works the same way as extracting from PBCS and writing a CSV; the tool doesn’t need to know about that combination specifically.
The tool is used the same way whether you’re running it by hand or from a script: a graphical interface for interactive use, and a command-line interface for automation, both built on the same underlying engine.
A long history
This isn’t a new tool wearing a new coat of paint. It started life as a native Windows application written in C, was rewritten in Java some years later, and this release rewrites it again - this time onto a modern (Java 17+) foundation, built around the source-neutral Common Outline Format described above in place of one writer per source format. Three eras, one name.
| Configuration files created by a previous version of this tool are not compatible with this one - the underlying format changed along with the rewrite. Start fresh rather than reusing an old configuration file; see Getting Started to get going. |