Redwood

Published Version 6 on April 27, 2024.

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.

overall

Included in Fusion Analytics are:

  • A library of ready-to-use metrics and dashboards for faster collaboration.
  • An extensible, Oracle-managed data platform with ready-to-use data extraction pipelines.
  • An extensible, Oracle-managed semantic data model.
  • An extensible, Oracle-managed security framework that leverages the security components in Oracle Fusion Cloud Applications.

Fusion Analytics is designed for easy and fast data analytics throughout the entire process, including data pipeline extraction, transformation, Fusion Cloud Applications data loading to a cross-functional data model, and organization in a semantic model that provides subject areas to business users.

Prebuilt data foundation components are shown below.

Prebuilt Data Platform

Prebuilt and custom components are shown below.

Prebuilt and Custom

This post is an Implementing Oracle Fusion Analytics Series member and guides customizing the prebuilt content in Fusion Analytics. It builds upon and assimilates the planning, preparing, provisioning, and configuring activities presented in preceding posts.

A Fusion Analytics implementation comprises a broad spectrum of activities. Save valuable time and prevent errors by carefully following best practices, using prebuilt components as much as feasible, and carefully planning the customizations rolled out to the business community.

Redwood
Customization

Customization is an implementation phase that follows the rollout of a phase with the same scope containing pre-built functional areas. Customize Fusion Analytics to satisfy business requirements and increase reporting capabilities.

Recommendations and Best Practices
  • Leverage prebuilt Fusion Analytics content as much as possible before creating custom content.
  • Limit the scope of the customization phase as much as possible to a subset of functional areas.
  • Limit the scope of the customization phase to a single Fusion Analytics application, e.g., ERP.
  • Procure an ATE (Additional Test Environment) for user acceptance and performance testing before beginning the customization phase.
  • Follow best practices and recommendations when customizing workbooks, extending the semantic model, and augmentating data.
  • If a partner is involved, ensure their implementation team has training, experience, and certification in Fusion Analytics.
  • Use the Fusion Analytics Implementation Guide to plan the project.
  • Leverage Fusion Cloud Applications custom data, security, and reporting when developing Fusion Analytics customizations.
Assumptions
Redwood
Customization Topics

The following topics are presented. Before and after each topic, review and complete the relevant checklist.

  • Required Performance Optimizations
  • Prepare for Customization
  • Customization
  • Required Performance Tests
  • Support Considerations
  • Checklists
Redwood

Required Performance Optimizations Recommendations

Evaluate and ensure that:

  • An ATE (Additional Test Environment) was obtained and scaled up, if necessary, for performance and concurrency testing.
  • Audit, network, and diagnostic logs were enabled for performance testing and investigation
  • Obtain an ATE (Additional Test Environment) for user acceptance and performance testing.
  • Obtain a concurrent user testing tool, e.g., JMeter.
  • Develop a plan to track ADW utilization, OCPUs, and storage.
  • Develop a plan to track OAC utilization.
  • Develop a plan to identify custom queries taking longer than 30 seconds.
  • Develop a plan to scale up the ATE and production environments if necessary
  • Ensure all developers know and adhere to workbook and visualization development and performance best practices.
References
Redwood
Prepare for Customization

OCI and Fusion Analytics Service administrators ensure that all environments are ready for the customization phase.

Phased Approach

The executive sponsor and project manager ensure the customization phase is scoped appropriately and follows the recommended phased approach.

Recommendations
  • Ensure the Fusion Analytics Implementation Guide is used to plan the project.
  • Limit the scope of the customization phase as much as possible.
    • Customize just one application pillar, e.g., HCM, ERP.
    • Limit the number of application functional areas as much as possible.
  • Customize application functional areas only after their prebuilt content has been rolled out.
References Fusion Analytics Phased Implementation Approach
Learnings

The executive sponsor and project manager ensure that the implementation team is trained and experienced with customizing Oracle Fusion Analytics

Recommendations
  • Ensure the system integration partner’s team has training, experience, and certification in Fusion Analytics.
  • Ensure the entire implementation team is familiar with Oracle’s best practices for customizing Fusion Analytics.
  • Ensure the Fusion Analytics functional administrator’s have training and experience with custom report content, including Data Sets, Data Flows, Workbooks, and Filters.
  • Ensure the functional administrators and developers have training and experience with custom report content, including Data Sets, Data Flows, Workbooks, and Filters.
  • Ensure the data administrators and developers have training and experience with data augmentations, including Flex Fields (DFFs), VOs (View Objects), Primary Keys, Joins, and ADW custom schemas.
  • Ensure the model administrators and developers have training and experience with semantic models, star schemas, and semantic model extensions.
  • Ensure the security administrators and developers have training and experience with users, licensed groups, job groups, application roles, security contexts, security authorizations, and security extensions.
References
Custom Catalog Folders

Custom catalog folders organize and manage custom reporting objects.

Recommendations
  • Create custom shared folders for customized reporting objects.
  • Use consistent custom prefixes when naming custom folders.
  • Model the custom hierarchical shared folder tree structure after the prebuilt Oracle shared folder structure.
  • Use inheritance in the custom shared folder tree to pass permissions to lower levels.
  • Grant exclusive read-write access to the custom parent folder to the Fusion Analytics service administrator.
  • Use inheritance to grant the Fusion Analytics service administrator read-write privileges to the entire folder tree.
References
Custom ADW Schemas

Custom schemas contain external data populated with customer-managed extraction, transformation, and load processes.

Recommendations
  • Create custom schemas for external data.
  • Use consistent custom prefixes when naming custom schemas.
References
Fusion Analytics Release Management Recommendations

Evaluate and ensure that:

  • The development, ATE, and production environments are on the same release and patch level.

References

Backup and Rollback

OCI and Fusion Analytics Service administrators develop the backup and rollback procedures for the customized environments.

Recommendations
  • Backup all environments.
    • Restore the phase’s functional area content from the production environment into the development and ATE environments.
  • Create a backup and rollback test plan for customizations. This includes plans for:
    • ADW Schemas
    • Reporting Content
    • Data Augementations
    • Semantic Model Extensions
    • Security Extensions
References
OCI Environment

OCI (Oracle Cloud Infrastructure) administrators ensure that changes to OCI components follow prebuilt architectures and do not impact prebuilt Fusion Analytics and Fusion Cloud Applications objects. Recommendations

Anticipate changes to OCI and have them approved by the OCI administrators for these and any other objects.

  • Identity Domain or Identity Cloud Service (IDCS) settings
  • Compartments
  • Security components
  • Governance components
  • Observability components (Audit and Diagnostic Logs)
  • Service limits and quotas
  • Networking components
  • DNS components
  • Fusion Analytics, OAC, and ADW service settings
Redwood
Customization

OCI, Fusion Analytics administrators and data engineers perform the customization activities.
Customizations fall into these broad categories.

  • Data Augmentations
  • Semantic Model Extensions
  • Custom Analytic Content
  • Security Extensions
Data Augmentation

Fusion Analytics service administrators and data engineers perform data augmentation.

Data augmentation enables extending analyses by blending data from multiple sources beyond what resides in Fusion Cloud Applications. Fusion Analytics provides a variety of ways to capture this data, from self-service methods to more governed, curated approaches.

The prebuilt database schema for the Fusion Cloud Applications contains read-only data to ensure all prebuilt visualizations and analyses are never broken. Custom database schemas in the same embedded Oracle Autonomous Data Warehouse (ADW) are used to store data from external sources efficiently. Fusion Analytics supports any data movement tool for loading data, such as Oracle Data Integration, any third-party tools, or even plain SQL.

Custom data can be used to extend existing dimensions and facts tables or add new ones.

Data Augmentation is accomplished using a variety of methods, including:

  • Adding descriptive flexfield (DFF) extensions from Fusion Cloud Applications using a Custom Data Configuration.
  • Using one or more of the data augmentation connectors offered by Fusion Analytics.
    • More than 50 native connectors to various sources are supported, such as Oracle Autonomous Database, Oracle Fusion Cloud EPM, Google Big Query, Salesforce, and Snowflake. You can also connect to any Java Database Connectivity (JDBC)-based data source. Get real-time data from Fusion Cloud Applications using the Oracle Cloud Applications connector.

Connectors

  • Self-service datasets and dataflows that leverage the capabilities of the underlying Oracle Analytics Cloud platform.

Self Service

  • Data integration tools. Fusion Analytics supports all data integration tools such as Oracle Data Integrator and Oracle SQL*Developer.
Recommendations
  • Synchronize custom data loads with Oracle-managed Fusion Analytics pipelines.  View incremental pipeline statuses in the DW_WH_REFRESH_SUMMARY table.
  • Load custom data outside of business hours to avoid data inconsistencies and performance issues when users access the data.
  • Use the Low ADW service connection. Using the High and Medium services consumes too many resources and causes performance issues for other processes running on the database.
  • Use custom prefixes, e.g., WC_, when naming custom schemas, tables, and columns.
  • Review all options when selecting the best solution for each augmentation.
  • Consult the data augmentation references for best practices.
  • Leverage prebuilt Fusion Analytics data augmentation components, including:
    • Prebuilt Entities and Attributes
    • Custom Data Configurations
    • Dimension Aliases
    • Fusion Analytics Connectors
    • Security Configuration Functional Area Pipelines
  • Join custom fact tables to all appropriate dimension tables.
  • Join custom dimension tables to all appropriate fact tables.
  • Populate all primary-key column values. Primary key columns cannot contain null values.
References
Semantic Model Extensions

Fusion Analytics service administrators, modelers, and model administrators perform semantic model extensions.

Note: Semantic Model Extensions for security use cases are presented in the Security Extensions section.

The Fusion Analytics semantic model provides simple business subject area views of hundreds of physical tables and views in the database. The mappings, rules, and translations between complex physical data structures are done for you in easily understood and consistent business terms. Conformed dimensions (customer, supplier, product, fiscal calendar, business units, ledgers, etc.) are available for easy cross-subject area analysis.

Subject areas are designed to optimize query execution with fine-grained tuning and data and role-level security. They are the building blocks for determining customization requirements and providing query performance baselines.

The semantic model is extended using a simple, wizard-driven interface supporting multi-user development and publishing. Semantic model changes follow a test-to-production, version-controlled publishing process.

Customizations include:

  • Creating new subject areas.
  • Creating new fact and dimension tables.
  • Adding session variables for use in visualizations and analyses.
  • Modifying existing subject areas.
  • Extending existing fact and dimension tables with derived columns.
  • Extending existing dimension tables with additional attributes and hierarchies.
  • Extending existing fact tables with additional metrics.

Semantic Model

Recommendations
  • Leverage the Best Practices guide referenced below.
  • Use custom prefixes when naming custom semantic model objects.
  • Create custom dimensions first, followed by custom facts.
  • Ensure join columns are of compatible data types.
  • Always specify the primary key and display attribute when defining custom dimensions hierarchies.
  • Combine multiple extensions for a dimension into one object to minimize the number of joins.
  • Always set content levels for custom dimensions when joining to custom facts.
  • Minimize the number of semantic layer customization steps by applying current and future modifications to an object in a single customization step.
References
Custom Report Content

Fusion Analytics service administrators, functional administrators, and content authors create custom reporting content.

Enrich and customize prebuilt analytics with custom visualizations, dashboards, and pixel-perfect reports using prebuilt and custom subject areas and self-service tools.

Catalog folders help organize, find, and manage reporting objects. Create custom shared folders for customized reporting objects.

Visualizations Recommendations

Use the Data Visualization features of Oracle Analytics Cloud to build compelling, visual stories with automated charts and graphs. Get started quickly with more than forty-five visualization types, such as waterfall bridge reports, performance tiles, natural language, and maps.

VISUALIZE

Dashboards Recommendations

Use the classic analytical features of Oracle Analytics Cloud to quickly create analyses, prompts, and dashboards using prebuilt and custom subject areas. These subject areas are designed with metrics and attributes that answer specific business questions at summary levels and allow drilling down to the lowest transactional grain.

Dashboard

Pixel-Perfect Reports Recommendations

Use the Oracle Analytics Publisher (formerly BI Publisher) reporting solution to author, manage, and deliver reports and documents easier and faster than traditional reporting tools. Use a web browser or familiar desktop tools to create everything from pixel-perfect customer-facing documents to interactive management reports against practically any data source. View reports online or on a schedule that can deliver thousands of documents per hour with minimal impact on transactional systems.

BIP

Recommendations
  • Leverage the common and pillar-specific authoring tips in the references below.
  • Organize custom report content using shared folders in the catalog.
  • Use custom prefixes when naming custom catalog folders and reporting content.
  • Create a custom hierarchical shared folder tree structure modeled after the prebuilt Oracle shared folder structure.
    • For example, the Oracle shared folder tree has:
      • The root node named Oracle.
      • First-level folders named after application pillars:
        • Oracle ERP
        • Oracle HCM
        • Oracle SCM
        • Oracle CX
    • An example custom shared folder tree may have:
      • The root node named Custom.
      • First-level folders named after application pillars:
        • Custom ERP
        • Custom HCM
        • Custom SCM
        • Custom CX
  • Organize the custom catalog folder to ensure the correct business users can access appropriate custom reporting objects.
  • Leverage prebuilt user groups and application duty roles as much as possible.
  • Follow best practices and use prebuilt and custom application duty roles to secure content.
  • Identify user groups and duty roles for granting read-only access to custom folders.
  • Identify user groups and duty roles for granting read-write access to custom folders.
  • Assign users to prebuilt and custom groups that contain prebuilt and custom duty roles.
  • Use inheritance to pass permissions to lower levels in the custom shared folder tree.
  • Grant exclusive read-write access on the custom root folder to the Fusion Analytics Service Administrators group. Use inheritance to ensure the Fusion Analytics Service Administrators group inherits read-write privileges to the entire tree.
  • Grant read-write access to first-level pillar folders to pillar-designated functional administrator groups and privileged duty roles. Use inheritance to ensure read-write access to lower levels of the tree.
  • Grant read-only access to first-level pillar folders to pillar-designated consumer duty roles. Use inheritance to ensure read-only access to lower levels of the tree.
References
Security Extensions

Fusion Analytics service administrators, security administrators, and model administrators perform Security Extensions.

Custom data, semantic model, and reporting objects are secured using a variety of methods that comprise Security Extensions.

The following security objects are used to secure most customization objects.

  • Custom User Groups
    • Custom Job Roles in Fusion Cloud Applications
    • Custom User Groups in Fusion Analytics
  • Custom Application Roles
    • Custom Data Roles
    • Custom Duty Roles
  • Custom Data Security
  • Custom Object Security
  • Custom User Security Assignments
Recommendations
  • Leverage prebuilt security constructs as much as possible before developing custom security.
  • Secure catalog folders to ensure that only specified business users can access relevant custom reporting objects.
  • Secure groups of users with read access to shared custom catalog folders.
  • Secure groups of users with write access to shared custom catalog folders.
  • Ensure custom data is secured at the row level and is visible only to relevant user groups with appropriate data roles.
  • Ensure custom semantic model and report objects are secured and are visible only to relevant user groups with appropriate duty roles.
References

Typical Workflow to Manage Users, Groups, Application Roles, and Data Access
Set Up Custom Security
Custom Security in Fusion Analytics
Configuring Custom Data Security in Fusion Analytics Warehouse in Nine Steps
Configure Data Security
Configure Object Security
Configure Object Permissions
Security Extensions

Redwood
Required Performance Tests

OCI and Fusion Analytics administrators plan, monitor, and perform performance tests on the customized content.

Recommendations

Evaluate and ensure that:

  • Audit, network, and diagnostic logs were enabled for performance testing and investigation.
  • Fusion Analytics administrators proactively monitor usage tracking data.
  • Ensure the development, ATE, and production environments are on the same release and patch level.
  • Engage Oracle sales, support, and product management to analyze consumption patterns and plan additional capacity.
  • Ensure the ATE initially matches the capacity of the production environment.
  • Backup and restore the customized development environment content into the ATE.
  • Monitor ADW memory, CPU, and storage usage and note where capacity increases are necessary.
  • Monitor and track OAC utilization and note where capacity increases are necessary.
  • Run concurrent user tests using the anticipated number of users for the next 90 days.
  • Test all prebuilt and customized workbooks, analyses, and visualizations.
  • Test all distinct security contexts and security assignments.
  • Test full loads of all prebuilt and custom data pipelines.
  • Test incremental loads of all prebuilt and custom data pipelines.
  • Scale up the ATE as necessary.
  • Scale up the production environment to match the ATE after completing all tests.
  • Provide the performance test results to the Oracle guidance team.
References

Redwood

Conduct User Acceptance Tests

Evaluate and ensure that:

  • Custom subject areas were available to appropriate user groups.
  • Custom visualizations were available to appropriate user groups.
  • Custom data was available to appropriate user groups.
  • Unaffected prebuilt content was re-accepted.
  • Custom metrics were validated.
  • Query response times were accepted.
  • All users, including those with different security profiles, accepted custom content.
  • The proper use of the folder and the shared folder structure was explained to the authors.
  • Custom data was available to appropriate user groups.

Redwood

Support Considerations

Fusion Analytics service administrators interact with Oracle Support to resolve issues.

Recommendations
  • Enable audit, network, and diagnostic logs to assist internal and Oracle Support activities.
  • If there are open severity-one SRs (service requests) related to customizations, share the following information with Oracle Support:
    • The Fusion Analytics OCID (Oracle Cloud Infrastructure Identifier), the number of concurrent users, and the number of ADW and OAC OCPUs.
    • A document summarizing customizations.
    • Recent environment changes, e.g., patching, upgrade, Fusion P2T, that may have contributed to the issue.
    • For dashboard issues:
      • Affected workbooks, canvases, visualizations, analyses, and key metrics.
      • Workbook and analysis session logs containing logical and physical SQLs.
      • Exports of workbooks and archives of analyses.
References

Redwood

Checklists

Read through the checklists before a customization phase begins and periodically as the phase progresses. The checklists provide an opportunity to document and ensure that customizations meet requirements, have followed best practices, and the required performance optimizations have been performed.

Performance Optimizations Checklist
Question Response
Was an ATE (Additional Test Environment) obtained for user acceptance and performance testing?  
Were audit, network, and diagnostic logs enabled for performance testing and investigation  
Was a concurrent user testing tool, e.g., JMeter, obtained?  
Was a plan developed to track ADW utilization, OCPUs, and storage?  
Was a plan developed to track OAC utilization?  
Was a plan developed to identify custom queries taking longer than 30 seconds?  
Was a plan developed to scale up the ATE and production environments if necessary  
Are all developers aware of workbook and visualization development best practices?  

Return to the list of Topics

Prepare for Customization Checklist
Category Question Response
Approach Was the phased approach used for the prebuilt and customization phases?  
Approach Was the scope of the customization phase limited as much as possible to a subset of functional areas?  
Approach Was the scope of the customization phase limited to a single Fusion Analytics application, e.g., ERP?  
Approach Was a previous phase, containing only prebuilt content with the same scope, rolled out successfully into the production environment?  
Approach Was the Fusion Analytics Implementation Guide used to plan the project?  
Learnings Were best practices and recommendations studied for customizing workbooks, extending the semantic model, and augmentating data?  
Learnings If a partner was involved, did their implementation team have training, experience, and certification in Fusion Analytics?  
Backup and Rollback Is there a backup and rollback plan for customizations?  
Backup and Rollback Were the ATE and development environments refreshed and restored from the production environment?  
Backup and Rollback Were backup procedures developed for custom schemas in the ADW?  
Backup and Rollback Were the development, ATE, and production environments backed up before beginning the customization phase?  
Custom ADW Schemas Were consistent custom prefixes used to name custom schemas?  
Custom ADW Schemas Were consistent custom prefixes used to name custom schemas?  
Release and Patching Are the development, ATE, and production environments on the same release and patch level?  
Custom Folders Were consistent custom prefixes used to name custom folders?  
Custom Folders Is the custom hierarchical shared folder tree structure modeled after the prebuilt Oracle shared folder structure?  
Custom Folders Does the custom shared folder tree use inheritance to pass permissions to lower levels?  
Custom Folders Does the Fusion Analytics Service Administrator have exclusive read-write access to the root (no parent) folder?  
Custom Folders Does the Fusion Analytics Service Administrator inherit read-write privileges to the entire tree via inheritance?  
Custom Folders Is read-write access to first-level pillar folders only granted to pillar-designated functional administrators and specific author duty roles?  
Custom Folders Is read-only access to first-level pillar folders granted to pillar-designated consumer duty roles?  

Return to the list of Topics

Customization Checklist
Category Question Response
Data Augmentation Were all options reviewed to select the best solution for each augmentation?  
Data Augmentation Were the relevant data augmentation documentation and spreadsheets consulted for best practices?  
Data Augmentation Were prebuilt fusion analytics components leveraged? Including:  
Data Augmentation Were custom prefixes used for custom schema, table, and column names?  
Data Augmentation Were custom fact tables joined to all relevant dimension tables?  
Data Augmentation Were custom dimension tables joined to all appropriate fact tables?  
Data Augmentation Were custom primary-key column values populated? Primary key columns cannot contain null values.  
Security Were prebuilt security configurations leveraged as much as possible (especially regarding HCM)?  
Security Was the upload center leveraged to upload security assignments into the prebuilt security context tables?  
Security Were security assignments for custom attributes loaded into a custom warehouse table?  
Security Were users assigned to custom security assignments that secure custom data, the semantic model, and reporting objects?  
Security Did custom security assignments protect access to custom subject areas, reporting content, and data?  
Security Were custom user groups granted appropriate permissions?  
Security Did network access control and security lists secure access to customizations?  
Security Was network threat testing performed, and were all services protected from unauthorized access?  
Semantic Model Extensions Were custom subject area elements secured using Fusion Analytics Object Permissions?  
Semantic Model Extensions Were custom semantic model objects developed according to best practices and prebuilt design principles?  
Semantic Model Extensions Were custom prefixes used for custom semantic model objects?  
Custom Report Content Has custom report development followed the best practices noted in the references above?  
Custom Report Content Is the custom hierarchical shared folder tree structure modeled after the prebuilt Oracle shared folder structure?  
Custom Report Content Does the custom shared folder tree use inheritance to pass permissions to lower levels?  
Custom Report Content Does the Fusion Analytics Service Administrator have exclusive read-write access to the root (no parent) folder?  
Custom Report Content Does the Fusion Analytics Service Administrator inherit read-write privileges to the entire tree via inheritance?  
Custom Report Content Are prebuilt groups and application duty roles leveraged as much as possible?  
Custom Report Content Are users assigned to prebuilt groups as much as possible?  
Custom Report Content Do custom application roles follow prebuilt best practices ( duty roles )?  
Custom Report Content Is read-write access to first-level pillar folders only granted to pillar-designated functional administrators and specific author duty roles?  
Custom Report Content Is read-only access to first-level pillar folders granted to pillar-designated consumer duty roles?  

Return to the list of Topics

Performance Test Checklist
Question Response
Were audit, network, and diagnostic logs enabled for performance testing and investigation?  
Were Fusion Analytics administrators proactively monitoring usage tracking data?  
Were the development, ATE, and production environments on the same release and patch level?  
Was Oracle sales, support, and product management engaged in analyzing consumption patterns and planning additional capacity?  
Did the ATE initially match the capacity of the production environment?  
Was the customized development environment content bundled and restored into the ATE?  
Was ADW memory, CPU, and storage usage monitored, and capacity increases noted?  
Was OAC utilization monitored, and capacity increases noted??  
Were concurrent user tests run using the anticipated number of users for the next 90 days?  
Were all prebuilt and customized workbooks, analyses, and visualizations tested?  
Were all distinct security contexts and security assignments tested?  
Were full loads of all prebuilt and custom data pipelines tested?  
Were incremental loads of all prebuilt and custom data pipelines tested?  
Was the ATE scaled up if necessary?  
Was the production environment scaled up to match the ATE after completing all tests?  
Were the performance test results provided to the Oracle guidance team?  

Return to the list of Topics

User Acceptance Checklist
Question Response
Did the Fusion Analytics CSM (Customer Success Manager) assist in developing a successful user adoption plan?  
Were custom subject areas available to appropriate user groups?  
Were custom visualizations available to appropriate user groups?  
Was custom data available to appropriate user groups?  
Was unaffected prebuilt content re-accepted?  
Were custom metrics validated?  
Did all users, including those with different security profiles, accept the custom content?  
Was the proper use of folders and the shared folder structure explained to the authors?  

Return to the list of Topics

Support Considerations Checklist
Question Response
Were audit, network, and diagnostic logs enabled to assist internal and Oracle support activities?  
Are outstanding customization issues within allowable severity limits?  

If there are open severity-one SRs (Service Requests) related to customizations, were the following shared with Oracle Support:

  • The Fusion Analytics OCID (Oracle Cloud Infrastructure identifier), the number of concurrent users, and the number of ADW and OAC OCPUs?
  • A document summarizing customizations?
  • Any recent environment changes, e.g., patching, upgrade, fusion T2P, that might have contributed to the issue?
  • For dashboard issues:
    • Affected workbooks, canvases, visualizations, analyses, and key metrics?
    • Workbook and analysis session logs containing logical and physical SQLs?
    • Exports of workbooks and archives of analyses?
  

Return to the list of Topics

Redwood

Call to Action

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

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

Implementing Oracle Fusion Analytics Series

Fusion Analytics Implementation Guide

CEAL Implementation Guidance Sessions, September 2023

Fusion Analytics Community

Fusion Analytics Blogs

Fusion Analytics Library

Redwood

var coll = document.getElementsByClassName(“collapsible”); var i; for (i = 0; i < coll.length; i++) { coll[i].addEventListener("click", function() { this.classList.toggle("active"); var content = this.nextElementSibling; if (content.style.display === "block") { content.style.display = "none"; } else { content.style.display = "block"; } }); }