Notas de la versión 25.6 de Scope
Con tu ayuda, estamos mejorando Scope cada día. Estas son las últimas mejoras y funciones añadidas.
Changelog
= New feature
= Enhancement
= Bug fix
Type |
Area |
Description |
|
Tracking Templates |
OrderTracking Emails supporting actual flights. When generating emails from OrderTracking actions, various fields for flight details had been available, but all reflecting the planned flights Actuals only: effective (actuals if available, plan otherwise): effective completed (as effective, but missing actual legs filled up from plan): |
|
Tracking Templates |
Grouped (leg) milestones updates no longer blocked after completion of one milestone within the group. This has been intended behavior from the times Scope did only offer ETD/ETA fields without supporting additional fields for STD/STA timestamps. Assumption was that milestones within the groups should not updated with delayed new ETD e.g. after actual (delayed) departure because the arrival milestone should still be measured against the original ETA, which represented the original STA. Nowadays,with STD/STA timestamps available for air and ocean, it is up to the forwarder to configure leg milestones based upon either scheduled or estimated timestamps. With this choice, it is no longer necessary to block updates after completion of one milestone in the group: A leg milestone setup based upon estimate anchor timestamps will update more related to operational legs while a leg milestone setup based upon scheduled anchor timestamps is more suitable to measure against the original planing. |
|
Tracking Templates |
Validate duplicate codes in tracking templates. Duplicate codes for milestones could lead to unexpected behaviour with some actions/functions. When editing a tracking template containing duplicate milestone codes, adjusting the codes is required prior saving. |
|
Forwarding / Documents | Added filters to the documents tab, allowing definition of filters by excluding document types. |
|
Forwarding / Documents |
Always enable document type entry on drag and drop on the document tab. Assigning the document type helps to reduce a lot of clicks where the type is required (e.g. due to outgoing interfaces) or useful. Entering a document type is not mandatory in the appearing dialog and can be skipped by canceling (ESC) or confirming (ENTER). |
Forwarding |
Enable country-based Order Tracking location applicability filter to work with postal addresses |
|
Forwarding |
Harmonize ‘Booking convertion to Simple Shipment’ for single and multiple selection: A missing cost center no longer blocks convertion of a single booking. |
|
|
Simple Shipment |
An “Auto-Fix” functionality has been implemented for the simple shipment appliance, which removes null-value handling units from the shipment before it is opened. |
Type |
Area |
Description |
|
Booking |
Add option ’Assign to shipment’ also for import bookings (air, ocean, simple). Added option Extras > Air Import > Assign to Shipment… for bookings (additional to the existing Extras > Air Export > Assign to Shipment…) |
|
Air Export | Harmonize and smoothing the default for country of origin field in AWB from various use-cases, e.g. the with country of origin entered for multiple packages etc. |
|
Air Export Booking |
Minor improvements for
|
Air Export Booking |
Synchronize and enhanced columns for Airline Booking tables via
|
|
Departure Control | Remove volume (validation) for flights in Departure Control. Since volume information is not included in airline events, the volume field on flights got removed for Departure Control. | |
Departure Control | Handle splitting of shipment on multiple flights by airlines properly in Departure Control | |
Interface / EDI | Scope Shipment Status Interface to support container numbers for ocean LCL import house shipments | |
Air Freight Booking Portal | New column ‘allotment code’ in Airfreight Booking Portal search results (data depends on airline providing flight results with an agreed allotment code) | |
Air Freight Booking Portal | For Airfreight Booking Portal bookings without an AWB number which are not instantly confirmed by the airline, Scope now extracts the AWB number from a later airline confirmation. | |
Air Import | Flight lookup was missing departure value when an air import shipment got created from a booking | |
Airline Messaging | For the case when a shipment was created as a Direct and then changed to a Back2Back (or vice versa), the AWB consolidation/direct flag for airline messaging (eAWB/FWB) did not reset properly when resetting the AWB. | |
Master Data | Fix a save problem on partners with a missing default airport location, only occurring on agents which are no branch offices. | |
Tasks | Task Manager – Freshly assigned own tasks are not showing up in task overview under some scenarios | |
Forwarding: Transport Order Air Import | Transport Order type DELIVER_FROM_TERMINAL which is deployed for Air Import only is supported for generating generic TransportOrderMessage XML. |
Type |
Area |
Description |
|
RSIXML2 | Added container number to universal shipment (for consolidated seafreight house LCL shipments) in case an outgoing RSIXML2 shall be created. |
|
Seafreight Appliance | Added name of the seafreight carrier as column and in the preview of the sea export and sea import appliance. |
|
Ocean Event Message | Enhanced the existing Ocean Event Interface FCL to also allow LCL events. |
|
Container Validation | Removed the specific container number validation for container numbers with prefix HANU. |
|
Manifest Actions | Improved sea export / import editor models to only contact server repository once for activation of the manifest filing option. |
|
Manifest Filing | Made customer code transmitted to the counter system to be unique. |
|
Dakosy |
Support Terms (Prepaid/Collect) to be included in the BL to Dakosy. |
|
Ocean Events |
New generic Ocean Events |
|
Carbon Care | For seafreight house LCL shipments, which has goods in an active reefer container of the relating master, the “temperature” flag is set when checking the carbon care calculation. |
|
Combined HBL PDFs | When generating combined HBL PDFs (without any physical print) a new event is generated (COMBINED_HBL_PDF_CREATED), which can also be used in Order Tracking. |
|
Portbase Secure Chain | When creating nominations for containers of a shipment, only those nominations are transmitted to portbase, where either a new trucker EAN has been assigned or a previously assigned EAN has been removed. This allows a smoother setup of portbase communication by direct API calls. |
|
Forwarding: TransportOrder |
Cargo dimensions and volume in imperial measurement have been added as print values into transport orders in addition to existing weight. |
|
CRM quotation | We have added the sailing schedule to the quotation application to be able to pull sailing data to an offer. |
|
Ocean Carrier EDI | A note is created on shipment level if a contract number has been updated by an EDI carrier booking confirmation |
|
Fiata FCR on Simple Shipments | Fixed an NPE occuring when printing Fiata FCRs, where no issuing agent is defined. |
|
Ocean Carrier EDI Notifications | Improved sea export editor models to react only on sea carrier EDI notifications, which relate to the currently opened shipment / master. By that the number of server calls has been reduced. |
|
Ocean Carrier EDI | Fixed a bug on empty SCAC when sending SeaCarrier EDI messages to CC. |
|
Portbase | Fixed a bug when sending a Portbase track request Issue. |
|
Dakosy | Fixed a bug when receiving Dakosy Message. |
|
Ocean Events | Fix timezone handling for incoming estimates. |
|
Simple Shipment Events | Inbound RSIXML2 FCL Events can now also be processed for matching Simple Shipments, where the Event is linked to the shipment and does not produce a failed Job anymore. Fix is also available for Scope 25.4 now. |
|
Dakosy / IMP Status | Customs Status CDX in inbound IMP Status messages can be handled now. Change is backported to 25.4. |
|
Vesselschedule | Fixed Bug, where a lot of requests timed out. |
|
Vesselschedule | Fix problems with change from OI to INTTRA. |
|
Sea Export / Customs Shipment | When creating a customs shipment (e.g. for ISF 10+2 or other customs entries) for a house consolidated onto a master, where goods of the house were assigned to a master container, the customs shipment now shows the container into which the goods are stuffed (again). This fixes some printing issues (ISF 10+2). Fix was also backported to 25.4 |
|
Sea Export Master Editor | Sea Carrier EDI notifications for sea export masters are now evaluated properly again in the master editor model and update relating action links in the view. This fix has also been backported to 25.4. |
|
Sea Import Superhouse FCL | When creating new house shipments within the superhouse FCL editor, the houses — when storing the superhouse FCL — are linked to the main transport of the superhouse FCL. This fix has been backported to 25.4 |
|
Sea Export Consolmaster | When printing loading lists handling units of consolidated house shipments from other branches will be taken as well. This fix has been backported to 25.4 |
|
Ocean Carrier EDI | Fixed a bug in ShippingInstructions to the Carrier where an unexpected error was shown to the user in rare cases. |
|
Ocean Insight Events | Changed the description displayed for ocean insight events (used as replacement for incoming generic FCL events from gatehouse) to not show “first” or “final” port as text (to prevent confusions). |
|
Portbase Secure Chain | Added handling for so far uncaught exceptions, when transmitting messages to Portbase for the secure chain. |
Type |
Area |
Description |
|
Scope Documents Interface | Die Verwahrmitteilung der summarischen Anmeldung (SumA) steht nun in der Dokumentenschnittstelle zur Verfügung. |
|
Scope Customs Events | Die Scope Customs Event Schnittstelle wurde um eine zusätzliche SumA Nachricht erweitert. Bei Erhalt einer CUSCAN Nachricht wird nun ein CPR-Event bei Stornierung einer Position und ein CCL-Event bei Stornierung des gesamten SumA Vorgangs durch den Zoll erstellt. |
|
ATLAS Statistik | Die NCTS Positionsdatenliste der ATLAS Statistik wurde um die Daten der Einzelsendung erweitert. |
|
ATLAS EGZ | Für das Drucken Steuerbescheides im Verfahrensbereich ATLAS EGZ wurde die MRN der VZA/AZ zusätzlich zur Verfügung gestellt |
|
ATLAS Statistik | In der ATLAS SumA Statistik können jetzt auch die folgenden Daten des vorangegangenen Versandvorgangs ausgewertet werden: LRN, MRN & Bezugsnummer. |
|
ATLAS SumA | In ATLAS SumA wurde die Funktion des Actionlinks zum Öffnen der vorangegangenen NCTS-Vorgänge wiederhergestellt. |
|
ATLAS AES | Nach der Erstellung eines ATLAS AES Betriebkontiuitätsverfahren (Notfallverfahren) konnte der Vorgang gelöscht werden, obwohl das Formular bereits gedruckt war. Das Löschen eines Vorgangs im Status Notfallverfahren ist nun nicht mehr möglich. |
|
ATLAS AES | Bei eingehenden Statusnachrichten im Verfahren ATLAS AES wurde die Uhrzeit in UTC dargestellt. Dies wurde behoben, sodass die Zeiten nun in CET dargestellt werden. |
|
IntraStat | Es wurde eine fehlerhafte Vorbelegung beim Generieren des IntraStat-Bestandes behoben. Das Bestimmungs-/ Versendungsland im IntraStat-Bestand wird nun korrekt mit dem Bestimmungsland aus der Einzelzollanmeldung vorbelegt. |
|
ATLAS EGZ, BA | Es wurde ein Fehler beim Verschieben von VZA Positionen in neue EGZ / BA Vorgänge behoben. |
|
ATLAS Einfuhr (Alle Verfahren) | In allen Nachrichten des Einfuhrbereichs können Angaben zu Verbrauchssteuerwerten nur noch in EUR getätigt werden. |
Type |
Area |
Description |
|
Passar Durchfuhr | Die Reihenfolge der Nachrichten unter „Neu“ wurden neu sortiert. |
|
Passar Durchfuhr | Es können nun auch für Ankunftsanmeldungen Vorlagen erstellt werden. |
|
Passar Ausfuhr |
Es gibt eine neue Spalte „Verknüpfung mit WA-D“ im Homeview von Passar Ausfuhr, die anzeigt, ob eine Warenanmeldung Ausfuhr WA-A mit einer Warenanmeldung Durchfuhr WA-D verknüpft ist. |
|
Edec Import |
Analog zu Atlas hat man nun die Möglichkeit, eine edec Import zeitverzögert zu senden. |
|
Passar Ausfuhr |
Unser SCI (Scope Customs Integration) wurde um den Vorgang Warenanmeldung Ausfuhr erweitert. Es können nun auch WA-A via SCI zu Scope geschickt werden. Passend dazu, werden dann auch Events ausgelöst. |
|
Passar |
PDF können nun per E-Mail versendet werden - Einstellungen via Rolle „EZV Teilnehmer“ |
|
Passar Durchfuhr |
Vorgang Ankunftsanmeldung: Es gibt die Möglichkeit eine MRN Übersicht, welche den Status der einzelnen MRN anzeigt. |
|
Passar Ausfuhr | Sobald im Feld Kompensationstyp eine 1 eingetragen wird, taucht ein Pop-Up auf, um die VOC Menge einzutragen. Dieses wird dann im Reiter Dokumente/Bewilligungen unter Zusatzinformationen angelegt und kann dort korrigiert werden. |
|
Passar Ausfuhr | Es gibt eine Spalte ‘Gültig bis’, welche anzeigt, bis wann eine WA-A aktiviert werden kann. |
|
Passar Durchfuhr/Ausfuhr |
Die Filter in der Übersicht wurden nun alphabetisch sortiert. |
|
Passar Ausfuhr |
Wenn Sie auf einer WA-A eine Transportanmeldung machen, wird die WA-A GDRN automatisch übernommen. |
|
Passar Ausfuhr |
Bei einer Ausfuhranmeldung werden unter „neue Nachricht“ nur die Nachrichten angezeigt, die vom fachlichen Ablauf her sinnvoll sind. |
|
Passar Ausfuhr | Die Validierungsmeldung NP70065 wurde umgesetzt: Bei einer Warenanmeldung Ausfuhr darf die Postleitzahl des Versenders nicht 7562 oder 7563 sein |
|
Passar Ausfuhr |
Wenn die Anmeldeart „2 - ordentlich” ist, werden folgende Felder automatisch vorbelegt: Reiter Allgemein - Eigenantrieb und Nichthandelsware „Nein“ |
|
Passar Ausfuhr | Die Validierungsmeldung NP70271 wurde umgesetzt: Wenn bei der Warensendung der Haken bei „Präferenz“ nicht gesetzt ist, dürfen folgende Begleitpapiertypen nicht ausgewählt werden: 9541 WVB EUR.1, 9542 WVB EUR.1 CN, 9543 WVB EUR-MED, 9544 WVB EUR.1 „Transitional Rules“ |
|
Passar Durchfuhr | Eine WA-D kann nun ausschliessen im selben Vorgang aktiviert werden. Falls man versucht eine neue NC123 anzulegen und die MRN kopiert, kommt eine rote Validierung. |
|
Passar Durchfuhr | In einer WA-D, bei den Sicherheiten wird nun ein Hinweis im Feld Betrag in CHF: angezeigt welcher besagt: Grundsätzlich gilt 10% des Warenwerts einzutragen |
|
Passar Dokumente | Die Passar Dokumente für Durchfuhr und Ausfuhr können nun auch über die Dokumenten-Archivschnittstelle übertragen werden. |
|
Passar |
Aktivierung der Warenanmeldung am Domizil - Felder wurden umbenannt: |
Type |
Area |
Description |
|
Reporting |
In the NL Customs reporting an additional filter has been added to allow filtering items on one of the following items:
The Filter criteria to be used is called “Bescheiden(NL) - Certificate/Documents(EN)” |
Type |
Area |
Description |
|
Account Payables | The SEPA payment file generation on Accounts Payable overview has been updated to use the new format pain.001.001.09, which will soon become mandatory. |
|
Payment Terms | Support for the payment term 'End of Month plus 0 Days' has been added. |
|
Quotations | Loading meters are now automatically calculated for all quotations that include package details. Previously, this was only calculated for simple shipment road quotations. |
|
Accounts Payable Imports |
Improvements to the account payables import:
|
|
Activity Types | Scope now validates duplicate entries within an activity type for the same activity as an error, as they can cause issues during jobcosting calculations. If a charge type needs to be added more than once, it must be placed in separate activities. |
|
Partner | The tax ID format PIB has been added for partners in Serbia. |
|
Accounting Interface | The Quickbooks Online accounting interface has been updated to use the latest API version. |
|
Charge Types | The Charge Type overview can now be sorted by the column General Ledger Filter. This can be used to easily identify charge types that are not assigned to any filter. |
|
Document Interfaces |
The Document Archive and Incoming Documents interface has been enhanced with a new document type: Invoicing Data Sheet (UN/EDIFACT 1001 code 130). This document type is now available for use with uploaded documents in Scope. |
|
Document Archive Interface |
The Document Archive interface now exports the old ATC customs registration number using the new reference type ‘legacyCustomsRegistrationNumber’. This legacy number remains necessary for customs invoices as the Bundeskasse Trier still uses it. |
|
Customs Invoices |
Outgoing and incoming customs invoices created for ATLAS Einfuhr procedures include both the new MRN and the old ATC customs registration number in the remarks field, allowing the invoices to be found in Scope using either reference number. |
|
Exchange Rates | Cross exchange rates (for example on charge lines) are now consistently rounded to five decimal digits. |
|
Accounts Payables |
The issue with creating incoming credit notes from negative cost estimates using the fast incoming credit note entry in Scope has been fixed. |
|
E-Invoicing |
The Finalize Shipment wizard for Air Export now automatically attaches e-invoices to emails, if an e-invoice is generated and the email recipient has been designated to receive the invoice. |
|
Partner |
Partners can now be found by their tax ID when using the address search in fields such as Vendor or Invoice Recipient. |
|
Month Closing |
To ensure consistent data in the accounting system, the economic date or cost center of a shipment can no longer be changed once any of its estimates have been transferred to accounting through a month-end closing invoice. |
|
Order API |
Previously, the last change time of an order returned by the Order API was not updated in certain cases. This issue has now been resolved. |
|
Order API |
Milestones are now returned only on shipment level. They are no longer exported on transport order level, as they currently cannot be clearly assigned to a specific transport order, if applicable. |
|
Partner Address Interface |
A bug affecting the import of partners through the partner address interface has been fixed. The issue occurred when updating debtor or creditor profile data for partners with an EU VAT ID. As part of this update, all existing partners in Scope will be checked and corrected if necessary. |
|
Salesperson Allocations |
If a salesperson is automatically assigned to a shipment, the assignment may be removed if no matching allocation exists anymore. |
|
Order API |
Resolved an issue where documented sorting criteria could not be used in the Order API. Additionally, the default sort criterion has been changed to 'OrderDate'. |