Legend
- bug fix
- improvement
- new feature
Changes for:
Airfreight
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Air | Tracking Tab - Actionlinks (Register,Edit,Invalidate -Exception) vanish or move depending on screen size | Shipment Tracking Tab: Some of the actionlinks under the table of Milestones and Exceptions vanished depending on the screen size. Scrollbars were not available. This has been fixed. Actionslinks located under the table are now displayed properly, scrollbars are available now. | ||
Ordertracking | Shipment Monitor: More filter options | New filter options for the "Shipment Monitor" | ||
Air,Export | Airline Booking Appliance: Add contract no. and allotment id in overview | In the Airline Booking Appliance, additional columns have been added. Allotment ID and contract No are available now. | ||
Air,Import | AI (SI?) Super House - don't validate duplicate MAWB number | The MAWB number of the corresponding pre alert import MAWB was validated as a duplicate MAWB number when entered in the input field MAWB number in a Super House Import editor. This has been corrected. | ||
Air,Forwarding | Improve conditions for ULD split regarding mandatory fields | Air Export: In case of splitting a shipment to load on different ULD´s the volume entry is is not a mandatory field anymore. | ||
Air,Finance | Quotation / Booking / Shipment: Create Airline Booking when pulling AWB from Pool | Creating a shipment or booking from a quotation pulls an AWB number from stock if the quotation is related to an air carrier. For (direct / b2b) shipments that was fine, but for bookings this could lead to problems as the awb number in a booking is just a reference which can be removed without restocking the AWB number to the pool. Also if the booking is not converted to an AE direct / b2b the AWB number will not get restocked. To solve the issue the following changes have been implemented. 1. Create an airline booking together with booking and shipment if an AWB number gets pulled from pool. 2. Directly save booking and shipment together with the airline booking for AE. | ||
Air,Forwarding | Air Import - Error during shipment store when e.g. TOA is entered with year 20201 | An error occured during shipment store when e.g. TOA is entered with year 20201. This has been corrected. Now with the error validation the attempt to store is just not possible. | ||
Forwarding | [GON][Luftfracht Import] Change shipment type to B2B not allowed for coload in | Coload In Shipment Air Import The option to Convert to an air import Coload In shipment to a type B2B shipments has been added. | ||
Air,Import | Air Import Warehouse Order: Rating Basis Weight | Air Import Warehouse Order now also works for tariff with rating basis weight. Also the values in the entry fields pieces, weight ad volume of the warehosue order can now be edited. | ||
Air,Export | AWB Editor: Make Checking Print Options ("As Agreed" etc.) Easier | AWB Editor: New Button "Edit print details" it is possible to open with accelerator alt+P | ||
Air | Add Export Terminal among the filter criteria for Air Export | Search and filter option for "Export Terminal" in the Air Export Homeview. | ||
Forwarding | add possibility to find an individual package | It is possible to add unique package identifiers to individual packages as Label customer or Label Forwarder. With this ticket it is now also possible to serach for these identifiers in the in the homeview Air Export, Import or simple shipments. | ||
Air,Export | Departure Control: Handle incomplete actual flights deviating from plan | In case of a shipment with 2 legs the departure control is keep open as long as there are no two flight with the First Departure Airport and Last Destination Airport include. | ||
Ordertracking | [GTL][Email Settings] Place holder {exception creator/ manual completion user} | A new placeholder e.registeredByUser for the username of the user registering an exception for the exception email Template has been introduced. If an expeption created by an event scope event, the user is displayed as scope system. If an exception is manually added, the user creating the exception will be shown in the email. | ||
Ordertracking | Events for manual Departure Control | New visible event for manual Departure Control | ||
Air,Export | Wrong Warning for Loaned AWBs | AWB pool warnings did not consider loaned AWBs. If AWBs were loaned to other branches, the pool warning still considered them available for the original branch. This has been fixed. | ||
Air | Cannot Change Shipment Type With Deactivated Delivery Order | It was not possible to change the Shipment Type of a B2B shipment which has a deactivated Delivery Order. This has been fixed. | ||
Air,Import,Ocean,Printing | Air Import Master: Print filecovers (house shipments) should print in order of house shipments in master | Air Import: Printed file covers (house) are in the same order as the house shipments are shown on the shipment. | ||
Air | Air Export: Improve sorting of actual flights | Air Export Shipment: In Case of just one DEP Confirmation for two different flights the flights are still shown in the right chronological order. | ||
Air,Export | Show AWB number at the bottom of screen in departure control | AWB number of selected shipment is now shown at the bottom of the screen in Air Export Departure Control. | ||
Air,Export | Air Export: Enable shipment search by screening reference | Now it is possible to found a shipment by the screening reference | ||
Air,Export | Airline Product Validation for Cancelled, Billed, Closed, and Departed Shipments | Validation for Product (Airline) as a warning in case it was not filled | ||
Air | Compliance check also for Carrier / Airline | Compliance check on a shipment via "Extras" -> "Compliance Check" is including address of the airline / carrier now | ||
Air,Export | Air Export: Enable carrier specific other charge codes | We (programmatically) introduced the option to have airline specific other charge codes. We added only LH specific codes for the moment. Airline specific codes are not usable outside of the airline context (eg.: you can not use an LH code on an AF AWB, or generally link an airline specific code to a Scope charge type). Airline specific codes are shown with the airline in brackets (eg. (020)) after the text in the Scope entry fields. In case an airline specific charge code (general IATA code or real airline specific) is defined in the master data the text on the airwaybill will now always be taken from that code, the manual text from the AWB Other Charge profile is only used when the general code is applied. | ||
Air,Import | Air Import Templates: Chg Weight should be editable | Air Import Templates: Field for Chg Weight is editable now. | ||
Air | Cache some values reloaded in Home Views | Shipment details on the Homeview have been optimised. | ||
Air | Flights Editor: Validate Time Consistency | Flights Editor: Validation for ETA-time and ETD-time in case of two flights on the same day | ||
Ordertracking | Milestone User Notification: Event Code / Description Not Taken Into Account | If a milestone template has an action of type "User Notification" the event code and the value of the field event description will be shown in the notification to the user that is created with the completion of the milestone. | ||
Air,Master Data | Air Export - airline and airline role for non-IATA airlines too restrictive | Airline Role: The field for the entry of prefix for Non IATA Airlines is more flexibel | ||
Ordertracking | Not show cancelled shipments in Departure Control | Shipments which were cancelled are not shown in the departure control anymore | ||
Forwarding,Master Data | [GTL][Equipment] Package Type Maintenance: Show UN Rec 21 Code in overview | The Type of UNrec 21 Code is now also visible in the Equipment Type Overview. | ||
Air,Ordertracking | Tracking-Tab | improve display of timestamps | The display of timestamps in the shipments tracking tab has been improved. In tracking tab, events are now shown in timezone of location, timezone is shown in new column In tracking tab, action log is now shown in local time. In tracking tab, time of manual completion now also shows timezone | ||
Ordertracking | Order Tracking: Register generic exception on tracking plan | OrderTracking: Exception enhancements - UI changes: -Manual registration of an exception is now done in a wizard - Finishing the wizard on page one will only register the exception, finish on page 2 will register and immideatly solve. - There is more space to show remarks in the Tracking Plan view - New fields are added to the quality report / exception tab. - New fields are available in the Map Producer | ||
Ordertracking | OrderTracking: Shipment entry enhancements | In case of an existing unhandled exception a growl message notification is presented to the user when opening the shipment in the editor (any editor supporting the order tracking tab). | ||
Ordertracking | OrderTracking: Exception Templates connect with Generic Templates | When changing/adding the generic exception template in order tracking templates, anything possible is copied from the generic template to the order tracking exception template. | ||
Air | Add fowarding customer options to agent role | For prealerts the settings of the orderer in an airfreight shipment are now taken from the Agent instead of the ForwardingCustomer profile in case the import agent is the orderer. | ||
Air | Notes | creator/creation time should not change by converting booking into shipment | When converting a booking with a note into a shipment, the creator and creation time of the note were changed to the time/person that converted the shipment. This has been changed. The note keeps the former creator/creation time of the booking now. |
Customs CH
Ticket | Area | Summary | Description | |
---|---|---|---|---|
CH Customs | Edec Import: Zollabgaben Button ist immer ausgegraut | Der Button zu Berechnung der Zollabgaben in e-dec Import wird jetzt korrekt aktiviert. | ||
CH Customs | e-dec Import: Dossiernummer als uniqueReference im SCI-Assessment verwenden | Im SCI-customsAssessment zu einer EVV wird jetzt die Dossiernummer als <uniqueReference> übermittelt, anstelle der Deklarationsnummer Spediteur. | ||
CH Customs | E-dec Taraverteiltung bei CSV-Positionsimport | Beim Import von Anmeldepositionen aus CSV in eine eDec-Importanmeldung errechnet Scope jetzt das Brutto- oder Nettogewicht in den Positionen, wenn im Anmeldekopf Gesamt-Brutto- und -nettogewicht angegeben wurde und in den Warenpositionen nur Brutto- oder Nettogewicht mitgegeben wird. |
Customs DE
Ticket | Area | Summary | Description | |
---|---|---|---|---|
ATLAS | Einfuhr: Bei der Verdichtung soll die Art und Anzahl der Packstücke in der ersten Position stehen | Wird ein Positionsimport inkl. Position verdichten in Scope durchgeführt und stehen die Packstücke in einer anderen Position als in der ersten Position, so wird diese Position an die erste Stelle gesetzt, in der die Packstücke erfasst werden. | ||
ATLAS | Scope übernimmt nicht die Daten die der Nutzer als Fracht erfasst | Wird ein Incoterm verwendet, der eigentlich einen Frachtabzug für den Zollwert vorsieht, und wird die Kostenaufteilung genutzt, so hat Scope auch bei der Verwendung der Codierung 010 immer die 014 für den Abzug gesetzt. Dies wurde behoben, so das Scope nun den Wert 010 oder 014 übernimmt, der vom Benutzer erfasst wird. | ||
ATLAS | ATLAS AES: Ansprechpartner des Empfängers wird falsch validiert | Der Sachbearbeiter beim Empfänger wird nicht mehr Validiert, sofern ein Vertreter erfasst ist. | ||
ATLAS | ATLAS Statistik AES: Fremdsystemnummer in der Suche verfügbar machen | In der AES Kopfdatenstatistik ist nun die Suche nach der Fremdsystemnummer möglich. | ||
ATLAS | Nachjustierung der Vorbelegtung von Präferenzunterlagen | Die Vorbelegung der Präferenzunterlagen wurde weiter verbessert: - Scope erzeugt keine Unterlagen, wenn die Art der Begünstigung nicht gefüllt ist. - Abhängig von der Art der Begünstigung, müssen die folgenden Felder gefüllt sein, damit Scope Unterlagen anlegt: 400 = Versendungsland 300/320 = Usprungsland und Versendungsland - Dieses Verhalten gilt bei Vorlagen, SCI Importierten Vorgängen, außer die Unterlage wird bewusst in der Vorlage vordefiniert oder im SCI mit übergeben. | ||
ATLAS | ZL Bestand wird nicht freigegeben wenn ABD storniert wurde | Ein Fehler, der die ordnungsgemäße Freigabe des Bestandes im Zolllager bei einer Stornierung einer Ausfuhr verhindert hat, wurde behoben. | ||
ATLAS | Einarbeiten einer SCI Message nach NCTS mit Template / ATNEU Vorlage | Wenn eine Versandanmeldung über Schnittstelle nach Scope gesendet wurde und beim Erstellen der Anmeldung in Scope eine Vorlage mit Beendigungsanteil "ATNEU" ausgewählt wurde, wurde in Scope nicht die Art der Identifikation angezeigt. Erst nach Löschen und Neueingabe des Vorpapiertyps kam die Art der Identifikation. Der Fehler ist behoben. | ||
ATLAS | Kopie eines verknüpften AES Vorgangs landet nicht aut. in der Senudng | Wird ein AES Vorgang kopiert, welcher einen Sendungsbezug hat, so wird die Kopie automatisch mit der Sendung verknüpft. Möchte man den neuen AES Vorgang nicht mit der alten Sendung verknüpfen, da es sich um ein neues Shipment handelt, so muss der Vorgang aus einer Vorlage generiert werden oder als neuer Vorgang aus der Sendung generiert werden. | ||
ATLAS | Neue Felder in der NCTS-Warnliste | Die NCTS-Warnliste wurde um Versender, Empfänger, Rohmasse und Packstücke erweitert. | ||
ATLAS | SCI: VAT-Nr. Absender und Empfänger mitgeben | Die VAT-ID wird ab sofort bei ausgehenden SCI Aufträgen inkludiert, sofern diese in dem jeweiligen Geschäftspartner erfasst wurde. | ||
ATLAS | EGZ Bewilligung auch im Anmelder mitgeben | Für vereinfachte Einfuhranmeldungen liest Scope jetzt eine eigene Bewilligung für den Anmelder, wenn sie über die Schnittstelle mitgegeben wird. Wenn über die Schnittstelle keine Bewilligung kommt, wird sie weiterhin aus den Stammdaten gelesen. Haben Anmelder und Vertreter jeweils eine S1-Bewilligung in den Stammdaten hinterlegt haben, so setzt Scope die Bewilligungsnummer aus dem Anmelder ein. |
Customs NL
Ticket | Area | Summary | Description | |
---|---|---|---|---|
NL Customs | [NL-NCTS] Use Consignee from Template. | It is now possible to add a Consignee Partner to the NL NCTS template, when this is populated it will overwrite the consignee from the shipment. | ||
NL Customs | [CLIENT VWA] Validation rule CCL_AIN12 - Purpose incorrect interperted. | The validation on Purpose was incorrect when the destination was set to DVR and/or WIR, this has been changed from "Must be empty" to "Mandatory". | ||
NL Customs | Article master data is used in AGS procedure and shows up when searched via de search option in AGS | Changed the search fields so a search in AGS does not include master data from the article masterdata anymore. | ||
NL Customs | NL Customs TakeIn: In case Takein from masterShipment, check if Breakbulk warehouse can be used as Takein.ownwarehouse | When creating an PDE/RTO take in from an Import Master, the default warehouse will be taken from the Breakbulk warehouse, if this is a valid partner for PDE/RTO. | ||
NL Customs | PDE/RTO Takein: NCTS check should be improved | An incorrect validation blocked the confirmation of a take in, when the linked NCTS declaration was already at status goods released This has been corrected | ||
NL Customs | Validation on item of previous customs document in AGS improved | A validation has been added to ensure that the line number of a previous document meets the requirements of NL Customs 1-999 for AGS Exports 1-9999 for AGS Imports | ||
NL Customs | V2 number of CPD204 message should be taken to AGS as additional information with code 91004 | In VWA declarations we already received a V2 - EU Release number, until recently this number was not yet required/possible in AGS, VWA released a statement informing that this number needs to be in AGS with additional information code "91004". Scope has been adjusted to automatically use the number from the selected VWA declaration in the AGS declaration. | ||
customs | [Simple Shipments] Error when trying to link an existing Customs Order to a shipment | Linking Customs orders (AGS , NCTS etc) can now be transferred from 1 simple shipment to another shipment. |
Finance
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Finance | Quotation Jobcosting Entry Dialog - Allow selection of all exchange rate types for incomes | It is now possible to select the different types of exchange rates in the quotation for income | ||
Finance | Shipment Activity Calculators - Shipment supplier for order type security measure overwrites cost partner in activity type | Under certain conditions in quotations , the supplier to be defaulted was incorrect, this has been corrected | ||
Finance | Financial Status - Take TI/TP transfer jobcosting entries for status calculation into account | TI/TP on sub-houses are now considered for automatic change of financial status | ||
Finance | Reports Refactoring - Reduce memory consumption of Economic Month Report | Improved performance of Eco-Month-Report | ||
Finance | Tariff Refactoring - Maintain rates for different container types of the same trade lane in one tariff entry | The way Containertypes can be used as a basis in the tariffing has been improved. It is now possible to combine multiple container types within one tariff | ||
Finance | Consol-Profit-Tab - Add tab to export masters and super-house shipments | A new Tab has been added to Export Masters and Export Super-Houses to show the profit/loss of the whole consol | ||
Finance | Create income estimates from accounts payable at time of finalization | It is now possible to create income estimates from accounts payable at time of finalization | ||
Finance | Tariffs - Add customs order type as an additional tariff search criteria | It is now possible to use the basis "Base amount" and "Manual entry" for defined type of customs order | ||
Finance | Shipment Overview - Add customs declaration number of customs orders | The customs declaration number is now available on shipment overview and customer invoice reports (as reference type ABT) | ||
Finance | Accounts Payables - Show involved users and add search option for on-hold workflow | Account Payables: It is now possible to see more informations like involved users and on hold and release date for on-hold workflow |
Forwarding
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Ordertracking | Shipment Monitor: Filter on Customer Group | New added option to search by partner groups (shipper / consignee / orderer) in appliances | ||
Ordertracking | Shipment Monitor Export - Dynamic Column Headers | To improve the legibility of the Shipment Monitor, the Milestone code is added to the corresponding columns planned and actual time. | ||
Ordertracking,Partner | Extra roles within partner contacts | More partner contact roles are added. These roles can also be used on the tracking templates to send automated messages to. | ||
Ordertracking | Order Tracking template: Milestone Location: Add option Branch Partner Location | In the Tracking Template, its now possible to define the location (used to determine the time zone to display the date/time in) on the milestone to be taken from the location of the branch (partner) location. | ||
Forwarding | No switching of oderer when INCO term is changed once orderer was set manually | If a user changed the orderer manually Scope dont overwrite it anymore in case if the Incoterm or Exportagent will be changed. | ||
Ordertracking | Description for Tracking Plans | You can now add a description to Tracking templates. | ||
Ordertracking | [FFF][Shipment Monitor] Failed actions Shows incorrect shipments | manually retriggering an fixed action left the tracking plan incorrectly reported on the "Failed action" filter. This has been corrected | ||
Ordertracking | [GTL][Shipment Monitor] Add option to hide bookings | A new filter Criteria has been added to the shipment monitor where it is possible to include (default) / exclude Bookings from the overview. | ||
Ordertracking | Add event to a shipment when a tracking plan is initialized and/or deleted | New Event Types for the Order Tracking Plan | ||
Ordertracking | Shipment Monitor: Add column for Order Customer | The Shipment Monitor appliance can now also show the Customer of the related shipment. Use the right-mouse click menu to show the column: Customer | ||
Ordertracking | Quality Report and Deactivated Milestones | In the Shipment Monitor / Quality Report excelsheet, for milestones that are not active for a shipment, the milestone code will be suppressed. | ||
Air | ExportShipmentMapProducer has no TimeZone for TimePoints | it's fine now. the correct time stamp is on the CSD. Pls see printscreen. | ||
Ordertracking | OrderTracking: Master Data Generic Exception Templates | A new MasterData Appliance for Exception Templates has been introduced. Properties of the generic exception templates are a subset of the existing order tracking exception templates. |
General
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Core | If a user is not active a warning should appear when adding or maintaining the signature of this user | A warning appears when adding or maintaining the e-mail signature text of a locked user. |
Handling
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Warehouse | Warehouse Load: Improve Package Takeout | repair Package take-out, add function Package take-out to the Shipment take-out | ||
Warehouse | [SCO][LKW Be-/Entladungen] Screen abgeschnitten | The Information regarding security and warehouse for a truck unloading export entry are now shown in two additional tabs after entering the data. | ||
Warehouse | TourTemplates : remove unused field autoCreateTours | Auto create tours and edi mappings removed from Route Templates | ||
Warehouse | LKW Be-/Entladungen Druck von Cargomanifest (RFS Flight Import) soll auch Uloadtrk-Nr enthalten | on the RFS flight manifest the Truck unloading no. can be printed now |
Internal
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Forwarding | RSIXML2 Simple Shipment: Create closingForDelivery DTM | Tesla Interface API validations added: Active validations have been added to the Tesla Interface ; - Delivery window must have at least an end date/time (date only not sufficient) and be no more then 5 days in the past - Place of delivery must be set with code - Place of receipt must be set with code - Tesla shipment number must in set in Shippers Reference. - Multiple Shipment numbers is allowed, |
Seafreight
Ticket | Area | Summary | Description | |
---|---|---|---|---|
Import,Ocean | Fix FileCover Print for Ocean Import Super House | Fix FileCover Print for Ocean Import Super House | ||
Air,Ocean,PreAlert | Prealert creation fails, if nature of goods exceed 1023 characters | Prealerts containing "nature of goods" ftx entries exceeding 1023 characters can now be processed in Scope. No Error Jobs created anymore. | ||
Import | S - EDI Transport Order Docs not available in Import | Transport Order Editor Model shows now also the documents, which have been received by Prealerts from the export side. These documents were already visible in the documents tab of the import shipment, but not in the attachment tab of the transport order | ||
Forwarding,Ocean | Measurements on HBL are inserted in wrong order LxBxH | When inserting existing dimensions as text into the B/L, the layout of the text has been changed. It has been harmonized with other areas, where the option to insert dimensions existed. The "new" layout is now the same as in other areas and conform to the key in in the dimension editor, where the values are shown as "L x W x H" | ||
Forwarding,SimpleShipment,TransportOrder | Transport Orders for Simple Shipment: Use Pickup / Delivery Address Remarks | In case a simple shipment holds a shipper for which in the master data (Partner appliance -> Delivery / Pickup address) remarks are defined, these remarks are defaulted to new transport orders created for the simple shipment (eg. pickup / delivery transport orders). | ||
POMS | Forwarding order homeview: add sales-product as a new column + filter function | The forwarding order homeview now can show the property "Product" as new column in the table (showing available forwarding orders). It is also possible to use the "Product" as search criteria in the filter options. | ||
Forwarding,SimpleShipment | S - Simple Shipment: New from Selected (Copy) | The simple shipment appliance allows to create new shipments by the new function: "Copy selected Shipment(s)". In case one (or more) shipments are selected in the appliance overview and the new function is used, for the selected shipments copies are created as new shipments and for each the simple shipment editor is opened. | ||
Forwarding,POMS | Simple Shipments always update the "export" side of a forwarding order leg | When updating the routing leg of a forwarding order from a linkes simple shipment, the update process tries to evaluate (by own partner / shipper / consignee / departure / destination of the shipment) whether the shipment is export or import related. According to that evaluation the legs properties export or import properties (shipment number / branch) are updated. In the past always the export fields were updated, even if the shipment was an import one. | ||
Forwarding,SimpleShipment | S - SimpleShipment / Create new shipment number | The Simple Shipment editor has the new functionality "Update Shipment Number" in the extras menu, which behaves in the same way as in the air- and sea shipment editors. | ||
Export,Ocean,Sea EDI | S - Validate Carrier Booking Ref on VERMAS send | Booking Number is validated before transmitting a Vermas Message in the same way as in the CC: Length must be between 6 and 20 characters; it may not contain invalid characters (only a-z,A-Z,0-9,_,- are allowed) and it must contain at least one digit (0-9) | ||
Forwarding | M - FedEx WebServices Update to Version 26 | OCT-2021 | Scope has been updated to use version V26 as Fedex Ship interface version for the Fedex communication. It had been updated from version V23. | ||
SimpleShipment | Simple shipment | show nature of goods in overview | Simple Shipment Home View now also shows the nature of goods in the preview below the table. | ||
Forwarding,Ocean | [FFF][Sea Import] Too long Ocean B/L number for Portbase Consignment Adoption | When the user tries to create a Portbase Consignment Adoption Request for a shipment or master, a dialog shows an error in case the ocean b/l number is longer than the interface allows. | ||
Forwarding,Ocean | FCL Logistic Validator: Add validation on too heavy goods | A new validation has been added to the FCL Logistics validator (which is available for transport orders to be sent to FCL Logistics): In case one (or more) goods entries of the transport order are defined with a weight equal or higher than 100.000 kg a validation error is shown, since the interface to be used for FCL Logistics only allows weights upto 99.999 kg. | ||
Forwarding,Ocean | Dakosy response messages with wrong filename | To prevent errors due to a wrong / invalid filenames, when processing incoming Dakosy messages, the evaluation of the filename has been changed. In case no calendar date / counter can be derived from the filename, the current date is used and as counter the value "1" (instead of throwing an exception). | ||
Import,Ocean | M - Populate Container Movement fields with Events Data (OceanImport) | Dates for Terminal Entry, Terminal Exit and Container Depot Entry per Container of an import shipment / master is updated by specific incoming events from Inttra/GTNexus/Cargosmart/OceanInsights in case the relating address (terminal / depot) is defined in the shipment/master, the containernumber matches and the date/time was not set so far for this container. Relevant events are "UV", "OA", "RD" (for Inttra and GTNexus), "UV", "B0" (for Cargosmart) and "CDD", "CGO", "CER" (for OceanInsights) | ||
Forwarding,Ocean | M - Make Entering IMO Contacts Easier | The emergency contact in the dangerous goods editor view (part of the goods editor) has now two additional context actions: * Shippers Contact Info (short cut: ctrl shift I) * Next Shipper Contact (short cut: ctrl ADD) The actions are enabled in case the shipper of the relating shipment / template has a partner with one or more contacts (in master data). With "Shippers Contact Info) the existing contacts are displayed and can be selected by double click or by the "apply" button (if one is selected). With "Next Shipper Contact" the next contact in the list is selected (depending on the current value of the emergency contact in the dangerous goods entry). When adding new dangerous goods declarations, the new declaration gets per default the emergency contact of the first dangerous goods declaration defined for the shipment / template. The functionality is available for * sea export / import shipments * edi shipments (export / import) * templates for edi shipments / seafreight shipments (export / import) For bookings and master shipments, only the defaulting for a new dangerous goods entry is available. | ||
Ocean | [CMD][Sea Import] GoodsHandlingUnitNode.initNodes NPE | When adding a foreign house shipment (not belonging to the current branch) to a seafreight import master, a Null-Pointer-Exception has been fixed. The exception occurred, since the goods of the house could not be found in the current branch. | ||
Import,Ocean | Speed up Sea Import Superhouse (even more) | The import superhouse (de-)consolidation process has been improved, so that adding / removing of shipments to / from the superhouse has been speed up. | ||
Export,Ocean | S - Shipping Instructions - "no of originals": default should be "E"xpress BL instead of 3-THREE | The default value for "number of original b/ls" for new B/L Instructions (aka Shipping Instructions) is now changed to "E" (Express B/L) for shipments and masters | ||
POMS | M - Forwarding Order: Show Shipment Number(s) | Shipment number (and other details from shipment) visible in leg view of forwarding order ... provided you wait 10 minutes (update done via job - as in the past). | ||
Forwarding | PO Excel Report should show container numbers/type for Orders without PO Link | The PO Excel Report now also shows container numbers and types of selected forwarding orders, in case these forwarding orders do not have a linked purchase order schedule. | ||
TransportOrder | S - Shipper and Consignee in Transport Order | In case RSIXML2 TransportOrders are transmitted from Scope for Simple Shipments, the created XML File now also contains a <shipment> data section of the simple shipment. Besides this change, RSIXML2 TransportOrder xml files now can be converted into Transport Order XML files of version 1.9, where a new shipment data section <shipmentDataRoad> is filled in case of transport orders for simple shipments with conveyance type road. | ||
TransportOrder | M - TransportOrder message generation to support binary documents | Enhanced the TO rsixml2 generation to add selected documents as binary attachments into rsiml2. | ||
TransportOrder | L - Transport Order Dialogue enhanced EDI view | The transport order dialog has been enhanced by a new tab "Edi attachments". In case the selected carrier may receive transport order data by interface and can process (pdf-) documents in the message, the new tab allows to add documents (linked to the relating shipment) for transmission together with the transport order. It also allows to upload and attach new documents to be transmitted together with the transport order. In case new documents are uploaded, they automatically become visible in the documents tab of the relating shipment. To enable (pdf-) documents to be transmitted with the transport order, the road carrier profile of the partner (used as carrier for the transport order) has to be maintained accordingly (means: the checkbox in the profile to allow pdf-document transmission needs to be checked). In the road carrier profile it is also possible now to maintain, whether the carrier may receive updates on a given transport order or not. If he cannot handle updates, only the first (initial) print of the transport order will trigger a transfer of the transport order data by interface. In this case, when reopening the transport order, the tab "Edi attachments" will show, that no documents can be selected. | ||
Export,Forwarding,Import | M - Improve Default Value for Port of Loading in Agent Profile | Agent Editor Model/View now allows to define distinct ports for air and sea to be used as default ports when creating new export / import shipments for a given branch. The view shows - in case agent represents a branch - by an icon (aircraft / vessel), which port in the list of ports represents the default. The default can - be set manually - be calculated automatically (by order of the ports) or - be deactivated |
Workflow Changes
Ticket | Area | Summary | Description | |
---|---|---|---|---|
ATLAS | Kopie eines verknüpften AES Vorgangs landet nicht aut. in der Senudng | Wird ein AES Vorgang kopiert, welcher einen Sendungsbezug hat, so wird die Kopie automatisch mit der Sendung verknüpft. Möchte man den neuen AES Vorgang nicht mit der alten Sendung verknüpfen, da es sich um ein neues Shipment handelt, so muss der Vorgang aus einer Vorlage generiert werden oder als neuer Vorgang aus der Sendung generiert werden. | ||
Ordertracking | OrderTracking: Shipment entry enhancements | In case of an existing unhandled exception a growl message notification is presented to the user when opening the shipment in the editor (any editor supporting the order tracking tab). | ||
Ordertracking | OrderTracking: Master Data Generic Exception Templates | A new MasterData Appliance for Exception Templates has been introduced. Properties of the generic exception templates are a subset of the existing order tracking exception templates. |