...
| Aura panel | ||||
|---|---|---|---|---|
| ||||
To create a new manifest, select the Airfreight → Truck manifest in the orderand then File → New.
|
...
Contents
| Table of Contents |
|---|
| Child pages (Children Display) |
|---|
Basic data
...
Header data in the truck manifest
Field | Function |
|---|---|
Manifest ID | These fields are automatically filled by the system when a new manifest is created. |
Employee | |
Branch | |
Print date | The date fills in as the manifest is printed. |
Alternative print | This field enables to print an alternative manifest. Please note that there could be modifications in your report, which are subject to a charge. |
EDI partner | The TM can be sent to a partner via an interface. |
Gateway | The Gateway is preallocated according to your configuration in the AIR Parameter. For this, pls see Truck manifest - gateway function setup. Change the gateway, if necessary. |
Trucker | The address for the trucker is preallocated from the AIR Parameter. For this, pls see Truck manifest - gateway function setup. Change it, if necessary. |
Delivery address | The delivery address is preallocated, if an address is deposited in the gateway basic data or else in the AIR Parameter. The addresses can be overwritten, if necessary. |
Pick up date | Enter on demand. |
LKW type | The input for the truck type is entered in basic data CS Admin → CS CODES.  This field is needed for the interface, e.g. FAIR@Link. |
Buying service | The buying rate of the trucker can be entered here.
See Using services in TMS. |
Add files to the truck manifest
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
HAWBs and IATA AWBs can be assigned to a truck manifest and transmitted via the FAIR@Link interface. |
Files tab
In the lower area you can create file numbers or search for files via the search mask.
The search mask can be opened by pressing the F2 key or double-clicking in the field Files.
...
The search result will open immediately:
All files of the own branch are displayed, which are intended for the gateway according to the truck manifest header and which are not yet assigned to another truck manifest.
→ Files that are not available for transfer (e.g. HAWB number is missing) are displayed, but cannot be transferred.
...
In the result the Gateway is displayed.
The Truck manifest ID for already overtaken files and the status as to whether the manifest has already been printed (green) or not yet (red) is shown in the print column.
This serves as information - for control purposes you can also use the search mask to search for already overtaken files or files not intended for the truck manifest (Truck manifest = N).
Sort result = Click on a column heading to sort the result. A black arrow indicates the direction of sorting →
Overview - change size = Hold down the CTRL key and turn the mouse wheel. This allows you to reduce or enlarge the content of the results window.
Example: Truck manifest → Results - reduce the content of the results window
...
Example: Truck manifest → Results - enlarge the content of the results window
Set the checkmark in the column Use in order to accept the corresponding file into the truck manifest.
→ The Use-Box does not exist for files that cannot be accepted (e.g. because the HAWB number is missing or because the file was already added to a different manifest).
After having made your selection, click on the Accept button.
The adopted files are displayed on the Files tab.
The sum of the weights and volumes are displayed in the bottom line.
...
Dimensions tab
The dimensions of the files are displayed in the dimension tab.
...
Text tab
In the text tab additional information for the manifest can be recorded.
Via double click thetext modules can be selected.
It might be necessary to adjust the report for the print of the texts in the manifest.
...
EDI status tab
The tab displays the provider responses.
→ The status of the provider FLINK and the truck manifest ID (= reference number) are displayed.
When sending a TPA or BUP message, the status INTERR is set in the EDI status tab in the event of an error.
→ The status exists as a status event with all default functionalities.
There is also the INTOK status, which is set when a TPA or BUP message has been successfully processed.
...