GT Nexus
Background
An Entity can use GT Nexus to track shipments. There are specific details which are entered in the GT Nexus system which need to be entered into ITAS.
This process is very specialist and should only be applied for the customer that commissioned NEXUS.
The work-flow is:-
- File will be downloaded from GT Nexus in CSV format
- File will be transformed by a Company manual process to convert to ITAS specific format.
- CSV Formatted file will then be imported into ITAS.
Requirements:
- Need functionality to import these fields into the Trade/Traffic area per tranche/split.
- A report that would show the old value –vs- the new value when files are imported. Entity needs to be aware of changes made in ITAS when imports have completed
Use S01/View/Data Import/Export fields with Data table = nexus i.e. specific list of data elements. These are not all enabled for every Entity in ITAS.
The file is imported via NEXUS option.
Below are the fields that are required for import into ITAS. If fields in the import are blank, no action is taken (i.e. do not delete existing information and replace it with spaces).
| Friendly Name | fieldname | table | notes |
| Vessel | phys01_vessel | phys01 |
|
| Voyage | phys01_journey | phys01aa | |
| ETS | phys01_etsdate | phys01ac |
|
| ETA | phys01_eta | phys01ac | |
| Arrival Date | phys01_arrivaldate | phys01ac | |
| Vessel C/O | phys01_vesscutoff | phys01ac | |
| Port C/O | phys01_portcutoff | phys01ac | |
| Port2 | phys01_portorig1 | phys01ac | Only used when shipment departing from multiple ports |
| Rec2 | phys01_portrecdate1 | phys01ac | Only used when shipment departing from multiple ports |
| BL2 | phys01_bldate1 | phys01ac | Only used when shipment departing from multiple ports |
| bl ref | phys01_blref | phys01 |
|
| bl date | phys01_bldate | phys01 |
|
| shipping line | phys01_shippingline | phys01 |
|
| freight rate | phys01_freightrate | phys01ac |
|