Distinguish status events by order sector

In the lower section you control status messages by means of the /wiki/spaces/ONLINEDOKENENGLO/pages/30650082/wiki/spaces/ONLINEDOKENENGLO/pages/30650082(import/export) and mode (Air/Sea/KEP, etc.).

→ Entries per mode/sector always take priority.

You can add lines to the selected status by using the context menu.
Lines can also be copied.
However, the fields Mode and Sector will be cleared since duplicate entries are not permitted.

Status events recorded per mode/sector are currently only used by the standard EDI interfaces.

Responses from providers Champ (Traxon), ATLAS, ZAPP-Air/Sea (via 4gl program) do not yet take status events per mode/sector into account.

Oceanbooking Fill Field Rules 5 and 11

If the fill field rule 5 - B/L sent/printed or the fill field rule 11 - DAKOSY B/L sent is stored in a status type and this status is then set in an order, this has the consequence that the booking number in the order → status is no longer overwritten by incoming carrier confirmations.

• Carrier Bookingnumber - Respones in ocean booking

Adopt container no. (Export) after acceptance in the order

In order to determine where in the order the transmitted container number from the status confirmation is to be taken over, the following fills field rules are available in the status events:

• 040 - container number in goods (order)
• 041 - container number in goods (service order)
• 042 - container number in Calculation tab
• 043 - container number in EDI status tab
  

So far, only one fills field rule could be stored per statuscode.

However, if more than one fills field rule should apply, these can be entered separately in the lower area in the statuscodes for each mode and sector.

Status including port/transhipment port

If a port is transmitted with the receipt of a status, the system compares it to the port of arrival or departure of the order provided that fills field rule 002 or 003 has been recorded for the status.

→ If the ports correspond to those in the order, the fills field rule takes effect.
→ If they do not correspond, this rule will not take effect and the fields on the Transport tab will not be filled.

Fills-field rule 003 also evaluates the transhipment port. If the port of the final destination does nto correspond to the port of the status, the application compares the port with the transhipment port:

→ Ports match: If the ports match, the program fills the fields eakopf_t.ank_tship_dat and eakopf_t.ank_tship_zeitank.
→ Ports do not match: If the ports do not match, the date (arrival and transhipment date) will not be entered. d

If no port is transmitted via interfaces (status message) and if fills-field rule 003 is in effect, the program does not check the ports and enters the date of the final destination (arrival date) instead.

Champ

Actual arrival at airport of loading

For responses from CHAMP you can use fills field-rule 011 (act. arrival at port/airport of loading).

This automatically fills the field Act. arrival at port/airport of loading in the Transport tab with the data from the response.

Champ QR

Goods recipient can be automatically placed in the transport tab of an order

Enter the fills field code 044 in the status code DLV.

ZAPP-Air

Evaluate actual warehouse

For status event GIN (Gate-In for ZAPP-Air) you can select the fills-field-rule 010 (act. warehouse).

The field Warehouse Actual date/time in the Additionals tab in AWB Main will be filled along with the Gate-in message as from Airfreight version 2021.4.

→ If you do not see this field automatically in the mask, you can add it via the mask editor.

CURREL

Customs cleared per container

With status CURREL (contains the container numbers) the fields eawarecon_t.verzollung_am and verzollung_zeit are filled.

This requires that the field Filled field in the status events is filled with value 008.