Introduction

The Oracle EPM Cloud Integration Adapter integrates with Oracle EPM Cloud source by exporting the data and meta-data and loading it through a SQL Server database into a SQL Server Analysis Services (SSAS) database. After a data-export the resulting OLAP Cube can be used standalone without a live connection to Oracle EPM Cloud.

Architectural overview

...

Oracle EPM Cloud Adapter is retrieving metadata and data from the Oracle EPM Cloud source by starting jobs at the source’s side and later downloading metadata and data files. The extracted data is then transformed and loaded into a fact database that is connected to a SSAS cube. This cube providing the information to show reports in the CXO Dashboard.

In order to define which data should be extracted when, the integration administrator sets up the adapter using a web-based Configuration UI. This UI also allows applying some filtering and transformations on the extracted data. Once the Adapter is set up, the CXO Software Agent will (per user-defined extraction schedule) invoke the adapter to start the extraction process.

Prerequisites

The following components already have to be installed

• CXO version 20.4.4 or later

• CXO Identity provider

• .NET 5.0 has to be installed

• Account to connect from the adapter to the Oracle Cloud system

Installation

• (Details to be added)

  • Installing Oracle EPM Cloud Adapter

  • Configure the license key

  • Create a new source system

  • Configuring Oracle EPM Cloud system

User guide

Setting up Oracle EPM source in CXO

• (Details to be added)

Configuring the adapter

Configuring the adapter is done using the web-based Configuration UI. The access to this UI is limited only CXO Admins - other users are not authorized to see these pages.

...

After opening the Configuration UI, all the Oracle EPM Cloud sources are visible on the left. For the currently selected source, the navigation on top leads a specific aspect of the adapter configuration: Connection, Dimension Mappings, Metadata, Data, Scheduling, and Logs. All dates & times in this UI are shown in the user’s local timezone.

Configuration

The goal of this page is to set up the connection to the Oracle system so that the adapter knows from where (ans using what credentials) the data can be extracted.

• API URL is the access point from the Oracle Cloud, the URL used to log into Oracle Cloud

• Cube: name of the oracle cube from which the data is extracted, found in Oracle Cloud under Tools → Overview → Cubes.

• Application name: Application that contains the given cube, found in Oracle Cloud under Tools → Overview

• User: credentials used by the adapter to retrieve information from the Oracle Cloud.

Dimension Mappings

The goal of this page is to define how oracle dimensions are mapped to the CXO dimension

• Some CXO standard dimensions (such as Account) are by default mapped to a certain Oracle EPM standard dimensions.

• CXO custom dimensions (such as A01) can be mapped to an Oracle EPM analytical dimensions, or left unmapped

• CXO dimension Value can be mapped to Oracle EPM dimension Currency, or left unmapped

• If an Oracle EPM dimension has an alias defined in the Oracle EPM Cloud system, then this dimension alias also needs to be added when making the dimension mappings

More info about PBCS dimensions can be found here, and FCCS dimensions here

Metadata

The goal of this page is to define general properties for the metadata extraction job and filters that are applied when extracting the metadata from Oracle EPM Cloud

Export job general settings

• Export job name: name of the job that extracts metadata from Oracle EPM Cloud. Useful to change mainly for the troubleshooting purposes.

• Export job file delimiter: delimiter used in the downloaded metadata file (CSV), will be typically either comma (,) or semicolon (;)

• Dimension Alias: Column name in the extracted CSV that corresponds to a dimension alias

  • CXO allows for 3 dimension aliases to support multiple languages. When metadata is extracted from Oracle EPM, aliases in CSV are typically stored in a column named “Alias: Default“ or “Alias: English“.

Filters

By default the whole dimension hierarchy will be loaded. As this might be too much data, there is an option to exclude unwanted parts of the hierarchy (or unwanted members). This can be done by adding filters. For example, if filter for entity (ENT) Europe is added, then member Europe and all of its descendants will be excluded from the metadata extraction,

Data:

The goal of this page is to define general properties and filter that are applied when extracting the data from Oracle EPM Cloud

Export job general settings

• Export job name: name of the job that extracts data from Oracle EPM Cloud. Useful to change mainly for the troubleshooting purposes

• Export job file delimiter: delimiter used in the downloaded metadata file (CSV), will be typically either comma (,) or semicolon (;)

File structure and selection

Extracted data file is structured as follows: TBD

Scheduling

The goal of this page is the define which the moments when metadata and data will be extracted in which moments

• Schedule can be on a daily or weekly basis

• Data that is extracted is defined per combination Period, Year, and Scenario (e.g. Q1 2020 Actual)

Logs

The goal of this page is to help in troubleshooting problems when running the adapter.

• Firstly only recent log entries are loaded, as the user scrolls down, more entries are loaded.

• Filtering log entries is possible to narrow down of the amount of long entries

• Log entries are not updated live, but only on when the page is loaded or filtering is applied.

FAQ

The credentials don’t seem to work, even though I can log in to Oracle Cloud in my browser?

...

Check API URL, it should contain only protocol and domain (e.g., https://something.else.oraclecloud.com/) and no subdirectory (so not https://something.else.oraclecloud.com/HyperionPlanning/)

Check if there is a domain when logging in to Oracle Cloud. If so, then API URL and username should contain the domain.

...