Installation

...

• Configure proper license key

  • Based on the client’s source, generate the right key using the License Key generator: Oracle EPM Planning / Oracle EPM Financial Consolidation and Close.
    Path to generator: \\cxo-fileserv\Data\Internal Tools\(not-released) LicenseKeyGenerator for B Licenses (with Oracle Cloud EPM adapter)

• 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

• Run configuration database creation command: e.g.
  .\CXO.Adapter.OracleCloudEpm.Cli.exe create-configuration-db server-name:cxo-dev-sql02 database-name:oracleEpmConfigTest authentication-type:Proprietary username:cxo password:somePassword
  Parameters:

  • server-name: name of the server on which the database should be created

  • database-name: name of the database to be created

  • authentication-type: windows / proprietary

  • username: SQL user name (if authentication-type == proprietary)

  • password: SQL user password (if authentication-type == proprietary)

...

1. Go to the Overview screen

2. Choose Export Data in the dropdown on the right side of the screen
   

   

3. Create a new data job

   

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 Gjensidige

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

...

Oracle EPM adapter configuration

1. Configure connection.

   1. Cube

   2. Image Added

      For Api Url use host url without any path

   3. Application name is the same you see in oracle

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

      Image Added

2. Configure dimension mappings. Most standard dimensions would be mapped already – you need to map custom ones. Number of custom Oracle Dimension doesn’t matter and only used on our side. You only need to fill in allias corresponding to custom dimension name.

Example:

...

3. Configure metadata.

Go to Overview → Dimensions → Extract

...

4. Configure Data

This one should be filled in consultation with customer.

• Multiple members are supported and should be separated by comma

• Don’t use quotes around members (even if they contain spaces)

• Don’t use “@” before selector methods (like @Children(YearTotal))

Fill in Account dimension on Row and Period on Column

Select all other dimensions in any order and fill in desired selectors.

Order of POV dimensions is important – we 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 logs that data extraction is finished successfully but there would be worning stating that 0 records were mapped)

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

...

Add “.zip” extension to file if necessary.

Open a file. Identify for any record “Porint-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.

...

5. Configure schedule.

Create new schedule, name and schedule is up to customer (or you) and not connected to oracle configuration.

Initially you want “Extract Metadata” to be enabled.

Create a data slice.

Multiple members separated by commas are supported.

Don’t use quotes.

Selector functions are not supported yet (e.g. Children(YearTotal)) there is no worning for this so make sure there are not included in Data Slices. Use multiple members to replace such functions.

Example:

...

(Older instructions for reference:

• For Gjensidige: Check the old PBCS configuration for connection info, dimension mappings etc.

• Set up connection information (see old PBCS)

• Map the Oracle dimensions to CXO dimensions (see old PBCS)

• Set default properties for metadata extraction: delimiters, job name, aliases

• Configure data extraction settings

  • Set default properties: delimiters, job name

  • Set file structure, matching the configuration in the Oracle EPM system

    • Put it in the database in Source table: row, then column, then POV in order

  • Set data filters

    • 1 member expression per mapped dimension in DataFilters table, excluding period, year and scenario

...

• Run metadata extraction

  • Command:
    CXO.Adapter.OracleCloudEpm.Cli.exe extract-metadata source:<source-id-here>

  • Review hierarchies, add metadata filters for members that should be excluded from extraction

• Run data extraction

  • Command:
    CXO.Adapter.OracleCloudEpm.Cli.exe extract-data source:<source-id-here> period:Jan year:FY2021 scenario:Forecast
    

• Process cube from SQL Server Management Studio

)

Logging

• The log level can be set in appsettings.json in "LogLevel" property (Both Web project and CLI project have own appsettings.json file)

• Location of the log files:

  • CLI command {CXO-Installation-Dir}\Oracle Cloud EPM Adapter\Extraction\logs

  • Web application {CXO-Installation-Dir}\Oracle Cloud EPM Adapter\Web API\logs

• Log files are split into two file types

  • nlog-all -contains cxo defined logs and logs generated by other Microsoft libraries. Usually it is more verbose

  • nlog-own-detailed -contains logs defined by cxo with more detailed information then info in “nlog-all“ and additionally filters logs created by Microsoft libraries.

• Logging to the console in CLI tool

...