Type | Area | Description |
 | Ocean Carrier EDI | Open Container Level Tracking incoming Event interface |
| Ocean Carrier EDI | Set the VGM user signature |
| Dakosy IMP | When receiving an IMP status message with code “930” (“Vorzeitige SumA”), the ATB number(s) contained in the message are shown in the Dakosy Appliance and when opening the relating IMP Verfügung (in the title line of the editor). |
| Ocean | Display Container Number on House Shipment |
| Transport Order | Allow secondary addresses of a partner for positioning in transport order before/after the main positioning |
| Sea Export/ Validation | In sea export shipments (types Single, Single FCL and Master) a new validation warning message is displayed, in case the entered OBL number of the shipment already appears in another shipment/master of the same branch.
(This validation already exists in Ocean Import.) |
| Ocean | Removed space between container prefix and number |
| Dakosy IMP Events | The evaluation of Dakosy IMP status messages (with status codes 710, 910, 911, 912, 913 and 954) has been improved. These status messages (types) are linked to relating generic FCL event types (to simplify order tracking plan setup) and the attributes have been harmonized (to match the generic FCL event attributes). Besides that, they are also used to update data in the relating import shipment (e.g. ETA, ATA or Gate-In, Gate-Out per Container). |
| Documents | Document Upload Type as SearchField |
| Documents | New Function Key F3 to change kind of document |
| UNLOCode Service | Reduce data for UNLOcodes |
| Ocean Carrier EDI | Shipping Instructions - AMS self filer as default (own SCAC) |
| BHT | Default Booking References from Shipment on order 125 |
| Ocean Carrier EDI: LCL Bookings | When transmitting LCL Bookings via our Inttra CC to the Carrier, the email address containing the rootMessageID is transmitted as additional email address of the information contact. |
| Documents | Unification of spelling for bill of lading in documents |
| Ocean | FCL in column header of shipment overview is shown completely |
| Ocean Carrier EDI | Booking amendment configuration |
| LCL Booking | When transmitting an LCL Booking via INTTRA to the Carrier, the information contact (IC) in the Edifact Message (IFTMBF) is now also holding the email address of the clearing center (including the root message id). |
| Ocean Carrier Events | The conversion of inbound events for a set of existing carrier event types, which represent ‘estimated’ event types, into rsixml2 events has been enhanced to now also hold an additional date/time attribute “etd” or “eta” in the generated rsixml2 event. |
| Sea Import | Date validation for ATS |
| Simple Shipment Road | Take over the pre-defined road carrier into the transport order |
| Sea Import | Add Shipper & Consignee Reference to consolidated house entry |
| Ocean | Renaming of requested PUP/DLV Time to Date |
| Sailing Schedule | Add «transit time» to the sailing schedule and ability to sort the list of sailings |
| Sailing Schedule | Forward Total Duration & Transit Duration received from data providers to Scope |
| Sailing Schedule | Increase Number of Weeks added to ETD to cover the full available range received from data providers |
| Email Templates | A new parameter “s.mainTransportSummary” is available in the email templates for the shipment monitor. With this parameter, a summary of the main transport of the relating shipment can be inserted in a fix layout into the email. |
| Ocean Carrier EDI | When transmitting events from the past: only the most recent event per container and event-type will be transmitted |
| Simple Shipments | Multiple simple shipment templates can be selected and deleted in one go |
| Container Transport Order | Additionally to the existing Delivery Party, Chassis Location and Customs Clearance, three new address types have been added: Weight Station (De)Fumigation location Documentation address
|
| Transport Order | Positioning Times Update on address switch |
| Sea Export | Fixed Display of Main Transport (if Booking is present) |
| Dakosy | Improved MRN validation |
| Booking/Simple Shipment | When printing the transport order for a simple shipment ‘Road’, which was created from a ‘Road’ booking, the transmission of an EDI message to the WINK CC is triggered, in case the originally selected road carrier allows EDI messages. |
| Inbound XML Prealert | The Edibooking CC (Live & Dev) has been updated with a fix concerning the converted qualifiers for incoming prealerts. Some qualifier tags contained a space in front (or after) the qualifier - this issue has been fixed. |
| Dakosy Message Processing | The processor to link Dakosy messages has been corrected to prevent potentially endless creation of new linking jobs for the same processor. |
| Road Carrier | Fixed behavior of Properties in Road Carrier Role |
| Ocean Container monitor | Container Monitor: Missing Resource Translation & Filter Field |
| Event Processing | When processing incoming carrier events sometimes an exception was thrown, when user remained in an open shipment and converted this into a House FCL after which the event process was continued (only happened at BKM). This bug is fixed now. |
| Sea Import | When printing documents for a sea import house, which is consolidated onto a master, always the current value of the import warehouse (shed) address of the master is available for printout. |
| Sea Import Superhouse | When transmitting a superhouse prealert from export to import (internally = same server), the documents of the consolidated export houses are visible on the import house created from the superhouse-prealert. |
| Transport Order | Fix the default for the details handling when printing the CMR |
