Creating a Data Export File Integration

Data Export to File enables you to export data from an Oracle Fusion Cloud Enterprise Performance Management application to a data file. You can use the data file to load data into an ERP application or an external system.

When creating a data export to file application, note the following:

• When dimensions are created, the order of the column in the data file is used to assign the column order. The first column in file is assigned ACCOUNT data column.

• It is recommended that you export only a year at a time. If date ranges cross a year boundary, data may be duplicated.

• The POV category is not validated.

• Target values are not validated for data export to file applications.

• When the option to export the data file is enabled, Data Integrationcreates 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 the OUTPUT file column.

  If you have a data export job scheduled on a daily basis and need to have the output file distributed to an individual automatically, use the Download Application Snapshot in REST API for Enterprise Performance Management Cloud to download a particular file, provide the path to that file as the value of applicationSnapshotName. For example, to download a Data Integration file called s112.csv in the inbox, refer to the file as "inbox\s112.csv" as the path parameter.

  When the integration is executed, Data Integration exports the data.

• Check Rules can be created from a data export file. Check rules cannot be based on target values.

• Write-back is not applicable from data export files.

• Only numeric data types are supported. If you need to export text, SmartList, and dates, use an EPM Data File application with the type: "EPM Data File," and the data extract option "Level 0 Data." Use this application as the target when creating your integration.

  You can also use the groovy public class DataExporter. For more information, see Class DataExporter.

• The default Workflow Mode setting is Simple for Data Export to File. When you are exporting data from the Cloud EPM, there is no drill support so the default workflow mode is set to Simple.

  If you want to see the data in Workbench for testing purpose set the Workflow Mode to Full. For more information, see Defining Application Detail Options.

To define a data export to file target application:

1. Create a .CSV file with the list of columns in the order that you want exported.

   Note:

   Do not include the Amount column in the data file. If it's included, you can delete it after the application is created.

   The name of the file is the name of the application so name the file appropriately.

2. From the Data Integration home page, then Actions, and select Applications.
3. On the Applications page, click .
4. On the Create Application page, and then Category, select Data Export.
   
5. From Type, select Data Export to File.
6. From File, select the name of the source file from which to create the application.

   You can also click and search for a file from the File Browser page.

7. In Prefix, specify a prefix to make the application name unique.
   The prefix is concatenated with the file name to form a unique application name. For example, if you want to name an application with the same name as an existing one, you can assign your initials as the prefix.
8. Click OK.

   The system registers the application.

9. From the Application page, click to the right of the data target application, and then select Application Details.
10. Select the Dimensions tab.
11. In Application Details, select the Dimension Details tab.
12. Edit the Dimension Name and Data Column Name as needed.
13. In Sequence, specify the order in which the maps are processed.

    For example, when Account is set to 1, Product is set to 2, and Entity is set to 3, then Data Integration first processes the mapping for Account dimension, followed by Product, and then by Entity.

14. In Column Order, specify the order of each column in the data export file.
    By default, Data Integration assigns the "Account" dimension as the first column in the order.
15. Click Save.
16. Click the Application Options tab, and select any applicable properties and values for the data export file.
    For more information, see Data Export Target Application Options.
17. Click Save.
18. From the Data Integration home page, click (Create), and then select Integration.

    The General page is displayed in Create Integration view.

19. In Name and Description, enter a name and description for the new direct integration.
20. In Location, enter a new location name, or pick an existing location to specify where to load data.

    A location is used to link a Source and Target along with the associated member mappings. You can define multiple integrations within a same location with different set of Options and Filter criteria. The location is primarily used to control access to an integration. You can use Location Security to control access to end users.

    If you enter a new location, you must provide the Source and Target. When you save the integration, Data Integration creates the location automatically.

    If you select an existing location, Data Integration populates the Source and Target values automatically and you cannot change them.

21. Click (Select a Source).
22. From the Select a Source page, select the direct integration source system.
23. Click (Select a Target).
24. From the Select a Target page, select the data export file target application.
25. Click Save.
26. Select Map Dimensions and map source dimension members to their corresponding target application dimension members.

    For more information, see Mapping Dimensions.

27. Run the integration to extract the data from the source system and load it to the data export file target application.
    For more information, see Running an Integration.