Extracting data from Planning and exporting it to a flat file is made easy with Data Management. The process can then be automated with EPM Automate. Here’s how:
Starting in Data Management, select the Setup tab. Add a custom target application where the data extracted from Planning will be staged, before being exported to a flat file. For Type, select Custom Application. Enter an application name in the Application Details section. On the Dimension Details tab, add a row for each Planning dimension to be exported. The Target Dimension Class is determined by the dimension type. The Data Table Column Name is the name of the column in the Data Management staging table.
To create an output data file for the custom target application, set Enable export to file to Yes. A file will be created in the Data Management Outbox folder of your server. The Import Format determines the integration mapping between the Planning source and target application. The source Planning application and target application are selected, and descriptions can be added.
To define the relationship between source and target columns, select the source dimension that maps to the target dimension for each row. You can choose to load data into a specific member by specifying a default in the Expression text box. The location links the import format to the source and target systems. Enter a name and select the import format defined earlier. Verify and save your entries.
Period mappings are used to match period formats between the source and target systems. Global mappings are shared by applications in the EPM System, whereas Application Mapping tab mappings apply only to the target application selected. Source mappings allow specifying explicit and adjustment period mappings.
Move on to Workflow and create data load mappings, selecting the location and period to be imported from. Create a mapping for each dimension that needs to be exported. Options in the Dimension drop-down list depend on the dimensions configured in the import format. All mapped dimensions are used using the Like mapping type.
To run the data load process, define a data load rule. Verify that the correct location and POV are selected, enter a data load rule name, select the category, period mapping type, and source plan type. Filter the data to import in the Source Filters section of the Source Options tab. Enable the export to file option in the Target Options tab and specify a file name for the data file. Save your data load rule.
To execute the data load rule, select Import from Source & Export to Target, verify period selections, and refresh until a checkmark appears in the Status column. Navigate to the workbench to view the results. The data is staged in Data Management. Download the data file by locating the process and scrolling until you see the Output File column. Click the Download link and save your data file to a local folder. The exported data file contents are displayed.
After executing the data load rule, you can use EPM Automate to rerun the export process. You can also automate the execution of the batch file using a scheduler. Download EPM Automate from the Settings and Actions menu. The batch file containing command lines used to complete the export process needs the following: Cloud EPM Planning URL and credentials, a dummy text file in your local folder, your data load rule, start and end periods, and import and export modes.
The first section logs you on to Planning, the next runs the data load rule with the periods, import and export mode, and dummy file. This section downloads the data file to your local folder. The last section tells you if the process completed successfully and logs you out of Planning.
With this guide, you can open an EPM file with ease. For more information, visit docs.oracle.com.