PerformancePoint Planning Server uses the application calendar to configure periods of time that match the practices that are used in your company. An accurate application calendar forms an essential foundation for your data. A good calendar provides context for successful financial tracking and benchmarking.
After you create and configure the application calendar, Planning Server uses your specifications to create and populate the Time dimension for your application. Because nearly every aspect of an application refers to the Time dimension, it is critical that it correctly represents your business processes. For example, if your standard reports use a quarterly time period, make sure that you specify that pattern when you configure the calendar. To learn more about how Planning Server handles time, see About the Time dimension in Planning Business Modeler.
Once you create a calendar, you cannot modify it. To change a calendar, you must create a new application and then repopulate the data.
To learn about the values that you need to configure an application calendar, follow the links in this article. To learn how to create or extend an application calendar, see Create or extend the application calendar.
What do you want to learn about?
Calendar start and end dates
When you create an application calendar in PerformancePoint Planning Business Modeler, you can define a custom calendar that matches the specific patterns of your financial system. For example, you can create a fiscal-year calendar that starts on July 1 and ends on June 30. Alternatively, you can also create a more traditional calendar year that starts on January 1 and ends on December 31.
Multiple applications might need multiple calendars to track different aspects of the business. For example, although the internal fiscal reporting calendar might end on June 30, the manufacturing division calendar might end the year on December 31.
In addition, you can configure an application calendar with a year end date that varies. In this way, you can add an extra week to some years in the calendar. For example, your company might want to add an extra week during leap years.
When you create an application calendar, Planning Server uses the locale on the client computer. Thus, calendar data is displayed in the formats and standards of the locale in which the calendar was created.
Important: If a user from a different locale makes a change to the calendar for this application, such as extending the calendar, the new data appears in the forms that are standard for the locale of the user who made the changes. Old data is expressed in the forms of the original locale.
When you create an application calendar, you can select a monthly period pattern that matches the periods that are used in your company. The list shows the common patterns that are available in Planning Business Modeler:
445 pattern. Months in a year contain weeks as follows: 4 weeks, 4 weeks, 5 weeks, and then the pattern is repeated.
454 pattern. Months in a year contain weeks as follows: 4 weeks, 5 week, 4 weeks, and then the pattern is repeated.
544 pattern. Months in a year contain weeks as follows: 5 weeks, 4 weeks, 4 weeks, and then the pattern is repeated.
13. A year contains 13 equal periods.
When you create the application calendar or extend the calendar, you can create additional custom views of the calendar data. Calendar views can be used to show members of the Time dimension in a convenient way. For example, if your calendar includes the frequencies year, quarter, month, and day, you can create a view of the data that shows only year and month data. You can then use these views in a model.