Installation Prerequisites

The following instructions are applied to both PBCS and FCCS. Instructions which are specific to FCCS only have been mentioned.

• CXO version 21.1.3 (or higher)

• CXO Identity provider

• .NET 5.0 has to be installed

• .NET 5.0 Hosting Bundle:
  https://dotnet.microsoft.com/download/dotnet/5.0

Setting up

1. Install Oracle EPM Cloud Adapter.

2. Open CXO Configurator>Maintenance and click Register Services and Websites.

   

3. Select Register Oracle EPM Adapter Api to add service account details.
   

   

4. Create Client in the CXO Identity Provider.

Identity Provider Configuration

1. Create new Generic Client.

2. Select Allow Offline Access option.

3. Add the following scopes:

   1. User profile

   2. User groups

4. Add Redirect URL(s) in the following format:
   {OraclEPMAdapterUrl}/signin-oidc

5. Add Post Logout Redirect URL(s) in the following format:
   {OraclEPMAdapterUrl}/signin-oidc-auth

CXO Configuration and Source Creation

1. Create a new source system in the SSM for the correct source type: Oracle EPM Planning / Oracle EPM Financial Consolidation and Close. This should create:

   • Fact database

   • SSAS cube

2. Open command line as Administrator and run configuration database creation command, for example:
   .\CXO.Adapter.OracleCloudEpm.Cli.exe create-configuration-db server-name:cxo-dev-sql02 database-name:oracleEpmConfigTest authentication-type:Proprietary username:cxo password:somePassword
   Parameters:
   o   server-name: Name of the server on which the database should be created.

   o   database-name: Name of the database to be created.

   o   authentication-type: windows / proprietary

   o   username: SQL username (if authentication-type == proprietary).

   o   password: SQL user password (if authentication-type == proprietary).
   Refer CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command.

3. Run set-authentication-settings command, for example:
   .\CXO.Adapter.OracleCloudEpm.Cli.exe set-authentication-settings idp-authority: https://cxoUrl/idp idp-client-id:clientId idp-client-secret:secret idp-client-allowed-user-group:ADM
   Refer CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command.

4. Run create-source-in-adapter command for example:
   .\CXO.Adapter.OracleCloudEpm.Cli.exe create-source-in-adapter source-type:pbcs source-name:source factdb-name:factdb-name factdb-server:factdb-server factdb-authentication-type:1 ssas-server-name:ssas-server-name ssas-database-name:ssas-database-name ssas-cube-name:ssas-cube-name
   Refer CXO.Adapter.OracleCloudEpm.Cli.exe help for detailed description of the command.

5. Restart IIS Application Pool for Oracle EPM Adapter.

Oracle EPM System Configuration

• Make sure you have an account to connect from the adapter to the Oracle system (A user with rights to create export job is required - admin user)

• Configure metadata export job

• Configure data export job

Configure metadata export job

Steps to perform:

1. Click Overview.

2. Under Dimensions, click Export.

On the export metadata screen, you will see the existing CXO jobs.

a. Click Create.

b. Select Location to Outbox and select all dimensions which should be extracted.

The export job name created in Oracle Cloud and export job file delimiter must be later used in Oracle EPM Adapter in Metadata General Settings.

Configure data export job

1. Click Overview.

2. Choose Export Data.
   

   

3. Click Create.
   

   

4. Specify the following values:

   1. Location: Outbox

   2. Pick right cube

   3. Choose a delimiter, preferably set it to Other and use “|”

   4. Smart Lists are not used currently

   5. Dynamic Members: Exclude

   6. Decimals: None (or discuss with the customer)

   7. Slice definition: Take Account on rows, Period on columns, set default slice values for all dimensions including POV.
      Note: This configuration will not be used in the actual data extraction, as it will be input to the job API call.
      

      

The export job name created in Oracle Cloud and export job file delimiter must be later used in Oracle EPM Adapter in Metadata General Settings.

Oracle EPM Adapter Configuration

1. Configure connection.

   1. Cube

   2. 

      Use host url for Api Url without any path for example: https://epm a000000.epm.em2.oraclecloud.com.
      Application name is the same you see in Oracle.
      

      

   3. For credentials use username combining domain + “.” + username
      Example: for picture below username would be a000000.xxxxxxxxxxxxx
      

      

2. Configure dimension mappings. Most standard dimensions would be mapped already – you need to map the custom ones. Number of custom Oracle Dimension doesn’t matter and are only used by CXO. Fill in the alias corresponding to custom dimension name.
   Example:

3. Configure metadata.
   Please follow instructions for FCCS here and then proceed.

4. Go to Overview> Dimensions>Extract.
   

   

5. Configure Data.
   Should be filled in consultation with the customer.
   - Multiple members are supported and should be separated by comma
   - Do not use quotes around members (even if they contain spaces)
   - Do not use “@” before selector methods (like @ILvl0Descendants(YearTotal))

6. Fill in Account dimension on Row and Period on Column.

7. Select all other dimensions in any order and fill in desired selectors.
   The Order of POV dimensions is important – to parse data extraction file using it. To figure it out fill in at first in a random order, finish configuration and return to the next step after you have successfully run an extraction. (You will see in the logs that data extraction has finished successfully but there are warnings of zero records being mapped).

8. Download the export data file for your last extraction (it should have at least one record).
   

   

9. Add .zip extension to file if necessary.

10. Open a file. Identify for any record “Point-of-View” member (it would be few members enclosed in quotes). Identify to which dimension each members belongs. Reorder your POV dimensions in adapter in the same order.
    

    

11. Configure schedule.

12. Create a new schedule. Name and schedule are up to the customer (or CXO) and not connected to Oracle configuration.
    - Initially its best to have “Extract Metadata” enabled.

13. Create a data slice.
    - Multiple members separated by commas are supported.
    - Do not use quotes.
    

    

14. Click Run now to extract data and metadata.
    

    

You can see the progress of the extraction under the Logs tab.