You can define an organization’s working calendar. A working calendar is a span of dates for a defined period for which you can define any working shifts (for example, Day Shift, Night Shift), exception shifts (for example, extra shifts on the last day of the month for performing inventory stock), and exception days (for example, Fourth of July, New Years Day).
A node or an organization can choose its calendars as well as the calendars of its primary enterprise as its business calendar, shipping calendar, or receiving calendar.
A node or an organization can also inherit calendar definition from its primary enterprise when creating calendars. If a calendar is inherited from another calendar, the parent calendar’s components such as Effective Periods, Shifts, Calendar Day Exceptions, and Exception Shifts can be used by the child calendar during runtime. This implies that the inherited calendars cannot specify their own effective periods or shifts. However, a child calendar has the ability to specify its own set of Calendar Day Exceptions and Exception Shifts. These are used in conjunction with the parent calendar’s components while retrieving the day details of the child calendar during runtime.
The following limitations are assumed when inheriting calendars: