You can run data rules for one period or a range of them. The global or application period mappings of the target application are used as in the standard data load process.
The source periods to be extracted are determined by the period mapping type.
Default period mappings default to the list of source application periods using the application or global period mappings based on the period key. The list of source periods is added as Year and Period filters. For example, you can load data loading from Financial Management to Essbase.
In the following example, Financial Management Application Period Mapping are loaded to Essbase Application Period Mapping for the period Jan-14 to Mar-15:
Table 30. Financial Management Application Period Mapping
| Period | Year | Month |
|---|---|---|
| 1/1/2014 | 2014 | Jan |
| 2/1/2014 | 2014 | Feb |
| 3/1/2014 | 2014 | Mar |
Table 31. Essbase Application Period Mapping
| Period | Year | Month |
|---|---|---|
| 1/1/2014 | FY14 | January |
| 2/1/2014 | FY14 | February |
| 3/1/2014 | FY14 | March |
Using the example above, when the data is loaded, FDMEE:
Uses the Essbase period mapping to determine the list of period keys: 1/1/2014, 2/1/2014, and 3/1/2014.
Determines the Financial Management period mapping, and inserts them into the AIF_PROCESS_PERIODS table.
Note: | You can have multiple source Financial Management period mappings to a given target Essbase period when the target application has a larger time frame (for example, Quarter) than the source period (for example, by Month). |
Adds 2014 as a Year filter and Jan, Feb, Mar as Period filters.
The Explicit method for loading data is used when the granularity of the source periods and target application periods are not the same. For example, you need to load data from a Financial Management application with monthly periods and a Planning with quarterly periods.
In the following example, Financial Management Application Period Mapping are loaded to Essbase Application Period Mapping for the period Jan-14 to Mar-15:
Table 32. Financial Management Application Period Mapping
| Period | Year | Month |
|---|---|---|
| 1/1/2014 | 2014 | Jan |
| 2/ 1/2014 | 2014 | Feb |
| 3/1/2014 | 2014 | Mar |
| 4/1/2014 | 2014 | April |
| 5/1/2014 | 2014 | May |
| 6/1/2014 | 2014 | June |
The result of this method of mapping:
Table 34. Result of loading Financial Management Application Period Mapping to Planning Application Period Mapping
| Period | Year | Month | Fiscal Year | Quarter |
|---|---|---|---|---|
| 1/1/2014 | 2014 | Jan | FY14 | Q1 |
| 2/1/2014 | 2014 | Feb | FY14 | Q1 |
| 3/1/2014 | 2014 | Mar | FY14 | Q1 |
| 4/1/2014 | 2014 | April | FY14 | Q2 |
| 5/1/2014 | 2014 | May | FY14 | Q2 |
| 6/1/2014 | 2014 | June | FY14 | Q2 |
Using the example above, when the data is loaded, FDMEE:
Determines the period key which is 1/1/2014, 4/1/2014.
Determines the Financial Management from the Financial Management period mapping to these period keys.
This mapping returns Year: 2014 and Periods: Jan. Feb, Mar, Apr, May, and Jun.
Adds Year and Period as source filters.