...
| Aura panel | ||||
|---|---|---|---|---|
| ||||
A freight forwarder can transfer transport orders to its service providers electronically via the FORTRAS interface. In CargoSoft, transport orders are created and transmitted on the Services tab. An order is referred to as aBordero. The file number with the suffix [T001] with the order type and a 3-digit serial number is the reference number, reference of the order and Bordero number at the same time. |
...
Contents
| Table of Contents |
|---|
| Child pages (Children Display) |
|---|
Basic data
...
Header data tab
The Header data tab must be configured for the FORTRAS transmission, i.e. to have all necessary additional fields and functions, via the mask editor.
The mask for the transport order is configured according to the requirements and contains the fields that FORTRAS requires.
All required data are contained in the basic data; the dropdown lists thus only contain valid entries.
...
Fields in the upper section
Field | Description |
|---|---|
Reference order | File number + suffix [T001]; automatically generated upon creation Serial number per transport order Also referred to as: reference number, Bordero number (Fortras term) |
ECM Contract (buy) | Description of the ECM contract, if available. |
Freight charge | Currency code and amount for price agreements. |
Main carriage with | These fields are pre-assigned with data from the main order and cannot be edited. |
Created on | The system automatically enters creation date of the transport order. |
Created by | Pre-assigned with the user code |
Transport type | This field is pre-assigned with the entry selected on the Overview tab - this field is not used. |
Address fields
The address fields in the service order are controlled by preallocations made in basic data ADMIN → PREALLOCATIONS through address qualifier and address basic data.
→ These preallocations are made separately for import and export orders.
| Note |
|---|
Certain FORTRAS fields in the addresses are crucial for the data transmission. |
Address | → | Field |
|---|---|---|
Service provider | → | EDI partner |
Customer | → | Delivery term |
Delivery address | → | Delivery date |
Address section | Address/Field | Description |
|---|---|---|
Service provider
| Address | The service provider address is pre-assigned with the address on the Overview tab. The service provider must be recorded as an address → configuration of the service provider→ ADDRESSES → ADDRESSES. |
EDI partner in ADMIN field | This field must contain the receiving transport company. | |
Customer | Address | The SENDING branch MUST be the customer of the transport order. The branch must be recorded as an address → configuration of the customer in COMPANY → BRANCHES. |
Delivery terms | The customer address contains the delivery term for this transport order. The delivery terms are pre-assigned with fixed entries from a table - these are not the delivery terms of the main tab. | |
Freight payer | Address | The freight payer can be transmitted to the transport company. This ought to be an address existing in the basic data. |
Pick up address | Address PUP | The pickup address can be pre-assigned automatically through preallocations of the PUP address (Pick-up in the Address qualifier in ADMIN). |
Delivery address | Address DEL | The delivery address can be pre-assigned automatically through preallocations of the DEL address (Delivery in the Address qualifier in ADMIN). |
Field Delivery date | The delivery address also contains the delivery date. The delivery dates are pre-assigned with fixed entries from a table. A date and/or time field appears depending on the selection of the code. These field combinations cannot be changed. |
Free text
The Transport type field in this lower section is crucial and must be filled with the FORTRAS transport type.
General | You can transmit 4 free texts. |
|---|---|
Delivery | |
Pickup | |
Invoice | |
Text code 1 - 24 | These fields originate from Codes_ext and correspond to the FORTRAS interface data. Up to 24 information text fields (add-on fields) for the transmission can be added and placed in the mask, if required. |
Transport type | Required field FORTRAS for the transmission = FORTRAS transport type. The valid entries are configured in your basic data. Select an entry from the dropdown list. |
Goods tab
Field Packaging code | The packaging codes must be recorded in the EDI code conversions in ADMIN. |
|---|
Dangerous goods sub tab
| Warning |
|---|
Please check whether dangerous goods right IMDG is pre-assigned when transferring the order data from a seafreight file. It MUST be changed manually to ADR! In dangerous goods shipments the field Hazardous legislation MUST be checked and corrected if necessary! |
FieldAmendment | For dangerous goods right ADR = required field → Possible entries are [15] or [17] Converted through EDI code conversions in ADMIN(Attention: These data must be maintained!) |
|---|
The Dangerous goods tab contains more fields than can be transmitted via the interface.
...
The following fields are used currently:
Amendment
BAM no.
Classification code
Environment. hazardous
Gross weight
Hazard label 1-4
Limited quantities
Multiplier
Name
Net weight / Liter
Packaging code
Packaging group
Quantity
Transport category
Tunnel constraint code
UN no.
Customs sub tab
The following fields of customs data are available for the colli line of the shipment description.
...
eFile tab
The documents in the eFile are added to the transport order are sent accordingly.
→ Every document type is supported and can be added.
Up to 4 added documents are transmitted when sending. Before sending pelase check whether all of the documents ought to be sent to the service provider.