| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Cargo Controller has replaced the Portbase Information System. For detailled information on this service pls |
...
see https://www.portbase.com/en/services/cargo-controller/. This new service only applies to the tracking of import shipments, not to the import customs data that are sent via the Portbase tab of an order or export shipments! |
| Aura panel | ||||
|---|---|---|---|---|
| ||||
Cargo Controller is a status system for tracking sea freight IMPORT shipments via Dutch seaports. |
...
The Portbase interface has now been adapted accordingly so that the new Cargo Controller service can be used in the TMS. |
...
This means that the status of Portbase is automatically imported into the order for import shipments. These are displayed in the order on the EDI-Status tab. |
CargoSoft can activate automation to send status requests automatically from the TMS.
Contents
| Table of Contents |
|---|
Related topics
Basic data for this function
...
...
Status request tab in the order
A status request is sent in the CargoSoft order.
By setting a specific status, the Cargo Controller places a confirmation directly in the order.
The status request can be made both manually and automatically.
Field | Description |
|---|---|
Container number | Required field |
B/L | Required field |
Automatically send status requests
To avoid having to send a status request manually for each individual shipment, CargoSoft can activate an automation that sends the status requests automatically from the TMS.
The following entry is activated in Global_sett_t for this purpose:
Key | PORTBASECC-AUTOMATIK |
|---|---|
Value | J |
Preconditions
A consignment must meet the following requirements for the system to send an automatic status request:
Only if all these criteria are met this automatic system will be activated!
Mode | (eakopf_t.modus) | Sea |
|---|---|---|
Sector | (eakopf_t.bereich) | Import |
Port of discharge | (eakopf_t.fk_hafen_mc_best) | Rotterdam (NLRTM) |
| ||
| ||
Manual status request
Status request tab
One status request must be sent for each B/L on the Status request tab.
The status request is manually sent by the user.
...
This must contain a container number (at least one of the order, even if several containers are contained in the file) and the OB/L number.
A status request does not have to be sent for each container - a status only needs to be requested once for each master OB/L.
...
EDI-Status tab
The status of the B/L is reported back for all containers on it and displayed on the EDI Status tab.
...
Current Portbase status codes
Status code | Meaning |
|---|---|
Accepted | Technical o.k. Cargo Information |
Rejected | Technical error Cargo Information |
PRE | Pre-Arrival |
ARR | Arrived |
DEP | Departed |
CAN | Cancelled |
ACC | functional o.k. Cargo Information |
BLOCK | Blocked |
SCAN | Scan Inspection |
FYCOI | Physical Inspection |
FYCOU | Physical Inspection Unpack |
SCFYU | Scan + Physical Inspection Unpack |
SCFYI | Scan + Physical Inspection |
ACD | Terminal actual discharge date |
INTERR | Interface runs for an error while processing the data, the export of the data to Portbase does not work. |