Importing Data
Before importing data, you must:
-
Define or load metadata and refresh the database. See Importing Metadata.
-
Prepare the data load file. Source data must be in a business process-specific data file format or in an Oracle Essbase data file format.
-
Ensure the data load files do not contain any thousands separators, quotes, and so on, around data values. Up to one single . (decimal point) character is supported.
-
Ensure the data import file type is .csv, .txt, or .zip.
You can create a data import file based on a template, or you can generate one based on the source system. To use a template, run the export data process in your business process and use the exported file as a template. See Exporting Data.
Note:
When importing data, no validation is performed on intersections to determine which are valid, and data is loaded to all intersections. To review data that has been loaded into invalid intersections, run the Invalid Intersection report before importing data to see and clear invalid intersections. See Working With Invalid Intersection Reports.
To import data:
Note:
There is no import option in this business process to clear data before import. Therefore, the import will not overwrite existing data values with #MISSING values. However, you can run a clear cube job prior to import, or clear data with a script/rule or using the REST API:
-
You can run a Clear Cube job that enables you to clear specific business process data within input and reporting cubes. See Clearing Cubes.
-
You can write a business rule that uses the CLEARDATA Essbase command to clear specific data values. See CLEARDATA in Technical Reference for Oracle Analytics Cloud - Essbase.
-
You can use the Clear Data Slices REST API to clear business process and Essbase data for a specified region. See Clear Data Slices in REST API for Enterprise Performance Management Cloud.
Caution:
If the evaluation order in the application is changed after exporting data, the import may have unexpected results.
If a value in a data load input file doesn't match the evaluated driver member type; for example, if the evaluated type of a driver member is "date" and it's corresponding input value isn't a valid date format, a driver member casting error occurs. See Driver Member Casting Errors.
Table 6-3 Videos
Your Goal | Watch This Video |
---|---|
Learn the highlights of loading data into your business process. | Overview: Loading Data in Planning and Budgeting Cloud |
Table 6-4 Tutorials
Your Goal | Learn How |
---|---|
Learn how to import and export data in your business process, including importing exchange rates into multicurrency business processes. | Loading Data in Planning |