| Aura panel |
|---|
| summary | Introduction |
|---|
| params | JTdCJTIyYm9keSUyMiUzQSU3QiUyMnRleHQlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzQ2NTY3MSUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExNiU3RCU3RCUyQyUyMmhlYWRlciUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDE0OWIwJTIyJTdEJTJDJTIyaWNvbiUyMiUzQSU3QiUyMnNpemUlMjIlM0ExOCUyQyUyMm5hbWUlMjIlM0ElMjJib29rLW9wZW4lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiU3RCU3RCUyQyUyMmhlYWRsaW5lJTIyJTNBJTdCJTIydGV4dCUyMiUzQSU3QiUyMnRleHQlMjIlM0ElMjJJbnRyb2R1Y3Rpb24lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExOCU3RCUyQyUyMmFsaWdubWVudCUyMiUzQSU3QiUyMmhvcml6b250YWwlMjIlM0ElMjJzdGFydCUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDA0OWIwJTIyJTJDJTIyc3R5bGUlMjIlM0ElMjJzb2xpZCUyMiUyQyUyMnRvcCUyMiUzQWZhbHNlJTJDJTIycmlnaHQlMjIlM0FmYWxzZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBZmFsc2UlMkMlMjJ3aWR0aCUyMiUzQTElN0QlN0QlMkMlMjJiYXNlJTIyJTNBJTdCJTIyYm94U2hhZG93JTIyJTNBJTdCJTIyc2hhZG93cyUyMiUzQSU1QiU3QiUyMmNvbG9yJTIyJTNBJTIycmdiYSgwJTJDJTIwMCUyQyUyMDAlMkMlMjAwLjA4KSUyMiUyQyUyMnglMjIlM0EwJTJDJTIyeSUyMiUzQTElMkMlMjJibHVyJTIyJTNBMSUyQyUyMnNwcmVhZCUyMiUzQTAlN0QlMkMlN0IlMjJjb2xvciUyMiUzQSUyMnJnYmEoMCUyQyUyMDAlMkMlMjAwJTJDJTIwMC4xNiklMjIlMkMlMjJ4JTIyJTNBMCUyQyUyMnklMjIlM0ExJTJDJTIyYmx1ciUyMiUzQTMlMkMlMjJzcHJlYWQlMjIlM0ExJTdEJTVEJTdEJTJDJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmZmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzAwNDliMCUyMiUyQyUyMnN0eWxlJTIyJTNBJTIyc29saWQlMjIlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJib3R0b20lMjIlM0F0cnVlJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmxlZnQlMjIlM0F0cnVlJTJDJTIycmlnaHQlMjIlM0F0cnVlJTdEJTJDJTIyc2l6ZSUyMiUzQSU3QiU3RCUyQyUyMmJvcmRlclJhZGl1cyUyMiUzQSU3QiUyMnJhZGl1cyUyMiUzQTglN0QlN0QlN0Q= |
|---|
|
The functions described below are available in the seafreight export and import sector.
The transhipment port is located between the port of loading and the port of discharge in the header data of a seafreight file. |
...
Contents
| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 6 |
|---|
| outline | false |
|---|
| style | disc |
|---|
| type | list |
|---|
| printable | false |
|---|
|
Links for further information
...
Example for Transhipment
The transhipment port for a shipment from Hamburg to Auckland via Singapore can be filled into the field Transhipment.
A date field for the arrival at the transhipment port is available as well.
...
→ The entries are transferred accordingly to the Transport tabin the order.
Search for vessels in transhipment
The search for shipping options is based on the entered transhipment port.
If a transhipment port has been entered, it is pre-assigned as port of discharge in the search mask.
Upon selection of the vessel, the arrival date is entered in the field Arrival transhipment.
Search for vessels with transhipment port Dakosy:
...
If no transhipmet port has been entered, the entry in the field Port of discharge is pre-assigned in the search mask instead.
ZAPP: send HDS with transhipment
On the quay request a transhipment port is transferred to the field Port of discharge.
If no transhipment port is available, the port of discharge is transferred instead.
Quay request with transhipments:
...
...
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
ATTENTION:
If the transhipment port is entered in the order header data, it will be sent as port of discharge in the HDS.
The field Port fo discharge on the Quay request tab changes its name to Transhipment and displays the transhipment port (see screenshot above).
This field is linked to the field in the header data of the file. The field Final destination on the Quay request tabis always filled wit the entry in the field Final destination in the header data. |
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
|
Particularities: If the transhipment port is DEHAM, marine transit goods is automatically pre-assigned in the HDS.
The field Port of discharge in the HDS is pre-assigned with the port of discharge from the header data.
The name Port of discharge changes to Transhipment. If the transhipment port is NOT DEHAM, the preallocation is made as described above.
|
BHT: shipment with transhipment
According to the vessel no., the port of discharge entered in the sailing list is the transhipment port.
This is transferred to the field Port of destination in BHT → Port order tab in BHT.
Image Removed
...
Port entries on the B/L tab
Transmission of ports to the B/L tab if the transhipment port is filled:
Port of discharg → Transhipment port Place of delivery → Port of discharge Final destination → Final destination
|
...
 Image Added |
Transmission of ports to the B/L tab if the transhipment port is NOT filled:
Port of discharge → Port of discharge Place of delivery → Final destination Final destination → Final destination
|
...
 Image Added |
The Transhipment field in other tabs
In the FormGen
The field via corresponds to the transhipment port and is available in the field list.
Not available on the Statistic tab
The trafffic area on the Statistic tab is pre-assigned with the entry from the field Port of discharge (export)/Port of loading (import).
→ The transhipment port is not taken into consideration.
Transfer of the field into the outgoing invoicing and invoice layout
The fields Transhipment and Arrival Transhipment are transferred into the outgoing invoicing on the Transport tab in the order.
→ If necessary, these fields can also be integrated into the invoice layout.
...
...