Changelog Scope Version 25.10 (Preliminary)
With your help, we are improving Scope every day. These are the newest improvements and added functions.
Preliminary version
Changelog
= New feature
= Enhancement
= Bug fix
|
Type |
Area |
Description/Note |
| |
Documents | Add a filter option in the documents tab for master shipments to exclude documents associated to house shipments. |
| |
Various Shipment Home Views |
On shipment home views which come with a table and filter criteria, some option got enhanced and partially fixed:
|
| |
Scope Events appliance |
Improved event type filter by sorting lexicographically. |
| |
Order Tracking | Improved sorting of document types for applicability definition. |
| |
Shipment Monitor | Fixed a bug where opening a shipment from shipment monitor could create an error. |
| |
Shipment Templates | Fixed a bug where movement scope was not applied from template when a shipment is first created and then later connected to a shipment. |
|
Type |
Area |
Description |
| |
Package Editor |
Add copy function in packages editor to easy adding more packages with similar or same package details. The |
| |
Air Security |
Additional (optional) air security free text is now also transmitted in the eHouse (FHL) message. Formerly text transmission was limited to eAWB (FWB). This covers requirements when airlines demand “EBR OK” as OCI///ST lines on house level as air security free text. Nevertheless most airlines ask for “EBR OK” added into handling info if applicable. |
| |
Air Freight Booking Portal | Under some circumstances, an air export shipment could loose the associated carrier during a Cargo Ai booking. This is fixed now. |
| |
Various | Fixed various smaller glitches notably in order tracking event processing, uploading of Outlook mails. |
|
Type |
Area |
Description |
| |
vessel-schedule (sailing-schedule) |
Added a SCAC mapping for some Dakosy liner agents. If Dakosy provides a sailing without SCAC, we will try to map the liner agent code into a propper SCAC (if one exists). |
| |
Portbase / Secure Release | Technical change of the Portbase API calls, where we try to get rid of some exceptions, which were so far not caught in Scope and led to sentry issues. |
| |
Set / Withdraw Embargo | Enabled setting / withdrawing of embargo for simple shipment, air/sea export / import shipments, where it was only possible in air (export or import) so far. |
| |
Gatehouse Events |
Removed the mapping of received generic FCL events from Gathouse to relating ocean insight events (in Scope). |
| |
Tradetech Events | Inbound tradetech events, which contained no USI lead to an error in Scope. That issue has been fixed now (by ignoring such messages). |
| |
Portbase Webhook Events | When receiving webhook events, where no ETA is set for the destination terminal, the port ETA is used instead to update trucker nomination entries. |
| |
Prealert (EDI) Events | Prealerts with same ID but a different receiver-branch will no longer be imported. Instead an error EDI event indicating the original branch and the update branch will be created. |
| |
Simple Shipment ROAD | Whencreating a simple shipment type Road and selecting a Road carrier with EDI setup, empty pieces and weight will now show a validation error. If the selected road carrier has no setup, the error will instead be a warning. This does not affect Simple shipments or type Air or Sea. |
| |
LCL Bookings (OCE CC) |
Fixed conversion of RSIXML2 LCL Bookings to IFTMBF (Inttra only), where DTM segments of the pre-/on-carriage were inserted in the wrong position. |
| |
OCE CC | An error was fixed in the OCE CC, where the Gatehouse Event registration by OBL number (instead of Booking Number) did not work. |
| |
OCE CC | An error was fixed in the OCE CC, where transmitted LCL bookings to Inttra with pre-/on-carriage information were converted incorrectly (wrong position of a DTM segment). |
| |
Codelist generator | The CSV delimiter set in the UI (of the codelist generator website) is now used, when parsing a CSV file. |
| |
Sea Carrier Booking | When transmitting RSIXML2 bookings from Scope to the OCE CC, the destination port is now filled with the destination port of the booking. Before, the departure port was used. |
| |
Dakosy APERAK message | When receiving APERAK messages from Dakosy with a too long error description, the message processing failed, when trying to store the message in the database. This issue has been fixed now. |
|
Type |
Area |
Description |
| |
ATLAS - NCTS | Die Funktionalität der Datenübernahme von AES MRNs in Versandanmeldungen wurde verbessert und erweitert. |
| |
ATLAS - NCTS |
Seit der vollständigen Umstellung auf NCTS P5 werden Ereignisse während des Transportes nicht mehr vom zugelassenen Empfänger in der E_DES_NOT (Eingangsanzeige) erfasst, sondern vom Zoll selbst, von der sog. Unterwegszollstelle. Im Vorgang selbst steht neben der Entladeerlaubnis ebenfalls eine Warnung. |
| |
ATLAS Einfuhr |
Beim Absenden einer EZA, die Barzahlung von Antidumpingabgaben erfordert, zeigt Scope nun einen Hinweisdialog an. Dieser informiert darüber, dass jemand gegebenenfalls Bargeld besorgen muss. Der Dialog kann vom Benutzer abgebrochen werden. Hinweis: |
| |
ATLAS Einfuhr |
Scope zeigt dem Benutzer jetzt eine Warnmeldung an, wenn eine Kombination aus Warentarifnummer und Ursprungsland eingegeben wird, für die es im EZT eine Maßnahme 142 (Zollpräferenz) gibt. Dabei gilt es zu beachten, dass die Warnung nur auftaucht, wenn zusätzlich bei der Art der Begünstigung die 100 für Drittlandszollsatz ausgewählt wird, welche die Nutzung der möglichen Zollpräferenz unterbinden würde. |
| |
ATLAS Einfuhr | Wenn die Dakosy-Anbindung genutzt wird und eine IMP Verfügung eingeht, so kann Scope nun auch mit der MRN der vorübergehenden Verwahrung einen Verwahrerwechsel und eine ZvG bestätigen. |
| |
ATLAS NCTS | In der Versandanmeldung E_DEP_DAT wird nun die Angabe des Beförderungsmittels an der Grenze rot validiert, wenn ein inländischer Verkehrszweig angegeben ist bzw. nicht den Wert 5-Postsendung enthält. Diese Validierung wurde auf Grund von Rückweisungen durch den Zoll hinzugefügt. |
| |
ATLAS NCTS | In einer Versandanmeldung E_DEP_DAT konnte der Verfahrensübergang Zolllager nach der ersten Erfassung nicht weiter editiert werden. Dieser Fehler wurde behoben. |
| |
ATLAS AES | In einer Ausfuhranmeldung E_EXP_DAT konnte im Feld Gesamtbetrag ein negativer Wert eingegeben werden, wodurch nach dem Senden ein XML-Schema-Fehler aufgetreten ist. Dieser Fehler wird nun mit einer Validierung verhindert. |
|
Type |
Area |
Description |
| |
PDE RTO | In the take out function, an extra menu option under "extra" automates transferring a take out to another warehouse. For example, when RTO inventory reaches 90 days, this option automates the take in and confirmation of the take out. |
|
Type |
Area |
Description |
| |
Passar Durchfuhr | Die Referenznummer/Anmeldenummer ZE kann nun durch einen automatischen Zähler mit der Dossiernummer befüllt oder manuell erfasst werden. |
| |
Passar Durchfuhr | Statistiken und Layouts nun auch für Passar Ausfuhr. |
| |
Passar Ausfuhr | Die AEO Nummer wird nun aus den Stammdaten des Geschäftspartners (Rolle zugelassener Wirtschaftsbeteiligter) vorbelegt, falls vorhanden. |
| |
Passar Durchfuhr | Bei einer nationalen Durchfuhr ist das Bestimmungsland mit CH vorbelegt. |
| |
Passar Ausfuhr / Durchfuhr | Der Status wird nun in Gross/Kleinbuchstaben dargestellt. |
| |
Passar Ausfuhr | In der Übersicht kann die Spalte Exporteur angezeigt werden. |
| |
edec Import | Die MwSt Codes werden nun aus den Stammdaten gezogen. |
| |
edec Import | Das Feld Total Nettogewicht kann nun auch via SCI Schnittstelle befüllt werden. |
| |
Passar Ausfuhr | Bewilligungen: Codeliste wird nun im Feld Ausnahme der Bewilligungspflicht angezeigt. |
|
Type |
Area |
Description |
|
|
Permissions |
To improve control of financial processes, two new permissions have been introduced:
These new permissions have been automatically granted to all users or permission groups that already have permissions to create outgoing invoices and payment deductions. To adjust the permission setup, please contact the Riege Service Team. |
|
|
E-Invoicing |
The payment type direct debit is now available for use in e-invoicing. To support this enhancement, new fields have been added to the E-Invoicing tab on the debtor partner role, allowing for structured entry of direct debit information.
|
|
|
XRechnung E-Invoice Format |
Several improvements have been made to the XRechnung e-invoice format to enhance functionality and compliance:
|
|
|
Estimates |
To support audit requirements, additional data will now be stored when estimates are transferred to accounting via a month-closing invoice. This enhancement applies only to future invoices. The following data will be available in the estimate export:
|
|
|
Partners | Added the field 'Payment Type' from the debtor partner role as a new column to the export on partner overview. |
|
|
Partners | You can now maintain a secondary tax ID for a partner to support compliance with local e-invoicing regulations in applicable countries. The primary tax ID continues to serve as the basis for tax determination and invoicing. The availability of secondary tax ID types is determined by the partner’s country and the selected primary tax ID. |
|
|
Partners |
Support for additional tax ID formats has been introduced for partners:
|
|
|
Sea Import | The consol profit tab, already known from other shipment types, has been added to the seafreight import super-house FCL editor. |
|
|
Accounts Receivables | Resolved an issue where the base units of a calculation were not displayed in the charge line invoice text for certain calculation bases. |
|
|
Shipment Blocks | Resolved an issue with payment term checks for shipments involving child debtors. Previously, the system did not consistently apply the master debtor’s payment terms for prepayment and cash-on-delivery checks. |
|
|
Payment Import | Resolved an issue with the Scope payment import format where, in certain cases, a cancelled invoice was incorrectly displayed as open after the import. |
|
|
Quotations | An issue has been resolved in the quotation export that could occur when the column ‘First Printed At’ was selected. |
|
|
Order API | An issue in the Order API has been resolved where an internal server error (HTTP 500) was returned instead of a proper client error (HTTP 400) with an error message. |
|
|
Swiss QR Bill | When the QR bill generation is enabled, a validation rule now ensures that invoice addresses include a zip code to prevent generation errors. |