This document explains how season handling affects the customer order flow.
A season is a limited period of time defined with valid from and to dates. It is a frequently used concept for aggregation and following-up within the fashion industry. A season consists of several delivery windows. One style can be connected to several seasons simultaneously. There is a capability to extend the selling period of a style to include it in the next season while the current season is still operating.
You can connect the season identity to customer orders and to customer order lines.
The purpose of using season handling on customer orders is to create better follow-up possibilities for accounting and statistics.
It is possible to seamlessly divide the seasons into several delivery windows. For example, a year could be divided into four seasons, and one season could be split into three delivery windows.
The season is connected to both the order header and the order line by using the 'Project number' and 'Project element number' fields. The season is checked during order entry to ensure that only items that are valid for the given season are allowed.
Default values can be defined and retrieved during order entry for the following fields: 'Season', 'Delivery window', 'First delivery date' and 'Last delivery date'.
Customer orders and customer order lines are connected to a specific season.
The connection makes it possible to select and sort the season identity.