...
| Project44 provides an extensive container tracking in the form of incoming status messages on the EDI-Status tab in the order after you have configured the interface. |
|---|
Requirements for the reception of status messages of the provider project44:
|
This program can be found on the Status request tab of a file. |
| Status codes are administered in the status events. |
| Contents | |
|---|---|
| |
Basic data | |
Related topics | |
ADMIN → STATUS TYPES → STATUS EVENTS
The required status codes and settings for the status request for provider project44 are entered in the basic data along with the configuration of the interface.
- These settings can be changed individually as necessary.
- In our example, the old name OCEANINS is still used for hte interface - the explanation in the Name field refers to project44.
Status messages and codes
The following status messages are transmitted and processed on the EDI status tab:
| Status code | Status description |
|---|---|
| 10 | POL changed |
| 100 | Shipment initialized |
| 101 | Shipment invalid |
| 102 | Shipment expired |
| 103 | Shipment re-initialized |
| 104 | Shipment AIS data flushed and re-generated |
| 11 | T/S port 1 changed |
| 110 | Container removed from booking |
| 12 | T/S port 2 changed |
| 13 | T/S port 3 changed |
| 14 | T/S port 4 changed |
| 15 | POD changed |
| 16 | Port changed (rerouting) |
| 17 | Number of transshipments changed (rerouting) |
| 20 | Location update |
| 25 | Discrepancy between contracted and reported ETA at POD |
| 26 | Discrepancy between contracted and reported ETA at place of delivery |
| 3 | Vessel approaching POD (time) |
| 4 | Rollover warning (vessel change) |
| 5 | Vessel entered POD |
| 6 | Vessel moored in POD |
| 7 | Vessel approaching POD (distance) |
| 8 | Vessel ETA changed while approaching POD |
| 9 | New actuals received or actuals changed |
| CDC | Container delivery to consignee |
| CDD | Container discharge at final POD |
| CDT1,CDT2,CDT3,CDT4 | Container discharge at T/S port1,2,3,4 |
| CER | Container empty return to depot |
| CGO | Container departure from final POD (Gate-out) |
| CIF | Container arrival at last inland facility (Gate-in) |
| CLT1,CLT2,CLT3,CLT4 | Container loaded at T/S port 1,2,3,4 |
| COF | Container departure from last inland facility (Gate-out) |
| VAD | Vessel arrival at final POD |
| VAT2,VAT3,VAT4 | Vessel arrival at T/S port 2,3,4 |
| VDT1,2,3,4 | Vessel departure from T/S 1,2,3,4 |
Status request tab
The queries are sent via the Status request tab in the order.
The tab must be integrated into the order via the mask editor.
Send status request
A request can be made by means of the container number, booking number and/or the B/L number.
Entry of the SCAC code is required.
By setting the checkbox request and saving, the status request is sent to the provider.
EDI Status tab
If the request has been activated, the program shows the current data about the container on the EDI-Status tab in the order.
The tab must be integrated into the order via the mask editor.
Display responses
After an incoming status message has arrived, the system prepares the status messages and checks whether the container number is already available in the goods description of the order.
If this is not the case, the system automatically creates a new package line (level 1) with the transmitted container number and the packaging code.
In case of multiple containers that have not been entered in the file, the system will enter a new package line (level 1) per container in the goods description.
Deactivate status request
You also have the option to deactivate the status request with a cancelation message on the Status request tab.
- After the transport has been completed, the status transmission is automatically set up for the containers of the order.