Designing Cubes

This chapter provides an overview of cube design and components and discusses how to:

Design a cube.
Design cube definitions.
Design attribute names.

Understanding Cube Design and Components

Before using PeopleSoft Cube Manager, you should define the specific goals and results that you expect from online data analysis. After defining your goals, you should design the PeopleSoft trees and queries that are appropriate for creating both the structure and the data of the cube that you plan to build. These trees and queries supply data from your PeopleSoft application to any cubes that you create. After you establish your goals and create the necessary trees and queries upon which the resulting cube will be built, use PeopleSoft Cube Manager to begin designing a cube.

See Designing Cube Metadata.

Many different kinds of components comprise the cubes that you build with PeopleSoft Cube Manager:

Dimensions	The most basic component of a cube is a dimension. When you create a dimension, you specify the PeopleSoft metadata to be used to create the dimension’s rollup structure. PeopleSoft Cube Manager dimensions are platform-independent; you can reuse them again and again to build different cubes. See Understanding Cubes.
Attributes	Dimension members may have various attributes associated with them. For example, if you have a product dimension, you might want to add color as an attribute of the actual product.
Level Attributes	Not Used.
Cube Definitions	A cube definition defines the basic structure of a cube. You select the dimensions and measures that make up the cube and the data source queries that populate the members and cube cells with data. Like dimensions, cube definitions are platform-independent and reusable.
Cube Instance Definitions	Cube instance definitions are platform-specific. In a cube instance definition, you specify the platform for which the cube will be built and choose the cube definition on which the cube will be based. You then set various other options that are specific to the chosen platform.
Filters	You use filters on the cube instance definition to limit the contents of the cube that you are building. Filters enable you to use a single cube definition when building different data marts. For example, you might define the rules for building a generic profitability cube, but give each region in your company a cube with its own information. Filters enable you to specify the subset of the possible cube data to be contained in a specific cube.
Platform Options	Each of the Online Analytical Processing (OLAP) target databases has an associated set of options with which PeopleSoft Cube Manager controls how the cube is built. These options can provide PeopleSoft Cube Manager with any required security information or information on how to allocate database space for dimensions in the cube.
Bookmarks	Bookmarks identify a set of facts in the cube. You use them to determine whether facts are being loaded for the first time or reloaded. PeopleSoft Cube Manager uses bookmarks to ensure that facts are not counted twice when they are reloaded into a cube.
Run Control IDs	When you have defined your dimensions, cube definition, and cube instance definition, you are ready to start the build process. PeopleSoft Process Scheduler runs this process and—as with all PeopleSoft Process Scheduler processes—you create a run control ID that defines the specifics of the process: Specify which cube instance definition you want to use to build the cube. Choose whether the build process is to create a new cube or to update an existing one. Specify a post-build script to run on the cube. Define any query bind variables that you want to use to limit the data source queries during the build.
Cube Instance	A cube instance is the output of the PeopleSoft Cube Manager. It is a physical cube that is built by the Cube Builder process in Cognos PowerPlay or Hyperion Essbase.

Designing a Cube

This section discusses how to:

Define the dimensional structures of the cube.
Define dimension options.
Define rollup options.
Specify the source of the metadata for each rollup.
Map fields to a role in the rollup.

Pages Used to Design a Cube

Page Name	Object Name	Navigation	Usage
Dimension	DIMENSION	PeopleTools, Cube Manager, Dimensions, Dimension	Define the structure of each dimension. Define the PowerPlay time dimension.
Dimension Options	DIM_OPTIONS	Click the Dimension Options link on the Dimension page. Click the Dimension Options link on the Rollup Inputs page.	Name blank members of a hierarchy so that you can see them in your cube.
Rollup Options	DIM_ROLLUP_OPTIONS	Click the Rollup Options link on the Dimension page. Click the Rollup Options link on the Rollup Inputs page.	Name blank members of a hierarchy so that you can see them in your cube.
Rollup Inputs	DIM_ROLLUP_INPUTS	PeopleTools, Cube Manager, Dimensions, Dimension, Rollup Inputs	Define the source of the metadata for each rollup.
Dim Input Field	DIM_INPUT_FLD	Click the Field Map link on the Rollup Inputs page.	Map the fields to a role in the rollup.

Defining the Dimensional Structures of the Cube

Access the Dimension page.

Dimension ID

Identifies the dimension of the target OLAP database.

Note. You cannot rename or delete a dimension ID after you have saved it.

Description

Appears by default to the dimension, but you can provide another description. This is used as the description of the dimension in the resulting cube.

Dimension Options

See Defining Dimension Options.

Dim Type (dimension type)

Select one of the following dimension types:

Standard: Select for every kind of dimension that does not contain account, time, currency, or country data. You can have many standard dimensions in each cube.

Account: Select if the dimension is based on account information. You can have only one account dimension for each cube.

Time: Select if the dimension is time-based. You can have only one time dimension for each cube.

Currency Partition: Valid only for Hyperion Essbase. Select if the dimension is based on currency. You can have only one currency dimension for each cube.

Country: Valid only for Hyperion Essbase. Select if the dimension is based on countries. You can have only one country dimension in each cube.

See your Hyperion Essbase documentation.

Rollup Name

The default rollup name is based on the dimension ID. You can change the rollup name, but the name cannot be identical to the dimension ID.

The rollup name becomes the top node of the dimension if you specify more than one rollup in the dimension. If you have multiple rollups, rolling up to a single top node, this name is used only for the alternate rollups. A node is created for each rollup as a child of the dimension’s top node.

Rollup Options

See Defining Rollup Options.

Level Name (All Platforms)

(Required) If you want to explicitly define level names in the rollup, specify them in the Rollup Levels group box. Level names defined in this manner override the level names that might be returned from the tree or any names that PeopleSoft Cube Manager creates as defaults. You are required to specify levels to be used in mapping wide queries or for defining aggregates.

When you enter multiple level names, PeopleSoft Cube Manager assigns a level number to the declared level name in the order in which the level name is entered. This number also populates the Dim Input Field page.

Designing a Dimension

The structure of a dimension is based on a PeopleSoft tree that you build, but dimensions can also be based on queries. You must create one dimension definition for each dimension of your cube.

Because dimensions are independent of cubes, you can use them in any number of cube definitions. Where possible (such as in star schemas), PeopleSoft Cube Manager creates dimensions that can be shared across conforming dimensions (unless the underlying data relies on different business units). This method ensures consistent results across different data marts.

To design a dimension:

Access the Dimension page.
Select the Add a New Value tab.
Enter a value for the Dimension/Measure/Attribute field, and click the Add button.

You must provide a unique name for each dimension that you define. The dimension ID uniquely identifies the dimension of the target OLAP database. After you enter a dimension ID, the Dimension page appears.

Warning! After you create and save a dimension ID, you cannot rename or delete it. You can change the description, but you cannot remove the ID from the system.
Enter a description and specify the dimension type.
Set additional parameters for the dimension by clicking the Dimension Options link.

The Dimension Options page appears.
Enter the dimension options, and click OK.
Define the rollups for the dimension.
Define the level name or names.
Define additional rollup parameters by clicking the Rollup Options link.

The Rollup Options page appears.
Define the sources of the rollup structure and attributes by selecting the Rollup Inputs tab.

The Rollup Inputs page appears. The Rollups scroll area on the Dimension page determines which rollup appears on the Rollup Inputs page.

Defining PowerPlay Time Dimensions

For a PowerPlay time dimension, you do not need to set a tree or query as an input source. Instead, you must do the following:

Identify the dimension as time.
Define the levels.
Set the corresponding date formats and date functions on the Dimension page.
Select the earliest date and latest date for the time dimension by using the Cognos PowerPlay options.

See Defining Cube Settings for Cognos PowerPlay.

See your Cognos PowerPlay Transformer documentation.

If you are creating a time dimension specifically for another platform, you should build the dimension as you would any other dimension, ignoring the Date Function and Format columns on the Dimension page. If you create a dimension that has both input source and the Cognos PowerPlay options, you can use it on any platform. PeopleSoft Cube Manager ignores the unnecessary information for the specific platform and uses only what is required on that platform.

To define a PowerPlay time dimension:

On the Dimension page, specify Time as the dimension type.

This value also sets the DimType in the .mdl file to Date when the cube is finally built, enabling the cube to use the Cognos PowerPlay date wizard.

Note. When building PowerPlay time dimensions, you are not required to complete the fields on the Dimensions - Rollup Inputs page or the Rollup Options page (prefix and suffix information for node and details). However, if you want to build a time definition for a platform-independent cube, you should still specify them. PeopleSoft Cube Manager ignores the input source while building a Cognos PowerPlay cube, even if you specify the source.
Identify each level name with a date function.

When you create a Cognos PowerPlay cube, the levels in the hierarchy must be identified by one of the following date functions. The cube build process ignores this information if the cube is intended for another platform.

Date Functions

None

Year

LunarYear

Quarter

LunarQuarter

Month

LunarMonth

LunarMonth445

LunarMonth454

LunarMonth544

Week

Day

Note. Do not mix lunar calendar and standard calendar in the Date Function column when setting levels. If you want to use both calendars, create two different time dimensions—one for the lunar calendar and one for the standard calendar.

Date Functions
None
Year
LunarYear
Quarter
LunarQuarter
Month
LunarMonth
LunarMonth445
LunarMonth454
LunarMonth544
Week
Day

Identify each level name with a date format.

Specify the format—in which you want to see a year, quarter, month, and so on—from the following available formats:

Format	Description	Comments
YY	Two-digit year	01
YYYY	Four-digit year	2001
Q	One-digit quarter indicator	1
MM	Two-digit month	01
MMM	Abbreviated month name	Jan
MMMM	Full name of month	January
DD	Two-digit day	01
DDDD	Day of week	Sunday
/, –, or space character	Separator characters	01/01/2001, 01-01-2001
Any quoted string	The quoted string	AD displays the abbreviation AD

Select the earliest and latest date options on the Cognos PowerPlay Options page.

These settings are optional. The default values are 1901-01-01 for the Earliest Date and 2100-12-31 for the Latest Date. The Current Date option is controlled by settings in Cognos PowerPlay. The As of Date option instructs the system to use the As of Date that is specified on the run control page.
Set up a fact query to return the lowest level of detail.

Defining Dimension Options

Access the Dimension Options page.

Not all data in the cube is associated with every dimension. For example, some data might be related to an account, but not to a product. In that case, the product dimension has blank members for that data . This means that there is an additional implied valid value of the product dimension that might not be on the product tree—blank (or No Product). You must provide a name to this blank member and make sure that it is on your dimension hierarchy because every valid member of a dimension must have a unique, non-blank name.

You can either add the unique, non-blank name to your tree or query and then specify it in the Dimension Options page, or just enter a name and let the Cube Builder add it to your dimension for you. Then, when the PeopleSoft Cube Manager is building the cube, it creates a new node directly off the top node of the dimension with the blank member name that you specify. All blank members are grouped under this node name for this dimension. However, the blank member’s name does not accumulate cube data into a single-dimension member.

Blank Member

The default name is based on the dimension name. Enter a name for each dimension that might have data that is not already associated with a named hierarchy.

The default value is a name based on the dimension name that you create. Change it if necessary. However, keep in mind that different dimensions within a single cube must have unique names for blank members. Thus, if a cube has a Department dimension and a Product dimension, and both of these dimensions have blank members, the blank member names must be different—for example, [No DEPARTMENT] and [No PRODUCT].

Some dimensions, such as the Time dimension, may not have blank members. If you’re sure that a dimension falls into this category, you can delete the default blank member value and leave the field blank. If you do this and a blank member is found in the dimension, it is excluded from the dimension.

Note. Your blank member name can match a node or detail value elsewhere in the cube structure. This enables you to insert blank members at a level other than directly below the current dimension.

Label Prefix/Suffix

(Required) The default value is None.

Both Hyperion Essbase and Cognos PowerPlay require unique member names and labels. You can apply a unique prefix or suffix to each member label to fulfill this requirement. To do so, select either the Prefix or Suffix option from the Label Prefix/Suffix drop-down list box. To bypass this option, select None.

Defining Rollup Options

Access the Rollup Options page.

Type

In the Node Prefix/Suffix group box, set prefix and suffix preferences at the node level. You can choose between Prefix, Suffix, or None. The prefix or suffix that you specify is applied to all members in the rollup, except the lowest level members, providing a convenient mechanism for ensuring that all node members have unique names between rollups.

In the Detail Prefix/Suffix group box, set prefix and suffix preferences at the detail level. As with nodes, choose Prefix, Suffix, or None. This value is valid only in the first rollup of the dimension.

Style

Choose to give your prefix or suffix no style, a custom style, or a dimension or level name. If you select Dimension or Level, the text is either the name of the dimension in the Description field on the Dimension page, or the level name that you specified in the Rollup Levels section on the Dimension page.

Text

Enter the text to be used for the prefix or suffix, if applicable. This field is only editable if you have given your prefix or suffix a custom style.

Specifying the Source of the Metadata for Each Rollup

Access the Rollup Inputs page.

Src Type (source type)

(Required) Select one from the following options:

Calendar: This option is not yet implemented, but will enable you to use PeopleSoft Calendar.

Level Attr (level attribute): Not used.

Query: Specify how the hierarchical relationships, as well as member attributes, are defined.

Security: Not used.

Tree: Specify how the hierarchical relationships, as well as member attributes, are defined.

Note. PeopleSoft Cube Manager currently supports only trees that are keyed by setID or no additional key. For example, PeopleSoft Cube Manager does not support Business Unit (BU) or User Defined Node Key (UKV) trees.

Input Name

Enter the name of the tree or query to be used to define the dimension.

Click the Lookup Input Name button to search for existing input names.

Top Node

Prepopulated with the top node from the tree based on the input name that you selected.

Click the Lookup Top Node button to search for the existing top node.

Levels From Top

Specify the number of levels from the top node (including the top node) to the stop level that corresponds to the lowest level of the tree to be included in the rollup. See the example in this section.

Click the Lookup Levels From Top button to search for existing levels from the top node.

Field Map

Available only when the source type is a query.

See Mapping Fields to a Role in the Rollup.

Mapped

This check box is selected when the input name is mapped; if the field is not mapped, the check box is clear. Map the field by using the Field Map link.

Defining the Levels From Top Example

Use the following example for calculating the number of Levels from Top:

Definition	Description
Source Input	QE_PERS_DATA tree
Top Node	10100 Office of President
Top Node Level	Company
Stop Level	Department

Top Node Level

The Stop Level is Department, so the Levels From Top value is calculated by counting the number of levels from Company (1) to Department. Using the following list of levels, the Levels From Top value equals three.

Example of organization levels for calculating Levels from Top

Adding Rollup Inputs

After you have defined the high-level dimensional metadata (identifying the dimension name, defining the number of different rollups, defining prefix and suffix options, and so on), the next step is to define the source of each rollup’s metadata.

If there are multiple rollups for an Essbase dimension, only the total from the first rollup for the dimension is aggregated to the dimension total.

Note. Rollup level names that you enter on the Rollup Inputs page appear in a Hyperion Essbase cube only if the cube contains a dimension with a multiple rollup. Rollup level names are always used in Cognos PowerPlay.

To add rollup inputs:

Access the Rollup Inputs page.
Define cube inputs, such as queries or trees, and their associated field mappings.
In the Src Type field, select the source input.
In the Input Name field, click the Lookup button to display and select from the valid values.
If you selected the Tree option as the source type, specify a value for the Top Node field by clicking the Lookup button and specifying a valid value.
If you selected the Tree option as the source type, select a value for the Levels from Top field by clicking the Lookup button and selecting a valid value from the list.
If you selected the Query option as the source type, define how each field in the result set is used in the rollup.

Mapping Fields to a Role in the Rollup

Access the Dim Input Field page.

Query Fld Name (query field name)

Value is based on the query’s column names.

Role

Select one from the following options:

Attribute: If you select the Attribute option, you must also select the attribute name.

Class ID: Not implemented.

Member: If all sources are members, select the level name.

Parent: If a parent exists, you cannot select level names or numbers. The parent is the top of the dimension, and the member is the child of the parent.

Level Name

Click the field to display a list of valid level names, and select one of the names that is specified on the Dimension page.

This field is available only if all roles are set to Member.

Seq

Automatically assigned to the level name when the level name is declared on the Dimension page.

Attribute Name

This field is available only if the Role field is set to Attribute.

Add to or change the values that are available in the drop-down list box on the Attribute Name page.

Mapping Fields to a Role

Now that you have created the high-level rollup information, you must map each of the fields in the query-based rollup inputs to a role.

To add Dim Input Field (dimension input field) maps:

Access the Dim Input Field page to define the fields that you want to map from the input to the cube.

The Dim Input Field page appears with the source query fields already completed.
In the Input Field Map group box, specify the fields, roles, levels, and attributes of the cube dimension.

Note. Use unique attribute names when configuring a dimension with multiple attributes. If you duplicate a name, PeopleSoft Cube Manager only populates the first instance.
Click the OK button to save your changes, or the Cancel button to exit the page without saving changes.

Designing Cube Definitions

This section discusses how to:

Map data sources to dimensions and select dimensions for the cube.
Add cube inputs to a cube definition.
Map source query fields to cube components.

Pages Used to Design Cube Definitions

Page Name	Object Name	Navigation	Usage
Cube Definition	CUBE_DEF	PeopleTools, Cube Manager, Cube Definitions, Cube Definition	Map data sources to any dimension that you have defined using the Dimension page, and select which dimensions are used in the cube.
Cube Inputs	CUBE_DEF_INPUTS	Cube Manager, Cube Definitions, Cube Definition, Cube Inputs	Add cube inputs to your cube definition.
Cube Input Field	CUBE_INPUT_FLD	Click the Field Map button on the Cube Inputs page.	Map the fields of the source query to the appropriate cube components to associate the data from the source query to a dimension. The cube inputs are the source values for the facts to be created in the OLAP database.

Mapping Data Sources to Dimensions and Selecting Dimensions for the Cube

Access the Cube Definition page.

Description

Enter the description that you want to associate with the cube. The description is not transferred to the resulting cube definition; it is used for prompting within PeopleSoft Cube Manager only.

Long Description

Enter the long description that you want to associate with the cube. This description is not transferred to the resulting cube definition; it is used for prompting within PeopleSoft Cube Manager only.

Role

(Required) Select one from the following options:

Cube Attribute: Select this option if the component is an attribute. A cube attribute is a field that can be included in the fact table for external processing. The Bookmark field on the fact table is an example of a cube attribute. You cannot use this bookmark in analysis, but PeopleSoft Cube Manager uses it to manage facts.

Dimension: Select this option if the component is a dimension.

Measure: Select this option if the component is a measure or fact.

Dimension/Measure/Attribute

Specify the dimension, measure, or attribute that you want to associate with the cube.

Click the Open button to display the Cube Input Field page.

This button is available only if you selected the Dimension option in the Dimension/Measure/Attribute field.

Dim Type (dimension type)

This field is read-only. If you selected the Dimension option in the Dimension/Measure/Attribute field, PeopleSoft Cube Manager displays the value that you entered for the Dim Type field on the Dimension page.

Status

This field is read-only. The value that PeopleSoft Cube Manager displays is based on the information that you entered on the Dim Input Field page.

Designing a Cube Definition

After creating data source queries and defining the dimensions, you must define a cube definition by mapping fields from the data source queries to the dimensions you have defined. For each dimension, you must specify which field in the data source query is the source field for the dimension. You must define the dimensions, measures, and attributes that PeopleSoft Cube Manager uses to pull data into the cube that you are defining. When you define a component, its dimension and rollup types appear, as well as the mapped status.

To design a cube definition:

Select PeopleTools, Cube Manager, Cube Definitions, Cube Definition.
Select the Add a New Value tab.
Enter a cube definition ID, and click the Add button.

Provide a unique name for each cube definition that you define. After you enter a cube definition ID, the Cube Definition page appears.
Enter a description and a long description for the cube definition.
In the Components section, define the role of the cube definition—Cube Attribute, Dimension, or Measure.
Specify a dimension, measure, or attribute to be used in the cube.

Because you can reuse the same dimension for various cubes, you have the opportunity to rename dimensions for use with this particular cube definition. By default, the label you enter here corresponds to the name of the dimension that you have specified and is used as the dimension’s alias or label in the resulting cube. You might want to put the word ALL in front of the dimension name—ALL PRODUCTS, ALL REGIONS, and so on.

The number to the left of the Role column determines the order in which the dimensions and measures appear to the user in the OLAP tool. When you add dimensions and measures, this number increments automatically.
Click the Add button to add additional dimensions and measures.

For each additional dimension or measure, repeat the previous two steps.
Click the Save button to save your cube definition and all of the components that you have added.

It is important to save your new cube definition at this stage so that you can effectively add cube inputs.

Adding Cube Inputs to a Cube Definition

Access the Cube Inputs page.

Input Name

Add the name of inputs by selecting one value from the list of valid values.

Click the Add button to insert new rows for additional input names.

Specify as many input sources as you want; however, you must completely map all of them to save the cube definition.

Field Map

Click to view how each field in the fact source data is mapped to a dimension.

Mapping Source Query Fields to Cube Components

Access the Cube Input Field page.

Query Fld Name (query field name)

This field is populated from the Cube Inputs page.

Dimension /Measure /Attribute

Specify the dimension, measure, or attribute to which you want to map the corresponding source field.

Role

Indicates whether a field has been mapped to a dimension, measure, or attribute.

OK

Click to save your changes.

The system automatically selects the Mapped check box on the Cube Inputs page. This option enables you to come back in the future and easily see whether fields have been mapped for this cube input.

Designing Attribute Names

You can specify member attributes yourself by using the Attribute Name page. This feature enables you to specify user-defined attributes for members. Users can also set these attributes in Hyperion Essbase and Star Schema platforms. You can then use calculation scripts to search for and manipulate members with particular user-defined attribute values. PeopleSoft Workbenches uses calculation scripts extensively.

Page Used to Design Attribute Names

Page Name	Object Name	Navigation	Usage
Attribute Name	OLAP_ATTRIB_NAM	PeopleTools, Cube Manager, Attribute Definitions, Attribute Names	Specify user-defined attributes for members.

Specifying User-Defined Attributes

Access the Attribute Name page.

Attribute Number

If you are working with large numbers of attributes, this field helps you to group the attributes into more manageable categories. For example, you might want to list human resource attributes in the 100-300 range, and finance attributes in the 400-600 range. The attribute number is not used anywhere else in the system.

Attribute Name

Enter a descriptive name for the attribute.

Dimension ID	Identifies the dimension of the target OLAP database. Note. You cannot rename or delete a dimension ID after you have saved it.
Description	Appears by default to the dimension, but you can provide another description. This is used as the description of the dimension in the resulting cube.
Dimension Options	See Defining Dimension Options.
Dim Type (dimension type)	Select one of the following dimension types: Standard: Select for every kind of dimension that does not contain account, time, currency, or country data. You can have many standard dimensions in each cube. Account: Select if the dimension is based on account information. You can have only one account dimension for each cube. Time: Select if the dimension is time-based. You can have only one time dimension for each cube. Currency Partition: Valid only for Hyperion Essbase. Select if the dimension is based on currency. You can have only one currency dimension for each cube. Country: Valid only for Hyperion Essbase. Select if the dimension is based on countries. You can have only one country dimension in each cube. See your Hyperion Essbase documentation.
Rollup Name	The default rollup name is based on the dimension ID. You can change the rollup name, but the name cannot be identical to the dimension ID. The rollup name becomes the top node of the dimension if you specify more than one rollup in the dimension. If you have multiple rollups, rolling up to a single top node, this name is used only for the alternate rollups. A node is created for each rollup as a child of the dimension’s top node.
Rollup Options	See Defining Rollup Options.
Level Name (All Platforms)	(Required) If you want to explicitly define level names in the rollup, specify them in the Rollup Levels group box. Level names defined in this manner override the level names that might be returned from the tree or any names that PeopleSoft Cube Manager creates as defaults. You are required to specify levels to be used in mapping wide queries or for defining aggregates. When you enter multiple level names, PeopleSoft Cube Manager assigns a level number to the declared level name in the order in which the level name is entered. This number also populates the Dim Input Field page.

Src Type (source type)	(Required) Select one from the following options: Calendar: This option is not yet implemented, but will enable you to use PeopleSoft Calendar. Level Attr (level attribute): Not used. Query: Specify how the hierarchical relationships, as well as member attributes, are defined. Security: Not used. Tree: Specify how the hierarchical relationships, as well as member attributes, are defined. Note. PeopleSoft Cube Manager currently supports only trees that are keyed by setID or no additional key. For example, PeopleSoft Cube Manager does not support Business Unit (BU) or User Defined Node Key (UKV) trees.
Input Name	Enter the name of the tree or query to be used to define the dimension.
	Click the Lookup Input Name button to search for existing input names.
Top Node	Prepopulated with the top node from the tree based on the input name that you selected.
	Click the Lookup Top Node button to search for the existing top node.
Levels From Top	Specify the number of levels from the top node (including the top node) to the stop level that corresponds to the lowest level of the tree to be included in the rollup. See the example in this section.
	Click the Lookup Levels From Top button to search for existing levels from the top node.
Field Map	Available only when the source type is a query. See Mapping Fields to a Role in the Rollup.
Mapped	This check box is selected when the input name is mapped; if the field is not mapped, the check box is clear. Map the field by using the Field Map link.

Query Fld Name (query field name)	Value is based on the query’s column names.
Role	Select one from the following options: Attribute: If you select the Attribute option, you must also select the attribute name. Class ID: Not implemented. Member: If all sources are members, select the level name. Parent: If a parent exists, you cannot select level names or numbers. The parent is the top of the dimension, and the member is the child of the parent.
Level Name	Click the field to display a list of valid level names, and select one of the names that is specified on the Dimension page. This field is available only if all roles are set to Member.
Seq	Automatically assigned to the level name when the level name is declared on the Dimension page.
Attribute Name	This field is available only if the Role field is set to Attribute. Add to or change the values that are available in the drop-down list box on the Attribute Name page.

Description	Enter the description that you want to associate with the cube. The description is not transferred to the resulting cube definition; it is used for prompting within PeopleSoft Cube Manager only.
Long Description	Enter the long description that you want to associate with the cube. This description is not transferred to the resulting cube definition; it is used for prompting within PeopleSoft Cube Manager only.
Role	(Required) Select one from the following options: Cube Attribute: Select this option if the component is an attribute. A cube attribute is a field that can be included in the fact table for external processing. The Bookmark field on the fact table is an example of a cube attribute. You cannot use this bookmark in analysis, but PeopleSoft Cube Manager uses it to manage facts. Dimension: Select this option if the component is a dimension. Measure: Select this option if the component is a measure or fact.
Dimension/Measure/Attribute	Specify the dimension, measure, or attribute that you want to associate with the cube.
	Click the Open button to display the Cube Input Field page. This button is available only if you selected the Dimension option in the Dimension/Measure/Attribute field.
Dim Type (dimension type)	This field is read-only. If you selected the Dimension option in the Dimension/Measure/Attribute field, PeopleSoft Cube Manager displays the value that you entered for the Dim Type field on the Dimension page.
Status	This field is read-only. The value that PeopleSoft Cube Manager displays is based on the information that you entered on the Dim Input Field page.

Query Fld Name (query field name)	This field is populated from the Cube Inputs page.
Dimension /Measure /Attribute	Specify the dimension, measure, or attribute to which you want to map the corresponding source field.
Role	Indicates whether a field has been mapped to a dimension, measure, or attribute.
OK	Click to save your changes. The system automatically selects the Mapped check box on the Cube Inputs page. This option enables you to come back in the future and easily see whether fields have been mapped for this cube input.

Attribute Number	If you are working with large numbers of attributes, this field helps you to group the attributes into more manageable categories. For example, you might want to list human resource attributes in the 100-300 range, and finance attributes in the 400-600 range. The attribute number is not used anywhere else in the system.
Attribute Name	Enter a descriptive name for the attribute.