A metaoutline has several components:
One or more measures. Measures are data values and typically include items such as SALES and COGS (cost of goods sold). Every metaoutline used to build an Essbase outline requires at least one measure.
The Essbase database calculates the measures for each dimension intersection of the associated metaoutline. Measures can be aggregated in a pre-defined order using an SQL expression. The SQL expression uses an SQL template and a list of specified columns, attributes, and measures.
Two or more dimensions. A dimension is a data category, containing members, used to organize business data for retrieval and preservation of data values.
A dimension in a metaoutline creates a dimension in the associated Essbase outline. Every metaoutline used to create an Essbase outline must include at least two dimensions.
One or more member levels. A member level is a hierarchical level of detail within a dimension. A member level in a metaoutline creates members at the same level in the associated Essbase outline.
For example, if the Product dimension of a metaoutline contains a PRODUCT_DESC member level, the Product dimension in the Essbase outline contains members, such as Birch Beer and Caffeine Free Cola, that correspond to values in the PRODUCT_DESC member level in the source database.
You can designate user-defined members as shared members. They can share storage space with other members of the same name.
Filters. Filters determine which members of a member level that Integration Services adds to the associated Essbase outline. You can define transformation rules to determine what transformations Integration Services performs on the members of a member level as it builds the Essbase outline.
Optional attribute dimensions. Attribute dimensions are based on attribute-enabled columns in the OLAP model. After an attribute dimension and member are created, you can define attribute properties, such as Boolean and numeric ranges, to view business data in finer detail than would otherwise be easily available.
Optional Hybrid Analysis low-level members. Hybrid Analysis integrates source databases with Essbase multidimensional databases so that applications and reporting tools can directly retrieve data within both databases. When Hybrid Analysis is enabled, users of spreadsheets and report writer interfaces can access data contained in the Essbase database and drill down to data accessed directly from the data source.
Optional drill-through report members. A drill-through report is based on an intersection level (member combination) that spreadsheet users double-click to start drill-through operations. Spreadsheet users can view or customize pre-defined drill-through reports that retrieve detail columns from data sources. Integration Server returns the drill-through report in the context of the data that spreadsheet users are viewing.
Drill-through report to a URL. Customize the drill-through SQL template, replacing the data source with an HTML source. Integration Services passes the URL to Oracle Essbase Spreadsheet Add-in or Oracle Hyperion Smart View for Office, Fusion Edition (or another drill-through client).
Drill-through report to attributes and members enabled for Hybrid Analysis. Select from several options for attribute drill-through reporting: