Physical Layer

The Physical layer contains the metadata of Oracle ADF View objects and Essbase Cubes used for building Transactional Business Intelligence business model. See Modeling Essbase Cubes for Essbase connection details.

In accordance with the Oracle Fusion applications deployment model, Transactional Business Intelligence uses three database connections of type Oracle ADF in this layer. Financials, Oracle Fusion Supply Chain Management Connection Pool, Projects, and Incentive Compensation use the FSCM connection. For more information on Oracle Fusion applications, see the Oracle Fusion Applications Help.

Figure 2. Transactional Business Intelligence Oracle ADF Connections in the Physical Layer

This screen shot displays the Transactional Business Intelligence Oracle ADF Connections in the Physical Layer.

Figure 3. Financials and Supply Chain Management Oracle ADF Connection Properties

This screen shot displays the Supply Chain Management Oracle ADF Connection Properties.

Each connection has one connection pool containing Oracle ADF server connection information, such as application server, application module name, and user information. Oracle BI Server uses this information in connecting to the data source.

Figure 4. Connection Pool – General Tab

This screen shot displays the Connection Pool – General Tab and the associated fields to complete.

Setting SQL Bypass Database

Note:

Setting up an SQL Bypass Database is required.

Setting the SQL Bypass Database option is an important feature for Transactional Business Intelligence. Setting a value for this property allows Oracle BI EE to extract the underlying SQL of view objects and send it directly to the database for execution, eliminating the extra processing overhead that may come by going through the Oracle ADF view object layer and then to the database. Figure 5, Diagram of SQL Bypass Functionality illustrates how query execution works in Transactional Business Intelligence.

Figure 5. Diagram of SQL Bypass Functionality

The diagram shows the SQL Bypass Functionality architecture.

Note:

Setting up an SQL Bypass Database is required.

  To set the SQL Bypass Database option:

  1. Create a database connection pointing to an Oracle Fusion application database in the physical layer.

  2. Open the connection pool from Transactional Business Intelligence database connection.

  3. Select the Miscellaneous tab.

  4. Select Set.

    Available database connections are displayed.

  5. Select the database connection that is pointing to the Fusion Applications database, as shown in Figure 6, Connection Pool Miscellaneous Tab.

  6. Select OK.

Figure 6. Connection Pool Miscellaneous Tab

This screen shot displays the Connection Pool – Miscellaneous Tab and the associated fields to complete.

See the “Oracle Fusion Middleware Developer's Guide for Oracle Business Intelligence Enterprise Edition” for more information on options available in the connection pool screen. Each connection has all the view objects and corresponding alias objects that are used in building the business model.

View objects are named using the following convention, which can help in tracking back to the corresponding module in Oracle Fusion applications:

Global Application Module Name. Sub-Application Module Name.view object-Name.

For example:

HCMTopModelAnalyticsGlobalAM.AnalyticsServiceAM.CurrenciesPVO, where

HCMTopModelAnalyticsGlobalAM is the application module name,

AnalyticsServiceAM is the sub-application module name, and

CurrenciesPVO is the view object name.

Similarly, all the alias physical tables are named as <Dim/Fact>__VO-Name_Role.

Figure 7. View Objects and Aliases in a Connection

This screen shot displays the view objects and alias in a connection.

You can see attributes in a view object by expanding the view object in the physical layer. Attribute names are the same as in the underlying view object in Oracle ADF. The relationship between Oracle ADF view objects is created using Oracle ADF view links component. View links are modeled as physical joins in Oracle BI EE. Finding the join between view objects in the Oracle BI repository is the same as finding the physical join between tables. Figure 8, View Link Between View Objects displays a physical join between view objects using a view link.

Figure 8. View Link Between View Objects

This screen shot displays the complex join View Link between view objects.