Categories
Coparn EDI Translations

EDI Party Enquiry – Coparn

EDI Party Enquiry is part of the EDI functions of Master Terminal.  It allows users to configure how certain EDI messages are processed, given Operators often use standard EDI formats differently to relate information to the terminals.

Based on feedback from terminals, Master Terminal enables users to determine how values in EDI messages load into the database for the following messages;

  • Coparn
  • IFMCS
  • X12 315 BOL
  • CUSCAR
  • X12 301
  • Qatar Customs
  • Baplie
  • IFCSUM
Access to the EDI Party screen is based on two permissions;
  1. EDI Party Maintenance; Enables you to view and maintain EDI party information.
  2. EDI Party View; Enables you to view EDI party information but not maintain it
To create any EDI Party Maintenance for an Operator, the details section must be completed;
Name and Description enable users to name and describe the party enquiry.
Each Party Enquiry relates to a specific Operator, and so a Translation Operator must be selected.  This ensures any translations set up for an Operator in the EDI Translations screen work in conjunction with the EDI Party Enquiry line.
The EDIFACT Code relates to the Sender Code used in the EDI message.  Maersk use MAEU as their senders code in the below example;
Over the next few weeks, we will look at each message type and how the EDI Party Enquiry screen can be used.
COPARN
The Coparn tab allows the following lines in an EDI message to be loaded correctly into the database based on the specifications of an Operator.
Here is an example of a Coparn Party Enquiry for MSK.
  • BGM1.1- the operator uses 12 to identify the Coparn message as a release request, as shown in the example above.  So the value will be 12 and the function will be ‘Release Request’.
  • FTX4.1 – the operator uses the FTX+AAI line to determine whether the container needs to be identified as Heavy Rated.  If the value is specified as ‘FTX+AAI+++Heavy Rated’, this information will be written in the Cargo Remarks field and also the Heavy Duty attribute will be ticked.
  • DTM1.1 – In the EDI message as shown below, the operator includes the estimated required date and time of the release in the DTM+201 line, so the value will be ‘201’.
  • FTX4.1 – Operators often include a description of the type of container  required for the release request in a FTX (free text) line of the message.  In this case, the operator uses FTX+QQD+++ to provide information about the containers.  In the example below, the FTX segment relates to the availability grade of an empty container used by the terminal.
Once the terminal has decided how they want to manage the additional information, they can then set up an translation in the EDI translations screen to select what availability grade they want to use.
In this example the word ‘CHILLED’ is always translated to availability grade 9.
The values you can map for Coparn using the EDI Party Enquiry screen are
  • BGM or UNH line used to determine how the Coparn message is to be handled i.e. as a release request, booking or prenote.
  • DTM1.1- for release request time and date or the release request estimated time and date
  • FTX1.1 – for mapping to the Booking cargo remarks field
  • FTX4.1 – for heavy rated criteria, empty grade translations, estimated required date and time for release requests or ventilation information and ignoring the line for Bookings.
  • MEA3.2 – for heavy rated containers on release requests, Master Terminal can determine if a container is heavy rated by the second value in the MEA line e.g. MEA+AAE+EGW+KGM:28480 will classify any container with a weight over 28480kg as heavy rated.
  • TMP1.1 – for using the temperature in the EDI message to determine the availability grade used e.g. the value will be 2 in the EDI Party enquiry configuration if the EDI message includes the temperature.
  • RFF1.1 – The RFF applies to the reference number of a release.  The ‘Ignore Rel No after Char’ means you can ignore any information after the release request number after the specified character.  For example, if you enter ‑ and the message segment is RFF+BN:21330361‑0001, 21330361 is processed as the release request number; that is, everything after the ‘‑’ is ignored.

Leave a Reply

Your email address will not be published. Required fields are marked *