| Aura panel |
|---|
| summary | Introduction |
|---|
| params | JTdCJTIyYm9keSUyMiUzQSU3QiUyMnRleHQlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzQ2NTY3MSUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExNiU3RCU3RCUyQyUyMmhlYWRlciUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDE0OWIwJTIyJTdEJTJDJTIyaWNvbiUyMiUzQSU3QiUyMnNpemUlMjIlM0ExOCUyQyUyMm5hbWUlMjIlM0ElMjJib29rLW9wZW4lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiU3RCU3RCUyQyUyMmhlYWRsaW5lJTIyJTNBJTdCJTIydGV4dCUyMiUzQSU3QiUyMnRleHQlMjIlM0ElMjJJbnRyb2R1Y3Rpb24lMjIlMkMlMjJjb2xvciUyMiUzQSUyMiUyM2ZmZiUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybm9ybWFsJTIyJTJDJTIyZm9udFNpemUlMjIlM0ExOCU3RCUyQyUyMmFsaWdubWVudCUyMiUzQSU3QiUyMmhvcml6b250YWwlMjIlM0ElMjJzdGFydCUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzMDA0OWIwJTIyJTJDJTIyc3R5bGUlMjIlM0ElMjJzb2xpZCUyMiUyQyUyMnRvcCUyMiUzQWZhbHNlJTJDJTIycmlnaHQlMjIlM0FmYWxzZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBZmFsc2UlMkMlMjJ3aWR0aCUyMiUzQTElN0QlN0QlMkMlMjJiYXNlJTIyJTNBJTdCJTIyYm94U2hhZG93JTIyJTNBJTdCJTIyc2hhZG93cyUyMiUzQSU1QiU3QiUyMmNvbG9yJTIyJTNBJTIycmdiYSgwJTJDJTIwMCUyQyUyMDAlMkMlMjAwLjA4KSUyMiUyQyUyMnglMjIlM0EwJTJDJTIyeSUyMiUzQTElMkMlMjJibHVyJTIyJTNBMSUyQyUyMnNwcmVhZCUyMiUzQTAlN0QlMkMlN0IlMjJjb2xvciUyMiUzQSUyMnJnYmEoMCUyQyUyMDAlMkMlMjAwJTJDJTIwMC4xNiklMjIlMkMlMjJ4JTIyJTNBMCUyQyUyMnklMjIlM0ExJTJDJTIyYmx1ciUyMiUzQTMlMkMlMjJzcHJlYWQlMjIlM0ExJTdEJTVEJTdEJTJDJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmZmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyMzAwNDliMCUyMiUyQyUyMnN0eWxlJTIyJTNBJTIyc29saWQlMjIlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJib3R0b20lMjIlM0F0cnVlJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmxlZnQlMjIlM0F0cnVlJTJDJTIycmlnaHQlMjIlM0F0cnVlJTdEJTJDJTIyc2l6ZSUyMiUzQSU3QiU3RCUyQyUyMmJvcmRlclJhZGl1cyUyMiUzQSU3QiUyMnJhZGl1cyUyMiUzQTglN0QlN0QlN0Q= |
|---|
|
On the Header data tabyou can enter additional data per container (the current container number is displayed at the upper edge of the mask). |
...
Contents
...
Fields | Description |
|---|
Trucker | Planned:
The trucker address can be drawn from the address basic data.
As is customary in CargoSoft, you can find the address through the matchcode, number or search mask.
The address is transmitted to IMP and serves to provide information to the terminal about who will accept the shipment. |
|---|
Delivery address | Here you can enter the delivery address of the container. This address is transmitted to IMP. |
|---|
Dakosy code | Truckers (trucking company) linked to the Dakosy IMP Platform have their own participant code.
The code can be recorded in the address on the EDI References tab – the EDI code must be IMP!
By entering the code, participants can view all information in their IMP Platform. To set up the participant code, pls see the basic data IMP documentation. |
|---|
Est. pickup | Here you can enter the estimated pickup date → information for the terminal. |
|---|
Terminal | The system pre-assigns the terminal from the order → Header data.
You can also enter the code only now - a search mask is available.
TBN is transmitted if no terminal has been entered. |
|---|
Final destination | UN location code (optional) |
|---|
Release |
|---|
referenceYou can transmit a release reference. In the overview, this reference is displayed under Pickup request | By setting this indicator, it is possible to apply for the eRelease electronically with the carrier (note: currently only Hapag Lloyd) in the German Ports Platform via the IMP order. Requirements for this are to use of the IMP platform in the TMS, the signing of the contract for the German Ports Platform with DAKOSY (release Hamburg) and dbh (release Bremerhaven), the configuration of the IMP participant by DAKOSY so that the redirection from the IMP to the GP platform works.
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #FFFAE6 |
|---|
| Look after the field description on this page to find out how to apply for eRelease from the TMS. |
|
|---|
Release reference | A release reference can be transmitted. This reference is displayed in the overview under Pick-up reference. |
|---|
Valid to | Validity date for the transmitted release reference |
|---|
Dangerous | Whether these are dangerous goods |
|---|
Fumigated Cntr. | Whether this is a fumigated container |
|---|
Measure protocol | Whether a measure protocol is available |
|---|
Mode of transport on-carriage | 31 = LKW (truck) is pre-assigned.
This is a required field. |
|---|
Send obligation paper A18 automatically | Activate the checkbox to inform IMP that an A18 is to be created. |
|---|
Status info email 1-3 (for one-time status) | You can enter one email address per line.
Recipients will receive a link with access to the current status in the IMP.
This link only applies to one package line. |
|---|
The IMP_Platform is required for Hamburg.
The checkbox Request release can be set on theIMP tab → Header data tab. When the order is sent, DAKOSY forwards the release request to the German Ports platform.
As soon as the exemption from German Ports is available, the IMP status 950 is sent.
If the exemption is no longer valid, status 951 is sent.
The release reference transmitted in the confirmation and its validity are read into the Release reference and Valid until fields in the IMP tab → Header data tab.
Additionally the status confirmations are processed in the Order tab → EDI status tab.
The status codes are available in the master data Status events for the provider IMP and can be configured there.
For Bremerhaven, the application could be made with the BIT. However, CargoSoft has not currently implemented this.
If you only want to use the eRelease for Bremerhaven, the eRelease can also be sent via IMP!
For this purpose, the German Ports contract with DBH and DAKOSY must be signed. The IMP must be set up in the TMS. It will be sent via the IMP tab.
In this case, the IMP order would simply expire and the release request would be forwarded to German Ports.
...