Linking Objects to Essbase Data

In This Section:

Understanding LROs

Understanding LRO Types and Data Cells

Setting Up Permissions for LROs

Viewing and Deleting LROs

Exporting and Importing LROs

Limiting LRO File Sizes for Storage Conservation

The information in this chapter applies only to block storage databases and is not relevant to aggregate storage databases. Also see Comparison of Aggregate and Block Storage.

Understanding LROs

You can link various kinds of data with any cell in an Essbase database, using a linked reporting object (LRO). This ability is similar to attaching a file to e-mail. An LRO provides improved support for planning and reporting applications and can enhance your data analysis capabilities.

LROs are objects (alternatively called artifacts) that you associate with specific data cells in an Essbase database. Users create linked objects through Spreadsheet Add-in by selecting a data cell and choosing a menu item. You can link an unlimited number of objects to a cell. The objects are stored on the Essbase Server, where they are available to any user with the appropriate access permissions. Users retrieve and edit the objects through the Spreadsheet Add-in Linked Objects Browser feature, which enables them to view objects linked to the selected cell. For the maximum sizes of the types of linked objects described in Table 28, see Limits.

Table 28. Types of Linked Objects

Object Type

Description

Cell note

A text annotation

File

An external file, such as a Microsoft Word document, an Excel spreadsheet, a scanned image, an audio clip, or an HTML file (for example, mypage.htm).

URL

For example:

http://www.oracle.com
ftp://ftp.oracle.com

Linked partition

A set of data cells that you can link to in another Essbase database.

For example, a sales manager may attach cell notes to recently updated budget items. A finance manager may link a spreadsheet containing supporting data for this quarter’s results. A product manager may link bitmap images of new products. A sales manager may link the URL of a company’s Web site to quickly access the information on the Web site.

Understanding LRO Types and Data Cells

LROs are linked to data cells—not to the data contained in the cells. The link is based on a member combination in the database. Adding or removing links to a cell does not affect the cell contents.

When a user links an object to a cell, Essbase stores in the object catalog information about the type of object, the name of the last user to modify the object, and the date the object was modified.

How Essbase stores the LRO depends on the LRO type:

  • If the object is a cell note, the text is stored as part of the object description in the catalog entry.

  • If the object is a file, Essbase stores the contents of the file in the database directory on the Essbase Server, giving it an .lro extension. Essbase imposes no restrictions on the data formats of linked files and performs no file-type checking. It is up to the user’s client computer to render the file after retrieving it from the Essbase Server.

  • If the object is a URL, Essbase stores it as part of the object description in the catalog entry. When the user tries to view the URL, Essbase does a preliminary syntax check; then the default Web browser checks for the existence of the URL.

  • If the object is a linked partition, it is available through the Essbase Partitioning module.

Before you perform tasks related to LROs, be aware of these facts:

  • Essbase uses the database index to locate and retrieve linked objects. If you clear all data values from a database, the index is deleted, and so are the links to linked objects. If you restructure a database, the index is preserved, as are the links to linked objects.

  • Shared members share data values but not LROs, because LROs are linked to specific member combinations, and shared members do not have identical member combinations. To link an object to shared members, link it to each shared member individually.

  • You cannot change the member combination associated with any linked object. To move an object to another member combination, delete it, and then use Spreadsheet Add-in to re-link the object to the desired member combination.

Setting Up Permissions for LROs

Users who add, edit, and delete LROs through client interfaces must have the appropriate permissions in the active database. If the object is a linked partition, the user must also have the required permissions in the database containing the linked partition. Table 29 lists the permissions required for several different tasks.

Table 29. Permissions Required for LRO Tasks

Task

Permission

Add a linked object to a database

Read-write

View an existing linked object

Read

Edit an existing linked object

Read-write

Delete a linked object

Read-write

Export the LRO catalog to a file

Read

Import the LROs from the LRO-catalog file

Read-write

To prevent users from linking files to data cells without changing user access to other data in a database, you can set the maximum file size for linked files to 1. Users can then create cell notes, link to a URL, or view linked partitions but can attach only files smaller than 1 KB.

  To set the maximum LRO file size for an application, see “Limiting LRO File Sizes” in the Oracle Essbase Administration Services Online Help.

Viewing and Deleting LROs

Users work with LROs on a cell-by-cell basis through Spreadsheet Add-in. That is, they select a cell and open the Linked Object Browser, which displays the objects linked to the selected cell. With Administration Services, you can view LROs, and you can delete all LROs for the entire database. You can also view LROs based on selection criteria such as user name and last modification date. For example, you can purge all objects older than a certain date or remove the objects belonging to a user who has left the company.

  To view a list of the linked objects for a database, use a tool:

Tool

Topic

Location

Administration Services

Managing LROs

Oracle Essbase Administration Services Online Help

MaxL

query database

Oracle Essbase Technical Reference

ESSCMD

LISTLINKEDOBJECTS

Oracle Essbase Technical Reference

  To delete the linked objects for a database, use a tool:

Tool

Topic

Location

Administration Services

Managing LROs

Oracle Essbase Administration Services Online Help

MaxL

alter database

Oracle Essbase Technical Reference

ESSCMD

PURGELINKEDOBJECTS

Oracle Essbase Technical Reference

Exporting and Importing LROs

To improve backup and data-migration capabilities, you can export and re-import LROs from data intersections in a database.

  To export and import linked objects for a database, use a tool:

Tool

Topic

Location

Administration Services

Exporting LROs

Importing LROs

Oracle Essbase Administration Services Online Help

MaxL

export lro

import lro

Oracle Essbase Technical Reference

Limiting LRO File Sizes for Storage Conservation

Because Essbase stores linked files in a repository on the server, by default, the size is unlimited. Limiting the file size prevents users from taking up too much of the server resources by storing extremely large objects. You can set the maximum linked file size for each application. If a user attempts to link a file that is larger than the limit, an error message displays.

To prevent users from attaching anything except very small files, enter 1. Setting the file size to 1 lets users link only cell notes, URLs, and files smaller than 1 KB.

Note:

The maximum file size setting applies only to linked files and does not affect cell notes or URLs. The lengths of the cell note, URL string, and LRO descriptions are fixed. For the maximum sizes of these objects, see Limits.

  To limit the size of a linked object, use a tool:

Tool

Topic

Location

Administration Services

Limiting LRO File Sizes

Oracle Essbase Administration Services Online Help

MaxL

alter application

Oracle Essbase Technical Reference

ESSCMD

SETAPPSTATE

Oracle Essbase Technical Reference