Building Essbase Cubes

This chapter discusses how to:

Click to jump to parent topicBuilding Essbase Cubes

This section discusses how to:

Click to jump to top of pageClick to jump to parent topicBuilding Essbase Cubes

Access the Create Cubes page (CUB_RUNCNTL) by selecting PeopleTools, Cube Builder, Essbase Cube Builder, Create Cube.

Use the Create Cubes page to run the process that sends all of the defined information to the Essbase database to build Essbase cubes.

Outline

Displays the outline that is used in this cube creation process.

Essbase Connection ID

Displays Essbase connection ID that is used in this creation process.

Application Name

Displays the Essbase application name that is used in the Essbase system to create the Online Transaction Processing (OLAP) cube.

Database Name

Displays the database name that is used in the Essbase system to create the OLAP cube.

Meta-Data Update Action

Select an update action to use to build the metadata (the cube shape). The selected update action controls what to do in case this cube creation process is not the first time the cube is built.

Available options are:

  • Create or Re-create: creates or recreates metadata from scratch.

  • Incremental Replace All: incrementally updates existing metadata and removes unspecified members.

  • Incremental Update: incrementally merges updates with existing metadata.

  • No Action: no action on metadata.

Restructuring Options

Select an option to build the data (the cube contents).

Available options are:

  • Discard all data: discards all previously loaded or manually modified data.

  • Keep all data: no data modifications.

  • Keep only input data: keep only input data or data blocks created by data loading.

  • Keep only level 0 data:incremental delete upper level.

  • Reload all data: reloads all data from its source.

Log Level

Enter the log level that pertains to the level of logging while the process is running.

These are the logging levels that can be selected to view specific messages or errors:

  • 0 (eRequisite): no logging.

  • 1 (eBasic): basic logging.

  • 2 (eDetail): detailed logging.

  • 4 (eDimensional): single dimension logging.

  • 8 (eFactMapping): single factory logging.

  • 16 (eAPITrace): Essbase API traces.

For example, to see logging for Single Dimensions and Essbase API, enter 20 (sum of eDimensional and eAPITrace = 4+16 = 20). To see all the logs available, enter 31 (1+2+4+8+16 = 31).

Dimension

Select a dimension as a single dimension that loads data.

This selection sets the data update action to No Action. The only action that will happen in the current run is for the structure of dimension to be rebuilt. No data will be loaded.

Query

Select a query as a single query that loads data.

This selection sets the metadata action to No Action. While the process is loading in a single query, no structural changes are made to the cube.

Note. You should not provide both a dimension and a query, because this action would cause nothing to occur in the current run of the cube builder.

Last Update Dttm (last update date and time)

Displays the date and time that the cube creation run control ID was last modified.

Run

After saving the defined information, click this button to run the batch program.

See Also

Submitting and Scheduling Process Requests

Click to jump to parent topicIntegrating with Oracle Smart View

Using Oracle Smart View for Microsoft Excel, you can view the data and metadata of the recently built cube from Process Monitor. To view data of cube using Smart View:

  1. Build Essbase cube.

    See Building Essbase Cubes.

  2. After an Essbase cube is successfully built, click the Process Monitor link in the Create Cube page to access the Process List page.

  3. Click the Details link for selected process instance.

    If an Essbase cube was built successfully, the Open Cube in Smart View link is available in Process Detail page as shown in this example:

  4. Click the Open Cube in Smart View link.

  5. If required, enter the user name and password that was used to build the cube.

    If your user name and password are authorized, Smart View displays the top members of the two dimensions created as shown in this example:

  6. (Optional) Drill down or use the POV Smart View tool to manage the data.

Note. If you modify data or metadata using Smart View, these modifications will affect the cube that is stored in Essbase, but will not affect the PeopleSoft tree or query that are used by PS2Essbase to create the cube.

If you make any modification using Smart View, these modifications may be overwritten in the next run of PS2Essbase.

If multiple process instances of PS2Essbase have been ran using Process Scheduler, the Process List page displays only one Open Cube in Smart View link for the latest cube built.

Click to jump to parent topicUsing API and Command-line Specifications

You can run PS2Essbase from the Create Cube page using process scheduler or the command line.

This table lists the parameters that ps2essbase uses when ps2essbase runs from the command line:

Parameter

Description

A, a

Outline Name.

R, r

Run Control ID.

I, i

Process Instance ID number, such as I42, usually passed by process scheduler.

CT, ct

Database type (for example, -CTORACLE).

CD, cd

Database name (for example, -CDPT850RC1).

CO, co

Operator ID (for example, -COPTDMO).

CP, cp

Password (for example, -CPPTDMO).

EC, ec

Essbase Connection Name.

OP, op

Log files output destination.

Note. When running PS2Essbase from the command line, in the –OP command line option, you must enclose the output destination patch in quotes. For example, –OP “c:\tmp\ps”.

M, m

Metadata action, such as -mC:

  • N - No action on metadata.

  • C - (Re)create metadata from scratch.

  • U - Incrementally merge updates with existing metadata.

  • R - Incrementally update existing metadata, remove unspecified members.

D, d

Outline Restructure Option:

  • N - Keep all data.

  • R - Discard all data.

  • I - Reload all data.

  • D - Keep only level 0 data.

  • A - Keep only input data or data blocks created by data loading.

L, l

Logging level (for example, L31).

X, x (optional)

Dimension name for single dimension execution.

Y, y (optional)

PS Data Query name for single factory execution.

Example: the parameters list passed using this command line:

ps2essbase.exe -CX -CTORACLE -CDPT850RC1 -COPTDMO -CPPTDMO -I42 -OP "c:\tmp\ps" -
REMPLOYMENT -aEG_
DIVISION -mC -dR-L15 -XGL_ACCOUNT -YQRY_MEASURES

Logging

You can pass the log level with the L option to the command line of psolap.exe; for example, L2 or L6, and so on.

This table lists the log level and what is recorded in each log level:

Log Level

What is recorded

1

Basic logging

2

Detail logging

4

Dimension member logging

8

Fact map logging

16

API logging

When you run process using Process Scheduler, the logging level is set in the Create Cube page. When you run process from the command line, the logging level is set using the –L parameter. To calculate these logging settings, PeopleSoft Cube Builder add the options that you define. For example: