1. Administering Data Management for Oracle Enterprise Performance Management Cloud
  2. Integration Tasks
  3. Loading Data
  4. Loading Multiple Periods for EPM Cloud or File-Based Source Systems

Loading Multiple Periods for EPM Cloud or File-Based Source Systems

For an Oracle Enterprise Performance Management Cloud or file-based source system, Data Management supports a "Period" as a column in a data file. If you have data for multiple periods in a single file, then you can include the year and period on each row of the data. In Import Formats, you select the source period rows of Year and Period, so that they are identified as columns in the file, and then map them to the appropriate dimension in the target system. Then you run the data load rule and select a range of dates to load. The range of dates can be based on a default or explicit period mapping type.

For example, in the following sample file, there is multiple period data, "Jan" and "Feb" in a single data file. 

E1,100,2016,Jan,USD,100
E2,100,2016,Jan,USD,200
E3,100,2016,Feb,USD,300
E4,100,2016,Feb,USD,400

In another example, if you select a Jan-March period range, and the file includes: Jan, Feb, Mar, and Apr, then Data Management only loads Jan, Feb, and Mar. 

E1,100,2016,Jan,USD,100
E2,100,2016,Jan,USD,200
E3,100,2016,Feb,USD,300
E4,100,2016,Feb,USD,400
E4,100,2016,Mar,USD,400
E4,100,2016,Mar,USD,400
E4,100,2016,Apr,USD,400
E4,100,2016,Apr,USD,400

Data Management loads the periods specified on the Execute Rule screen, and ignores rows in the file that don't match what you selected to load.