Glossary

Analysis role in Integrated Operational Planning with a typical workflow of using the Administration Workbench to perform administrative tasks.

Analysis role in Integrated Operational Planning with a typical workflow of creating scenarios to perform an analysis.

Analysis role in Integrated Operational Planning with a typical workflow of approving proposed plan changes developed as the result of an analysis.

Analysis role in Integrated Operational Planning with a typical workflow of monitoring exceptions in the base data and assigning new exceptions for users to investigate on their home page.

A configured business rule or threshold.

A block of data that contains three or more dimensions.

An XML file that defines the dimensions in a cube, the names of measures in the cube and measure formulas, the names of row sources mapped to the cube, and cube-to-cube mapping information.

Analysis role in Integrated Operational Planning with a typical workflow of receiving e-mailed report workbooks and providing updated report data.

A relational table in the Integrated Operational Planning database where copies of external modeling data are stored.

An XML file that defines what data source columns to use.

In block storage databases, a dimension likely to contain data for every combination of dimension members.

A data category used to organize business data for retrieval and preservation of values. Dimensions usually contain hierarchies of related members grouped within them.

An XML file that defines the namespace name, hierarchy names, and hierarchy level names for a dimension.

Values that satisfy predefined conditions. You can define formatting indicators or notify subscribing users when exceptions are generated.

Original source of data to load in to Integrated Operational Planning.

A language comprising a set of tags used to assign attributes to data that can be interpreted between applications according to a schema.

The organization of multidimensional dimension members in an outline.

Data in Integrated Operational Planning used in what-if scenarios.

A file that contains a list of isadmin commands. To execute this file, enter isadmin –u admin –p password –f <isa file with full path>.

A client-side command-line tool that interacts with the Integrated Operational Planning server.

A driver behind the underlying planning model. Similar to a key metric in the sense that it represents intersections in a cube; however, a key assumption represents a driver behind the planning model while a key metric represent the results from the planning model. Examples of key assumptions include future prices, inflation, currency exchange rates, and labor rates.

One or more intersections in a cube that are of significant business interest. .

Component that stages and loads to data sources, row sources, and cube cells.

The language that gives instructions to OLE DB for OLAP- compliant databases, as SQL is used for relational databases.

A dimension whose members are the measures calculated in an analysis.

A mapping that matches dimension member names to internal system IDs.

Analysis role in Integrated Operational Planning with a typical workflow of collaborating on an analysis to review scenarios and providing comments to the analysis owner.

A predefined Excel workbook used in what-if analysis.

A subset of modeling data in the Integrated Operational Planning database.

A process by which open scenarios resolve their changes with new changes submitted to the baseline. A new baseline is started and the changes for each scenario are reapplied.

A predefined Excel worksheet that uses tabular reports and charts to display data in the Integrated Operational Planning database.

A relational table in the Integrated Operational Planning database that contains data values.

An XML file that defines the columns in a row source and the parent-child relationships between row sources.

Uses SQL to return row source data. Row source data is transactional, component-level data loaded into relational tables in the Integrated Operational Planning database from an execution database.

Internal and external data structures that support the ability to do changes in isolation for different users.

Commands invoked to perform specific activities in Integrated Operational Planning.

In block storage databases, a dimension unlikely to contain data for all member combinations when compared to other dimensions.

An XML file that maps data sources to row sources or dimensions in the Integrated Operational Planning database.

Forecast data generated with ForecastPro and displayed in Oracle Integrated Operational Planning, Fusion Edition.

The action of saving/committing data to the data base.

See Extensible Markup Language.