Planning calendar, working days, and holidays¶

The planning calendar has two connected layers:

the planning bucket defines how dates are grouped into daily, weekly, monthly, or other periods;
the operational calendar classifies each date as a weekday or holiday and translates it into an effective working-day value.

The operational tables below are available when the edition includes configurable working-day calendars. They do not change the selected bucket; they refine how the days inside each period are interpreted.

Path in the platform¶

Data > Data Operations > Transactional Data > Campaign / Event Data

From this group, use:

Holidays > National Holidays;
Holidays > State Holidays;
Holidays > City Holidays;
Working Days > Working Day Configuration.

Granularity and keys¶

Data set	One row per	Key
National Holidays	holiday date and country	`country` + `holidayDate`
State Holidays	holiday date, country, and state	`country` + `state` + `holidayDate`
City Holidays	holiday date, country, state, and city	`country` + `state` + `city` + `holidayDate`
Working Day Configuration	weekday or holiday type	`dayOfWeekOrHoliday`

National Holidays¶

Required fields¶

Field	Meaning
`country`	Country whose locations observe the holiday
`holidayDate`	Holiday date

Optional fields¶

Field	Meaning	Default Value When Not Provided
`holidayName`	Human-readable holiday name	Blank

State Holidays¶

Required fields¶

Field	Meaning
`country`	Country of the state
`state`	State whose locations observe the holiday
`holidayDate`	Holiday date

Optional fields¶

Field	Meaning	Default Value When Not Provided
`holidayName`	Human-readable holiday name	Blank

City Holidays¶

Required fields¶

Field	Meaning
`country`	Country of the city
`state`	State of the city
`city`	City whose locations observe the holiday
`holidayDate`	Holiday date

Optional fields¶

Field	Meaning	Default Value When Not Provided
`holidayName`	Human-readable holiday name	Blank

Working Day Configuration¶

Required fields¶

Field	Meaning
`dayOfWeekOrHoliday`	Weekday or Holiday Type

Optional fields¶

Field	Meaning	Default Value When Not Provided
`workingDaysEquivalence`	Share of one effective working day, from `0` to `1`	`1` for Monday through Friday; `0` for Saturday, Sunday, and Holiday

An equivalence of 0.5, for example, means that the day contributes half of a standard working day to the period.

holidayName is descriptive. Country, state, city, and date continue to classify the holiday when the name is blank.

How the four data sets work together¶

The selected Planning Bucket Size defines the dates inside each period.
The platform compares each date with national, state, and city holidays applicable to the location.
A matching date is classified as Holiday; otherwise, its weekday is used.
The corresponding workingDaysEquivalence is applied.
The period receives the sum of the effective working days.

Country, state, and city are matched with the geography recorded in Locations. Standardize spelling and codes across both data sets.

Dependencies¶

Locations, including country, state, and city;
Weekday or Holiday Type;
Planning Bucket Size;
the horizon and frequency in the Demand Planning execution profile;
production-resource and shift availability when working days affect capacity.

Used by¶

working-day regressors and other internal signals in Cluster-level AutoFit;
Demand Planning key figures expressed per working day;
production-capacity materialization by period;
S&OE and Line Sequencing;
validation of effective working days by period and location.

Validations¶

use one row per key;
use an unambiguous date format;
keep country, state, and city consistent with Locations;
use only the accepted weekday or holiday values;
keep workingDaysEquivalence between 0 and 1;
confirm that the holiday range covers the planning horizon.

Changing the calendar affects future executions and analyses. It does not rewrite plans that were already generated.