Contents

Function in the order

• FAIR@Link Export

Configure participant codes

Dakosy links the airlines with the handling partners of the airlines in order to provide data for the handling partners.

Basic data maintenance in CargoSoft is thus not required.

Data can thus be provided to the parties involved via FAIR@Link.

The following participant codes are configured by DAKOSY:

ADMIN → EDI → EDI PARTNER

Configure EDI partner 

Description and ID sender in Header data 

The name of the EDI partner must be FLINK.

In the EDI partner the own Sender_ID (forwarder) as well as the general code for the partner FAIR@Link = FLNK is stored in the header data.

Open

Provider field in General tab

The EDI partner is also informed whether the truck manifest data is transmitted as a forecast list or already as a compiled truck manifest.

• For sending the Forecast list the code PREP has to be sent.

• For sending the TPA manifests the Code FIRM has to be sent.

Enter this code in the field Provider in the General tab in EDI partner.

Open

ADDRESSES → Adress tab → EDI References sub tab

Deposit recipient code (qualifier) in address

Qualifier are entered on the EDI References sub tab in Addresses:

• F@L = FAIR@Link Address code

• FLUNL = FAIR@Link Delivery address

The deposition is done with the qualifier F@L.

The delivery address of the truck manifest (=TPA recipient address) contains the data for the purpose of pre-advice.

TPA Recipient in the Airfreight order

• In the Truck maniffest the TPA_recipient address is entered in the Delivery address.

• Sender  of the data (Truck manifest and Build Up) is the own branch.

Determine and deposit branch address

in COMPANY → BRANCHES

Sender of the data (Truck manifest und Build Up) is the own branch.

The right branch address is recorded in the basic data Branches in the Address field (with the account no.).

in the EDI References sub tab in the Addresses

• Deposit the participant coe of the TPA_Issuer/the sending branch:

   

• Deposit the participant code in the trucker's address, in case of connection to FAIR@Link.

ADMIN → ADDRESS QUALIFIERS

With the build up message from the consol file, shipper and consignee data is transferred.

In the consol file, the address from the DES Agent (receiving agent) address field is transferred as the consignee.
If this is not filled, the consignee address will be transferred.

The handling agent that is to receive the build up message must be entered in the Handling agent address field:

The address fields must be classified accordingly:

ADMIN → STATUS TYPES → STATUS TYPES

Enter status types

The forwarder receives status types for the sent data e.g.

• from the handling partner (shipment arrived) or

• from the truck operator (delay).

In the TMS order, the status codes are displayed in the HAWB files on the Status tab (eastatus_t table):

ADMIN → STATUS TYPES → STATUS EVENTS

Available status codes from FAIR@Link

The possible status events are stored in the master data ADMIN → STATUS TYPES → STATUSEVENTS.
Here it is also controlled whether an additional eMail is sent to the user, to a distribution list and/or to the responsible empl

The status codes stored here are specified by the FAIR@Link system (Dakosy).

If you want to use your own status codes, you can store them in the master data Status types and assign them here in the Status events in the Status type field.
Your own status type is then entered in the HAWB.