Monday, 18 February 2019

Preventing Operator Stops in COREOR Messages Being Reapplied

Some stops have an expiry date after which the stop is reapplied to a cargo item. The information is contained in the DTM+400 or DTM+36 message segments in COREOR messages.

Some shipping lines use these message segments to mean something different than an expiry date for the operator stop clearance. You can configure the system to ignore the DTM+400 or DTM+36 message segments in COREOR messages from specified senders so that if the container is not picked up before the specified date, the operator stop remains cleared instead of being reapplied.

On the Coreor sheet of the EDI Party Maintenance screen for a specified sender, check the Ignore Expiry Dates check box. This effectively disables the expiry date functionality for operator stops for this sender.

This enhancement is available in release

Friday, 25 January 2019

Searching for Cargo in the Road Gate Picker screen

You can configure the Road Gate Picker screen to display a filter, which makes it easier to find a cargo item if the list is large.

To display the filter in the Picker screen when processing cargo on the Road Gate screen, check the Show Filter in Picker check box on the Gate sheet of the Terminal Config screen.

 If you check this check box, the filter is displayed on the Picker screen, shown in the following diagram.

The filter lets you to search for some or all of the specified text associated with the cargo item in the table; for example, if you enter 45 in the Filter by text box and then click Filter, any item that contains 45 is displayed in the filtered list.

Similarly, if you enter MES in the Filter by text box and then click Filter, the items that have MES anywhere in the table are then listed.

Click the Reset button to remove the filter and redisplay the original list.

This enhancement is available in Master Terminal

Friday, 4 January 2019

Cargo Reporting With Proforma Charges like Demurrage

Proforma Invoices

It is possible in Master Terminal to produce a cargo report that includes proforma charge amounts for any configured invoice line. This means that charges like storage can be included in a cargo report.

If you have an invoice license with invoicing configured, you can configured proforma invoices, you do not need a cash license to do this.

See a previous blog post Blog Post - Proforma Invoices

Proforma invoicing is cargo only at the time of this blog post.

Proforma invoicing does not create any permanent records in the database, it is purely read only; but does use the full cargo invoicing configuration.

In Report Maintenance a Proforma Invoice Report can be configured.

The parameters can be configured to include voyage, BOL and cargo Id(s).

This means that it is possible to put a proforma invoice report in the JMT WebPortal that lets the user enter a cargo id and see how much the cargo is going to cost.

Because the report view includes full cargo details it is possible to create a cargo report that lists normal cargo details plus the proforma cost of any configured charge, the report can be configured to filter by certain charges like storage.

Automated Proforma Reporting

The Cargo Id parameter allows a comma separated list of Ids to be entered this makes the report multi cargo.

A new enhancement allows a cargo selector query to be chosen for the report that will put the IDs of the select query results into the cargo ids parameter. This allows proforma costs to be included on automated reporting.

Friday, 21 December 2018

Season’s Greetings from the Master Terminal team

Here in New Zealand, we are celebrating our main holiday season.  Rest assured we will still be on deck to answer your calls and questions throughout our holiday period. 

For those celebrating with us, we hope you have wonderful time with family and friends and come back refreshed and ready for a new and exciting year! 

No matter where you are in the world, we look forward to being of service to you and wish you a prosperous 2019.


The Master Terminal Dev team

Thursday, 20 December 2018

Modify Action Added to the Voyage User-Defined EDI File

The modify (M) action is now available to the Voyage user‑defined EDI file.

The modify action enables you to update specified voyage data without overwriting existing voyage data.

When the Action in the file is:
  • M, only the fields specified in the Voyage user-defined EDI file will be updated in the database, all the other fields remain unchanged.
  • U, all data for that voyage will be deleted and replaced with the data in the Voyage user-defined EDI file.

The following example shows the use of the modify action to update the arrival and departure dates and times of a voyage.

Load a Voyage user‑defined EDI file to modify the arrival and departure dates and times of the voyage.

After you verify and load the file to the database, the arrival and departure dates and times of the voyage are updated.

This enhancement is available in Master Terminal