Creating a Custom Target Application
Create a custom target application that enables you to extract data from the Oracle Enterprise Performance Management Cloud, and then push the data into a flat file instead of loading it to an EPM Cloud application.
You can define the custom target application with required dimensionality. Instead of exporting the data to a target application, Data Management generates a data file that can be loaded to an external system using a custom process.
When creating a custom target application, note the following:
-
Data is written to the file in the following predefined order: Account, Entity, UD1, UD2 ... UD20, AMOUNT.
-
The sequence that is specified when you create the custom application definition is used to order the dimensions for mapping processing. Note the sequence in case you have scripts that have an order of processing dependency.
-
Data Rule—The POV category is not validated.
-
Data Load Mapping—Target values are not validated for custom applications.
-
Data Load Execution—Data Management creates an output data file. The name of the data file is
<Target App Name>_<Process ID>.dat
, and it is written to the<APPL ROOT FOLDER>/outbox
directory. You can access the data file from the Process Details page from theOUTPUT file
column.When the data load rule is executed, Data Management exports the data.
- To extract data from an EPM Cloud application with Data Management, the Period dimension must be set to "dense." The only exception is the Financial Consolidation and Close, where the account dimension is set to "dense" instead of the Period dimension.
-
Check Rules can be created from a custom target application. Check rules cannot be based on target values.
-
Write-back is not applicable from custom target applications.
To define a custom target application: