...

Contents

Basic data settings

• FAIR@Link export set up

• FAIR@Link Export: Pre-assign EDI partner in Truck manifest

...

Send truck manifest to FAIR@Link

The truck manifest is sent to FAIR@Link and from there distributed or made available to the participants. 

Required entries

Certain details need to be entered before the manifest can be sent.

The following fields need to be filled:

• Trucker

• Delivery address

• Truck plate no.

• Truck type

• Delivery date

• Status: The added files must contain a security status (Security text field in AWB Main tab).
  The security status for the shipment data is loaded from the field  [ecsd_t.sec_status] and transmitted accordingly.
  If this field is not filled, the application uses [eaairkopf_t.text_known_shp] instead.

The interface connects the statuses entered in CargoSoft with the FAIR@Link codes as follows:

Send truck manifest

Enter the EDI partner in ADMIN in the header data of the manifest.

Double click into the field EDI Partner to see a selection of the EDI partners available for the truck manifest.

...

Click here for more information on activating EDI partners for TMAIR and automatically pre-assigning the EDI partner.

Activate the checkbox Send to send the manifest. 

Then you can save the manifest.

...

The Send checkbox is activated automatically when you print the manifest.

The manifest will not be sent along with the print if there is no entry of an EDI partner.

Basic data FAIR@Link: configure participant code

• The TPA_Recipient address must be entered as delivery address in the truck manifest.
  

• Sender of the data (truck manifest and build up) is your branch.
  The correct branch address can be found in the menu COMPANY  → BRANCH → field Address.

Status/responses in the order

All responses are displayed on the Status tabin HAWB files.

Errors that are reported for a transmitted truck manifest also arrive in all HAWB files.

Adding a status area to the truck manifest is in planning.

In the following example, STC (Storage complete) was the last status entered.
This status is sent by the handling partner when the goods are unloaded from the truck.

...

You will receive status DVT or STC for every HAWB of a truck manifest.

CargoSoft EDI (nor FLINK) then enters status TMC – Truckmanifest completely unloaded. This status is also entered on the EDI-Status tab.

Like every other status, status TMC is recorded in basic data ADMIN → STATUS TYPES → STATUS EVENTS.

If you have activated emails about the status, the user who created the truck manifest as well as the email address entered in the mailing list will receive an email.

The email lists all HAWBs with status DVT or STC.

Automatically generate Gate-in message

The Gate In message is sent automatically once the truck has arrived at Frankfurt Airport.

→ Cameras at the gate read the number plate.

The transmission of the number plate in the truck manifest message automatically triggers the transmission of the Gate In for all shipments on the truck manifest registered through ZAPP-Air.

Send consol compilation to handling partner (BUP)

The handling agent receives information about the HAWBs belonging to a consol.

The handlings agent then can consolidate and compile the shipment and start loading.

This EDI message is also referred to as Build up (BUP).

→ The BUP message is sent from within the completely consolidated consol file.

Requirements for the transmission of the BUP message

FAIR@Link needs the participant code to identify the recipient of the BUP message.

The consol must therefore contain the address of the handling partner.
This address needs to be filled in the address field with classification [HDL].

The participant code of the partner must be available in the address itself:

Enter the participant code in the address EDI references sub tab of the handling partner with qualifier F@L:

...

Add classification HDL for handling agent to the order address field: menu ADMIN → ADDRESS QUALIFIER  

...

Enter the address of the handling partner in the order address field with classification HDL.

...

Send build up message

Open the consol file to send the message.

• Select File menu → Export → XML to Partner.

• Enter the EDI partner [FLINK].

• Activate the checkbox Send.

• Save and close the mask.

...

Capture EDI partner and store.

...

Transmit security status and reason per AWB

Just like for the TPA message, the program takes the security status for shipment details from field [ecsd_t.sec_status] and transmits it accordingly.

If this field is not filled, [eaairkopf_t.text_known_shp] is used instead.

The interface links the status entered in CargoSoft with the FAIR@Link codes as follows:

Per HAWB you need to transmit a reason code (=screening method) along with the security status in the BUP message.

These are entered on the eCSD tab.

The interface links the statuses entered in CargoSoft with the FAIR@Link codes as follows:

Status message with security measures triggers security status for HAWB in the consol

If you receive status code SEC for the HAWB, the /wiki/spaces/ONLINEDOKENTMSAIR/pages/30651434 for the HAWB is automatically entered in the field Status Consol (eaairconpos_t.status_xray=J) in the consol file, provided that it has not already been filled.

• The SPX status (eaairconpos_t.spx_status) is entered as well. This status consists of the values: codes_t.name for 'D1' + " by " + IssuingRa from the XML.

The interface also enters the security status of the consol file. The security status of the HAWBs is checked as usual.

• When entering the security status, the program reads the code entries for the language selected in the company parameters.

• The corresponding security status is entered in the CSD.