X

Best Practices from Oracle Development's A‑Team

Oracle Analytics for Applications – Extensibility Reference Architecture

Matthieu Lombard
Consulting Solution Architect

Co-authors:

Satnam Singh, Vice President, Product Management

Profile photo for Balaji Krishnan

Balaji Krishnan, Product Management Architect, Analytics Apps

 

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/8a46a959443a4df8879c88ef087c67de/32_1.png Background

Oracle Analytics for Application (Fusion Analytics Warehouse or FAW) is an optimized analytics solution that provides rapid time to insights for multifarious lines of business through Oracle’s feature-rich production-ready business intelligence software for Fusion Cloud Apps.

FAW incorporates the robust combination of Oracle Analytics Cloud (OAC) and Oracle Autonomous Data Warehouse (ADW) delivering ready-to-use dashboards, industry KPIs, and machine learning models that leverage Oracle’s sophisticated Cloud architecture.

FAW is fully extensible and customizable; allowing customers to import external data into ADW, expand the base semantic model, and add additional content to OAC.

This blog is a prologue to a series of forthcoming topics on how to utilize Oracle ETL and Data Integration tools to extract data from various sources and extend Oracle’s delivered Analytics offerings.

These blogs are a collaboration effort between various Oracle teams: FAW Product Management, the CEAL Team, and the A-Team.

Future blog topics will include:

  • Data Extensibility:  extracting data from Oracle SaaS Applications, Oracle on-premise applications (e.g. EBS), other Oracle applications (e.g. Responsys & Eloqua), and third-party data sources (e.g. Salesforce & Workday).

  • Semantic Layer Extensibility:  adding new/extending dimensions, defining new presentation hierarchies, adding calculations, extending Oracle Facts, creating new subject areas, and customizing the presentation layer (re-ordering columns, hiding / showing columns, leveraging translations).

  • Content Extensibility:  creating new KPIs, and creating new Cards and Decks.

See below “Figure 1: FAW Extensibility Use Cases”:

The FAW Oracle-managed components shown in red on the left are immutable and cannot be modified.

Oracle-managed components comprise of:

  • Fusion SaaS Applications source

  • ETL service to extract Fusion data, transform and load it to the Factory schema

  • Prepackaged semantic model covering the FAW subject areas (GL balances, GL Journals, Account Payables, Account Receivables, etc.)

  • Prepackaged content (KPIs, visualizations, machine learnings models.)

The Customer-managed components shown in blue on the right represent customizable elements.
Customizations may include: 

  •  Using independent custom extractions to onboard additional data to one or more custom schemas.

  • Extending the semantic layer to map schemas to the presentation layer.

  • Creating custom content on semantic layer extensions.

 

Figure 1: OAX extensibility use cases

This blog is broken into three main chapters:

  • Data Extensibility Use Cases

  • Semantic Extensibility Use Cases

  • Content Extensibility Use Cases

 

Suggested Prerequisite Reading Material:

* Oracle Analytics for Application Product Page

* Oracle Analytics for Application Documentation Library

* Using Oracle Data Integrator on Oracle Cloud Marketplace

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/26bad7248c8436b19181d3800fa0ad4a/32_2.png Reference Architecture - Data Extensibility Use Cases

Overview

FAW comprises of three main components:

1) OAC the foundation for FAW Analytics.

2) ADW to house the data warehouse.

3) Pre-packaged dashboards, visualizations, KPIs, content, and data pipeline.

Customers have disparate systems, applications that generate and store data critical for analytical decision-making. Customers can create schemas to host additional data sources not available out-of-the-box in FAW and to have all business-critical data collated into Oracle ADW.

Use Cases

Use Case 1 – Replicate Oracle Fusion SaaS data in ADW using Oracle Data Integrator (ODI) Marketplace

Figure 2: Fusion SaaS data replication use case

Scenario: Fusion View Objects (VOs) such as Tax or Cash Management VOs are not in the OAX roadmap; however, they are often required for custom analytics.

Solution: Leverage the transformation/orchestration capabilities of ODI Market Place to extract the VOs or additional attributes from ERP and load them into Customer Managed Schemas within the same ADW instance.

Methodology: In this blog the A-Team walks you through how to replicate Oracle Fusion SaaS VOs data into ADW using ODI Marketplace and BI Cloud Connector (BICC). Topics Include:

  • Provisioning ODI Marketplace

  • Fulfill OCI, ODI and ADW prerequisites

  • Configure BICC to write to object storage

  • Configuring Oracle Object Storage and BICC ODI Topology

  • Create ODI Models

  • Create ODI Project and Mapping

  • Run the ODI Mapping

Use Case 2 – Replicate Salesforce data in data in ADW using ODI Marketplace

Scenario: Customer would like to extract data from Oracle Non-Fusion sources such as Salesforce.

Solution(s):

(a) Use ODI Marketplace to extract data using the source extract capabilities.

(b) Use alternative ETL methods such as REST API calls, Web Service calls, JDBC/ODBC drivers, etc…

(c) Use FSCM, HCM & CRM Extract

Figure 3: Non-Fusion SaaS or Third-Party data replication use case

Methodology: In this blog, the A-Team walks you through how to replicate Salesforce data into ADW using ODI Marketplace. Topics Include:

  • Reset Salesforce Security Token

  • Set up Salesforce Topology in ODI Marketplace

  • Create ODI Models and Reverse Engineer Salesforce Datastores

  • Update ADW diagram and create target ADW Datastore

  • Create and run ODI Mapping

Use Case 3 – Replicate Taleo Recruiting Cloud data in data in ADW using ODI Marketplace

Scenario: Customer would like to extract data from Oracle Non-Fusion sources such as Taleo Recruiting Cloud.

Solution(s):

(a) Use ODI Marketplace to extract data using the Taleo client connect utility

(b) Use alternative ETL methods such as REST API calls, Web Service calls, JDBC/ODBC drivers, etc…

 

Figure 4: Taleo Recruiting Cloud data replication use case

Methodology: In this blog, the A-Team walks you through how to replicate Taleo Recruting Cloud data into ADW using ODI Marketplace. Topics Include:

  • Set up Taleo Client Connect in ODI Marketplace

  • Create ODI Models and Reverse Engineer Taleo Extract Datastores

  • Update ADW diagram and create target ADW Datastore

  • Create and run ODI Mapping

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/4ebb591f08fad62258bba1f09b7d4b91/32_3.png  Reference Architecture - Semantic Extensibility Use Cases

Overview

A semantic model is a business representation of physical data that helps business users understand and access data through commonly understood business terms.  

The OAC Semantic model consists of three layers:

  • Physical – Maps to our Physical Data Model

  • Logical – Mapping or a transformation layer where complex calculations are defined

  • Presentation – End user access layer

Using the semantic model has the following advantages:

  • Security and Governance

  • Performance and Scalability

  • Clean way to obfuscate complex physical model, joins, filters, calculations etc.

Figure 4: Semantic Layer Details

The OAX Semantic Model is immutable: the out of the box subject areas are preconfigured to map the OAX star schema tables. However, OAX offers capabilities for extending the semantic model through Extension Wizards. Extension wizards are customer-managed and accessed through the OAX Console.

Figure 5: OAX Console for Semantic Model Extensions

Extension Wizard Capabilities:

  • Add new dimensions.

  • Extend an existing dimension.

  • Define a new presentation hierarchy.

  • Add a calculation or extend an Oracle Fact.

  • Create a new subject area.

  • Customize the presentation layer.

Figure 6: OAX Semantic Layer Extension Wizards

Use Cases

**** At the time of writing this blog – February,18 2020 –  in the OAX current version (v2.1.0), only the first use case is available. ****

Use Case 1 – Extend an existing dimension

Scenario: Customer has onboarded an additional data element (column) from one of the Fusion SaaS data store and want to add this column to one of the OAX delivered dimension.

Solution(s): Use the Extend a Dimension Wizard to onboard the new column and expose it to the presentation layer.

Methodology: In this blog <Incoming – Stay tuned!>, the CEAL Team will walk you through how to enrich the OAX delivered dimension with custom attributes and enrich the semantic layer with a new dimension.

Figure 7: OAX Semantic Layer Extension Wizard – Extend a Dimension

 

Use Case 2 – Add a new dimension to the semantic layer and define a new hierarchy in the semantic layer

Scenario: Customer has onboarded a new dimension (column) and corresponding hierarchy from one of Fusion SaaS data stores and want to add this dimension and hierarchy to the OAX presentation layer.

Solution(s): Use the Add a Dimension and Define a Hierarchy Wizards to onboard the new column and expose it to the presentation layer.

Methodology: In this blog <Incoming – Stay tuned!>, the CEAL Team will walk you through how to enrich the OAX delivered semantic model with a new hierarchy. This use case will be cover in a later OAX version.

Use Case 3 – Add a new calculation or extend an Oracle Fact in the semantic layer

Scenario: Customer wants to create a derived calculation and add it to an existing OAX fact table.

Solution(s): Use the Add a Calculation and Extend and Oracle Fact Wizards to onboard the new calculation and expose it to the presentation layer.

Methodology: In this blog <Incoming – Stay tuned!>, the CEAL Team will walk you through how to enrich the OAX delivered semantic model with a new hierarchy. This use case will be cover in a later OAX version.

Use Case 4 – Credit a new subject area in the semantic layer

Scenario: Customer has onboarded data elements (dimension and facts) into a custom schema and wants to be able map the physical tables to the presentation layer so users can build reports on this new subject area.

Solution(s): Use the Create a Subject Area Wizard to organize the new data elements into a subject area and expose it to the presentation layer.

Methodology: In this blog <Incoming – Stay tuned!>, the CEAL Team will walk you through how to enrich the OAX delivered semantic model with a new hierarchy. This use case will be cover in a later OAX version.

Use Case 5 – Customizing the presentation layer of the semantic layer

Scenario: Customer has created a new subject area and wants to reorganize its content.

Solution(s): Use the Reorder Columns and Show/Hide Columns Wizards to reorganize the data elements in the custom subject area.

Methodology: In this blog <Incoming – Stay tuned!>, the CEAL Team will walk you through how to customize the OAX delivered presentation layer, by reordering columns and hiding/showing columns. This use case will be cover in a later OAX version.

 

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/d2832b32fea8413bc12af98700b2a767/32_4.png Reference Architecture - Content Extensibility Use Cases

Overview

OAX offers a new set of analytics objects:

  • Homepage – Collect individual, personal favourites across whole app

  • Decks - Collections of cards that show status of organization at a glance with simple filtering to illuminate status. Sharable sets to service shorter and longer-term needs.

  • Cards / Large Cards – Provide personalizable instantiations of core KPIs. Serve as a location for collaboration, and present adjacent metrics for context or tangential investigation. 

  • KPIs – Capture shared business concepts – core set created/managed by analyst.

  • Detail Analysis – Projects deliver detailed analysis, and bridge to ad hoc exploration.

  • Dataset – Incorporate non-subject area data and support joins for mashups.

  • Subject Areas – Provide Semantic Model

  • Data Pipeline – Support data movement and transformations

  • Data – Oracle Fusion SaaS or other

Figure 8: OAX Semantic Layer Extension Wizards

Use Cases

Across the series of blog, the following use cases will be covered:

Use Case 1 – Create a new KPI in OAX

In this blog <Incoming – Stay tuned!>, the A-Team will walk you through how to create a new OAX KPI.

Use Case 2 – Create a new Card in OAX

In this blog <Incoming – Stay tuned!>, the A-Team will walk you through how to create a new OAX Card and attach the previously created KPI.

Use Case 3 – Create a new Deck in OAX

In this blog <Incoming – Stay tuned!>, the A-Team will walk you through how to create a new OAX Deck and attach the previously created Card.

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/3fc2da0e81c4b3da43f20a159590bdf6/32_more.png Want to Learn More?

Click here for more detail around Oracle Analytics for Applications

Click here for more CEAL Team Blogs

Click here for more A-Team Oracle Data Integrator (ODI) Blogs

Click here for more detail around the ODI Salesforce integration capabilities

Click here to sign up to the RSS feed to receive notifications for when new A-team blogs are published

Click here to access the ODI Marketplace documentation library 

https://cdn.app.compendium.com/uploads/user/e7c690e8-6ff9-102a-ac6d-e4aebca50425/891b37fd-cb85-48ba-bde5-7b091037d6be/Image/cae504aea0989e9e2f1dae4627816c87/32_begin.png Summary

This article walked through multiple extensibility use cases for Oracle Analytics for Application (OAX) covering:

* Data Extensibility Use Cases

* Semantic Extensibility Use Cases

* Content Extensibility Use Cases

This blog is a prologue to a series of forthcoming topics on how to utilize Oracle ETL and Data Integration tools to extract data from various sources and extend Oracle’s delivered Analytics offerings. Stay tuned for more to come!

These blogs are a collaboration effort between various Oracle teams: OAX Product Management, the CEAL, and the A-Team.

Bookmark this post to stay up-to-date on changes made to this blog as our products evolve.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha