How Demands and Supplies Are Impacted in Supply Plans That Use Telescoping Time Buckets

When you configure your supply plan to use telescoping time buckets, you can set your planning horizon to include only days, weeks, periods, or months.

Or you can use telescoping buckets to plan in a combination of daily time buckets and more aggregate time buckets, such as weeks, months, or periods.

Let's say that you have a plan with time buckets larger than days.

The net forecast quantities that remain after forecast spreading and forecast consumption are aggregated up to the planning time bucket level.
These net forecast quantities are placed on the last working day of the planning time bucket.
The supply planning process considers each combination of item, organization, demand schedule, demand class, customer, and customer site.

For example, suppose the net forecast quantity is 10 units per working day per combination of item, organization, and demand class in a plan with all daily buckets. Your organization is set up for 5 working days per week. The same plan with weekly buckets displays an aggregated net forecast for a quantity of 50 units for each demand class. This aggregated forecast has a suggested due date of the last working day of each weekly bucket.

These are other ways that demands and supplies are impacted when you use weekly, monthly, or period time buckets.

All supply and demand orders and all resource requirement dates are subject to bucketing logic. In other words, for time buckets larger than days, dates calculated on supply and demand orders are bucketed to the last working day of the bucket. The working days specification is based on the supply planning calendar that you select on the Plan Options page, Scope tab, not the organization calendar.
When you release make or transfer planned orders created in planning time buckets larger than days, the orders have a suggested due date that corresponds to the last working day of the time bucket. Buy planned orders also have a suggested due date that corresponds to the last calendar day of the bucket. However, the implement date is set as the first calendar day of the bucket. This implement date ensures that the supplier delivers the material in time to meet the entire planning time bucket's demand for the item.
Firm dates, implement dates, and dates in the input data such as requested ship date or scheduled ship dates aren't subject to the bucketing logic. For example, you can firm a planned order that was previously bucketed to the last working day of the month to any day, regardless of whether that day is the last day of the supply planning bucket or even a working day.
When component demand is planned for a firmed supply, the component demand is subject to bucketing logic. This might cause the need-by date of the component demand to be after the due date of the firmed supply.
When generating planned orders in aggregate buckets, all order modifiers are honored except for fixed days of supply.