Rounds
This function is used to manage the shipment rounds, i.e.:
- View a shipment round
- Create a shipment round for unassigned DOs, or DOs that are already assigned to a round
- Modify a shipment round
- Delete a shipment round
- Display the quay schedule of the site
- Print the loading sheet
- Display and print the load of a round
The shipment round is a single-site, single-depositor round.
The shipment rounds can be processed with or without generic round management, depending on the configuration of the DO depositor and they can be of "inter-site" type or not, depending on the site-level configuration.
The round also includes, or not, a "validated" status, depending on whether or not the round has been validated (shipment confirmation).
In order to be able to manage the shipment rounds, it is necessary to manage the shipments at the output configuration level of at least one depositor of the site.
Only the non-validated rounds can be modified or deleted.
When entering the functin, only the non-validated rounds are displayed. To display the validated rounds, choose 'Select', then 'All'.
Prerequisite
Refer to documentation Implementation
Screen management
The screen is composed of three tabs: a tab to identify the round, a tab with the general information on the round, and a tab listing the DOs attached to the round.
Header
Presentation
This tab displays the round identification information: Round no., round status, generic round, date and time of the round, quay and quay occupancy duration.
This information is updated upon creation of the round
The creation of a shipment round is sub-divided into 2 steps: creation of the round header and assignment of at least one DO to the round.
When creating the round, the user selects a generic round code.
The date and time of removal (date and time of the round) are updated based on the date and time of creation, and the day and time of the next passage defined in the generic round table.
The Shipment quay and the period of immobilization of the quay (Available from version G2) are also deduced from the generic round table if the fields are entered, otherwise these pieces of information can be entered upon creation of the round, if, for instance, each round is not systematically assigned to the same quay.
The shipping quay is a store of Quay type as well as a location, whose storage type has the quay type.
The compulsory nature of these pieces of information can be set up by means of the quay Occupancy Management parameter of the current site table.
The round status is used to know its progress status.
The round number is automatically assigned to the creation of the entity.
Inter-site: used to stipulate if the round is of "inter-site" type or not.
- If this is the case, the 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 round destination is the final customers.
Destination site: used to indicate the destination site of an "inter-site" 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 :
| Number assigned by the system and used to identify the round in a unique way within a site. |
|
|
| A generic round is a set delivery round (with respect to days and maximum shipping time), a round being the content of a truck. |
|
|
|
|
| Creation date of the document (expected input, input, DO, etc.). |
| Document creation time. By default it is equal to the system time. |
| Code used to identify the store. This code is controlled in the store table. |
Address of the location. |
|
|
| Quay occupancy duration. |
| Used to stipulate whether the round is of "inter-site" type or not. |
| Destination site of the "inter-site" round. |
Close
Tab General
Presentation
This tab displays the round general information:
Some pieces of information are initialized from the information relating to the generic round:
- the carrier
- the transport method
- the freight port if it is entered
- the ship-to customer if it is entered
When creating the round, the Loading information is updated: weight, volume, linear metering, number of DOs and DO lines of the round.
Calculation formula for a DO < status 4- Pending preparation :
Weight/Volume/LM of the product container of the DO line * qty to be launched of the DO line for DO lines <> status 9.
The kit type lines are not taken into account.
Calculation formula for DOs > status 4- Pending preparation:
For packed movements: Weight/Volume of the parcles of the DO (actual weight or theoretical weight)
For unpacked movements: Weight/Volume/LM of the original container of the output movement in case of a homogeneous object, otherwise, tare of the container of origin and weight of the lower container of the original container.
Close
Fields
The following fields are present on this tab :
Transport
| 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. |
| Carrier reference. |
| Code of the freight type defined in the freight type table. |
| Code of the ship-to customer defined in the customer table. |
Loading
|
|
|
|
|
|
|
|
|
|
|
|
| Linear metering of an entity. |
|
|
|
|
|
|
|
|
|
|
|
|
Close
Tab DO list
Presentation
This tab is used to:
- assign the DOs to the round
- either by entering the DO no. in the Number column,
- or by selecting the DOs in the left list ‘DO to be shipped’,
- or by selecting the DOs "pending transfer" in the left list ‘DO pending transfer’,
- or by using the selection utility via a memo code.
The selected DO nos. must be managed with shipment management at DO header level.
As the selection progresses, the grid is filled witthe the selected DOs. They are sorted by increasing order of round position, then by increasing DO no.
The Weight and CU no. information is calculated for the movements that are not deferred, not cancelled and not shipped.
Once the DOs to be assigned have been selected, press the button "Save".
- Consistency controls are performed:
- the sum of the weight, volume and linear metering of the DOs of the round must not exceed the maximum levels set up at generic round level (if entered).
- for each SU of the round, the system checks that the DOs of each SU belong to the same round.
The Transport tab of the DO header is updated with the information of the created round and the round no. is updated for the output movements that can be shipped.
- disallocate one or several DOs of the round
-either by selecting the round, positioned on the line to be disallocated from the DO line, and right-clicking to delete the line.
The action must be validated via the "Save" button.
- or by displaying in the left list "DOs to be shipped" those DOs allocated to the round and displayed in blue and then disallocating them by clicking on the blue dots (which turn white).
The ‘DO List’ grid is updated accordingly.
The action must be validated by means of the "Save" button. - modify the position of the DO in the round.
This position can be transmitted via an interface or assigned to the ship-to customer code.
If it is entered, it enables the truck to be loaded in the requested order by means of the loading sheet so as to optimize the unloading of the various delivery points.
Close
Fields
The following fields are present on this tab :
Grid
| Code representing the depositor. In logistics terms, the concept of depositor makes it possible to process separate flows or traffics within the same site. It encompasses the concept of order-issuing customer for the service providers. After the site, the depositor is the second access key to the Product, Input and Delivery Order files. For the location, the depositor code is entered if the location is allocated to the depositor or to the product, and if the location is single-depositor or single-product or if it is not empty. |
| Numerical sequence automatically assigned by the system upon validation of the DO header. This number features an information specific to the system, all depositors included. This piece of information features a unique access key to a Delivery Order. |
| Site of origin of the DO. |
|
|
| Order in which the round must be loaded. This information is used to allocate an unloading or loading sequence number to the DOs of a round. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Close
Action icon
Other conditions
Deletion of a round
- A round can be deleted by being selected and deleted using the "Delete" button. Only the non validated rounds can be deleted.
- The round information like the no., the date and the time are reset to zero in the Transport tab of the DO header.
- A round can also be deleted by assigning all the DOs of this round to an already exisitng round or to a new round. The system then detects that the original round is without DO and deletes it.
Left lists
- The "Rounds" left list enumerates the already composed rounds that can be selected for modification purposes.
- The "DOs to be shipped" left list enumerates the DOs that are not shipped and having the shipment management activated.
- The "DOs pending transfer" left list enumerates the DOs originating from a remote site and whose destination is the current site. There only appear the DOs "pending transfer" for which the "inter-site" round of the distant site, to which they belong, has been confirmed.
Reports
By default, the following reports are associated with this function :
TOURNEE : Loading sheet
This can be changed using a different setup.
Menu Bar
The "Planning" button provides access to a quay occupancy display screen based on the carrier appointment taking for the receipts and on the quay allocations for the shipping rounds. This functionality is available from the G2 version. |
Menu Bar
Drill Down / SUs
From a round, it is possible to display the Shipping Units of the DOs assigned to the round.
Drill Down/Parcels
From a round, it is possible to display the parcels of the DOs assigned to the round.
Drill Down/Transactions
From a round, it is possible to display the movements of the DOs assigned to the round.
Drill Down/Overview
Used to launch the load analysis for the selected round.
The load analysis function is dependent on the LA0 activity code and on the presence of at least one active DO (status < 9) in the round.
The analysis will deal with the list of active DOs (status 2 to 8) from the round.
If a SU is linked to several DOs from the round, the load considered for each station corresponds to the average calculated loads for each pair (SU/DO).
Further to a load analysis request
• a new analysis is created with the following characteristics:
- Flag to be kept to "no"
- Template (for information):
the template associated with the triplet (function, current site, current depositor) for a single-depositor function.
By default, or for a multi-depositor function, the template associated with the triplet (function, current site, depositor set to "blank".
By default, the template associated with the triplet (function, site set to "blank", depositor set to "blank").
By default, the template is left blank.
The calculation is launched for the analysis
The operator has access to the display screens of the load from which they will also have access to the information relating to the analysis (description and flag "to be kept") and be able to request the printing of the analysis results.
Functions / Round load
This function enables the creation, calculation and access to a load analysis corresponding to the list of the DOs not assigned to the current round of the picking list.
This function does not take into account the DOs flagged "pending transfer" in the load calculation.
This analysis integrates the aspect of the possible filters applied to the picking list via the advanced selections of the "Sort" option.
Functions/To be shipped DO load
Used to declare 1 or n stock-issue movements of consumables within the framework of the round.
This entry can take place at any moment, irrespective of the round status.
It is necessary to enter various information to perform a consumable output movement:
- The consumable code: is specified in the product record of the consumables
- The movement code: must belong to the group of the 'CONSUMABLE' processes and be of 'OUTPUT' type
- The quantity:quantity of the output movement
Since the output movement of the consumable is declared from a known entity, the carrier, transport method, customer and customer title information is, if need be, entered with that of the entity.
For an output movement, such information as supplier, supplier title, type of entity and number of said entity is not accessible.
Depending on the setup, it is requested to enter an operator code to validate the input movement. The stock is incremented upon validation.
The movement can no longer be modified after validation. Therefore it is not updated when updates are carried out on the entity with which this movement is associated.
It is possible to generate 3 reports:
- In File/Print/Record:
- Stock of the consumables sorted by consumable or by quantity
- Screen print for the selected record
- In File/Print/List:
- Movements of the consumables sorted by consumable or by date
Functions / Consumable movements
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Quay: Mandatory field
The quay occupancy management is set up in the site table, consequently the quay must also be entered.
Type of store <> type of quay
The entered store does not have the Quay type.
Incorrect format
The entered address format is not the one of the entered store.
Overlapping with round XX.
A round XX has already been created and assigned to the same quay and the same period (non blocking message).
Record already exists
A round XX has already been created for the same reference and the same round date and time (non blocking message).
Unauthorized day
The entered round date is not authorized for the generic round (non blocking message).
Ship-to customer incompatible
The round is associated with a customer and the DO to be assigned to it has a different ship-to customer.
Freight type incompatible
The round is associated with a freight type and the DO to be assigned to it has a different freight type.
DO without shipment management
The DO header is not set up to allow shipment management.
The error messages associated with the consumable movement declaration are the following:
"Consumable" field error. Mandatory field
The consumable code is a mandatory entry.
"Movement code" field error Mandatory field
The movement code is a mandatory entry.
"Movement code" field error Movement code of non-consumable type.
The entered movement code must belong to the group of the 'CONSUMABLE' processes.
"Movement code" field error Movement code of entry type.
The entered movement code must necessarily be of 'OUTPUT' type.
"Quantity" field error. Mandatory field
The quantity of the input movement must necessarily be entered.
Application error. The depositor must be entered for this origin.
When an input movement is associated with an expected input or a direct input, the depositor must necessarily be entered.
"Mvt origin no." field error. Reference of the origin not found.
The number of the Warehousing entity must necessarily be entered and exist for the site.
"Consumable" field error: Consumbale blocked upon output.
The consumable must necessarily be authorized for output for an output movement to be completed.
The destination site must be different from the current site.
An "inter-site" round cannot have the current site as its destination site.
"Destination site" field error: Record does not exist
The destination site must belong to the same folder as the current site.