Defining Period Mappings
Note:
Starting with the September (23.09) update, the user interface pages for Period Mapping will no longer be available in Data Management, but will be available in Data Integration. Data Integration is available now from the Data Exchange card from the home screen in the Oracle Enterprise Performance Management Cloud Business Process. Users will be able access the Period Mapping features in the current EPM Cloud update from the Data Integration user interface by selecting the Actions drop down, and then Period Mapping. For more information, see Managing Period Mapping in Administering Data Integration for Oracle Enterprise Performance Management Cloud.
You can use various kinds of calendars (for example, monthly, weekly, or daily) based on your business and statutory requirements. In your EPM Cloud application, you can also use different calendars, based on your application requirements (for example, different levels of periods). Because Data Management extracts the ERP source system data to the target EPM application, it establishes the mapping relationship by defining a period mapping between the source system periods and the target EPM Cloud application periods.
Before you can define data rules, define the period mappings. Period mapping define the mapping between Enterprise Resource Planning (ERP) calendars and the EPM application year or periods. You can define period mappings in three ways:
-
Global Mapping—You define a global mapping in cases where you do not have many target applications getting data from multiple source systems with different types of source calendars. Use a global mapping to ensure that various periods are accommodated in the individual mapping. As a first step, define a global mapping.
-
Application Mapping—If you have multiple target applications, getting data from various source systems with complex period types, you can create application mappings in addition to global mappings. When you define an application mapping, you can modify the Target Period Month as necessary.
-
Source Mapping—Specifies source period mapping for adapter-based integrations.
Note:
Source mappings are also used to set up Oracle General Ledger adjustment periods. For more information, see Processing Oracle General Ledger Adjustment Periods.
Global Mapping—Sample Monthly Period Mapping
The following table shows how a monthly calendar from a source maps to monthly periods in a target application.
Note:
You should define global mapping at the most granular level. For example, if you have a monthly calendar and a weekly calendar, define your global mapping at the lowest level of granularity. In this case, the period keys are at the week level and you map weeks to months. You can create application mappings for the higher-level periods.
Table 4-7 Sample Monthly Period Mapping
| Period Key | Prior Period Key | Period Name | Target Period Month | Target Period Quarter | Target Period Year | Target Period Day | Year Target |
|---|---|---|---|---|---|---|---|
| Jan 1 2010 | Dec 1 2009 | January 1, 2010 | Jan | Q1 | FY10 | ||
| Feb 1 2010 | Jan 1 2010 | February 1, 2010 | Feb | Q1 | FY10 | ||
| Mar 1 2010 | Feb 1 2010 | March 1, 2010 | Mar | Q1 | FY10 | ||
| April 1 2010 | March 1 2010 | April 1, 2010 | Apr | Q2 | FY10 | ||
| May 1 2010 | April 1 2010 | May 1, 2010 | May | Q2 | FY10 |
Global Mapping—Sample Weekly Period Mapping
The following table shows how a weekly calendar from an Enterprise Resource Planning (ERP) source system maps to monthly periods in the EPM application.
Table 4-8 Sample Weekly Period Mapping
| Period Key | Prior Period Key | Period Name | Target Period Month | Target Period Quarter | Target Period Year | Target Period Day | Year Target |
|---|---|---|---|---|---|---|---|
| Jan 26 2009 | Jan 19 2009 | January 26, 2010 | Jan | Q1 | FY09 | ||
| Feb 2 2009 | Jan 26 2009 | February 2, 2010 | Feb | Q1 | FY09 | ||
| Feb 9 2009 | Feb 2 2009 | February 9, 2010 | Feb | Q1 | FY09 | ||
| Feb 16 2009 | Feb 9 2009 | February 16, 2010 | Feb | Q1 | FY09 |
Application Mapping—Sample Target Application Sourcing from a Monthly Calendar Source
The following table shows a sample where the target application is sourcing from a monthly calendar. This mapping is performed on the Application Mapping tab.
Table 4-9 Sample Application Mapping—Target Application #1 with a Monthly Calendar Source
| Period Key | Target Period Month | Target Period Quarter | Target Period Year | Target Period Day | Year Target |
|---|---|---|---|---|---|
| Jan 1 2009 | Jan | Q1 | FY09 | ||
| Feb 1 2009 | Feb | Q1 | FY09 | ||
| Mar 1 2009 | Mar | Q1 | FY09 |
Application Mapping—Sample Target Application #2 Sourcing from a Weekly Calendar Source
The following table shows a sample where the target application is derived from a weekly calendar. This mapping is performed on the Application Mapping tab.
Table 4-10 Sample Application Mapping—Target Application #2 with a Weekly Calendar Source
| Period Key | Target Period Month | Target Period Quarter | Target Period Year | Target Period Day | Year Target |
|---|---|---|---|---|---|
| Jan 26 2009 | Jan | Q1 | FY09 | ||
| Feb 2 2009 | Feb | Q1 | FY09 | ||
| Feb 9 2009 | Feb | Q1 | FY09 | ||
| Feb 16 2009 | Feb | Q1 | FY09 |
Note:
To avoid double counting on Income Statement accounts, be sure not to define a mapping where the adjustment period of one year goes into the period of the next fiscal year.