Creating a New Business Area Definition and Instance

When you select Create a new Business Area definition and instance in the Create Business Area screen, additional fields appear.

1. Enter values in the following fields:

   • Name. See Naming Objects.

     Note:

     For OBIEE Business Areas, the Business Area name is displayed in the OBIEE Answers user interface as the Subject Area.

   • Description. See Creating and Using Object Descriptions.

   • Business Area Type. Select the adapter from the drop-down list.

     If you select GENERIC_VISUALIZATION, you must then enter a schema name for the Business Area. See Defining Generic Visualization Business Areas for more information.

2. In the Classification section, select the following for both the definition and the instance:

   • Subtype. Select a subtype according to your company's policies.

   • Classification Values. See Classifying Objects and Outputs for instructions.

3. Click Apply to save your work and continue defining the Business Area.

   The system opens the Properties screen for the new Business Area instance.

4. Define the Business Area details. For information and instructions see:

   • Defining Table Descriptors

   • Defining Joins

   • Defining Business Area Hierarchies

   Note:

   A Generic Visualization Business Area does not contain Joins, Hierarchies, Source Code, or Parameters.

5. Click Check In. The system checks in Version 1 of both the Business Area definition and instance.
6. Install the Business Area instance (see Using, Installing, and Cloning Work Areas). On creation of the Generic Visualization Business Area, its status is 'Not Installable'.

   Note:

   When installing a GVA Business Area instance, a database schema is created. The schema name is an attribute of the Generic Visualization Business Area instance and its default value is the Business Area instance name. The schema name must be unique within the Oracle LSH installation. If the name is not unique, Namings' uniqueness rule appends _n to the schema name; where n is the next non-unique integer. If a schema name is not unique, the installation fails.

7. Validate both the definition and the instance according to your company's policies.