The calendar establishes the application’s base time periods, first fiscal year and month, and total number of years. Select the base time period and monthly distribution pattern based on the number of fiscal weeks in a month. The base time period options are the bottom-level time periods in the application. You can create a custom base time period, such as weeks or days. Use monthly distribution patterns to determine how data entered into a summary time period is distributed or spread among the base time period that you select. Users can enter data into summary time periods, such as years or quarters. Planning distributes these values over the base time periods that constitute the summary time period.
For the fiscal year, you can set the fiscal year first month and specify whether the fiscal year starts from the same calendar year or the previous calendar year. You can later set up calculations based on the calendar year, for example, using formula expressions. When setting up formulas for a Planning application, keep in mind that formula expressions such as [TPDate] and [FirstDate] produce different results if the application starts in the same calendar year or previous calendar year.
The following table provides examples of how the Fiscal Year First Month and the Fiscal Start Year options affect the calendar for the application, assuming the Fiscal Start Year is 2012.
Table 31. Examples of Fiscal Year First Month and Fiscal Start Year Calendar Options
| Fiscal Year First Month | Fiscal Start Year | Period - Year | Years Dimension |
|---|---|---|---|
| January | Same Calendar Year | Jan-12 to Dec-12 | FY12 |
| July | Same Calendar Year | Jul-12 to Jun-13 | FY12 |
| July | Previous Calendar Year | Jul-11 to Jun-12 | FY12 |
| February | Same Calendar Year | Feb-12 to Jan-13 | FY12 |
| February | Previous Calendar Year | Feb-11 to Jan-12 | FY12 |
| December | Same Calendar Year | Dec-12 to Nov-13 | FY12 |
| December | Previous Calendar Year | Dec-11 to Nov-12 | FY12 |
To set up the calendar:In Create Application, to set how calendars roll up, select a Base Time Period option:
12 Months: Four quarters per year; months roll up into parent quarters and quarters into years.
Quarters: Quarters roll up into years.
Custom: A custom time period, such as weeks or days.
This selection defines the starting fiscal year for the application. You cannot change it after creating the application. Before specifying the first fiscal year, consider how much historical data your organization needs and wants in the application.
Select the Number of Fiscal Years for the application.
This selection defines the number of years in the calendar. You can add more years to the calendar after the application is created.
Enter or select the Fiscal Year Start Date.
This selection is the start date in the fiscal year for the application, which depends on the First Fiscal Year option.
If you set the base time period as 12 Months, select a Weekly Distribution option: Even, 445, 454, or 544.
Weekly distribution sets the monthly distribution pattern, based on the number of fiscal weeks in a month. This selection determines how data in summary time periods spreads within the base time period. When users enter data into summary time periods, such as quarters, the value is distributed over base time periods in the summary time period.
If you select a weekly distribution pattern other than Even, Planning treats quarterly values as if they were divided into 13 weeks and distributes weeks according to the selected pattern. For example, if you select 5-4-4, the first month in a quarter has five weeks, and the last two months in the quarter have four weeks.
To create an All Years parent member that includes all years, select Yes for All Years parent.
The All Years parent member enables users to view the accumulated data across multiple years, for example, a project's total cost up to its end date. The parent member does not include the No Year member, if one is defined for the application.
Set up custom dimensions for the application. See Setting Up Custom Dimensions and Metadata.