Building Cubes

This chapter provides an overview of cube instance definitions and discusses how to:

• Build cube instances.

• Build cubes.

Understanding Cube Instance Definitions

PeopleSoft Cube Manager provides a powerful template feature that enables you to set up cube instance definitions for use and reuse when building and updating cubes. Having a cube instance definition simplifies your work in managing updates to the cube structure, loading and reloading data, and setting platform-specific options when you create the cube. Without the benefit of PeopleSoft Cube Manager—and the Cube Instance Definition feature in particular—building or updating a cube would require tedious and error-prone steps.

Each cube instance definition is associated with a single physical cube. You typically have one cube instance definition for each cube. At times you might find it useful to have more than one. For example, you might have one cube instance definition for Cognos PowerPlay and one for Hyperion Essbase.

Up to this point, everything that you have done in creating a cube is more or less generic, and does not require you to specify the platform (Cognos PowerPlay, Hyperion Essbase, or Star Schema) that you will ultimately use. Thus, if you decide to switch platforms, the majority of your cube design remains unchanged. When building the cube instance definition, however, you must designate the specific platform for which you are creating the cube.

Building Cube Instances

This section discusses how to:

• Build a cube instance definition.

• Define cube settings and select dimensions, measures, and attributes.

• Create the cube filter.

• Define cube settings for Hyperion Essbase.

• Define cube settings for Cognos PowerPlay.

• Add a prefix to field and record objects.

• Define cube aggregates.

Note. The definition of a cube instance creates the link between the platform-independent definition of the cube and the actual physical storage mechanism of the cube. In essence, you tell PeopleSoft Cube Manager where to create the cube that you have defined.

Pages Used to Build Cube Instances

Building a Cube Instance Definition

To build a cube instance definition:

1. Design the cube definition.

2. Select PeopleTools, Cube Manager, Cube Instances, Cube Inst Def.

3. Select the Add a New Value tab.

4. Enter a cube instance ID and click the Add button to define the cube platform and included components.

   You must provide a unique name for each cube instance definition that you define. After you enter a cube instance ID, the Cube Inst Def page appears.

5. Enter a description and long description.

6. Specify the platform.

7. Specify the criteria for this cube instance definition: either a cube definition or an existing star schema-based cube instance.

8. Remove any dimensions or measures that you do not want to be created in this cube instance.

   By default, PeopleSoft Cube Manager adds all of the dimensions and measures to the cube instance definition. However, if you do not need them all, you can remove any unwanted dimensions or measures by clicking the Remove (-) button to the right of the dimension name.

9. Click the Platform Options link to display platform-specific options, based on which platform you selected from the drop-down list box.

   Which page you see depends on which platform you chose. Platform options are as follows:

• Cognos PowerPlay.

  See Defining Cube Settings for Cognos PowerPlay.

• Generic Star Schema.

  See Adding a Prefix to Field and Record Objects.

• Hyperion Essbase.

  See Defining Cube Settings for Hyperion Essbase.

Defining Cube Settings and Selecting Dimensions, Measures, and Attributes

Access the Cube Inst Def page.

Common Page Information

Dimension Tab

Filter Tab

Creating the Cube Filter

Access the Cube Filter Criteria page.

Member Value

Enter the value for the criteria. If your source dimension has more information than you want to report, you can create a filter to eliminate selected information. For example, if you have data from the U.S., U.K., and Japan, but want to view only the data for Japan, create a Japan filter to eliminate the U.S. and U.K. data from the cube dimension.

Defining Cube Settings for Hyperion Essbase

Access the Essbase Advanced Options page.

Server	Enter your server ID address or machine name. See Defining Cube Settings for Hyperion Essbase.
Application	(Required) Enter the application name. In Hyperion Essbase, an application is a group of one or more databases.
Database	(Required) Enter the database name. In Hyperion Essbase, a database is essentially an Online Analytical Processing (OLAP) cube.
User Access	(Required) Set the access to Calculate, Design, Read-Only, Read-Write, or None. This setting sets the default user security on the resulting cube, if explicit security has not been granted in Hyperion Essbase. It applies to everyone except the system administrator (to whom the User Name and Password options apply). You typically set at least Read-Only access.
User Name	Enter your user name.
Password	Enter your password. Note that it should be same as the password that you use to set up the Hyperion Essbase server.
Meta-Data Update Action	(Required) Enables you to specify the update action that should occur in Hyperion Essbase when a cube structure has been redesigned in PeopleSoft Cube Manager. The options are: Replace All: Refreshes the cube's structure. Any members defined in PeopleSoft that don't exist in the cube are added to the cube. Any members in the cube that are no longer defined in PeopleSoft are deleted from the cube, and any associated data is lost. Members moved in PeopleSoft—from one node to another, for example—are moved in the cube with any associated data preserved. Incremental Update: Merges the metadata defined in your cube definition with the existing metadata of the cube. No members are deleted.
Data Update Action	(Required) Enables you to specify the update action that should occur in Hyperion Essbase when a cube’s data has been changed within a PeopleSoft application. You have three options: Delete Upper Level Data: Deletes all aggregate data. Delete Non-Input Data: Deletes any data that has not been loaded into a cube by the build process—for example, data that you have entered manually in Hyperion Essbase or data that results from a calculation in Hyperion Essbase. Incremental Update: Preserves existing data and enables you to add new data to the existing data for both multiple hierarchy and single hierarchy dimensions. Note. Both the Meta-Data Update Action and Data Update Action fields refer to the metadata and data action options on the Build Cube page and apply only to updating existing cubes.
Rate Cube Action	If the cube definition contains the appropriate dimensions (account, time, and country), you can create a rate cube. This setting enables you to specify the following rate cube creation options: Create All: Regenerates the currency cube definition from the cube that is defined in PeopleSoft Cube Manager. The system then populates the resulting currency rate cube with the data that is defined in the Rate Cube Mapping group box, if any mapping exists. Rate Update Only: Replaces the existing data in the currency rate cube without regenerating the outline. No Action: Does not perform any action on the currency rate cube.
Run Default Calc (run default calculation)	If you select this option, the system runs the default calculation script in Hyperion Essbase when the cube is created. Hyperion Essbase aggregates the tree in the given rollups, but does not do anything else. You may instead decide to create a custom calculation script, in which case you might clear this option.
Auto Config Sparsity (automatically configure sparsity)	If you clear this check box, you can manually set the sparsity levels on the Cube Instance Definition page. Otherwise, Hyperion Essbase automatically sets sparsity levels. After you have cleared this check box, you can set the sparsity of each dimension in the template to either Sparse or Dense. Note. Dimensions marked as Sparse might take up significantly more space in the resulting cube than those marked as Dense. If you mark every dimension as sparse, you could end up with an enormous cube that is not practical or even possible to store on even the most powerful servers. That's why the Time and Account dimensions default to Dense. It's possible to change these settings in Hyperion Essbase after you create your cube. Whether you change the sparsity settings from PeopleSoft Cube Manager or from Hyperion Essbase, take care when adjusting, and make sure to refer to the Hyperion Essbase documentation.
Language Code	Choose to build a Hyperion Essbase cube in multiple languages. When the cube is then viewed in Hyperion Essbase, it appears in the user’s preferred language. If the cube is not available in the user’s language, the default language (developer’s language) is used. To add one additional language, select a language from the drop-down list box. Note. You do not have to select your own language. The cube is automatically built in your own language.
Rate Cube Name	Enables you to supply a rate cube mapping. PeopleSoft Cube Manager generates the actual currency rate cube by default. Specify the cube name that you want PeopleSoft Cube Manager to create and map to the defined cube.
Query Name	Select the query that has your currency rate definition.
Time	Select the field name for time from the time dimension.
Account	Select the field name for currency category from the account dimension.
Country	Select the field name for currency name from the country dimension.
Type	Select the field name for currency type.
Rate	Select the field name for currency rate multiplier.
Default Currency Name	Enter the default currency name. If you do not specify a currency name for a member in your country dimension, the default currency name applies to the member.
Default Currency Category	Enter the default currency category. If you do not specify a currency category for a member in your account dimension, the default currency category applies to the member.

Multicurrency Rate Cubes

Hyperion Essbase supports multicurrency cubes. A Hyperion Essbase multicurrency cube contains two databases: the regular main database and the currency rate database. The currency rate database is created out of the main database. Before you can generate the currency rate database from the main database, the main database must have the appropriate dimensions:

• Accounts dimension contains items that you want to measure, such as profit and inventory, and makes Hyperion Essbase built-in accounting functionality available.

• Time dimension defines the time period for which you report and update data.

• Country dimension contains data about where business activities take place.

You can also specify the currency partition dimension (PeopleSoft Cube Manager also calls this Currency Dimension) in the main database for the Hyperion Essbase multicurrency cube. The currency partition dimension is for separating local currency members from a base currency that is defined in the application. If the base currency for analysis is U.S. dollars, the local currency members contain values that are based on the currency type of the region. The currency partition dimension is used only in the main database for currency conversion, using Hyperion Essbase script or other tools.

The following steps outline what you specify for the account dimension and the country dimension, specifically for Hyperion Essbase multicurrency cubes. You create attribute queries for the Account and Country dimensions, and specify the queries as an input source on the Rollup Inputs page.

To create a multicurrency cube in Hyperion Essbase:

1. Select PeopleTools, Cube Manager, Dimensions, Rollup Inputs.

2. Click the Field Map link for the appropriate input name.

3. Specify the currency category in your accounts dimension, for example P&L (for profit and loss).

4. Specify the currency name in your country dimension, for example US$.

Defining Cube Settings for Cognos PowerPlay

Access the PowerPlay Options page.

PowerCube Path/File (.MDC)	Specify the path and file name. Cognos PowerPlay requires both a PowerCube file and a model file. The PowerCube file has an .mdc extension and equates to a cube. Note. Cognos PowerPlay refers to a multidimensional database as a PowerCube, so we use this term in place of cube when referring specifically to the resulting cube in Cognos PowerPlay.
Model Path/File (.MDL)	Specify the path and file name. The model file has an .mdl filename extension and represents the cube structure.
Data Working Directory	Specify where the system writes the .dat file.
Language Override	If you are implementing the PowerCube in a non-English language, select a language.
Always Include	Select this check box to retain the category in the model and include it in cubes, even if it, or any of its descendants, fails to appear in the data source. The category is also included if any of its descendants are included and if the category has not been excluded, summarized, or cloaked in a dimension view. If necessary, the transformer includes ancestors of the category, regardless of their inclusion settings. Note. The Always Include check box is selected when you create a time dimension. If you exclude categories, special categories that use relative time concepts (such as Last Month) do not work properly.
Earliest Date	The fields in this group box are optional and are used when designing and creating time dimensions for Cognos PowerPlay. If not specified, the system supplies a default time of 1901-01-01.
Use As of Date	Select to use the As of Date option that is provided on the run control page.
Use Current Date	Select to use the current system date as controlled by settings in Cognos PowerPlay.
Use Specific Date	Select to set a specific date. If not specified, the default is 1901-01-01.
Latest Date	The fields in this group box are optional; you use them when designing and creating time dimensions for Cognos PowerPlay. If not specified, the system supplies a default time of 2100-12-31.
Use As of Date	Select to use the As of Date option that is provided on the run control page.
Use Current Date	Select to use the current system date as controlled by settings in Cognos PowerPlay.
Use Specific Date	Select to set a specific date. If not specified, the default is 2100-12-31.
Enterprise Server	Select if you want PeopleSoft Cube Manager to register your resulting cube automatically on the Cognos PowerPlay enterprise server. If you do not select the Enterprise Server option, PeopleSoft Cube Manager creates the cube by using the transformer.

Defining Cognos PowerPlay Cube Instance Definition Options

The following steps show both the optional and required options that enable PeopleSoft Cube Manager to build a Cognos PowerPlay cube.

Note. PeopleSoft Cube Manager and the enterprise server must be set up to run on the same machine.

The .mdl and .dat files merge to create the PowerCube (.mdc file)

To define Cognos PowerPlay cube instance definition options:

1. On the PowerPlay Options page, specify the file names to be created when the cube is built.

2. Enter the data working directory.

   When building a PowerCube, PeopleSoft Cube Manager sends output from each query used in the PowerCube to a flat data file before sending this data to the PowerCube (.mdc) file. This flat data file has a .dat extension, and is written to the data working directory that you specify.

   Note. The data file created in the data working directory is not automatically deleted or overwritten when PeopleSoft Cube Manager builds a PowerCube. You must manually delete the files.

3. If necessary, select a language override.

4. Click the OK button if you are not using the enterprise server; otherwise, continue to the next step.

5. Select the Enterprise Server check box if you want to use the enterprise server functionality.

   The Cube Instance Definitions page appears.

The default value for the Service Port field is 8010. This value should be the correct port for most machines. PowerPlay Enterprise Server is set to communicate on port number 8010 for both Windows and web connections.

Note. PeopleSoft Cube Manager assumes that the enterprise server is running locally. PeopleSoft Cube Manager retrieves the local machine name from the system to connect to the enterprise server.

PeopleSoft Cube Manager uses Ppadmtool.exe to communicate with the local enterprise server to add or remove cubes. PeopleSoft Cube Manager first tries to remove the cube from the enterprise server. If the cube already exists, it removes the cube from the enterprise server. This action prevents other users from trying to access the cube through the enterprise server while PeopleSoft Cube Manager is actually creating it. After removing the cube from the enterprise server, PeopleSoft Cube Manager uses the transformer to generate the .mdc file.

If the cube is not listed in the enterprise server, PeopleSoft Cube Manager uses the transformer to generate the .mdc file.

After creating the .mdc file, PeopleSoft Cube Manager uses the Ppadmtool.exe to add the .mdc file to the enterprise server. After the cube has been added to the enterprise server, any user connected to it from a local or remote machine can view the newly added cube.

If you do not select the Enterprise Server option on the PowerPlay Options page, PeopleSoft Cube Manager creates the cube by using the transformer.

Note. Cognos PowerPlay does not allow duplicate details in the same hierarchy, but it does allow duplicate details across hierarchies for the same dimension.

See Also

Cognos PowerPlay

Adding a Prefix to Field and Record Objects

Access the Star Schema Options page.

PeopleTools Object Name Prefix

The prefix is applied to each record and field definition that is created by PeopleSoft Cube Manager. The prefix provides some control over the record and field names. The default is DW_.

Defining Cube Aggregates

Access the Aggregates page.

The Aggregates page has not been implemented.

Building Cubes

This section provides an overview of building cubes and discusses how to:

• Define the cube build specifications and bind variables.

• Define bind variables.

• Define a cube build process using Process Scheduler Manager.

• Run the process to build the cube.

Understanding Cube Creation

When you are ready to build a cube, you need a place to specify the runtime parameters to be passed during the creation or update of the data cube using PeopleSoft Process Scheduler. The Build Cube page in PeopleSoft Cube Manager provides an example of how to pass this information from a PeopleSoft page to the resulting cube by using a PeopleSoft Process Scheduler run control. Most likely, you are building cubes using pages that were either supplied with your PeopleSoft applications or pages that you have built yourself.

You can configure the way in which a cube is built by creating your own run control pages and process definitions using the Cube Builder process type. Certain PeopleSoft applications deliver their own pages for building cubes that leverage product-specific metadata.

Note. If you are building a Hyperion Essbase cube and it contains time, account, and country dimension types, PeopleSoft Cube Manager automatically builds a currency cube, if one is defined. The calculation for the currency cube always has a default value of Division.

Note. After you have built a Hyperion Essbase cube, we do not support changing the dimension name by changing the cube instance definition. The work-around is to access Hyperion Essbase and manually change the dimension name to match the one in the cube instance. Another option is to recreate the cube with the Meta-data: Create and Data: Create option.

Pages Used to Build Cubes

Defining the Cube Build Specifications and Bind Variables

Access the Build Cube page.

	To view the cube instance definition, click the Open Cube Instance Definition button. The Cube Inst Def page appears with the instance definition that you specify. See Defining Cube Settings and Selecting Dimensions, Measures, and Attributes.
Meta-Data	Select an option from the following options: Create: Create the cube. If the cube already exists, PeopleSoft Cube Manager recreates it, overwriting any existing dimensions and data. Update: This option in Generic Star updates the metadata. In Hyperion Essbase, this option updates the structure of the cube according to the setting for the Meta-Data Update Action field on the Hyperion Essbase's Cube Instance Definition page. For Cognos PowerPlay, this setting has the same effect as Create. None: Do not make any changes to the structure of the cube or its individual dimensions. (You may want to update the data only.)
Data	Define the data action to take place when updating the cube: Create: Reload the data, overwriting any existing data. Update: Update the existing data in the cube. For Hyperion Essbase, this option is linked to the Data Update Action option that is selected on the Hyperion Essbase's Cube Instance Definition page. None: Do not make any changes to the data in the cube. (You may want to update the structure only.)
Aggregation	Select one option from the following options: Create: Reload the aggregates, overwriting any existing data. None: Do not make any changes to the aggregates in the cube. (You may want to update the structure only.)
Business Unit	Enables you to get the appropriate setIDs for tree metadata. Leave this field blank if your trees do not use set IDs.
As of Date	Enables you to get the appropriate effective dates for tree metadata.
Bookmark	Bookmarks identify a set of facts in the Generic Star Schema cube. These facts are used to determine whether facts are loaded for the first time or reloaded. The first time that you create a build cube definition, the bookmark is set to Initial. You can also add a build script.
Script	Refers to platform-specific, post-build scripts, such as the .mdl file for Cognos PowerPlay or any command line for Windows. This feature enables you to extend the capabilities of PeopleSoft Cube Manager. For example, you can specify an Esscmnd script that sets up security. Then, rather than having to configure security manually every time that you build a cube, you can write a script once and specify it in the Script field to execute it for each build.
Report Manager	Displays the report list in Report Manager. See Working With Processes and Reports.
Process Monitor	Displays the process list in Process Monitor. See Using Process Monitor.
Run	Click to display the Process Scheduler Request page.

To build a cube:

1. Build the cube instance definition.

   See Building Cube Instances.

2. Select PeopleTools, Cube Manager, Build Cubes.

3. If you add a new cube definition, enter a run control ID and click the Add button.

   Alternatively, if you update and display an existing cube definition, click the OK button.

4. In the Cube Specification group box of the Build Cube page, select a cube instance ID.

5. Define the run control information in the Run Time Parameters group box.

   Note. If you specified the default calculation script on the Hyperion Essbase's Cube Instance Definition page, the default calculation script runs first. The command line is then invoked to run a subsequent script.

6. Define the metadata action that should occur during the build.

7. Define the data action that you want to occur during the build.

8. Define the aggregate action that you want to occur during the build.

9. Set your Process Scheduler parameters and save the page.

   See Enterprise PeopleTools 8.49 PeopleBook: PeopleSoft Process Scheduler.

   Note. When working in a three-tier environment, you must build your cubes on a Windows Process Scheduler server, not on the client.

Defining Bind Variables

Access the Bind Variables page.

If you want to use dynamic queries , you must create a query that joins the run control with the desired record and joins the operator ID and the run control ID.

You can make any PeopleSoft Cube Manager query (dimension query, data source query, or attribute query) dynamic by joining in runtime parameters. The parameter value must be stored in the database on a Cube Builder run control record or on a record to which the run control record can join. Then, in PeopleSoft Query, join the run control record and set prompts for the operator ID and the run control ID. These prompts are completed at runtime with the operator ID and run control ID of the run control that is used to launch the Cube Builder process. The Description and Bind Value fields on the sample Build Cube run control page provide one way to join the parameters.

Adding Bind Variables

To add bind variables to a run control page:

1. Identify the run control record that is used to launch the Cube Builder process.

   In the case of the sample Build Cube page that is delivered in the PeopleTools Demo database (PTDMO), this record is MAKE_ANL_DB_REQ.

2. Identify the fields that you want to use for parameters for runtime queries.

   For example, values for From and To for time periods.

3. Ensure that the fields identified in step 2 are available on the run control record, or that they are on a record that can be joined with the run control record.

   See Record Definition Planning.

4. Ensure that these same fields are available on a page so that users can enter values for them.

   If these fields exist on the run control record, they most likely also exist on the run control page.

   See Creating Field Definitions.

5. In PeopleSoft Query, join the records that contain the fields mentioned above to the query that you want to make dynamic.

   For example, assume that you want to bind in values for the From and To periods and that these fields exist on the run control record. In the data source query, join the From and To periods on the run control record to the From and To fields in the main data record (the primary record in the query that contains the data that you want to return).

   See Joining Records.

6. In PeopleSoft Query, set up prompts for the operator ID (first) and the run control ID (second).

   Instead of prompting for these values at runtime, PeopleSoft Cube Manager automatically supplies the bind values that the user entered on the run control page.

7. Open the Bind Variables page by selecting the Bind Variables tab in the Build Cubes component.

   Alternatively, select PeopleTools, Cube Manager, Build Cubes, Build Cube; enter a cube instance ID; and select the Bind Variables tab.

8. Add variables and save your changes.

9. Enter a short text description and give the variable’s value.

Example of Bind Variables Used in PeopleSoft General Ledger

PeopleSoft General Ledger is just one of the PeopleSoft applications that provide a custom run control page. If you need to create a custom run control page, you might find it useful to follow the example that was delivered with this application.

The run control page in PeopleSoft General Ledger is the Build Ledger Cubes page . It provides a way for users to enter bind values for the Ledger, Currency Code, From Year, To Year, From Period, and To Period fields.

Note. Other than the bind variables mentioned above, the Build Ledger Cubes page is essentially the same as the sample Build Cube page that is delivered in the PTDMO database.

Cube Instance ID	Enter the name of the cube template or select it from the menu.
Open Cube Instance Definition	Click this link to change any settings on the Cube Inst Def page.
Business Unit	Select the setID for the tree that you are using.
As of Date	Select the effective date.
Post-Build Script	Enter the name of a script. This could be a Hyperion Essbase, Cognos PowerPlay, or ROLAP script that runs on the cube after the system builds and populates it.
Ledger	Select the ledger that you want to use when populating the cube.
Currency	Select the appropriate code, according to the currency type.
From Year	Enter the starting time range for the ledger data that you want to appear in the cube.
To Year	Enter the ending time range for the ledger data that you want to appear in the cube.
From Period	Enter the starting period range for the ledger data that you want to appear in the cube.
To Period	Enter the ending period range for the ledger data that you want to appear in the cube.
Meta-Data Action	Select one from the following options: Create: If the cube already exists, PeopleSoft Cube Manager recreates it, overwriting any existing dimensions and data. Update: In Hyperion Essbase, this option updates the structure of the cube according to settings for the Meta-Data Update Action field on the Hyperion Essbase's Cube Instance Definition page. For Cognos PowerPlay, this option has the same effect as Create. None: Do not make any changes to the structure of the cube or its individual dimensions. (You may want to update the data only.)
Data Action	Select one from the following options: Create: Reload the data, overwriting any existing data. Update: Update the existing data in the cube. For Hyperion Essbase, this option is linked to the Data Load Action field on the Hyperion Essbase's Cube Instance Definition page. This option does not apply to Cognos PowerPlay. None: Not applicable in PeopleSoft General Ledger.

Note. The General Ledger run control page makes it easy for a user to enter bind values by limiting the choices available. The user knows exactly the fields for which he or she is supplying values, because those controls are supplied on the page: Ledger, Currency, From Year, To Year, From Period, and To Period. This approach, while beneficial for the user, requires more time and care on the part of the designer.

Keep in mind that it is possible to create a run control page that is essentially identical to the sample Build Cube page—where the field for which the user supplies the bind values is determined at runtime by the user. In the Description text box, the user enters the name of the field that requires a bind value, and then enters that value in the Bind Value text box. Additional descriptions and bind values can be inserted as required.

See Also

PeopleSoft 8.8 PeopleBook: General Ledger

Defining a Cube Build Process Using Process Scheduler Manager

Access the Process Definition page.

Priority	Select a relative priority used by the Process Scheduler Server Agent to determine which process to initiate first, if multiple processes are queued to run on a given server.
API Aware	Select this option if this process is application programming interface (API) aware. If this option is selected for any process that is not API aware, Process Scheduler includes it in the concurrent task count. This inclusion can result in improper server load balancing. Selecting this option does not mean that your process becomes API aware. You must still add API code to your process.

Running the Process to Build the Cube

Access the Process Scheduler Request page by running the process to build a cube.

Server Name	Select the name of the server on which you want the process to run: PSNT: a Microsoft Windows server. (PeopleSoft Cube Manager runs only on Windows.)
Recurrence	Select the recurring time intervals for a process request to run. Select either Daily Purge or M-F at 5pm. See Enterprise PeopleTools 8.49 PeopleBook: PeopleSoft Process Scheduler.
Time Zone	Select the time zone in which your process runs. For example, you could be in Eastern Standard Time (EST) and schedule a process to run in Pacific Standard Time (PST).
Run Date	Select the date on which your process runs.
Run Time	Select the time when your process runs.
Reset to Current Date/Time	Click this button to set the run date and run time to the present date and time.
Select	Specify the cube to be built. If you select this check box, the process is included in the build process.
Description	Uniquely identifies the process.
Process Name	The name of the process as it appears in the definition.
Type	The type of output. Select None.
Format	The format of the output. Select None.
	Click the Distribution button to view a list of people who have the correct security to receive the output of this process.
OK	Click this button to run the process.