Notas de la versión 26.6 de Scope
Con tu ayuda, estamos mejorando Scope cada día. Estas son las últimas mejoras y funciones añadidas.
Looking for the Detailed Release Notes of Scope 26.6?
Changelog
= New feature
= Enhancement
= Bug fix
|
Type |
Area |
Description |
| |
Denied Party Screening Whitelist |
Smart ‘Whitelist’ feature for Denied Party Screening We improved the existing ‘Good Guy’ feature mechanic with a smarter process. Major advantages over ‘Good Guy’ are continued automated checking of whitelisted addresses and no need to manually re-check the same address with same match result after some days. Re-checking is limited to changes in address or changes with matches on denied party lists. |
| |
Denied Party Screening | Denied Party Screening not behaving as expected when a partner used as shipper but address details getting modified for the shipment. |
|
Type |
Area |
Description |
| |
Air Freight Booking Portal | Default stackable/non-stackable field for airfreight booking portal query properly from the stackable fields on quotation, booking or shipment package details |
| |
Transport Order |
Fixed default for delivery timeframe on Pickup transport orders. Scope now uses a better default for delivery timeframe of pickup orders and also applies opening hours when configured in for the applicable partner. |
| |
Transport Order |
Apply DTT creation settings also to master shipments. Default to create or not create a Deliver-to-Terminal (DTT) transport order is configurable in partner settings, role agent, airfreight section. This setting got enhanced to apply also to master shipments. |
| |
Master Data |
Default values for new AWB Print Configuration got changed:
|
| |
Permissions | Test of the permissions for Extras > Create Copy… harmonized over air/ocean export/import/simple shipments. |
| |
UI/UX | Various minor wording, layout and error handling improvements for a better user experience. |
| |
Air Export / AWB | Other charges with spot a base amount plus a rate / per shipment had not been applied calculated correct on an AWB. This got corrected. |
| |
Air Export / AWB | Improved consistency of currency usage - under some circumstance the currency of a quotation was not applied to some shipment charges for shipments created out of that quotation. |
| |
POMS | Allow seldom used length units (like millimeter) for on Forwarding Order XML outbound interface. |
| |
Air Messaging Premium | Fix a bug which caused subscription messages too often |
| |
Air Export | Fix a seldom occurring bug in cleanup of AWB Pool for expired blocked entries which could block saving of air export shipments. |
|
Type |
Area |
Description |
| |
Ocean Tracking |
Match Same City flag is automatically set on location-linked generic FCL milestones to improve milestone completion in tracking. |
| |
Manifest Filing |
The carriers booking number(s) will no longer be transmitted to Tradetech. |
| |
Manifest Filing/ICS2 |
We enhanced the validation for contacts on partners (shipper/consignee/notify) and will display an error if phone number is longer than 23 chars for all filing types. We will also display an error if the email is longer than 50 chars for ICS2 filings. |
| |
Sea Export | We renamed the field CFS/CY Closing to CY Closing for all Export shipment types and for Sea Export Bookings |
| |
Tradetech Manifest Filing | When changing relevant data in the shipment / master on an already transmitted manifest filing the status will be updated automatically to ‘OUTDATED’. By that the user is informed, that he should resend the filing. |
| |
CMR Printout / Ordertracking | Printing a CMR can now be used to complete milestones in the order tracking. |
| |
Dakosy | In the Dakosy partner profile a new checkbox allows to (de-)activate EDI communication with Dakosy. By default, the EDI communication is enabled, but it can be deactivated in case the Dakosy module is only used for printing or in case there is no EDI setup. |
| |
Sea freight | Weights on all (softcoded-)BL documents will always be printed with three decimals (e.g. metric: 5630,000 kg / imperial: 5630.000 kg) |
| |
Transport Order |
Two changes:
|
| |
Transport Order/ Sea Import | We have introduced a new transport order type “Delivery to branch” to give users the choice to handle the first part of the haulage from the CFS (= default pickup address) to the freight forwarders warehouse (= default delivery address) without triggering wrong events for final cargo delivery. |
| |
Ocean equipment | We will supply a new default set of container types for any new Scope instances which is also available for existing Scope forwarding customers. We have preselected container group codes (e.g. 22GP, 42GP, 45GP) rather than container type codes (e.g. 22G0, 42G0, 45G0, 22G1, 42G1, 45G1). |
| |
AMS relevant shipping instructions | We have introduced an option to pre-define an affix [“as agents of NVOCC / FMC#0123456789“] within the own agent role which will be automatically populated within the shipper for AMS relevant shipping instruction. |
| |
Sea Export | The master loading list will contain the details of the house shipments rather than the details of the super-house shipments. |
| |
Simple Shipment | Scope will generate departure and arrival events for simple shipments of type road•air•ocean if the user manually sets ATD and ATA date-time, with the ability to complete milestones. Add scp.man.simple.ACT_DEPARTURE and scp.man.simple.ACT_ARRIVAL to your simple shipment tracking templates. |
| |
Sea Export | We have implemented the maintenance of carriers who offer ICS2 filing on the ocean carriers application and will centrally maintain the flags to be supplied to your Scope instance. |
| |
See Export FCL/ Transport Order | We have introduced an option within pickup transport order FCL to print an alternative text for a combined packing order to the haulage operator which is the container packing operator at the same time. |
| |
Simple Shipment | We enhanced the handling to allow more than one Scope booking can be linked to a simple shipment. |
| |
XML Transport Order |
We fixed transmission of older versions of the transportOrderXML (up to 1.17) to not include the optional “displayName” of a file attachment if the name is too short according to the schema. The new schema (1.18) allows shorter displayNames. |
| |
CMR | Fixed error that rarely occurs in CMR dialog. |
| |
Prealert | Fixed exception, when opening an import shipment / master based on a prealert with multiple conveyance details. |
| |
Fiata FCR (CH) | Fixed error in Fiata FCR dialog for Switzerland if issuing agent is missing. |
| |
Prealert | For prealerts, which are manually or automatically transmitted via the Edibooking CC to an external party, Scope now checks if there exists an EDI mapping for the sender and receiver of the message. In case one (or both) mappings are missing the transmission is prevented. In case of a manual transmission (triggered by a user), a dialog shows the reason for not transmitting the prealert. |
| |
Sea freight | A bug has been fixed that resulted into houses on a master losing their goods details. |
| |
Sea Import Master | We fixed a bug that prevented a manual event creation when the user had set an ATS date/time on the sea import master |
| |
Sea Import Master | We fixed a bug that prevented sea import master shipments to be opened due to a bug. In very rare occasions it could have happened that a transport order was connected to an incorrect shipment (mainly by changing the shipment type several times). This was fixed by reassigning the transport order(s) to the shipment they currently belong to. Shipments with this issue are marked as changed on opening. |
|
Type |
Area |
Description |
| |
SCI - Scope Customs Integration | Die SCI-Schnittstelle wurde um das Verfahren ATLAS IMPOST erweitert. Es können nun Anmeldungen automatisiert über SCI in Scope eingespielt und versendet werden. Die angepasste Dokumentation finden Sie unter folgendem Link: Scope Customs Interface V5 |
| |
ATLAS WKS | Die Logik für die Felder LRN und Bezugsnummer wurde gemäß den zukünftig geltenden Bestimmungen angepasst: Bei der Neuanlage eines WKS Vorgangs wird von Scope sofort automatisch eine eindeutige LRN vergeben. Diese LRN hat immer den dreistelligen Branchcode als Präfix, gefolgt von 19 Ziffern und Großbuchstaben. (erweiterte Erklärung folgt in den Details zur neuen Scope Version 26.4) |
|
Type |
Area |
Description |
| |
Ausfuhr | Wenn eine NE060 (Unter Kontrolle/Intervention) einläuft, wird der User eine Scope Benachrichtigung direkt in Scope erhalten. |
| |
Ausfuhr |
Ein digitales EUR.1 wird in einer WA-A unter Dokumente nach erfolgreicher Aktivierung angezeigt. |
| |
edec-Import | ZAZ Konto Stammdaten - neue Checkbox in der edec Import - per Default ist diese gesetzt. Falls sich die Daten ändern, kann man diese händisch rausnehmen und die Konten bearbeiten. Ein Ändern der Adresse wird diese Daten dann nicht mehr überschreiben. |
| |
edec-Import | die FreiOhne EVVs werden nun unmittelbar abgeholt und in Scope zur Verfügung gestellt. |
| |
Generell | In den Modulen kann nun nach weiteren Elementen via Suchfeld gesucht werden. Zbsp. Tarifnummer, Vordokument, Fahrgestellnummer usw. |
| |
Generell | SCI Import - die Restriktion von max. 9 Zusatzattributen wurde gelockert und auf 99 Attribute pro Nachricht erhöht. Zudem kann auch das Feld ZB-Code befüllt werden. |
| |
Durchfuhr | automatischer E-Mail-Versand: Es wird nun nicht nur das Draft sondern auch das tatsächliche T Dokument per E-Mail versendet (PTAD5) |
| |
Durchfuhr | Wenn eine ‚fremd‘ WA‑A mittels Liste Ausfuhrdeklarationen auswählen verknüpft wird, ändert sich der Status der Anfrage Daten Fremd WA Ausfuhr in aktiviert, sobald die WA-A aktiviert wurde. |
| |
Durchfuhr | Neu wird ein Scope Customs Event Typ scp.customs.GUARANTEE_USED mit dem Sicherheitsbetrag generiert |
| |
nationale Durchfuhr | In einer WA-nD, auf Warenpositionsebene gibt es nun eine Checkbox für die Restriktionspflicht. |
| |
Ausfuhr | Die Regel NP70168 VOC Menge in kg mit bis zu 3 Nachkommastellen wird nun direkt in Scope validiert. |
| |
Ausfuhr | Die Regel NS30115 wurde umgesetzt - geht im Rückwarenprozess um das Feld Begründungscode. |
| |
Ausfuhr | Im Statistikmodul auf Kopfebene können nun weitere Spalten wie Datum der Ausfuhr und Datum der Aktivierung hinzugefügt werden. |
| |
Ausfuhr | Wenn in der Codeliste fälschlicherweise ein Leerzeichen übergeben wird, ignoriert Scope dieses ab sofort. |
| |
Ausfuhr | Wenn aus seiner Sendung eine WA-A erstellt wird, werden die Anzahl Packstücke nun wieder korrekt übernommen. |
|
Type |
Area |
Description |
|
|
Accounts Receivable & Quotation |
Extended support for the Step calculation method in Scope, which was previously only available in tariffs.
|
|
|
Economic Date | The rules for determining a shipment’s economic date (e.g., using ETD for export shipments) were previously set globally across the entire organization. These settings are now defined on legal entity level to better support local requirements. You can also view the current configuration under Settings → Finance → Accounting. The dialog for setting a shipment’s economic date has been improved. It now clearly indicates whether the date is assigned automatically based on configuration or manually overridden - giving users better control and transparency. |
|
|
Shipment Overview | The Allocate Sales Persons action on the Shipment Overview has been enhanced. It can now be used to assign or correct sales persons for all shipments - regardless of their financial status - that were automatically assigned through allocations unless manually overridden. The action applies to all shipments matching the current filter criteria within an economic date range of up to three months. The previous limitation that restricted this function to shipments without an assigned sales person has been removed. |
|
|
KSeF Interface |
The KSeF e-invoice export has been enhanced to include key shipment reference numbers and basic shipment data in a structured format as Additional Properties (Dodatkowy Opis) on invoice header level.
Each respective data is included automatically when a value is present in the related shipment. |
|
|
Accounts Payable Import Templates |
The Accounts Payable Import Templates have been enhanced:
|
|
|
Partner | The handling of business identification numbers in Scope has been improved. It is now possible to specify the type of business identification number (e.g. chamber of commerce number) when entering a number. Additionally, new business identification number types SIREN and SIRET have been introduced for partners in France. |
|
|
Accounts Receivable & Payable | The invoice type displayed in the Type column on invoice overview screens has been enhanced to include the type of aggregated invoices, self-billing credit notes and payment deductions. In addition, the advanced filters now support filtering specifically for self-billing credit notes and payment deductions. |
|
|
The user ID displayed in Finance overviews and spreadsheet exports has been replaced with the user name for improved readability.
|
|
|
|
Partner API |
A new query option, branchPartnersOnly, has been added to the Partner API to retrieve Scope branch partners. The API is documented at: https://riege.github.io/scope-rest-webservices/ |
|
|
The layout selection dialog for spreadsheet exports has been enhanced to include an action link that opens the Layouts appliance, allowing direct management of layouts for the respective report. | |
|
|
Fmuta 6 Accounting Interface | The Fmuta 6 accounting interface export has been changed to ensure that the booking date of invoice charge lines is exported with the same date as used in Scope. |
|
|
Accounts Payable Import | Fixed an issue where the kind of document could not be canged for files imported as attachments of e-invoices. |