Obiee Dbi Whitepaper

Building Oracle Daily Business Intelligence Dashboards with Oracle BI Enterprise Edition Whitepaper August, 2006

Building DBI Dashboards with OBIEE

EXECUTIVE OVERVIEW This white paper presents a case study of building dashboards on top of the Oracle Daily Business Intelligence (DBI) summary tables using Oracle BI Enterprise Edition (OBIEE). It provides an example of what is possible when we combine the flexibility and configurability of OBIEE platform with the traditional benefits of DBI, such as low cost of ownership.

INTRODUCTION Until now, the focus of DBI had been to provide a comprehensive set of pre-packaged dashboards and reports with tight integration to transactional applications. The flexibility of the pre-delivered dashboards, on the other hand, had been somewhat limited.

With the advent of OBIEE, we will be able to combine the richness of pre-packaged DBI content with the configurability and ad hoc capabilities of this powerful BI platform to deliver a comprehensive, easy-to-implement, tightly integrated, and highly flexible reporting solution for Oracle EBS customers.

Empower DBI customers with the flexibility and configurability of OBIEE

BEFORE YOU START This white paper assumes working knowledge of major components of OBIEE (Repository, Answers, and Dashboard), Oracle DBI, and understanding of the data model for certain Oracle EBS transactional modules.

The following resources are available for reference:

• Oracle University OBIEE Instructor-led Training (http://education.oracle.com)

• OBIEE On-line Documentation

• Oracle DBI Users Guide and Implementation Guide

• Oracle eTRM

PROFIT & LOSS CASE STUDY

Summary The sections below discuss the high-level steps taken to build an OBIEE P&L dashboard against the DBI for Financials summary tables and dimensions. It also

Building Oracle Daily Business Intelligence (DBI) Dashboards with Oracle BI Enterprise Edition Page 2

http://education.oracle.com/

provides general guidelines and pointers for those who may want to build OBIEE dashboards against other DBI content areas.

Steps to Build OBIEE Dashboard for DBI

To build an OBIEE dashboard, one first needs to create metadata in the OBIEE Administration tool (.RPD file) to model the relevant physical and logical data entities. Afterward, we will need to use OBIEE Web to create reports based on the metadata and assemble them into a Dashboard (webcat file).

The major steps for creating OBIEE dashboards are:

1. Create database connection; 2. Create the physical layer by importing the tables from EBS database 3. Create the business model layer 4. Create the presentation layer 5. Build a dashboard. 6. Publish the repository to the web.

Step 1 – Create database connection

We first need to create a connection to the Oracle EBS database. In this case, we connect to the database using ODBC

Subsequently, we need to create a new Physical Database. To do so, right click on the Physical layer in the Administration tool. Enter name and choose Oracle 9i/10g as the Database as shown below


In this case study, a small subset of the E-Business Suite (EBS) objects, such as materialized views and tables, were identified and imported into the Physical layer of OBIEE. Please note that all objects in EBS database are visible in the APPS schema. All connections should be done within that schema.

Please refer to the section in the OBIEE Server Administration guide titled – ‘Creating and Administering the Physical Layer in a Repository’ for additional information.

Step 2: Create Physical Layer

In the Administration tool, go to File->Import from Database to import all the necessary database tables and views. In the appendix, we’ve listed the major objects used in the P&L case study.

Please note that the DBI framework is tightly coupled with the Oracle EBS transactional applications. Many reference objects used within DBI come directly from transactional tables or views. Thus, many transactional entities will need to be brought into the physical layer.


Save all the entities in the Physical Schema folder named after the APPS schema. Then, please organize the entities into groupings using Physical Display folders as you see fit. Objects stored in the display folders appear as links (shortcuts) to objects in physical schema folder. The screenshot below shows the entities used for the P&L case study.

Next, you can set up the connection pools. Click on Connection Pools->Add to launch the Connection Pools dialog box. Enter user name and password for the


Apps schema and provide the tnsnames.ora entry. Please refer to the section in the OBIEE Server Administration guide titled – ‘Creating and Administering the Physical Layer in a Repository’ and ‘Query Caching in Siebel Analytics Server’ for additional information on connection pools. After importing the metadata to create the Physical layer, we now need to identify the key joins between the tables or views. Right click the ‘Physical’ pane of the OBIEE Administration tool. Select the ‘Physical Diagram->Objects and all joins’ option to launch the ‘Physical Diagram’ window. Create the foreign key joins between the Fact and Dimension tables. The screenshot below shows some of the physical table joins used for the Profit and Loss dashboards.

Step 3 - Create Model Business Layer

After the Physical layer is created, we are now ready to create the Business Model. We recommend creation of a business model for each functional data mart, and then dragging all relevant objects from the physical schema folder into the business model. Afterwards, rename the tables and columns to more meaningful names. Complex joins are recommended in Business Model layer. However, logical key/foreign key joins that are automatically created when tables are dragged from the physical layer are not recommended to use. Usage of physical joins in the Business Model layer could lead to erroneous results when the logical folder is mapped to multiple physical folders. We recommend deleting the foreign key joins that are copied automatically from the Physical layer as those can sometimes yield erroneous results. Re-create the joins manually between the logical entities in the Business Model. Create hierarchies for each dimension. All hierarchies should have a single root level but can have multiple branches, each branch representing a drill-path in the tree. Each level in the hierarchy should contain a unique key and all columns in a hierarchy should come from one logical table. Each level should be associated with at least one column, except the Grand Total level.


The following screenshots below show the business model diagram between a subset of tables used in the case study.

The screenshot below shows the business model and mapping layer created for the case study.


Please refer to the section in the OBIEE Server Administration guide titled – ‘Creating and Administering the Business Model and Mapping Layer in a Repository’ for additional information.

Step 4 - Create User Presentation Layer

The Presentation Layer controls what users will see in OBIEE Web when building Dashboards and Answers. We recommend creating one Presentation Catalog for each major functional analysis area such as P&L or Procurement and include relevant objects from the business model layer. Please repeat common dimensions in each Presentation Catalog as necessary. For example, Supplier dimension can be included in both Procurement and Payable Presentation Catalog. We also recommend including only columns that can be displayed in an Answer or report or used for drilldowns. For example, it is probably not necessary to include


“internal ids” or “who” columns if they are not going to be used for reporting. The diagram below shows the Presentation Layer created for the P&L case study.

Please refer to the section in the OBIEE Server Administration guide titled – ‘Creating and Maintaining the Presentation Layer in a Repository’ for additional information.

Step 5 - Compose "P&L" Dashboard

Prior to building the Dashboard, please make sure that the repository file (.RPD file) is consistent and the OBIEE server is able to start. Please also verify that the repository file name is listed in the NQSConfig.INI file in the SiebelAnalytics\Config folder before starting the OBIEE server. The screenshot below depicts the ‘P&L’ Dashboard page built in this case study.


Within traditional DBI dashboards, the behavior and interaction of parameters such as “As of Date” and “Compare To” are somewhat different from typical ad hoc BI reports or dashboards. The ability of going back into history to view data as of any date is also unique. As shown in the P&L Dashboard above, it is possible to achieve similar parameter behavior using OBIEE. However, users would need to leverage more sophisticated features, such as fragmentation, as well as build additional custom bridge tables when developing their Business and Physical layers, which may lead to a more complex model within their OBIEE metadata. Obviously, users have the flexibility in OBIEE framework to follow simpler parameter behavior if they so choose. The displayed P&L Dashboard has associated drilldown reports for further detailed analysis, as shown below:


Before building an OBIEE Dashboard, users need to first compose a library of reports, or “Answers”, which serve as components in the Dashboard. To build Answers, start with the associated Subject Area in OBIEE Web and select pertinent columns and metrics. Arrange the columns, add parameters or filters, and compose graphs as desired. Compose all the Answers needed for your Dashboard. Subsequently, navigate to Admin-> Manage Intelligence Dashboards to create a new Dashboard. Start adding ‘Sections’ from the left hand panel on a page. Each of these sections will have an Answer or a Prompt (parameter). The screenshot below depicts one of the P&L pages in edit mode.


Please note that native OBIEE features such as gauge style graphs, scrolling billboards, and color coding, previously not available in traditional DBI content, can now be easily leveraged by DBI customers. Please refer to the OBIEE Web Administration guide for additional information on creating Answers and Dashboards.

Step 6: Publish Repository to the Web

At this point, you are ready to deploy the .RPD and .WEBCAT file to the OBIEE server. Please follow the following steps:

• Shutdown the OBIEE services • Copy the .RPD and .WEBCAT file to proper folders • Update the ‘REPOSITORY’ section of ‘SiebelAnalytics\Config\

NQSConfig.INI’ file with .RPD file name • Update ‘SiebelAnalyticsData\Web\config\instanceconfig.xml’ file with the

.WEBCAT file name • Start the Web server and the OBIEE services.

Security Generally, it’s necessary to consider a couple points to properly secure data. First is access security, namely, controlling which users have access to which Subject Areas, Answers, and Dashboards. Second is data security, which has to do with controlling which subset of data can be viewed by a given user.


OBIEE has strong functionality to enable both access and data security. Administrators can group Dashboards, Answers, or content in Functional Areas into proper functional grouping and assign these to individual users for access control. One can also enable the data security used in DBI through use of proper filter conditions with OBIEE metadata. Please refer to chapter 7 (Managing Siebel Analytics Web Security) in the Siebel Analytics Web Administration Guide and chapter 17 (Creating and Administering the Physical Layer in Repository) in the Siebel Analytics Server Administration Guide for more details.

Performance and Summarization Performance is always one of the top concerns for a BI solution. To enhance the performance of dashboards built against DBI, it is possible to leverage existing DBI summarization within OBIEE. DBI base summaries are typically at transactional granularity. MV's are used to summarize data to along various dimensional hierarchies to enable better performance during dashboard runtime. OBIEE has query re-direction features. By incorporating DBI summary MV’s into the Physical and Business layer and properly establishing the granularity and mapping, OBIEE can make intelligent decisions at runtime to re-direct queries against summary MV’s depending on the specific report being run.

Including New Attributes and Metrics Within the existing DBI framework, it has been fairly challenging to bring in additional attributes or metrics into existing DBI dashboards. However, by combining the flexibility of OBIEE with DBI’s design principle of tight OLTP integration, it becomes much easier to incorporate additional dimensional attributes or metrics from the EBS transactional system. As mentioned before, most DBI base summaries are at the transactional level. In fact, they generally carry unique transactional ID’s. Using the ad hoc capabilities of OBIEE, one can easily join back to EBS transactional tables to pull in additional attributes. For example, the Payables Invoice Summary within DBI (FII_AP_INVOICE_B) can be joined back to the Invoice Header table within EBS (AP_INVOICES_ALL) by Invoice Id to expose additional transactional attributes, metrics, and even Descriptive Flexfield columns.

LOOKING FORWARD As implied in the paper, the future direction of DBI is to integrate with the OBIEE framework. The upcoming releases of DBI will gradually provide pre-packaged OBIEE Business and Physical layers so DBI customers can easily leverage features illustrated in this case study. Existing pre-built dashboards will also be converted from the current Performance Management Viewer/Framework to OBIEE.


As we integrate DBI with the OBIEE technology, customers will be empowered with a BI solution that is extremely flexible and extensible as well as rich in content, easy to implement, and tightly integrated with their transactional systems.


APPENDIX Below tables list available Facts and Dimensions in the E-Business Suite Intelligence (DBI) product family

APPENDIX A. – FACT TABLES

Product Suite Analytic Component Fact Table/Base Summary Table Physical Table Name Grain Statement Description/Comments

Financial DBI

Profit and Loss Payables Expense Fact FII_AP_INV_B One record per invoice expense distribution

This base summary contains expense accounting distributions for AP invoice documents

Payables Payables Invoice Fact FII_AP_INVOICE_B One record per AP invoice This base summary stores AP invoice documents

Payables Payables Payment Schedule Fact FII_AP_PAY_SCHED_B

One record per invoice or payment action

This base summary records all the events or actions that happen against an AP invoice document. Action includes invoice creation, payment, prepayment, discounting, aging, … etc.

Payables Payables Holds Fact FII_AP_INV_HOLDS_B One record per hold This base summary contains the holds placed against invoices

Payables Payables Overlapping Holds Fact FII_AP_HOLD_HIST_B

One record when invoice becomes on hold or gets released considering overlapping hold situation

This base summary is created to resolve overlapping holds. It stores holds in a different way than Payables Holds Fact. It creates one record for hold creation and another record for hold release. For an overlapping set of hold, one record is created

Payables Payables Aging Fact FII_AP_AGING_BKTS_B One record per bucket entered/exited for invoices not yet past due

This base summary is used for the due aging report. It tracks when an invoice enters or exits from one aging bucket

Payables Payabls Past Due Aging Fact FII_AP_DUE_COUNTS_B

One record per bucket entered/exited for invoices past due

This base summary is used for the past due aging report. It tracks when an invoice enters or exits from one aging bucket

Profit and Loss AR Revenue Fact FII_AR_REVENUE_B One record per <transaction_class, line_id, gl_date, code_combination_id>

This base summary contains revenue accounting distributions for AR invoice documents


Profit and Loss General Ledger Fact FII_GL_JE_SUMMARY_B

One record per combination of following dimensionality: - Company or balancing segment - Cost Center - Natural Account - User segment 1 (any additional segment in chart of account per user setup) - User segment 2 (any additional segment

This base summary store aggregation of profit and loss information. In other words, revenue, expense, and COGS information

Profit and Loss Budget Fact FII_BUDGET_BASE

One record per combination of following dimensionality: - Budget/Forecast version - Company or balancing segment - Cost Center - Natural Account - User segment 1 (any additional segment in chart of account per user setup)

This base summary stores budget and forecast for revenue, expense, and COGS

Receivables Receivables Adjustment Fact FII_AR_ADJUSTMENTS_F One record per invoice adjustment This base summary stores invoice adjustments

Receivables Dispute Fact FII_AR_DISPUTE_HISTORY_F One record per change in dispute

This base summary stores customer disputes against invoices

Receivables Payment Schedule Fact FII_AR_PMT_SCHEDULES_F

One record per transaction installment/payment schedule

This base summary stores invoice installments (ie payment schedules)

Receivables Receipt Application Fact FII_AR_RECEIPTS_F

One record every time an payment was applied to an invoice

This base summary stores applications of checks or payments against an invoice.

Receivables Transaction Fact FII_AR_TRANSACTIONS_F One record per AR transaction This base summary stores AR invoice documents

Receivables Aging FII_AR_AGING_RECEIVABLES Capture receivables in aging buckets

This base summary is used for the AR aging report. It tracks when an invoice enters or exits from one aging bucket

Receivables Receipt Aging FII_AR_AGING_RECEIPTS

Capture unpaid/unapplied receipts and their age

This base summary is used to track the aging of unapplied or unpaid receipts. It tracks when a receipt enters or exists from aging buckets

Receivables Dispute Aging FII_AR_AGING_DISPUTES Aging of disputes for open receivables

This base summary is used to track the aging of disputes for those invoices which were not yet paid


Human Resource DBI Workforce Assignment Events HRI_MB_ASGN_EVENTS_CT

One record per event per assignment (relevant assignment change, salary change, performance band, length of service band, ABV change, person type change) Work related information

Workforce

Assignment and Manager Hierarchy Events HRI_MAP_SUP_WRKFC_ASG

One record per event per assignment per manager (assignment events and manager hierarchy changes above the assignment)

Derived fact based on Assignment Events and Events generated from manager hierarchy changes

Absence Absence HRI_MB_UTL_ABSNC_CT One record per absence occurrence perday Absence related information

Benefits Enrollment Action HRI_MB_BEN_ENRLACTN_CT

One record per enrollment action transaction Enrollment action related transaction information

Benefits Eligibility & Enrollment Event

HRI_MB_BEN_ELIGENRL_EVNT_CT

One record per eligibility or enrollment event transaction Eligibility or enrollment event information

Benefits Election Events HRI_MB_BEN_ELCTN_EVNT_CT

One record per Election transaction Election information

Supply Chain DBI

Supply Chain

Activity Fact BIV_DBI_ACTIVITY_SUM_F

Activity Date level Customer Support Management: This contains counts of first opened, reopened and closed service requests (SR) for every activity date

Supply Chain

Resolution Fact BIV_DBI_RESOLUTION_SUM_F

Service request level Customer Support Management: This contains time taken to resolve a SR and SLA related related information for a SR

Supply Chain

Closure Fact BIV_DBI_CLOSED_SUM_F

Service request level Customer Support Management: This contains time taken to close a SR ,closed date etc.,

Supply Chain

Backlog Fact BIV_DBI_BACKLOG_SUM_F

Service request level Customer Support Management: This contains severity, status, urgency, channel, customer, etc related information for Backlog Srs

Supply Chain

Delivery Details Fact ISC_DBI_DEL_DETAILS_F Delivery detail level

Warehouse Management and Transportation Management: It contains the pick-released quantity, ship-confirmed quantity in primary uom, among other delivery detail-level information.

Supply Chain

Tasks Fact OPI_DBI_WMS_TASKS_F Organization- SubInventory - Item - Pick Completion Date

Warehouse Management: This contains the details of all the pick tasks in the warehouse by Subinventory and Item.


Supply Chain

Operations Fact OPI_DBI_WMS_OP_F Organization- SubInventory - Item - Operation Plan Id

Warehouse Management: This contains data pertaining to Operation Plans in the warehouse at the Operation Plan Instance Level.

Supply Chain

Receipt to Putaway Fact OPI_DBI_WMS_RTP_F Task Id - Organization - Subinventory - Item

Warehouse Management: This contains Receipt to Putaway Cycle Time information.

Supply Chain

Current Capacity Utilization Fact

OPI_DBI_WMS_CURR_UTZ_ITEM_F

Organization- Subinventory- Inventory Category- Item

Warehouse Management: This contains information on weight and volume of items stored in WMS enabled organizations and the individual subinventories in those organizations.

Supply Chain

Current Subinventory Utilization Fact

OPI_DBI_WMS_CURR_UTZ_SUB_F Organization- Subinventory

Warehouse Management: This contains weight and volume that can be stored in WMS enabled organizations and the individual subinventories in those organizations.

Supply Chain

Exceptions Fact OPI_DBI_WMS_EX_F Organization- SubInventory - Item - Operation Plan Id

Warehouse Management: This contains the details of all the exceptions created in the warehouse by pick tasks and operation plans, and the reasons for the exceptions.

Supply Chain

Item capacity UOM Conversion Fact

OPI_DBI_WMS_STOR_ITEM_CONV_F Organization - Item

Warehouse Management: This contains conversion rates of various item physical attributes such as weight/volume etc. from the item specific units of measure to the corresponding DBI reporting units of measure.

Supply Chain

Field Service Task Backlog Fact ISC_FS_TASK_BACKLOG_F task id, from/to date

Field Service Management: This contains data on Field Service Task Backlog movement.

Supply Chain

Field Service Task Assignments Fact

ISC_FS_TASK_ASSIGNMNTS_F Task Assignment id

Field Service Management: This Contains data for Field Service Task Assignments relating to Dispatch Tasks.

Supply Chain

Field Service Activity Fact ISC_FS_TASK_ACTIVITY_F task id

Field Service Management: This contains information Field Service Task Activity.

Supply Chain

Field Service Tasks Fact ISC_FS_TASKS_F Task id, activity date Field Service Management: This contains data for Field Service Dispatch Tasks.

Supply Chain

Field Service Inventory Usage Fact ISC_FS_INV_USG_VALUE_F Organization, subinventory, item

Field Service Management: This contains data on Field Service inventory usage transactions for all Field Service Usable subinventories at the organization, subinventory, transaction date and inventory item level.

Supply Chain

Field Service Capacity Fact ISC_FS_CAPACITY_F task_id, OBJECT_CAPACITY_ID

Field Service Management: This contains data for Field Service Trip Tasks.


Supply Chain

Contract Measures Fact OKI_DBI_CLE_B Contract covered line level

Service Contracts and Service Renewals Management: This contains measures at the contract covered line level.

Supply Chain

PO Distribution Fact POA_DBI_POD_F PO Distribution PO Distribution base summary table

Supply Chain

Receiving Transactions Fact POA_DBI_RTX_F Receiving Transactions Receiving Transactions base summary table

Supply Chain

Requisition Lines Fact POA_DBI_REQ_F Requisition Lines Requisition Line base summary table

Supply Chain

Bookings Fact ISC_BOOK_SUM2_F Order line level

Base summary table for the Customer Fulfillment Management page and Shipping Management page. It is built on the OE_ORDER_LINES_ALL table. It contains the following dimensions: header functional currency, organization functional currency, customer, item, organization, return reason, and time. It contains the following amounts in the global (primary and secondary) currency and organization functional currency: backlog value, booked value at selling price, fulfilled value, invoice value, return value, and shipped value, among other line-level information.

Supply Chain

Shipping Past Due Schedule Fact ISC_BOOK_SUM2_PDUE_F Snapshot and order line level

Base summary table for past due information on the Shipping Management page. This table stores current past due quantity and days late according to the scheduled shipment date. It stores the information in snapshots at the line level.

Supply Chain

Past Due Schedule/Promise Fact ISC_BOOK_SUM2_PDUE2_F Snapshot and order line level

Base summary table for past due information on the Customer Fulfillment Management page. This table stores current past due amounts and days late according to the scheduled shipment date and the promised date. It stores the information in snapshots at the line level. It contains current past due amounts in the global (primary and secondary) currency and organization functional currency.

Supply Chain

Backorders Fact ISC_BOOK_SUM2_BKORD_F Snapshot and order line level

Base summary table for backorder information on the Shipping Management page. This table stores current backorder quantity and days late according to the scheduled shipment date and request date. It stores the information in snapshots at the line level.

Supply Chain

Sales Credits Fact ISC_SALES_CREDITS_F Sales credit level

Base summary table for Product Revenue Bookings and Backlog Page. It is built on OE_SALES_CREDITS. It only contains the resource dimension. It contains the sales credit distribution amounts (as a percent) for each sales


representative for each order line that appears in ISC_BOOK_SUM2_F. It also contains various sales credit attributes such as sales credit type and the sales group of the sales representative.

Supply Chain

Delivery Details Fact ISC_DBI_DEL_DETAILS_F Delivery detail level

Base summary table for Warehouse Management page and Transportation Management page. It is mainly built on WSH_DELIVERY_DETAILS, WSH_DELIVERY_ASSIGNMENTS and WSH_NEW_DELIVERIES tables. It contains the following dimensions: item, subinventory, organization, shipment direction and time. It contains the pick-released quantity, ship-confirmed quantity in primary uom, among other delivery detail-level information.

Supply Chain

Delivery Legs Fact ISC_DBI_DEL_LEGS_F Delivery leg level

Base summary table for Transportation Management page. It is mainly built on WSH_DELIVERY_LEGS table. It contains the following dimensions: organization, shipment direction, carrier, mode of transport, service level and time. It contains the rated freight cost, gross weight in global weight uom and volume in global volume, among other delivery leg-level information.

Supply Chain

Trip Stops Fact ISC_DBI_TRIP_STOPS_F Trip stop level

Base summary table for Transportation Management page. It is mainly built on WSH_TRIP_STOPS table. It contains the following dimensions: carrier, mode of transport, service level and time among trip stop-level information.

Supply Chain

Freight Invoices Fact ISC_DBI_FTE_INVOICES_F Freight invoice level

Base summary table for Transportation Management page. It is built on FTE_INVOICE_HEADERS table. It contains the following dimensions: carrier, mode of transport, service level and time. It contains the following amounts in the global (primary and secondary) currency: billed amount, approved amount, among other invoice header-level information.

Supply Chain

Email Measures Fact BIX_EMAIL_DETAILS_F Agent, Classification, Account, Customer

Fact table for the Email Center Management page. This contains email measures at day level. The information is also rolled up to higher time dimension levels.

Supply Chain

Call Measures Fact BIX_CALL_DETAILS_F Agent, Classification, Account, Customer, Dialed Number

Fact table for the Inbound Telephony Management page. This fact contains call measures at day level. The information is also rolled up to higher time dimension levels. Stores both positive response measure and inbound telephony measures

Supply Chain

Agent Session Measures Fact BIX_AGENT_SESSION_F Agent

Fact to store agent session measures at day level. The information is also rolled up to higher time dimension levels.


Supply Chain

Supplies Fact ISC_DBI_SUPPLIES_F Plan snapshot, month, inventory organization, item, and supplier level

Base summary table for the Plan Management page, built mainly on MSC_SUPPLIES table. The base table contains the following dimensions: item, supplier, organization, plan snapshot, and time. It also contains the purchasing cost in the global (primary) currency and organization functional currency.

Supply Chain

Maintenance Work Order Costs Fact ISC_MAINT_WO_CST_SUM_F

work order id, organization, department, cost category id

This is the Work Order Cost base summary table. It stores summary of Actual and Estimated Cost for Completed Work Orders. These costs are in base currency together with the conversion rates for primary and secondary global currencies. Normally this table would only contain rows for completed work orders, however, if a work order is subsequently "uncompleted", the rows will remain but the completion date will be NULL. Costs are aggregated to Cost Category and unique operation Department for a Work Order

Supply Chain

Maintenance Work Orders Fact

ISC_MAINT_WORK_ORDERS_F work order id, organization

Base table of eAM maintenance work orders

Supply Chain

Maintenance Request to Completion Fact ISC_MAINT_REQ_WO_F

request id, work order id, organization, department

This is the Requested Work Order base fact table. It stores one row for each Work Request or Service Request associated with a Work Order. If all Work Orders associated the Work Request (can be no more than one) or Service Request (can be multiple), the row for the last completed Work Order will have COMPLETION_DATE, RESPONSE_DAYS, COMPLETION_DAYS and WORK_ORDER_COUNT populated

Supply Chain

Maintenance Labor Backlog Fact ISC_MAINT_LAB_BLG_F

work order id, operation, resource, department

This is the Labor Backlog Base Table. It stores instances of labor backlog i.e. when hours required is greater than the hours charged along with the associated workorder, resource, department and organization

Supply Chain

Maintenance Asset Downtime Fact ISC_MAINT_ASSET_DOWN_F asset_status_id

This is the Asset Downtime Base Table. It stores instances where an asset was down due to the work order, work order operation and manual shutdown. The table stores the asset related parameters of asset criticality, category, group and owning department and organization in a demoralized form along with the shutdown start and end dates of the asset

Supply Chain

Repair Orders Fact ISC_DR_REPAIR_ORDERS_F REPAIR_LINE_ID Contains Depot Repair orders

Supply Chain

Repair Orders Mean Time to Resolve Fact ISC_DR_MTTR_F REPAIR_LINE_ID Mean Time to resolve Depot Repair Fact table


Supply Chain

Repair Orders Cost Fact ISC_DR_COSTS_F REPAIR_LINE_ID Depot Repair Costs fact table

Supply Chain

Manufacturing Jobs Fact OPI_DBI_JOBS_F

Manufacturing Jobs Fact - One record for each job created.

Fact Table for Jobs Master ETL

Supply Chain

Manufacturing Cost Variance Fact OPI_DBI_MFG_CST_VAR_F

Manufacturing Cost Variance Fact - One record for each closed job. Fact Table for storing the total actual cost,

standard cost and the variance.

Supply Chain

Material Usage Actuals Fact

OPI_DBI_JOB_MTL_DETAILS_F

Material Usage Actuals Fact - One record per component per date used for a job. Base Table for extracting Material Usage by

Assembly and Component.

Supply Chain

Current Unrecognized Variance Fact

OPI_DBI_CURR_UNREC_VAR_F

Current Unrecognized Variance Fact - One record per open job Fact Table for Current Unrecognized Variance

ETL

Supply Chain

WIP Completions Activity Fact OPI_DBI_WIP_COMP_F

WIP Completions Activity Fact - One record per Product Completion per job per date

Stores WIP completion activity

Supply Chain

Scrap Fact OPI_DBI_WIP_SCRAP_F

Scrap Fact - One record per Scrap Txn per Job

Stores WIP scrap activity extracted from MMT

Supply Chain

Resource Usage Standards Fact OPI_DBI_RES_STD_F

Resource Usage Standards Fact - one record per resource usage according to routing per job

Resource Standard Usage Fact

Supply Chain

Resource Usage Actuals Fact OPI_DBI_RES_ACTUAL_F

Resource Usage Actuals Fact - one record per resource usage per job Stores transaction details both at Resource and

Job granularity

Supply Chain

Resource Availability Fact OPI_DBI_RES_AVAIL_F

Resource Availability Fact - One record per resource per org per available date

Stores Resource Availability Details.

Supply Chain

Production to Plan Fact OPI_DBI_PTP_PLAN_F

Production to Plan Fact - One record per baseline, per item and per date Base table for baseline, storing relatively frozen

planned production data.

Supply Chain

COGS Fact OPI_DBI_COGS_F

COGS Fact - One record per order line Stores Cost of Goods Sold Values for all Order Lines, Items and Customers.

Supply Chain

Material Usage Variance MV OPI_MTL_VAR_MV_F

This Materialized View is at the item-org-date level.

Stores information for Material Usage Variance by organization, inventory item, and completion date


Supply Chain

Material Usage Variance Actuals MV OPI_MTL_VAR_ACT_MV_F

This Materialized View is at the job-assembly-component-org level.

Stores information for Actual Material Usage by organization, Job, inventory item, and component item

Supply Chain

Inventory Value Summary Fact OPI_DBI_INV_VALUE_F

One record for each organization, item, transaction_date, subinventory

Inventory Value Summary Fact stores On Hand, WIP and Intransit Inventory transaction summaries.

Supply Chain

Inventory Turns Fact OPI_DBI_INV_TURNS_F One record for each organization, transaction_date

Fact table that stores inventory balances and cost of goods sold for inventory turns reporting.

Supply Chain

Cycle Count Summary Fact OPI_DBI_INV_CCA_F

One record for each organization, subinventory, item, cycle count entry id Fact table that stores inventory cycle count

accuracy and adjustment activity


APPENDIX B. – DIMENSION TABLES

Product Suite Dimension Name Dimension Table Financial DBI

Time dimension

fii_time_day fii_time_week fii_time_ent_period fii_time_ent_qtr fii_time_ent_year

Company dimension fii_company_hierarchies fii_full_company_hiers

Cost center dimension fii_cost_ctr_hierarchies fii_full_cost_ctr_hiers

Customer dimension fii_cust_accounts fii_customer_hierarchies

Party market class dimension fii_party_mkt_class

Operating unit dimension fii_operating_units_v Currency dimension fii_currencies_v

Financial category dimension (Natural Account)

fii_fin_item_hierarchies fii_fin_item_leaf_hiers fii_full_fin_item_hiers

Human Resource DBI Job dimension

HRI_CL_JOB_BX_V HRI_CL_JOB_FAMILY_V HRI_CL_JOB_FUNCTION_V

Organization dimension

HRI_CL_ORG_HR_HX_V HRI_CL_ORG_HRCYVRSN_BX_V HRI_CL_ORG_INHV_H_V

Separation Reason dimension HRI_CL_WAC_SEPCAT_X_V HRI_CL_RSN_SEP_X_V

Position dimension HRI_CL_POSITION_HX_V HRI_CL_POSITION_V

Person dimension

HRI_CL_PER_HX_V HRI_CL_PER_USRDR_H_V HRI_CL_PER_V

Performance Rating dimension HRI_CL_PRFMNC_RTNG_X_V

Training Activity Definition dimension HRI_CL_TRNACT_ACTDEF_V

Workforce Measurement Type dimension HRI_WMT_X

Gender dimension HRI_CL_GENDER_X_V


Grade dimension HRI_CL_GRADE_BX_V

HRI_CL_GRADE_V

Company Cost Center dimension HRI_CL_ORGCC

Supply Chain DBI Call Center BIX_BIS_CALL_CENTER_V

Call Classification BIX_BIS_CALL_CLASSIFICATION_V

Carrier Service Level ISC_CARRIER_SERVICE_LEVEL_V

Commodity POA_COMMODITIES_V

Depot Repair Backlog Distribution Buckets BIV_DR_BKLG_DIST_V

Dialed Number Identification Service BIX_BIS_DNIS_V

Distance UOM BIV_FS_DISTANCE_UOM_LVL_V

Email Account BIX_EMAIL_ACCOUNTS_V

Email Classification BIX_EMAIL_CLASSIFICATIONS_V

Freight Carrier ISC_FREIGHT_CARRIER_V

Inventory Cycle Count OPI_INV_CC_CLS_V

Invoice Creator HRI_CL_PER_V

Maintenance Activity BIV_MAINT_ACTIVITY_LVL_V

Maintenance Asset BIV_MAINT_ASSET_NUMBER_LVL_V

Maintenance Asset Category BIV_MAINT_ASSET_CATEGORY_LVL_V

Maintenance Asset Criticality BIV_MAINT_ASSET_CRITICAL_LVL_V

Maintenance Cost Element BIV_MAINT_CST_ELEMENT_LVL_V

Maintenance Request Type BIV_MAINT_REQUEST_TYPE_LVL_V

Maintenance Work Order Status BIV_MAINT_WO_STATUS_LVL_V

Maintenance Work Order Type BIV_MAINT_WK_ORDER_TYPE_LVL_V

Order Item Return Reason BIS_ORDER_ITEM_RET_REASON_V

Organization BIS_ORGANIZATIONS_V

Organization (Maintenance Organization) ISC_PLAN_SNAPSHOT_V

Purchased Items POA_ITEMS_V

Purchasing Category POA_ITEMS_V

Repair Organization BIV_DBI_RO_ORG_V

Repair Service Code BIV_DBI_SERVICE_CODES_V

Repair Type BIV_DBI_REPAIR_TYPES_V

Return Reason BIS_ORDER_ITEM_RET_REASON_V

Service Request Backlog Type BIV_BACKLOG_TYPE_V


Service Request Channel BIV_CHANNELS_V

Service Request Resolution BIV_RESOLUTIONS_V

Service Request Severity BIV_SEVERITIES_V

Service Request Status BIV_STATUSES_V

Service Request Type BIV_REQUESTTYPE_V

Shipment Direction ISC_SHIPMENT_DIRECTION_V

Supplier POA_SUPPLIERS_V

Supplier Classification POA_SUP_CLASSIFICATIONS_V

Supplier Site POA_SUPPLIER_SITES_V

Task Type BIV_FS_TASK_TYPE_LVL_V

Termination Reason OKI_TERM_REASONS_V

Transportation Mode ISC_TRANSPORTATION_MODE_V

Warehouse Operation Plan OPI_WMS_OP_PLAN_NAME_LVL_V

Warehouse Task Exception Reason OPI_WMS_TASK_EXC_REASONS_LVL_V

Warehouse Task Type OPI_WMS_TASK_TYPE_LVL_V


Building Oracle Daily Business Intelligence (DBI) Dashboards with Oracle BI Enterprise Edition August 2006 Author: ERP BI Applications Development Team Contributing Authors: Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 www.oracle.com Oracle is a registered trademark of Oracle Corporation. Various product and service names referenced herein may be trademarks of Oracle Corporation. All other product and service names mentioned may be trademarks of their respective owners. Copyright © 2006 Oracle Corporation All rights reserved.

Documents

Obiee Dbi Whitepaper