7 Managing Period Mappings
In your Oracle Enterprise Performance Management Cloud application, you can also use different calendars (for example, monthly, weekly, or daily), based on your application requirements (for example, different levels of periods). Because Data Integration extracts the ERP source system data to the target EPM Cloud application, it establishes the mapping relationship by defining a period mapping between the source system periods and the target EPM Cloud application periods.
Data Integration supports two types of period processing:
-
Default Period Processing
-
Explicit Period Processing
Use default period processing when the source and target applications use consistent period definitions and period naming. That is, an integration uses the Period Key and Prior Period Key defined in Data Integration to determine the source General Ledger periods mapped to each Data Integration period when the integration is run. For example, when a monthly calendar is used in both systems and the names of the periods like Jan-20 match both systems, then you use the Period Mapping Type of Default in the integration. No additional mapping is required.
Use explicit period processing when the source and target applications period definition or period naming conventions are different. Explicit period mappings enable also support additional Oracle General Ledger data sources where periods are not defined by start and end dates. Explicit mappings are set up using calendars periods in the source system option. You select the actual calendar to use for the integration from the Calendar drop-down.
In this case, you are required to define an Application Period and Source Period mapping.
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 file and adapter-based integrations.
Global Mapping—Sample Monthly Period Mapping
The following table shows how a monthly calendar from a source map 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 7-1 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 2021 | Dec 1 2020 | January 1, 2021 | Jan | Q1 | FY21 | ||
| Feb 1 2021 | Jan 1 2021 | February 1, 2021 | Feb | Q1 | FY21 | ||
| Mar 1 2021 | Feb 1 2021 | March 1, 2021 | Mar | Q1 | FY21 | ||
| April 1 2021 | March 1 2021 | April 1, 2021 | Apr | Q2 | FY21 | ||
| May 1 2021 | April 1 2021 | May 1, 2021 | May | Q2 | FY21 |
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 Cloud application.
Table 7-2 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 2020 | Jan 19 2020 | January 26, 2021 | Jan | Q1 | FY20 | ||
| Feb 2 2020 | Jan 26 2020 | February 2, 2021 | Feb | Q1 | FY20 | ||
| Feb 9 2020 | Feb 2 2020 | February 9, 2021 | Feb | Q1 | FY20 | ||
| Feb 16 2020 | Feb 9 2020 | February 16, 2021 | Feb | Q1 | FY20 |
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 7-3 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 2020 | Jan | Q1 | FY20 | ||
| Feb 1 2020 | Feb | Q1 | FY20 | ||
| Mar 1 2020 | Mar | Q1 | FY20 |
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 7-4 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 2020 | Jan | Q1 | FY20 | ||
| Feb 2 2020 | Feb | Q1 | FY20 | ||
| Feb 9 2020 | Feb | Q1 | FY20 | ||
| Feb 16 2020 | Feb | Q1 | FY20 |