In E-Business Suite and PeopleSoft Financials, you have the flexibility to use various kinds of calendars (for example, monthly, weekly, or daily) based on your business and statutory requirements. In your EPM system, you can also use different calendars, based on your application requirements (for example, different levels of periods). Because ERP Integrator extracts the ERP source system data to the target EPM application, the mapping relationship should be established by defining a period mapping between the source ERP source system periods and the target EPM application periods.
E-Business Suite and PeopleSoft calendars have these important elements:
Calendar—Identifier for a calendar
Start Date—Start date of the period
End Date—End date of the period
Before you can define data rules, define the period mappings. Period mappings define the mapping between ERP calendars and the EPM application year or periods. You have three options to define period mappings:
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; for example, if in Financial Management the name is January and in Planning the name is JAN.
Adjustment Period Mapping—Typically adjustment periods are uniquely identified in the source system to record adjustment entries for the year-end or year-beginning process. Map the adjustment periods to ensure that the source system adjustment periods map correctly to the ERP Integrator periods.
Global Mapping—Sample Monthly Period Mapping
The following table shows how a monthly calendar from an ERP source system would map to monthly periods in an EPM application.
Note: | A global mapping should be defined 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 would be at the week level. and you would map weeks to months. You can create application mappings for the higher-level periods. |
Table 6. 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 ERP source system would map to monthly periods in the EPM application.
Table 7. 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 would be performed on the Application Mapping tab.
Table 8. 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 sourcing from a weekly calendar. This mapping would be performed on the Application Mapping tab.
Table 9. 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. |
Adjustment Period Mapping—Mapping the Period Key to the Adjustment Period
Table 10. Sample Adjustment Period Mapping—Mapping the period to the adjustment period
| Period Key | Calendar | Adjustment Period | Description |
|---|---|---|---|
| Dec-2003 | Accounting 13 | 13-03 | Adj Period for 2003 |
| Dec-2004 | Accounting 13 | 13-04 | Adj Period for 2004 |
| Dec-2005 | Accounting 13 | 13-05 | Adj Period for 2005 |
| Dec-2007 | Accounting 13 | 13-07 | Adj Period for 2007 |
Note: | If the source is PeopleSoft General Ledger, set the adjustment period mapping in conjunction with the related accounting year. |