1. Administrator's Guide
  2. Working with Detailed Profitability
  3. Model Data Schema for Detailed Profitability
  4. Registering Database Views

Registering Database Views

If you made the appropriate grants to the Product Schema, you may also register database views from the Model Data Schema.

Any valid database view can be registered as the Source stage table or as a Lookup table. Only simple single-table updatable views may be registered as the Destination stage table.

Database views can be useful for several reasons:

  • Accessing tables that do not reside in the Model Data Schema. This may especially be useful for lookup tables.

  • Filtering rows or hiding columns in the underlying table to prevent exposure to the Detailed Profitability application.

  • Hiding complex joins within the view definition for read-only tables to simplify their use within the application.

During model development and model calculation, Oracle Hyperion Profitability and Cost Management creates system-generated reporting views in the Product Schema. Profitability and Cost Management also grants SELECT privilege on them to the Model Data Schema and attempts to create synonyms for them in the Model Data Schema. This provides users with access to that schema without having privileges on the Product Schema that are usually reserved for administrator access only. Model builders and report developers should normally be given access to this schema unless the administrator is expected to complete all the table registration tasks that Profitability and Cost Management requires, and the physical model setup in any reporting tools used.

Note:

In Oracle, a database user and a database schema are the same thing; however, in Microsoft SQL Server, they are two separate items. If you are using Microsoft SQL Server, you must create a user with the same name as the Model Data Schema, and grant the Model Data Schema access to that user. The grants on system-generated views made by Profitability and Cost Management reference the Model Data User. The synonyms that are created go into the Model Data Schema.

For SQL Server, references to the Model Data Schema in the Profitability and Cost Management product and documentation refer to either the schema, or the user, or both.

Note:

SQL Server: You must create the measure columns on the destination stage table and lookup tables with 4 or more decimal places to avoid rounding errors.

Caution:

Before you import data or artifacts, you must create a backup of the Model Data Schema. See the Oracle Enterprise Performance Management System Backup and Recovery Guide