...
a. create new job. See two screenshots below
...
b. select all dimensions which should be extracted
...
The export job name created in Oracle Cloud and export job file delimiter has to be later on used in Oracle EPM Adapter in Metadata General Settings
...
Configure data export job
Go to the Overview screen
Choose Export Data in the dropdown on the right side of the screen
Create a new data job
Specify the following values:
Location: Outbox
Pick right cube
Choose a delimiter, preferably set it to “Other” and use “|”
Smart Lists are not used currently
Dynamic Members: Exclude
Decimals: none (or discuss with the customer)
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.
...
The export job name created in Oracle Cloud and export job file delimiter has to be later on used in Oracle EPM Adapter in Metadata General Settings
...
Configure connection.
Cube
For Api Url use host url without any path
Application name is the same you see in oracle
For credentials use username combining domain + “.” + username
Example: for picture below username would be a619055a000000.xxxxxxxxxxxxx
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.
...
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.
...