Seasonalities
For a site and a depositor, this function allows to associate to each quintet (group, sub-group, family, sub-family and origin) the weighing coefficients, associated to a period of time, to be applied : 
on the movements carried out during the given period, on the movements expected for a given period,
allowing to anticipate the foreseeable variations of the prompting during the period of the picking rearrangement.
Example :
Management in the data base of the group of items with strong variations such as the group of items ‘swimming suits’
It is then interesting for these items to weigh :
- the movements carried out between June and September with a coefficient of 4
- the movements carried out between October and May with a coefficient of 1.
If the reassignment of the picking locations is put in place for the summer period(June to September) then in the calculation of the number of promptings of the movements realized during the month of October to November will be weighted by 4 (weighing coefficient of the reassignment period/weighing coefficient of the movement) and the movements realized during the month of June to September will be weighted 1(weighing coefficient of the reassignment period/weighing coefficient of the movement) so as to anticipate the important activity during the summer months.
Prerequisite
Refer to documentation Implementation
Screen management
The screen is made up of one tab.
Entry screen
Presentation
The screen allows to associate for each quintet (family, sub-family, group, sub-group, origin) a weighing coefficient for each period of the seasonality.
The weighing coefficients are applied to each take corresponding to the record with the smallest sequence number and for which all the given criteria correspond to that of the take.
For each created sequence number created, the system counts the number of items corresponding to the five criteria of the sequence.
The sequence n° is mandatory, strictly greater than 0 and allows to classify the seasonalities.
Thus, an item might corresponds to several sequences but it will always be counted on the sequence with the smallest number.
The system does not allow the creation of a sequence with a number greater than another sequence having much wider criteria.
A generic seasonality might be defined by leaving all the five criteria to blank.
If the user creates a seasonality sequence that corresponds to no item then the system warns the user who can continue or abandon his keying in.
If on the table, no record corresponds to the processed take, the system does not apply to the take the weighing linked to seasonal variations.
Definition of a chart to define the weighing coefficients by period of seasonality..
Close
Fields
The following fields are present on this tab :
Block number 1
| Number making it possible to use the rules defined in this screen by order of priority. |
Grid Seasons
| Start date of the period during which the weighing can be applied to the completed movements. |
| End date of the period during which the weighing can be applied to the performed movements. |
| Weighing criterion applied to products meeting the criteria with a view to taking seasonality into account. |
Block number 2
| The family enables products to be classified on the basis of a criterion chosen by the user. It features the entity that defines the packing rules at product level. |
| The Sub-family enables products to be classified on the basis of a criterion chosen by the user. |
| The Group enables products to be classified on the basis of a criterion chosen by the user. |
| The Sub-Grou enables products to be classified on the basis of a criterion chosen by the user. |
| L’The origin’ enables items to be classified on the basis of a criterion chosen by the user. It is generally used to define or further determine the origin (geographical or other) of the products managed by the system. |
Characteristics
|
|
| For each day from the 1st of January to the 31st of December, the quantities issued for the products of the specified seasonality are added for all the years of the processing folder and archive folder. This quantity is divided by the number of years found to obtain a yearly average for each day. |
Close
Menu Bar
Functions / Refresh
From the output movements of the items corresponding to the five criteria of the seasonality, the system : automatically defines the significative periods of the seasonality calculate for each period its weighing coefficient calculate the mean number of CU put out per day of the items corresponding to the seasonality.
The processing can be launched for a seasonality or for all the seasonalities of the site and the current depositor.
The parameter ‘polishing index’ allows to ease the strong variations of the output quantities per day by getting the mean put out quantities of the previous days.
The two parameters ‘Polishing index’ and ‘Maximum nbr of seasons’ allows to minimize the number of period of a seasonality calculated by the system.
After the launching of the process, the system displays a trace with the number of created significative seasonal variations for each seasonality.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Zone ‘sequence’, mandatory field
The sequence n° keyed in should be strictly greater than 0
Zone ‘Group’, Unknown record
The value keyed in is unknown on the table of groups
Zone ‘Sub-group’, Unknown record
The value keyed in is unknown on the table of sub-groups
Zone ‘Family’, Unknown record
The value keyed in is unknown on the table of families
Zone ‘Sub-family’, Unknown record
The value keyed in is unknown on the table of sub-families
Zone ‘Origin’, Unknown record
The value keyed in is unknown on the table of origins
Filter intercepting an earlier sequence
creation or modification of a sequence with values lesser than another sequence having an inferior number.
Filter intercepting a latter sequence
creation or modification of a sequence with values greater than another sequence having a superior number.
Warning, Empty selection
The sequence of the created seasonality does not correspond to any item. The user can then abandon or continue his keying in.
Zone ‘Start’, mandatory field
The start date of the seasonality period should be keyed in.
Zone ‘End’, mandatory field
The end date of the seasonality period should be keyed in
Zone ‘Weighing’, mandatory field
The weighingcoefficient of a season should be strictly greater than 0.
Zone ‘End’, overlapping with the line N°X
Key in of a new season that overlaps a season already existing.
Zone ‘Start’, code exists already on line X
There is already a season with the same start date.
Zone ‘End’, code exists already on line X
There is already a season with the same end date