Overview of Combining Calendars in Demand Plans with Aggregate Time Levels

You can combine manufacturing, Gregorian, and fiscal calendars in a demand plan with an aggregate time level to create hybrid time hierarchies.

By including a common, aggregate Hybrid time level that's above the Day level, hybrid time hierarchies for a set of calendars provide you with the flexibility to aggregate data to a week, month, quarter, year, or period in the same demand plan.

The Hybrid time level stores the definition of a partial week in the manufacturing calendar. If a manufacturing calendar week crosses 2 months, the week is split into two members at the Hybrid time level so that each member can be aggregated to a month.

The following table shows you how data is aggregated from the Hybrid time level to the Month time level in a hybrid time hierarchy for the months of December 2029 and January 2030:

Time Level	Time Level Member
Month Time Level	Saturday, 01-Dec-2029						Tuesday, 01-Jan-2030
Week Time Level	Monday, 26-Nov-2029	Monday, 03-Dec-2029	Monday, 10-Dec-2029	Monday, 17-Dec-2029	Monday, 24-Dec-2029	Monday, 31-Dec- 2029		Monday, 07-Jan-2030	Monday, 14-Jan-2030	Monday, 21-Jan-2030	Monday, 28-Jan-2030
Hybrid Time Level	Saturday, 01-Dec-2029	Monday, 03-Dec-2029	Monday, 10-Dec-2029	Monday, 17-Dec-2029	Monday, 24-Dec-2029	Monday, 31-Dec-2029	Tuesday, 01-Jan-2030	Monday, 07-Jan-2030	Monday, 14-Jan-2030	Monday, 21-Jan-2030	Monday, 28-Jan-2030

You can aggregate the data for the Hybrid time level members that begin on 01-Dec-2029, 03-Dec-2029, 10-Dec-2029, 17-Dec-2029, 24-Dec-2029, and 31-Dec-2029 to the month of December 2029. Similarly, you can aggregate the data for the Hybrid time level members that begin on 01-Jan-2030, 07-Jan-2030, 14-Jan -2030, 21-Jan-2030, and 28-Jan-2030 to the month of January 2030.

The week that begins on Monday, 31-Dec-2029, is split between the months of December 2029 and January 2030. This week is represented by two Hybrid time level members, one starting on 31-Dec-2029 for 1 day and the other starting on 01-Jan-2030 for 6 days. You can aggregate the first Hybrid time level member to December 2029 and the second to January 2030. You can aggregate the data for both Hybrid time level members to the week that begins on 31-Dec-2029.

Advantages of Hybrid Time Hierarchies

Hybrid time hierarchies provide you with these advantages:

Hybrid time hierarchies provide you with the flexibility to aggregate data to a week, month, quarter, year, or period in the same demand plan.
In contrast, if you select a manufacturing calendar, you can aggregate data to only a week or period. If you select a Gregorian or fiscal calendar, you can aggregate data to only a month, quarter, or year.
When a week spreads across two calendar months, you can use Hybrid time level members to aggregate data to the individual months.
By storing data at the aggregate Hybrid time level, you can avoid performance-related limitations of plans that store data at the Day time level.

Additional Points About Hybrid Time Hierarchies

Note these additional points about hybrid time hierarchies:

You can use hybrid time hierarchies in only demand plans.
You can't use hybrid time hierarchies in demand and supply plans.
You can select a demand plan with a hybrid time hierarchy as the demand schedule for a plan of the demand and supply or supply type.
On the Organizations and Schedules subtab on the Supply tab on the Plan Options page, in the Measure Levels dialog box, for the Time dimension, you can select only the parent levels for the Hybrid time level of the hybrid time hierarchies that are associated with the demand plan.
For a replenishment plan, on the Organizations and Schedules subtab on the Supply tab on the Plan Options page, you can select a demand plan with a hybrid time hierarchy as the demand schedule.
The definition of the Hybrid time level is unique to the calendar combination that you select for the Create Hybrid Time Hierarchies scheduled process. If you run the scheduled process multiple times with different calendar selections, each run creates a set of hybrid time hierarchies with a unique Hybrid time level.
You typically run the Create Hybrid Time Hierarchies scheduled process only once when you set up your demand plan. You need to rerun the scheduled process only if you change the start date, end date, or both of one of your selected calendars.
If you rerun the scheduled process, you also need to rerun your demand plan with the Refresh with current data option selected on the Parameters tab in the Run Plan dialog box.
Hybrid time hierarchies get created for only the time periods that are common to the selected calendars. For example, if your manufacturing calendar is from 2015 to 2025 and your Gregorian calendar from 2005 to 2035, when you run the scheduled process, hybrid time hierarchies get created for only the period from 2015 to 2025.
The buckets at the Hybrid time level can vary in length. The length of most buckets is 7 days. For each week that's split between months, two buckets of different time lengths are created. For example, one bucket could be created for 6 days and another for 1 day.
The Hierarchies tab in the Selector Tool for your demand plan displays the hybrid time hierarchies corresponding to your selection for the planning calendar on the Scope tab on the Plan Options page. For example, if you select a manufacturing-Gregorian hybrid hierarchy as the planning calendar, the Hierarchies tab displays this hybrid hierarchy as well as the corresponding Gregorian-manufacturing hybrid hierarchy.
You can select the levels of only one hybrid hierarchy on the Hierarchies tab.
The edit ranges of measures are enforced at the Hybrid time level.
For example, for the week starting 31-Dec-2029, there are two Hybrid time level members, one starting on 31-Dec-2029 and the other starting on 01-Jan-2030. If the forecasting time level is set to Week, and the plan is run on 02-Jan-2030, the forecast would begin on 31-Dec-2029. But, the first Hybrid time level member is before the plan run date and considered as history. Therefore, any measure with an edit range that's set to the future, such as Adjusted Shipments Forecast, isn't editable for the first Hybrid time level member.
In a demand plan that uses a hybrid time hierarchy, if you open a table or graph that doesn't use a hybrid time hierarchy, rows are displayed without time levels.
In a demand plan that uses a hybrid time hierarchy, for the forecasting time level, you can select only a parent level of the Hybrid time level for the hybrid time hierarchy that you selected as the planning calendar.
If you're using the file-based data import (FBDI) template for Supply Chain Planning measures (ScpMeasuresImportTemplate.xlsm) to import data for a demand plan that's using a hybrid time hierarchy, note these points:
- If you're not importing data at the time level of the measure, in the Time Hierarchy Name column of the template, enter the name of the hybrid time hierarchy that you specified as the planning calendar or any corresponding hybrid time hierarchy that contains the time level to which you want to import data.
- In the Time Level Name column of the template, if you're importing data at an aggregate level, enter Hybrid time level or a parent time level of the Hybrid time level for the hybrid time hierarchy to which you are importing data.
- In the Time Level Member Name column of the template, enter individual days within the specified time level member. The collection process automatically aggregates the data to the start date of the time level member. For example, if the time level name is Month and the time hierarchy name Gregorian:Manufacturing:Hybrid, if you enter 10-May-2022 as the time level member name, the data is automatically aggregated to 01-May-2022.
You can copy measure data between a demand plan with a hybrid time hierarchy and a sales and operations plan with an aggregate time level. The planning calendar for each available sales and operations plan is one of the calendars on the basis of which the hybrid time hierarchy for the demand plan is created. The planning calendar and planning time level of the sales and operations plan determine the level at which measure data is copied.
For example, if you copy measure data from a demand plan for which the planning calendar is a Gregorian hybrid hierarchy to a sales and operations plan that's defined at the Gregorian month, measure data gets copied at the Gregorian month level. If you copy measure data from a sales and operations plan defined at the fiscal Quarter level to a demand plan with a fiscal hybrid hierarchy, measure data gets copied at the fiscal Quarter level and disaggregated to the Hybrid time level.
You can archive a demand plan with a hybrid time hierarchy using only the hybrid time hierarchy that you selected as the planning calendar and the corresponding Hybrid time level.
You can't select another archive time hierarchy or archive time level in the Scope: Advanced Options dialog box that you open from the Scope tab on the Plan Options page.
You can extract data from a demand plan with a hybrid time hierarchy using only the hybrid time hierarchy that you selected as the planning calendar and a parent level of the Hybrid time level that corresponds to the hybrid time hierarchy.
You can't select another extract time hierarchy or extract time level in the Scope: Advanced Options dialog box that you open from the Scope tab on the Plan Options page.