Oracle Fusion Analytics Implementation Series: Configure and Validate

July 14, 2023 | 14 minute read
Krithika Raghavan
Director, Oracle Analytics
Text Size 100%:
Redwood

Published and added to the Implementation Guide on July 23rd, 2023, based on release 23.R2.
Updated August 31, 2023 for Data Validation and release 23.R3.

Introduction

Oracle Fusion Analytics (Fusion Analytics) is a family of prebuilt, cloud-native analytics services designed to deliver personalized insights for Oracle Fusion Cloud Applications (Fusion Cloud Applications).

overall

This post is an Implementing Oracle Fusion Analytics Series member and a reference for the Fusion Analytics Implementation Guide.

It provides detailed guidance for configuring and validating Fusion Analytics instances.

Assumption: The recommended Phased Implementation Approach is used for the implementation.
This post focuses on an initial phase containing one application and one functional area.

 

Implementing Fusion Analytics

Fusion Analytics data analysis and visualization depend on the following:

  • The Fusion Analytics service administrator configures data pipelines, reporting parameters, and security assignments.
  • An Oracle Cloud Infrastructure (OCI) administrator configures network access to the services.
  • The Fusion Analytics functional administrator performs data validations using a prebuilt metrics library.

Configurations are required for each Fusion Analytics environment. They determine what and how much source data from Fusion Cloud Applications is loaded, how frequently it is refreshed, how it is secured, and how it is displayed.

Data validation confirms the data loaded into Fusion Analytics is complete, accurate, and reliable and that there are no data losses or discrepancies.

This post covers the following topics:

  • Data Configuration
  • Security Configuration
  • Reporting Configuration
  • Data Vlaidation

Configuration icons

Redwood Prerequisites

Configuration and validation rely on prior planning, preparation, and provisioning activities.

Planning Determinations

This post uses the following:

  • The Fusion Cloud Applications cloud account name.
  • The cloud account name chosen for Fusion Analytics.
  • The phased implementation approach is used.
  • The Fusion Analytics application and functional area identified for the initial phase.
  • For each environment:
    • The Fusion Cloud Applications security administrator.
    • The Fusion Cloud Applications functional administrator.
    • The Fusion Cloud Applications functional administrator's security contexts and assignments.
    • The Fusion Analytics service administrator.

Preparation Activities

This post uses the following for each environment:

  • User - Group synchronization and Single Sign-On (SSO)
  • The Fusion Cloud Applications service account created for data validation impersonation.

Provisioning Activities

This post uses the following for each environment:

  • The Fusion Analytics instance provisioning option.
  • The created Fusion Analytics instance.
  • The private Fusion Analytics network access method.
Redwood Configure Fusion Analytics

A Fusion Analytics service administrator configures Fusion Analytics based on implementation planning decisions and preparation activities.

Configuration

Topics

Configuration Sequencing

Beginning with release 23.R2, Fusion Analytics applications or pillars must have a data pipeline activated and completed before performing report and security configurations.

Configuration Sequence

Redwood

 

Configure Data

DATA CONFIGURATION

Data configuration consists of setting parameters for and activating data pipelines.

Data pipelines extract, transform, and load data into the Fusion Analytics data warehouse. Pipelines are available for prebuilt application functional areas, e.g., ERP - Financial Analytics - General Ledger, HCM - HCM Analytics - Workforce Management. Data pipelines extract data from the Fusion Cloud Applications and load it into the Fusion Analytics data warehouse. Refer to About Data Pipelines for Functional Areas for additional information.

Planning determinations identified the application and functional area used in the initial phase. The examples use the ERP application and the General Ledger functional area.

Data Pipeline Settings

pipeline settings

Pipeline settings are configured before activating pipelines and apply to all functional areas.

Refer to Set Up the Pipeline Parameters for detailed guidance.

 

They are grouped into three sections:

  • Data Pipeline Status
  • Global Parameters
  • Data Refresh Schedule

Pipeline settings

Data Pipeline Status

Ensure the Data Pipeline Status is set to Enabled.

Global Parameters

Set the global parameters per your requirements.

Note: The Initial Extract Date is the date at which extracts begin and is used when performing full extracts. The time required to perform full extracts increases as the date decreases.

Data Refresh Schedule

Set the schedule per your requirements.


Data PipelinesData pipelines are activated for functional areas. They extract data from Fusion Cloud Applications and load it into the Fusion Analytics data warehouse.

Refer to Create a Data Pipeline for a Functional Area for detailed guidance.

Functional areas derive from offerings. Offerings derive from applications.

ERP

Initial PhaseThe best practice noted in the Oracle Fusion Analytics Implementation Planning Series: Accelerated Phased Approach post is to activate a single functional area in the initial phase.

Notes:
Oracle recommends activating applications separately. Activate all required functional areas for an application before proceeding to another application.
Only activate the functional areas necessary to meet your requirements.

Redwood

 

Configure Reporting

ReportingConfig

A functional area data pipeline must be activated and completed before configuring reporting.

Reporting configurations determine the presentation of visualizations, dashboards, and reports in functional areas.

Refer to About Reporting Configurations for detailed guidance.

Global Reporting Configurations

Global reporting configurations pertain to all functional areas. A data pipeline for a functional area must be activated and completed before global reporting configurations are available.

Select a calendar from the Enterprise Calendar dropdown to configure the reporting calendar used in Fusion Analytics.

GlobalReportingParamter


ERP Reporting Configurations

Select Yes from the Allow Financial Category Upload dropdown to enable the upload of financial categories to the applicable environment.

ERPReportingParamter

 


HCM Reporting Configurations

HCMReportingConfig

Refer to Set Up HCM Reporting Configurations for detailed guidance.

Redwood

 

Configure Security

SecurityConfig

Security configurations ensure administrators have the required privileges and business users have proper permissions to view analytic content and data.

Architecture

Security Configuration


Components

The Fusion Analytics service administrator inspects and adjusts the components shown in the illustration as necessary.

  • Users
  • Groups
  • Application Roles
  • Security Contexts
  • Security Assignments

Prerequisite: User synchronization and single sign-on were performed when preparing for Fusion Analytics.


Users

During the Fusion Analytics implementation planning activities, the functional administrator, a limited number of business users, and partner resources are identified.

During the Fusion Analytics implementation preparation activities, partner resource user accounts are created, and the Fusion Cloud Applications user accounts in Fusion Cloud Applications are synchronized into the Fusion Analytics environment's identity domain/stripe.

For each phase recommended in the Fusion Analytics Implementation Phased Approach:

  • Ensure the business users and phase administrators are synchronized into the Fusion Analytics environment's identity domain/stripe.
  • Ensure the partner user accounts are created.

Groups

During the Fusion Analytics implementation preparation activities, Fusion Cloud Applications job roles and user memberships are synchronized into the Fusion Analytics environment's identity domain/stripe.

For each phase:

  • Ensure the Fusion Cloud Applications job roles are synchronized as groups.
  • Ensure the functional administrator and business user group memberships are synchronized.
  • Ensure the Fusion Analytics license and system groups are created with the instance.
  • Grant the administrators membership into the appropriate system groups.
  • Grant the functional administrator membership to the Integration Specialist group.
  • Grant the business users membership into the appropriate license groups.
  • See About Groups for detailed guidance.

    Note: The functional administrator must be assigned to the synchronized Integration Specialist group to access the Data Validation workbook and subject area.


Application Roles

Application roles secure access to analytic and data content.

For each phase, ensure the Fusion Analytics functional area's application roles are created by the data pipeline.


Security Contexts

Security contexts are categories containing values used in security assignments to ensure users only see the data they are entitled to. A security context is directly related to an application data role.

Ensure the data pipeline creates the Fusion Analytics functional area's application roles.


Security Assignments

Security assignments assign relevant security context values to users.

Assign the planned security assignments to the phase's functional administrator and business users.

Note: The functional administrator assignments must match precisely those in Fusion Cloud Applications.

Refer to Create a Security Assignment for detailed guidance.

Redwood

Configure Oracle Cloud Infrastructure

The OCI administrators perform OCI configurations based on the implementation planning and preparations.

Private Fusion Analytics Network Access Configuration

Coming soon.

Fusion Analytics Network Security Configuration

Coming soon.

Redwood
 

Validate Data

Data Validation

Data validation confirms the data loaded into Fusion Analytics is complete, accurate, and reliable and that there are no data losses or discrepancies.

The functional administrator is added to the service administrator group by the OCI domain administrator for entering the data validation impersonator credentials and then removed from the group.

The functional administrator adds the data validation impersonator credentials and performs data validations based on a prebuilt metrics library.


Architecture

Data Validation


Components

These components are shown in the illustration above.

Fusion Cloud Applications User

The functional administrator.

Fusion Cloud Applications User Job Role

The functional administrator's job role.

Fusion Cloud Applications User Data Privileges

The functional administrator's security contexts and assignments.

Fusion Cloud Applications Impersonator Service Account

The service account created for preparation activities.

Fusion Cloud Applications Impersonator Job Role

The job role created and assigned to the impersonator service account.

Fusion Cloud Applications BI Impersonator Role

The application role attached to the impersonator job role.

Fusion Analytics User

The functional administrator's user account is synchronized from Fusion Cloud Applications.

Fusion Analytics User Group

The functional administrator's group is synchronized from the Fusion Cloud Applications job role.

Fusion Analytics User Data Privileges

The functional administrator's security contexts and assignments are created and validated during Security Configuration.

Note: The functional security contexts and assignments match precisely those in Fusion Cloud Applications.


Add the Functional Administrator to the Service Administrator Group

To access the Data Validation source credentials screen, the functional administrator must be a member of the service administrators group because the service administrator may not have a synchronized Fusion Cloud Applications account.

The OCI domain administrator adds the Fusion Analytics functional administrator to each environment's FAW Service Administrator group. To do this:

  • Sign into the Identity Domain.
  • Navigate to Identity and Security > Domains.
  • Click the environment's domain Name.
  • Click Users.
  • Click the functional administrator's Username.
  • Click Assign user to groups.
  • Check the box for FAW Service Administrator.
  • Click Assign user.

Add the Data Validation Impersonation User Credentials

The functional administrator adds the Fusion Cloud Applications impersonator service account's credentials in each environment. To do this:

  • Sign into Fusion Analytics.
  • Navigate to the Console > Data Validation > Source Credentials.
  • Enters the Username, e.g., Fusion.Analytics.Impersonator.User
  • Enters and confirms the Password, e.g., YOurPwd123-=
  • Click Save.

Note: The credentials must match precisely those in Fusion Cloud Applications.

 

Validation credentials


Remove the Functional Administrator from the Service Administrator Group

The OCI domain administrator removes the Fusion Analytics functional administrator from each environment's FAW Service Administrator group. To do this:

  • Sign into the OCI Identity Domain.
  • Navigate to Identity and Security > Domains.
  • Click the environment's domain Name.
  • Click Users.
  • Click the functional administrator's Username.
  • Check the box for FAW Service Administrator.
  • Click Remove user from group.
  • Click Remove user from group again to confirm.

Perform Data Validations

The Fusion Analytics functional administrator schedules validations for each environment or runs an ad-hoc detailed validation. To run an ad-hoc validation:

  • Sign into Fusion Analytics.
  • Navigate to the Console > Data Validation > Detailed Validation
  • Select the functional area's Subject Area from the dropdown, e.g., Financials - GL Detail Transactions.
  • Select a Metric, e.g., Credit Amount.
  • Select a Column Set.
  • Select Values for the required Columns, e.g.,
    • Ledger Name: US Primary Ledger
    • Fiscal Period: 03-23
    • Journal Source Name: Payables
  • Click Run

Note: Choose values from the functional administrator's security assignments, e.g., US Primary Ledger

Validation Results

Note: Refer to Validate Your Data for detailed guidance on scheduling data validations.

Redwood

Call to Action

Return to the Fusion Analytics Implementation Overview for the next steps in the implementation journey.

Explore and learn more about Fusion Analytics by visiting the Fusion Analytics community links, blogs, and documentation.

Implementing Oracle Fusion Analytics Series

Fusion Analytics Community

Fusion Analytics Blogs

Administering Fusion Analytics

Implementing Fusion Analytics

 

Dayne Carley

Krithika Raghavan

Director, Oracle Analytics


Previous Post

Oracle Analytics Cloud - How to Setup and Configure the Oracle Analytics Cloud Environment on OCI

Amit Tyagi | 7 min read

Next Post


Prepare Your Reports to Use Google Noto Fallback Font in Oracle Analytic Cloud (July 2023 Update)

Sandeep Chauhan | 4 min read