With your help, we are improving Scope every day. These are the newest improvements and added functions.
Looking for the Detailed Release Notes of Scope 25.2?
Changelog
= New feature
= Enhancement
= Bug fix
Type |
Area |
Description |
|
Filters | Default Filter on HomeViews persists until changed manually. This applies to all home views in Scope that allow to maintain filters. The last chosen filter will be active until manually removed or changed. Before: Filter was removed after a Scope client restart. |
Tasks |
The creator of a task is now shown in ‘My Tasks’, the task data editor and available as new optional column in the ‘Team Task’ table. Allow assignment of a task to administrator users. |
Type |
Area |
Description |
|
Air Export | When shipment type is changed from House to Direct, the Direct AWB main transport is always set to Prepaid even if the former House Incoterm might have been EXW and HAWB was Collect. |
|
Air Freight Booking Portal |
Air freight Booking Portal: Easy Select Adding a tile centered view to Air freight Booking Portal to easy decision making, additional to full table result view. The tile view shows the most economical flight option as well as the earliest arriving and a ‘balanced’ flight option. The balanced option represents a ‘slightly later’ than the earliest arrival flight option with costs being only ‘slightly more’ than the most economical flight option. While speed and price are equally weighted initially, a slider allows to fine tune to emphasis either speed or pricing over the other. The table view also allows to filter out ‘flight options arriving later than the most economical flight option’ plus ‘flight options being more expensive than the earliest arriving flight option’. |
|
Green Pixels / CO₂ Emissions | Add Transport Orders of Masters (deliver from gateway to airport) to CO₂ Emission calculation of Houses |
|
Green Pixels / CO₂ Emissions | Allow to set/unset “cool freight” for individual shipments |
|
UX/UI Improvement | Synchronize cargo totals from package editor better: do not overwrite chargeable or volume weight in shipment when details did not change in package editor. |
|
Air Export | Departure Control for empty / voided masters: Sometimes master shipments get voided (having all houses removed) but are stuck in departure control. This change excludes voided masters from departure control. |
|
Air Freight Booking Portal | Show rates from quotation when searching for new option on Air Freight Booking Portal |
|
Air Freight Booking Portal | Add warning if IATA Cass number doesn't match |
|
Air Freight Booking Portal | CO2 not calculated for all quote options when air freight booking portal creates multiple options |
|
Air Freight Booking Portal | Preserve information about unmapped charge codes for quotation created via air freight booking portal |
|
Air Freight Booking Portal | Block booking of DGR shipments |
|
Air Import | Air Import Master: Houses Table Shows Shipper Name in Consignee Column |
|
Air Security | Allow multiple notification email addresses about automatic EU Database validation |
|
Air Security | AirWaybill prints 'Not secured' instead NSC even if NSC is manually confirmed |
|
Tracking Templates | Fixed actions partially not executed on house shipment DEP/ARR milestones on leg level upon execution of departure control (flown as booked) on the corresponding master shipment. |
|
Transport Order/Activity Types | We have added an activity type for the Delivery from Terminal transport order type to be able to retrieve costs and revenues |
|
UX/UI Improvement | Moved ‘Missing EDI Mappings’ to the ‘Monitoring’ menu |
|
Air Export | Air Export “Finish action” on consol shipment: add warning if AWB data differs from shipment data after adding/removing houses |
|
Air Freight Booking Portal | Improved UI for error handling after booking |
|
Tracking Templates | Order Tracking: Translation of generic exception templates is not stored |
|
Tracking Templates | Tracking Templates Homeview : negation of constraint not shown properly |
|
UX/UI Improvement | Dimensions fields: Scope will automatically add “in” or “cm” if one of the three fields was already filled with the “in” or “cm”. |
|
Air Export | Under seldom circumstances, Scope did not calculate the chargeable weight precisely as per IATA TACT 3.9.4 due to internal rounding. Example is a package with 40 cm x 31 cm x 17 cm which corresponds to a volume of 0,02108m³. Scope shows a volume 0,021 m³ with only 3 digits, which could lead to the expectation of a chargeable weight of 3,5 kg while per IATA TACT rules the chargeable weight is to be calculated with a precision of 6 digits (based upon 0,02108 m³) plus rounding up and therefore is 4 kg. This got adopted and fixed. |
|
Air Export | Wrong “Total No. of pcs. MAWB” on Combi-Label when printed from House |
Type |
Area |
Description |
|
|
Shipping Instructions / Security Manifest Filing order for HBL data by Carrier |
We have completely re-worked the option to send HBL data to carriers within the shipping instructions. The user is able to activate / deactivate the filing request to the carrier by a new options selector which depends on port of discharge. To change the default users have to switch to the settings within the Ocean Carrier Portal Mapping. To disable filing by ocean carrier (for Canada and US) it is mandatory to set a NVOCC carrier code (“SCAC”) on entity level, which is by the way not required for IC2/ENS. The “SCAC” can be no longer maintained on the own partner’s agent role! Users are able to change the manifest filing order method (self- / carrier-filing) within the individual shipping instruction by levering out the default. |
|
|
BHT settings | In the BHT partner profile there is a new property (checkbox), which allows to activate the transmission of emails to the original sender of an outgoing BHT message in case critical status responses from BHT system are received. | |
|
Transport Order | A new option “Transfer” allows to generate a new type of transport order for pure transfer full-full from a terminal/depot to another terminal/depot without positioning address for loading or unloading the container. It is optional to put a multistop for weighing/fumigation/customs/documentation on the transfer order. | |
Trade Tech Interface / Security Manifest Filing |
Ocean Import Shipments can be transmitted to Trade Tech for Manifest Filing (before: only Export Shipments) |
||
|
Carbon Care | For ocean freight shipments holding one (or more) reefer containers, where the temperature is defined, the triggered CO2 calculation has been corrected. The carbon care calculator in this case gets a boolean value (true) to allow a different calculation. | |
|
Vermas (VGM) | Incoming Vermas messages of type ‘pending’ now generate a status message in Scope with a new status type “Vermas pending”, which is linked to the relating shipment/master. This new status/status type can also be used in the order tracking as a trigger for an exception or the completion of a milestone. | |
|
Prealert | Persist events when converting prealert to shipment | |
|
Transport Order & Booking confirmation |
we prefill the pickup details from the carrier booking if
|
|
|
Vessel Schedule |
Remove VS Link Lock in Main Transport |
|
|
Carrier Events |
For received carrier events received from Inttra, Cargosmart, GTNexus or OI, the transferred location code is stored as an attribute with the event in Scope. This code is now visible in the shipment’s event tab in the attribute list displayed for a selected event. |
|
|
Transport Order |
Container Return Reference on Container Delivery Order in Sea Import will be defaulted from the Depot Reference (Container Depot Entry on Goods Tab) |
|
|
Transport Order |
Adding of remarks field on handover note in addition for any type of instructions |
|
|
HBL editor |
Establishing of new design of print button in HBL editor |
|
|
Ocean Manifest |
Establishing of a better and reasonable validation when entering HS Code |
|
|
Transport Order / Activity Types |
We have added an activity type for the Delivery from Terminal transport order type |
|
|
Shipment Template |
Contract number for transmission of booking requests to ocean carriers can be maintained within the shipment template of ocean exports |
|
|
Document Types |
We have added “VGM” to the existing description of the Verified Gross Mass document to be able to find it easier |
|
|
Ocean Tracking |
Inbound events for FCL will be ignored for processing if no location has been given to avoid triggering milestones |
|
|
Ocean Tracking |
FILAM events can be optionally disabled on road carrier role |
|
|
Transport Order |
Delivery Party role in export container transport order has been renamed to Loading Party. Delivery Party role in import container transport order has been renamed to Unloading Party. Uncouple Container option has been disabled for Documentation Party and the Chassis Location. |
|
|
EMO House B/Ls |
Emotrans has a very specific implementation on how HBL numbers are finalized: When selecting the House B/L (3 different types are available) and printing (or storing it), the final HBL number is created and updated in the shipment. This was not working properly for softcoded House B/Ls, but is fixed now. |
|
|
Dakosy/BHT |
When receiving critical response messages from dakosy or BHT/ DBH there existed a bug, which led to an update of the dakosy/BHT partner profile. Result was an increasing number of email addresses (for critical responses) in the profile. This bug is fixed now. (Change also has been backported to Scope 25.0) |
|
|
Dakosy IMP / EDI Shipments | Received status messages of a “Dakosy IMP Verfügung” could not be correctly processed in case the message related to an EDI shipment. This bug has been fixed now. (Change also has been backported to Scope 25.0) | |
|
Transport Order |
Carrier booking reference in ocean shipment gets defaulted as empty pick up reference within the transport order in addition to full return reference. |
|
|
Import Superhouse |
When consolidating house shipments onto an import superhouse, where the house contains multiple shipper and/or consignee references, the house was displayed multiple times in the consolidation tab of the superhouse. This is fixed now and has also been backported to Scope 25.0. |
|
|
Sailing Schedule |
When receiving a schedule with a long service code the Voyage selection from Sailing Schedule will no longer trigger an error |
|
|
Transport Order - Display Bug | Display Bug in Transport Order Goods Assignment | |
|
Seafreight Bookings | When receiving a booking via interface (as rsixml2 shipment file of type “booking”) for sea, the contained goods, which may hold dimensions with a defined total volume are now converted into a booking, which shows the volume per dimensions entry in the goods editor. The volume was missing in the past. | |
|
BHT Order |
BHT Exception when trying to send a message due to 3 digits behind the decimal point |
|
|
BHT Order |
BHT Exception fixed, when trying to send an email for inbound critical status messages, where no email recipient was defined. Fix also backported to Scope 25.0 |
|
|
BHT Order |
Several BHT Status messages could not be displayed, since the status type was unknown in Scope — fixed now |
|
|
BHT Order |
For critical BHT Status messages, a growl message should be created, but lead to an exception. Bug is fixed now and also backported to Scope 25.0 |
|
|
CMR |
When creating PDFs only in the CMR editor, the combined CMR was still sent to a printer. This bug is fixed now. |
|
|
HBL document file |
Terms & Conditions were missing after establishing new print button in HBL editor on draft, copy, and original |
|
|
Ocean Carrier EDI |
Fix timestamp in response from INTTRA |
|
|
Ocean Carrier EDI | Do not transmit contact without name in booking to INTTRA | |
|
Transport Order |
Improve validation on DGR which appeared when entering dangerous goods for a simple shipment sea, the validation showed some warnings for fields, which were not visible on the screen. |
|
|
Sea Booking |
When copying a seafreight booking, the new and original booking could be found by the booking number of the original booking. This issue has been fixed, so that now only the “original” booking can be found by the “original” booking number. |
|
|
Transport Order XML for EDI |
We have included measuring unit MLT – which stands for milli-liters and used in net-weight of liquid dangerous goods – to be transmitted within the generic TransportOrderXML – latest version 1.16 of the schema – to road/rail/barge carriers. |
Type |
Area |
Description |
|
ATLAS SumA |
In der SumA wurde für die PrlCon der Positionsimport implementiert, um komfortabler Positionsdaten in Scope zu importieren. |
|
ATLAS AES |
Die Sammelgestellung wurde erweitert. Wenn die E_EXT_DAT vom Zoll empfangen wird, wird automatisch die Qualifizierung E_EXT_INF/LV übermittelt. Beim Anlegen wird nach der Verwendung einer Vorlage gefragt. Diese bezieht sich auf die E_EXT_PRE; für die E_EXT_INF gibt es keine Vorlage. |
|
ATLAS NCTS |
Bisher war es nur möglich, Warenpositionen über den Positionsimport zu importieren. Diese Funktion wurde nun auch für die Einzelsendung erweitert, sodass nun auch mehrere Einzelsendungen per CSV/ XLS importiert werden können. Beim Import der Einzelsendung werden auch — wenn in der Tabelle definiert — die Warenpositionen mit angelegt. |
ATLAS Einfuhr, ZL, AV |
In den Verfahen Einfuhr, Zolllager und AV wurde die erweiterte Suche hinzugefügt. Je nach Verfahren stehen die folgenden Suchparameter zur Auswahl, um die Anzeige im Homeview zu verfeinern:
|
|
ATLAS NCTS | NCTS Vorgänge die mehr als 100 Einzelsendungen hatten, konnten erst nach 5 bis 10 Minuten geöffnet/gesendet werden. Dies konnte auch zum kompletten einfrieren der Scope-Anwendung führen. Dies wurde behoben, sodass das Öffnen/ Senden/Speichern in einem angemessenen Zeitrahmen erfolgt, ohne dass sich das System aufhängt. | |
ATLAS AES | Es gibt für AES nun ein Notfallverfahren inkl. Statusansicht. Anders als zuvor muss die E_EXP_DAT im Falle eines Notfallverfahrens nach Wiederinbetriebnahme des Verfahrens nach einer Störung nachträglich an den Zoll übermittelt werden. | |
ATLAS EINFUHR | Werden steuerliche Verweise angemeldet und ein nicht passendes Verfahren (anderes als 42xx oder 63xx) wird eine Warnung ausgegeben, ob das angegebene Verfahren nicht 42 oder 63 sein sollte. | |
ATLAS EINFUHR | Es gibt Steuerbescheide, die keine Überlassungsmitteilung haben, da diese noch auf Zahlung der Einfuhrabgaben warten. Wird eine CusTax ohne Überlassung übermittelt, so wird der Status 52 angezeigt. Erfolgt im Anschluss eine Überlassungsmitteilung, wird der Status auf 60 geschrieben. | |
ATLAS RZT | Es kommt vor, dass der Zoll Codelisten veröffentlicht, diese zunächst aber nur intern hat und zu einem etwas späteren Zeitpunkt für die Wirtschaftsbeteiligten veröffentlicht. Dies führte dazu, dass einige Anmeldungen nicht übermittelt werden konnten, da gem. EZT Unterlage ein Wert erfasst werden musste in Scope, den der Zoll aber nicht mehr erwartet. Dies führte zu fachlichen Fehlern. Die Fehlermeldung wurde durch eine Warnung ausgetauscht, so das ein Senden immer möglich ist. Wird die Warnung ignoriert kann es im Zweifelsfall zu einem fachlichen Fehler kommen, der aber durch den Benutzer korrigiert werden kann und an den Zoll übertragbar ist. | |
|
ATLAS NCTS | Es gab einen XML Fehler, wenn über einen Import die Positonsnummer “0” als Vorpapier mitgegeben wurde, da Scope hier nicht auf >0 validiert hat. Dies wurde korrigiert, sodass eine rote Validierungsmeldung angezeigt wird. |
|
ATLAS NCTS | Die Anzahl der Einzelpositionen war auf 99 begrenzt, obwohl es mit Phase 5 erlaubt ist 1999 Einzelsendungen anzulegen. Dies wurde korrigiert. |
|
ATLAS SumA | Wollte man eine Warenpositon innerhalb eines SumA Vorgangs öffnen zu dem bereits eine Erledigung vorlag, konnte dieser nicht geöffnet werden und es wurde eine Information angezeigt, dass nichts gefunden wurde. Dies wurde behoben, sodass nun die Vorgänge wieder geöffnet und angezeigt werden. |
|
ATLAS SumA |
Bei der Übertragung via SCI wurde das Kennzeichen des Beförderungsmittels nicht mit gemappt. Dies wurde behoben. Bei der Erstellung eine CUSPRL via SCI wird diese wie folgt gemappt:
|
|
ATLAS AES | Wenn Art der Anmeldung *****4** beantragt wird, muss das vorangegangene Verfahren nicht in allen Positionen gleich sein. Dies wurde falsch in Scope validiert und nun angepasst. Das angemeldete Verfahren muss in allen Positionen gleich sein und das vorangegangene nicht. |
|
ATLAS Einfuhr | Die Events GENERAL_REGISTRATION und IMPORT_DUTIES hatten nur das Datum und nicht die entsprechenden Zeiten. Dies wurde angepasst, sodass die Events nun auch den Zeitstempel haben. |
ATLAS AES | Seit NCTS 5 ist es nicht mehr erlaubt, die einzelnen Empfänger eines Ausfuhrvorgangs in die Warenpositonen mit zu übernehmen. Wird ein AES Vorgang mit mehr als einem Empfänger auf dem ABD importiert, so werden die Empfänger alle gelöscht auch auf Einzel- und Sammelsendungsebene. Es ist der letztbekannte Empfänger für alle Waren anzugeben. | |
ATLAS Einfuhr | Die Suche nach Empfänger und Versender über die erweiterte Filterfunktion hat keine zuverlässigen Treffer angezeigt. Dies wurde angepasst. |
Type |
Area |
Description |
|
Passar Durchfuhr |
Im Homeview können nun Warnlisten erzeugt werden. Zusätzlich kann man sich diese Warnlisten per E-Mail zustellen lassen. |
|
Passar Durchfuhr |
Die SCI (Scope Customs Interface) wurde durch die Anbindung an Passar Durchfuhr (Warenanmeldung Durchfuhr) erweitert. |
|
Passar Durchfuhr |
Es gibt nun die Möglichkeit, nach Anweisung des BAZG, ein Notfalldokument zu drucken. |
|
Passar Durchfuhr |
Wenn der Vorgang mit einer Sendung verknüpft ist, werden die Dokumente in der Sendung abgelegt |
|
Passar Durchfuhr |
Es gibt eine neue Berechtigung “CHZoll: Senden von Zollnachrichten mit Validierungsfehlern und XML-Fehler”. |
|
Passar Durchfuhr | Die Transitfrist der Warenanmeldung Durchfuhr (WA-D) wird nach erfolgreicher Aktivierung neu berechnet und ist damit konform mit der Transitfrist auf dem Versandbegleitdokument |
Type |
Area |
Description |
|
|
Web Services |
The Order and Partner APIs in Scope have been enhanced with both technical improvements and additional data. Key updates include:
|
|
|
Sales Person Allocations |
As before sales persons are automatically assigned to shipments or quotations if sales person allocations have been entered. The automation now updates the assigned sales person not only when a shipment is saved for the first time but continues to update it until the shipment reaches the financial status ‘Billed’. Manually assigning a sales person disables the automatic function. The assignment process for quotations has been aligned with shipments: salespersons are automatically updated until the quotation reaches the status ‘Completed’. |
|
|
Quotations |
The email template for quotation emails has been enhanced with an option to upload a fixed document that will automatically be attached to all quotation emails alongside the quotation document. This feature allows general forwarding conditions or other standard attachments to be included in every email without requiring users to upload the document manually each time. | |
Quotations |
Sales persons are no longer included when copying a quotation. Instead, a sales person should be assigned either through the improved automatic function or manually. | ||
|
E-Invoicing |
In addition to configuring the XRechnung e-invoicing format for individual debtors, the Riege service team can activate it on legal entity level for all German invoice recipients. The E-Invoicing tab of the debtor partner profile now indicates when an e-invoice format is active for this debtor due to a legal entity-level configuration. If the XRechnung format is enabled on legal entity level, this general setting can be overruled for a given debtor by defining a debtor-specific format. |
|
|
Accounts Payable Imports |
The accounts payable import in Scope now displays payment term notes and can recognize Skonto payment terms according to the XRechnung specification. When importing a Skonto invoice, the process stops no later than the creation of the incoming document in Scope. At this stage, a clerk must decide whether and which Skonto conditions to be applied. The imported payment terms are shown as a note in the incoming invoice editor. Since the reduced Skonto amounts are not transmitted in the e-invoice, applying Skonto requires manual adjustment of the invoice amounts. This is the only case, where invoice amounts of an E-invoice can be changed |
|
|
Reporting |
A new column ‘Economic Date’ has been added to the ledger report of type ‘Turnover Details’ and ‘Cost Details’ in Finance > Reporting. | |
|
Document Archive Interface |
The document type ‘CusTax Komprimierter Ausdruck Bescheid/Befund’ is now supported by the document archive interface. |
|
|
Accounts Receivables |
A bug has been resolved regarding the automatic application of a deviating customs payment term in the accounts receivable editor. This issue occurred when customs estimates were added in an invoice through the estimates dialog. | |
|
Accounts Receivables |
The visibility issue with the checkbox ‘Restore original cost specifications’ on the confirmation dialog for the cancellation of aggregated invoices created by cost specifications has been resolved. | |
|
Accounts Payable Import |
For accounts payable imports of type CSV/Excel, the field ‘Internal Number’ was editable in certain cases, despite configuration settings that should prevent this. This issue has been resolved. |
|
Quotations |
In certain situations, manually entered airfreight costs on an airfreight export quotation were overwritten by rates from the IATA AWB of a back-to-back shipment. This issue has now been resolved. |