Planning the Bridge Implementation

In This Section:

Determining the Data Region of the Financial Management Application

Determining the Type of Bridge Target Database

About Financial Management Application Snapshots

Overview of Creating a Bridge for the First Time

Determining the Data Region of the Financial Management Application

A region defines a Financial Management application data set. Regions are used to limit the Financial Management data set that is extracted into Data Synchronization Server. Regions are also used to limit the data set that is copied from Data Synchronization Server to an Essbase replication partition database and to limit the data set that is extracted to RDBMS database tables.

About Region Types

Types of regions:

  • Default region—Named Default, this predefined region consists of non-aggregated Financial Management application data only. The default region is automatically created when a Financial Management application is added to a Analytics Link Server in the Analytics Link Servers node.

    The default region can only be viewed and cannot be edited or deleted. If the Default region does not suit your reporting needs, create a user-defined region.

  • User-defined regions—In a user-defined region, you specify the Financial Management application data set. User-defined regions are helpful for limiting the amount of Financial Management data that Analytics Link accesses. You can create multiple user-defined regions for the same Financial Management application.

See:

About Dimension Selection Types and Member Selection

A region includes all 12 Financial Management dimensions; however, the members that are extracted from each Financial Management dimension into Data Synchronization Server depend on the dimension selection type and member selection specification.

For the Default region, Table 6 lists the predefined selection type and member selection specification for each Financial Management dimension:

Table 6. Default Region Definition

HFM DimensionSelection TypeMember Selection
YearALL[empty]
ScenarioALL[empty]
EntityALL[empty]
PeriodBASE[empty]
ICPBASE[empty]
ValueBASE_AND_CONSOLIDATED[empty]
Custom1BASE[empty]
Custom2BASE[empty]
Custom3BASE[empty]
Custom4BASE[empty]
ViewMEMBERSPeriodic
AccountBASE[empty]

For a description of dimension selection types, see Adding a User-Defined Financial Management Application Data Region.

Analytics Link handles region member selection specifications based on whether you are creating the Data Synchronization Server database or extracting data to an RDBMS database.

  • On the Data Synch tab, you select a region when creating the Data Synchronization Server database.

    In extracting Financial Management application data to Data Synchronization Server, Analytics Link extracts data for the Year and Scenario dimensions based on the dimension selection type and member selection specification.

    For example, in the Default region, the selection type for the Year and Scenario dimensions is ALL; therefore, all data from those dimensions is extracted. However, assume that you select a user-defined region in which the Year dimension selection type is MEMBERS and the specified members are 2009 and 2010. Analytics Link extracts only those members from the Year dimension.

    For all dimensions other than Year and Scenario, Analytics Link ignores the selection type and member selection specification and extracts all Financial Management application data into Data Synchronization Server.

    For example, for the View dimension in the Default region, the selection type is MEMBERS and the specified member is Periodic. Analytics Link extracts all members from the View dimension, not just the Periodic member.

    See Creating the Data Synchronization Server Database for the Bridge.

  • On the Extract tab, you select a region when extracting data to an RDBMS.

    For all dimensions, Analytics Link extracts the data based on the dimension selection type and member selection specifications.

    For example, for the View dimension in the Default region, Analytics Link extracts only the Periodic member.

    See Extracting Financial Management Data and Metadata to an RDBMS Bridge Target.

Determining the Type of Bridge Target Database

The bridge target is either an Essbase or RDBMS database:

  • Essbase—When the bridge target is Essbase, the bridge acts as a link between the Financial Management application and the Essbase database. Analytics Link creates the Essbase database.

    The Essbase partition type determines whether Financial Management application data is stored in Data Synchronization Server or copied to the Essbase database:

    • Essbase transparent partition—Financial Management application data that was extracted to Data Synchronization Server remains in Data Synchronization Server. Essbase queries are served from Data Synchronization Server, not Essbase.

    • Essbase replicated partition—Financial Management application data that was extracted to Data Synchronization Server is copied to the Essbase replicated partition database. Essbase queries are served from the Essbase database, not Data Synchronization Server.

      The Essbase partition type is set on the Essbase tab. See Setting Essbase Database Connection Types.

  • RDBMS—When the bridge target is RDBMS, you can extract Financial Management application data that was extracted to Data Synchronization Server to an existing RDBMS database.

About Financial Management Application Snapshots

In Analytics Link, a snapshot is a complete copy of the data and metadata of a Financial Management application. You define a snapshot when you add a Financial Management application to a Analytics Link Server. See Adding a Financial Management Application.

You can add multiple instances of the same Financial Management application by providing a different snapshot name in the Financial Management application definition. The snapshot name is displayed in brackets after the application name. Figure 2, Snapshots of the Same Financial Management Application shows three instances of the TOTCONSOL application: TOTCONSOL [Default], TOTCONSOL [Jan_begin_data], and TOTCONSOL [Jan_end_data].

Figure 2. Snapshots of the Same Financial Management Application

This image shows the tree hierarchy of the Analytics Link Servers node, as described in the text preceding the image.

Snapshots are useful for working with different instances of the same Financial Management application and archiving Financial Management applications.

Multiple bridges that use the same Financial Management application: For example, assume Financial Management and Oracle Hyperion Planning users need to run reports against the same Financial Management application.

  • Financial Management users need to run live reports against the bridge target database at anytime; therefore, changes to the data in the Financial Management application must be synchronized with Data Synchronization Server on a continual basis.

    In the bridge for this scenario, you would set an interval for the Data Update Agent to automatically synchronize changes to the Financial Management application data with Data Synchronization Server.

  • Planning users need to run reports against the bridge target database, but the Financial Management administrator wants to control when Planning users see the Financial Management application data. Therefore, changes to the data in the Financial Management application can be synchronized with Data Synchronization Server on demand, before Oracle Hyperion Planning users need to run reports.

    In the bridge for this scenario, you would run the Data Update Agent manually.

Archiving Financial Management applications: Analytics Link snapshots simplify the process of archiving Financial Management applications. A snaphot is a static copy of the state of a Financial Management application at the time the snapshot was created in Analytics Link. From a snapshot, you can create an Essbase database, based on the Financial Management application snapshot, at any time.

Overview of Creating a Bridge for the First Time

  To create a bridge for the first time:

  1. Start Analytics Link components and the Oracle products that work with Analytics Link.

    See Startup Order of Oracle Products.

  2. Add a Analytics Link Server to the Analytics Link Servers node, and define a bridge.

    See Adding Components to an Analytics Link Server.

  3. Create the Data Synchronization Server database for the bridge.

    See Creating the Data Synchronization Server Database and Synchronizing Data.

  4. Set the properties for the bridge target database.

    See Setting Target Database Properties.

  5. Design the grid for the bridge target database.

    See Designing the Target Database Grid.

  6. Create an Essbase target database, or extract data to an RDBMS database.

    See: