Aura panel | ||||
---|---|---|---|---|
| ||||
The shipping data can be recorded via sailing lists. CargoSoft automatically accesses the sailing lists of the connected port systems Dakosy and BHT. The selection of the corresponding sailling list is based on the field port link, which is next to the order date and can be entered first. | ||||
summary |
...
Contents
...
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Links to further information
...
Record shipping route
All fields from the sailing list that are recorded for a vessel departure, either by the shipping company/agent or yourself, or that can be imported from external systems will be displayed.
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
The location code of the port of discharge entered in the order is already pre-assigned in the search in the sailing list. |
...
Fields of the section shipping route
...
Field description
Fields for shipment data | |
---|---|
Vessel no. | The vessel no. is either taken from the sailing list or can be entered manually. |
IMO code | The IMO no. is unique (similar to the chassis no. of a vehicle) and consists of the 3 letters IMO and a number with 7 digits.
Compliance → check vesselAs of SATIS version 5 the field IMO code is checked against the sanction lists. With automatic acceptance of the field from the vessel lists or with manual entry, the check is triggered. With changed values in above named field a new validation will be triggered after saving. This check is performed as part of the general compliance check that already applies to the addresses. The same threshold values apply accordingly. |
Flag | → Imported from the sailing list. |
Vessel name
| Access to the Sailing list like described above. Vessel departure list: Double click to open a search mask over vessel departures of the port link you have selected. If the transhipment or port of discarge has been filled in on the left side of the mask, they are pre-assigned in the search mask. Compliance → check vessel As of SATIS version 5 the field IMO code is checked against the sanction lists. With automatic acceptance of the field from the vessel lists or with manual entry, the check is triggered. With changed values in above named field a new validation will be triggered after saving. This check is performed as part of the general compliance check that already applies to the addresses. The same threshold values apply accordingly. |
Voyage no. | The voyage no. is either taken from te sailing list or can be entered manually. Access to the sailing list as described above. |
Call sign | The call sign of the vessel is imported from the sailing list. |
Departure (ets) | Estimated Time of Shipment = Departure date If your file number definition requires the field ets for export shipments, the ets field already appears upon entry of a file and is a required field. |
Arrival tranship. | Enter the date. |
Arrival (eta) | Enter the date or import data from the sailing list. This field may be a required field for import shipment if the file number definition has been generated accordingly. |
Terminal | If a terminal for the FCL or LCL shipment is recorded in the the sailing list, the terminal code entered there will be loaded as well. You have the option to configure terminals with client-dependency in basic data COMPANY → GENERAL COMPANY PARAMETER → TERMINAL. |
LCL/FCL | Display field only: FCL, LCL, FCL&LCL. This field is filled according to your setting in basic data SEAFREIGHT → DAKOSY → TERMINALS → field FCL/LCL. |
The field Gateway is displayed in seafreight export files if the gateway function has been acrivated and if this file has the B/L type HBL. Enter the gateway on which your LCL shipment is to be checked in. This field is not available in the seafreight import sector. Gateways are recorded individually in the basic data. → Please follow the link for more information on how to define a Gateway as profit center Seafreight and which processing and invoicing options will become available. |