V1_0

Detailed Release Notes for Scope 24.6

Explore the new features and find out how changes in Scope make your every day experience better.

Air Freight

UX/UI Improvement
Introduce new tracking plan icons, harmonize visuability with selected font size.
Air_updated tracking plan icons2_EN

Transport Order
Allow splitting of packages of a shipment when a Transport Order is created.
Air_split_tracking order packages_EN

Interface / EDI

Adding a new interface Scope Shipment Status Interface which sends shipment data including milestone information when a shipment or it's tracking plan changes. The interface is designed to send data to configured parties which might be involved in a shipment as customer, shipper, consignee or notify Here are some more details: https://service.riege.com/en/knowledge/scope-shipment-status-interface

Air Security

Improved Master-to-House Air Security dialog: Added a feature to multiple-select (shift-click) houses on a air export consol master and create security orders for all the selected house shipments via right click. Security orders will be created on every selected house and all generated PDF can be attached and send with one email to the security supplier.
Air_muli-select_Screening order_EN

Ocean Freight

Open Container Level Tracking incoming Event interface

A new incoming interface has been designed to allow the receipt of container level event in Scope. This events can originate from an external platform and can easily be imported by Scope after conversion to the new Ocean event message XML format.

https://service.riege.com/en/knowledge/ocean-events-interface

Transit Time in Sailing Schedule

When asking the global Sailing Schedule, the transit time in days is now available as a separate column in the result table.
Ocean_Sailing Schedule_Transit Time_EN

Set the VGM user signature

The users signature and name for VGM messages to the carrier can be provided by an EDI Profile to prevent validation errors on invalid characters contained in the default username.


ATB Number

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).

Order Tracking 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).

Container Number on House Shipment

Ocean_Container_on_HouseHouse shipments will now indicate the related container number in the shipment header line if already consolidated and assigned to a container.

Secondary Delivery Address on Container Transport Order

Allow secondary addresses of a partner for positioning in transport order before/after the main positioning.

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

OBL Number Validation in Export
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_OBL_number_validation_EN

No more space in Container Number

Scope has been redesigned in the backend to store and process container number without space between the prefix and the numeric part.

Finance

Grant of shipment waivers by non operational users

Users without access to certain shipment modules in Scope, like for example finance users, are now able to waiver shipment blocks using the read-only shipment editor on shipment overview.

Tax Authority Interfaces

In some countries, like Mexico or Romania, accounts receivables must be registered with local tax authorities.

Additional invoice statuses have been introduced:

  • Finish pending - whilst waiting for an answer from the authorities
  • Finish rejected - when the invoice has been rejected by the authorities.

The accounts receivable overview allows to filter for these statuses.


Pre-defined filters on accounts receivable overview

The accounts receivable overview has pre-defined filters to show invoices where the registration with local tax authorities is still pending (invoice status 'Finish pending') or that have been rejected by local authorities (invoice status ‘Finish rejected’)

Notification invoice rejected

The clerk who printed an invoice is notified via a persistent notification in Scope, if the invoice is rejected by local authorities

Workflow correct rejected invoice

In case an invoice has been rejected by local tax authorities Scope shows the rejection reason in the invoice editor. Scope offers a new workflow to re-open the rejected invoice, correct it and send it again to local tax authorities using the same invoice number.

API

Scope offers an API for external parties to mark an invoice registered with local tax authorities as accepted or rejected. 

Customs DE

ATLAS NCTS

If the administration or access code for the NCTS security is changed by message and this is successfully acknowledged by customs, the master data in the business partner is also adjusted. The security must then be manually deleted once for copied transactions and then inserted again so that the codes are transferred correctly. Alternatively, only the code in the application can be overwritten for new transactions.

Customs warehouse and AV

With Atlas 10.1, MRNs are also introduced for import procedures. Both the MRN and the AT no. are transferred to the stock and displayed. You can search for both numbers. Only the MRN has the action link to access the process, the AT no. does not have this. Exception: there is no MRN for the transaction, only an AT no.

Tyden seal (closure indicator)

If a Tyden seal is used in a process and the process is declared invalid (rejected), the Tyden seal is released again when the process is copied and used in the new copied process and written to the seal management. If an existing transaction or a transaction with the status 'error' is copied, the Tyden seal is not copied.

CustomsDE_Verschlusskennzeichen_Tyden-Seal


Go here for the complete changelog of version 24.6