Refer to documentation Implementation
To ship a round: select it, then select the DOs in the "DO list" tab.
Only the non-validated (non-confirmed) rounds are displayed.
Presentation
This tab summarizes the characteristics of the selected round (number, shipment date and time, transport code, transport mode, transport reference and quay).
Inter-site: used to stipulate if the round is of "inter-site" type or not.
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'.
Upon confirmation of an "inter-site" round, several documents dedicated to this type of shipment are generated (according to set-up):
- Inter-site delivery note (TNSBL) => 1 inter-site DN by DO present in the round, according to the output configuration set-up (depositor level set-up).
- Inter-site carriage receipt (TNSRT) => 1 inter-site CR by ship-to customer present in the round, according to the carrier record set-up.
- Inter-site carriag note (TNSRT) => 1 inter-site CN by inter-site round, according to the carrier record set-up.
For each of these 3 documents, if the set-up is not performed for the "inter-site" type shipments, the 'normal' documents will be the ones to be printed.
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. |
|   |
|   |
|   |
|   |
| 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. |
|   |
|   |
|   |
  |
| Used to stipulate whether the round is of "inter-site" type or not. |
| Destination site of the "inter-site" round. |
Close
Presentation
Step 1: Select the lines of the DOs to be shipped or right-click on "Check all" so that the system detects all the DOs that can be shipped.
A certain number of checks are carried out upon selection, namely:
For DOs without packing, there is at least one output movement to be shipped (neither deferred, nor cancelled upon shipment, nor cancelled upon preparation).
For packed DOs, the system ensures that, in addition with the condition above, all those operations necessary to the DO processing have been carried out. This is dependent on the DO context.
For instance, it will not be possible to ship an unloaded DO if the DO configuration provides for load management.
Likewise, it will not be posible to ship a partly palletized DO, even if the DO shipping configuration does not mention any load checking phase. In this instance, it is necessary to postpone or delete those parcels or SUs that must not be shipped via the corresponding functions.
Step 2: Selecting the "Save" button validates the action.
Controls: the DOs of the SUs to be shipped can be shipped (these controls are carried out to avoid accepting that a SU be shipped in several phases).
Processing:
For the unshipped DOs of the round, because they are not advanced enough, or they are deferred or not selected: DOs are automatically disallocated from the round.
For the only partly shipped DOs (in case of deferment): they remain assigned to the original round and will have to be manually reallocated to another shipment round.
For the shipped round:
Update of the Validated status and calculation of the weight/volume/LM information actually shipped.
Creation of a Carriage Note (CN) by shipment round.
Creation of a Carriage Receipt (CR) by ship-to customer code.
Creation or modification of the final or temporary Delivery Note (DN).
For the shipped DOs, according to the DO configuration:
Update of the statuses of the entities shipped with status 9-Shipped,
Update of the shipped quantities of the DO lines
Calculation of the DO balance if the balance management is activated at DO level.
The CN and the CRs are printed based on the set-up of the carrier associated with the round.
The DN and the packing list are printed based on the configuration of the outputs of the shipped DO.
Close
Fields
The following fields are present on this tab :
| No help linked to this field. |
|   |
|   |
|   |
| Site of origin of the DO. |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
|   |
Transport
| Truck's registration plate's number. |
| Seal number (customs). |
Close
Action icon
Presentation
This tab provides information on the shipment, such as its weight, volume, linear metering or number of DOs.
Close
Fields
The following fields are present on this tab :
|   |
|   |
|   |
|   |
|   |
|   |
|   |
Close
By default, the following reports are associated with this function :
EXPEDITION : Shipping statistics
This can be changed using a different setup.
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:
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 addition to the generic error messages, the following messages can appear during the entry :
DO XXX: No movement to be validated
The selected DO has the status 8 but its shipment was deferred and needs to be reintegrated to be shipped.
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: Consumable blocked upon output.
The consumable must necessarily be authorized for output for an output movement to be completed.
Application error. Forced DO shipment: Operator code not authorized.
The operator code must be authorized to perform "Forced DO shipment".
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.