Generic rounds
This table is used to define all the generic Rounds. This screen is used to:
Consult the detail of a generic round.
Modify the set-up of a generic round.
Delete a round.
Create a new round, in other words, predefined "fixed" delivery rounds.
Prerequisite
Refer to documentation Implementation
Screen management
The entry is made on a single screen.
It is an optional function that will be used depending on the site set-up.
Entry screen
Presentation
To create a generic round, a code is assigned to it that identifies it in a unique manner by site with 10 alphanumerical characters, and a name.
These pieces of information are located in the header of the management screen. Then information is provided on this generic round.
The generic code round is unique, there can be n round codes associated with the same pair (carrier/transport method).
Carrier code. It is the code that identifies the carrier. Its existence is controlled in the carrier table.
Transport method. This code is controlled in the transport method table. Usually the transport method corresponds to the concepts of Messaging, Chartering, Express, etc.. It must also be defined as being associated with the carrier code in the carrier table.
Freight type. This code is controlled in the freight type table. If this code is entered, the round includes either DOs without freight type, or DOs with the same freight type as the one specified in the round
Ship-to customer(Available from version G2). This code is controlled in the customer table. If this code is entered, the round includes either DOs without ship-to customer code, or DOs with the same ship-to customer code as the one specified in the round.
Maximum
Weight, volume, maximum linear metering. This information is used to limit the filling of the truck, trailer container, etc. above its clearance. A functional message will warn the operators that the maximum thresholds are reached.
Preparation times. Used to calculate the most appropriate round during the search for an optimum round for the DO.
For instance, it is 3 pm, the round will go through at 5 pm and the preparation time for this round is 3 hours. The DOs will be assigned to the next round. If generic rounds are not managed, the preparation time of the DOs mentioned in the transport criteria table is taken into account.
Quay occupancy
Quay.(Available from version G2).This code is controlled in the store table. Used to specify the loading quay of the round.
Duration. Quay occupancy duration for the generic round. In the quay occupancy schedule, the quay will be occupied from the time of the round until the specified duration has been reached.
Limit days and times
Used to define the days and times in the week when a delivery round takes place.
Inter-site
Inter-site: used to stipulate whether or not the generic round is of "inter-site" type.
- If this is the case, the generic round has the type "inter-site" and its destination is another site. In which case the next field, "destination site", must be entered.
- If this is not the case, the generic round destination is the final customers.
Destination site: used to indicate the destination site of an "inter-site" generic round. This field is mandatory when the previous parameter has been set to 'yes'.
- The destination site must be different from the current site.
- The destination site must belong to the same folder as the current site.
Close
Fields
The following fields are present on this tab :
Block number 1
| A generic round is a set delivery round (with respect to days and maximum shipping time), a round being the content of a truck. |
|
|
|
|
| Select this check box to activate the current record. Disabled records keep their content and setup but cannot be used (by recalling their code) on other records (documents, settings ...), or for mass processes. The authorizations to a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature Workflow. |
| Code identifying the carrier. This code must be defined in the carrier table. |
| Usually, the transport mode corresponds to the notions of messaging, freight, express,... The transport mode is checked against the transport modes table. |
| Code of the freight type defined in the freight type table. |
| Code of the ship-to customer defined in the customer table. |
Maximum
| Maximum weight. |
|
|
| Maximum volume. |
|
|
| Maximum linear metering. |
|
|
| Upon the automatic allocation of a DO to a round, the process takes this parameter into account, added to the process launching time, in order to determine the optimum round. If generic rounds are managed, the round parameter is the one to be taken into account, otherwise, it is the parameter of the transport criteria table that will be considered. In the absence of any automatic round allocation, this parameter is not used. |
Days and hours
| Week day. |
| Limit time during the day. |
Dock Assignment
| Code used to identify the store. This code is controlled in the store table. |
Address of the location. |
|
|
| Quay occupancy duration. |
Inter-site
| Used to stipulate whether the round is of "inter-site" type or not. |
| Destination site of the "inter-site" round. |
Close
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Carriers, Record non-existent
An attempt has been made to enter a non-existent carrier.
Transport methods, Record non-existent
An attempt has been made to enter a non-existent transport method.
Carriers, mandatory field
It is mandatory that the carrier is assigned.
Transport methods, mandatory field
The transport method MUST be entered.
Freight type, Record non-existent.
An attempt has been made to enter a non-existent freight type.
Ship-to customer, record does not exist
An attempt has been made to enter a non-existent customer.
Quay, record non-existent
An attempt has been made to enter a non-existent quay.
Transport method not associated with carrier XXX.
The entered transport method is not associated with the carrier in the carrier table.
Incorrect time
The entered value is higher than 23:59.
"Destination site" field error: Record does not exist
The entered destination site does not belong to the same folder as the current site.
The destination site cannot be the current site.
The destination site of the generic round must be different from the current site.