Carrier calendar constraints are important to calculate accurate delivery and shipping
dates to meet customer promises. You can configure carrier calendar constraints for non-transit and
non-delivery dates. All non-operational days are considered for transit and delivery calculations.
Before you begin
A carrier might define both non-transit days and non-delivery day constraints. To
familiarize yourself with this concept, see Calendar constraints.
About this task
To configure the carrier calendar constraints, you must configure the carrier calendar first.
Then, you apply the calendar to a carrier service.
Procedure
Configuring a carrier calendar
- To configure the carrier calendar with a unique carrier calendar ID, use the Set or update carrier calendar configuration API.
- A calendar can contain multiple fixed dates, days of the week, or both.
Use three-letter,
upper case abbreviations, such as MON, TUE for the days of the week.
- A fixed date might be any non-operational day.
Use the YYYY-MM-DD date
format for fixed dates.
Sterling Intelligent
Promising uses these dates and overrides to provide accurate
estimated delivery dates (edds) to customers.
You can apply the calendar that you
create to a carrier service.
Applying the calendar to a specific carrier service
- To apply the calendar that you created already to a carrier service, in the Set or update carrier calendar configuration API, add the
calendar ID to the non-transit or non-delivery constraints.
You can create both
non-transit and non-delivery constraints for a carrier service.
Results
The calendar constraints can be used at the carrier service level.
What to do next
View the scenarios for the carrier non-transit and non-delivery constraints. For more
information, see Scenario: Calendar
constraints.