Con tu ayuda, estamos mejorando Scope cada día. Estas son las últimas mejoras y funciones añadidas.
¿Busca el informe de lanzamiento de versión 23.8 de Scope?
Changelog
= Bug fix
= Improvement
= New feature
Type |
Area |
Description |
Air |
Added support for temperature controlled/pharma shipments |
|
Air Export |
Added a default screening method to the handling agent partner profile (applied to screening order if the handling agent is used as supplier) |
|
Order Tracking |
Introduced applicability filter and deviating EDI profile for milestone actions |
|
Order Tracking |
Introduced option to batch-delete (void) incomplete milestones |
|
Order Tracking |
Added Templates for Milestones in Order Tracking Templates for CargoIQ milestones |
|
EDI |
Added option to use Scope code as interface code for partners in outgoing interfaces |
|
Air Export |
Added view on RA/KC check events per shipment in the security section |
|
Air Export |
Added import agent related fields as optional placeholder for air export shipment prealert emails |
|
Air Export |
Added shipper related fields as optional placeholder for air screening order emails |
|
Air Export |
Added optional print parameters for number of customs orders (MRN) for the MRN manifest |
|
EDI |
Improved to resolve the emitter of an event for certain event types for incoming EDI events |
|
Order Tracking |
Minor UI improvements in shipment monitor and tracking plan visibility |
|
Master Data / Order Tracking |
Added validation on empty nearest UNLocode |
|
Air Export |
Scope now retrieves ETA CIMP DEP events for unknown flights |
|
Air Export |
Added more fields to the Flight Schedule Templates for direct / back 2 back shipments |
|
Tour |
Added the tour as quick search result |
|
Booking |
Added the export agents email for autocompletion on emails of import bookings |
|
Air Export |
Improved text of ‘shipment finished’ event to indicate the cause of the event (finish vs. AWB print) |
|
Air Export |
Fixed a bug that the handling codes in AWB Editor not correct shown after reset AWB |
|
Quotation / Booking |
Fixed a bug that notes from quotations were not shown on bookings when created from quotations |
|
Air Export |
Fixed a bug that the main address instead of delivery profile address was shown in the RAKC Query Report for a regulated agent |
|
Scope Connect |
Fixed a bug that shipments sometimes were not shown in the Shipment Monitor View |
|
Forwarding |
Fixed a bug that context related notes on countries were not shown in a shipment |
|
Order Tracking |
Fixed missing consideration of container delivery orders for applicability of delivery segment in tracking template |
|
Air Export |
Fixed a bug where slac-pieces > 1000 were cut on the AWB under certain circumstances |
|
Air Export |
Fixed a bug where the update of dimensions from shipment to AWB body was broken if a piece had a length > 10m |
|
Air Export |
Fixed missing validation of supplier as RegB for security status received from 3rd party at hub |
|
Transport Orders |
Fixed reopen tour without additional changes did not reopen the tour. |
|
Air Export |
Fixed search in mass send airline bookings when using ports |
|
Air Export |
Fixed embargo validation asynchronous validation of embargo status in shipment and AWB. |
|
Import |
Fixed documents from Import-prealerts of other Scope branches not available as attachments in emails. |
|
Order Tracking |
Fixed generation of alarms for manually deactivated milestones. |
|
Air Export |
Fixed copy of dimensions to clipboard for air export masters in some cases |
Type |
Area |
Description |
|
Transport Order / Road Carrier |
The road carrier profile has been enhanced to allow defining whether he complies with the minimum wage law and has a valid insurance (defined by a calendar date). Both fields can be (de-)activated by 2 new parameters. If activated, the selected road carrier will be validated in transport orders defined for a shipment - in case the selected road carrier does not comply with the minimum wage law or has no valid insurance, the transport order can not be stored and/or printed. |
||
Tracking / TransportOrder |
Allows the tracking module to use transport order related timestamps as planned time on milestones |
||
Ocean Manifest |
We introduce the AMS filing within Scope to our partner TradeTech. Shipment data is transmitted to them in Phase 1 of the implementation, for which the customer has to finalize the AMS filing within the platform of TradeTech |
||
Container Level Tracking |
Milestone Templates for Container Level Tracking have been introduced. This feature should not yet actively promoted because we will wait for the completion of the Epic. |
||
Booking Confirmation |
In the sea export booking confirmation dialog, the user can now select if to print the document only or if to also update the shipment with the changed fields (in case fields were changed in the dialog) by a new button Print & Update Shipment. |
||
Dakosy |
The Dakosy partner profile has been enhanced to allow defining the original sender of a Dakosy message as receiver of critical response messages. If this functionality is activated the responses are sent per email to the sender. |
||
Ocean Carrier EDI |
Bookings in state “pending” do now allow to send an update or to be cancelled. |
||
Ocean Carrier EDI |
For outgoing shipping instructions sent to carriers via a shipping portal (eg. Inttra), is is now possible to also transmit the entered shipper / consignee references of the relating shipment. To activate that feature, in the clearing center a specific new config parameter XXX-ShpCsgRef (where XXX is the organisation code) needs to be set (to value "true"). The parameter needs to be defined for each organisation individually. |
||
Portbase / MLI |
When transmitting cargo controller messages for ocean import, the status of the message (displayed in the shipment editor) now also shows changes when receiving response messages from portbase. |
||
Ordertracking |
For container related milestones outgoing event messages (xml) now also contain the container number of the relating container as reference. For email templates (used for order tracking) a new parameter is available to allow referencing the container number in case the email is generated for a container related milestone. |
||
Ordertracking |
Less validation information regarding replacement for generic Ocean events. |
||
Ocean Carrier EDI |
Ignore VGM confirmation from INTTRA because it’s the Carriers confirmation only which is crucial. |
||
Ocean Carrier EDI |
Enhanced Carrier Email Notification Settings allow to enable / disable notifications on message level and even completely. |
||
Ocean Carrier EDI |
Terminal Closing Date from Cargosmart Booking Confirmation now available. |
||
Acquisition of package data |
When the calculated volume differs from the initially entered volume a properly formatted information concerning the discrepancy of the volume is now displayed |
||
MX Carta Porte |
Add validation on missing UNSPSC code when sending Carta Porte |
||
Ordertracking |
Indicate repeatable group type on order tracking plan. |
||
Ocean Carrier EDI |
Allow SI to be sent for Canadian Export |
||
Ordertracking |
Container Monitor Rework: Make it more graphical / Use fix milestone columns |
|
|
Ordertracking |
Update ContainerHandlingUnit Descriptor when deleting OTPs |
||
Ordertracking |
Sea MilestoneTemplateTypes: Shorten Names and Improve Description |
||
Ocean Carrier EDI |
Rejections from Carriers on SI/Booking/VGM will create inbox notification for the shipment assigned clerk |
||
Prealert / EDI booking CC |
When converting incoming prealert (xmls) to rsixml2 the conversion is now fixed to not created two separate <refs/> elements in rsixml2 |
||
Sea Import / Printing |
When printing a sea import delivery note (on a single fcl shipment) for a newly defined container in a container transport order, the printed document is now directly visible in the documents tab of the editor. |
||
Transport Order |
Fixed a bug where the Economic Date of a newly created Transport Order had been set to today instead of the Eco Date of the related shipment. |
||
Dakosy |
When receiving critical Dakosy responses these replies can be sent to email addresses set up in the Dakosy partner profile of the relating branch. In case there are several profiles with the same Dakosy code it is now ensured that the correct profile is evaluated to access these email addresses. |
||
Prealerts |
Fixes too long strings in cargo description within the «DOTS» interface |
||
Port Community Systems |
Fixes too long user names in Portbase within the saving shipment attempt |
||
Transport Order |
Fixes sync between multiple addresses in partners and imaged UN/Locode |
||
Tracking Plan |
Increases the number of maximum characters for export of large XML tracking-plan-templates |
||
BHT |
Received BHT status messages with unknown status codes do not lead to failed Scope Jobs anymore. |
||
Ocean Carrier EDI |
Exporter Party and Goods Owner Party are not shown any longer within IFTMIN, if freight forwarder declares AMS self-filer SCAC to avoid ocean carrier take them potentially as real shipper and ultimate consignee parties |
||
Ordertracking |
Fixed storing the ordertracking plan descriptor for plans with many, many milestones (which might especially occur for plans with repeatable container milestones) |
||
Portbase |
Fixed automated transmission of cargo controller subscriptions in case the B/L number of a shipment is changed. Also renamed the action to transmit the subscription and enabled the transmission for superhouse FCL shipments (was missing there in the past). |
||
Ocean |
Fixed a bug where Freight amount / other charges disappeared after entry |
||
Ocean |
Wrong error message in German fixed if the POD is missing but showed POL |
Type |
Area |
Description |
Ausfuhr/NCTS |
Die alten Vorlagen aus der Ausfuhr 2.4 und NCTS 9.0 können per Migration in die neuen Versionen AES 3.0 und NCTS 9.1 übernommen werden. |
|
Einfuhr |
Die CusCon wird auch dann automatisch erstellt, wenn der IMP-Status 934 in einer anderen Niederlassung (derselben Organisation) eingeht als die vorzeitige Einfuhranmeldung angemeldet wurde. Wichtig ist, das die Checkbox entsprechend gesetzt wurde. |
|
Geschäfts-partner |
Es ist nun möglich je Geschäftspartner eine Mandatsreferenznummer für die Abrechnung und Einzug der Einfuhrabgaben aus einer EGZ zu erfassen. |
|
Intrastat |
Die Bezugsnummer wird jetzt mit in der Bestandsdatei angezeigt. |
|
ATLAS Statistik |
Die Kopf- und Positionsdatenstatisitk wurde um die Unterlagen N714, N740, N741, N703, N704 erweitert. Dies betrifft die folgenden Spalten:
|
|
Einfuhr |
Bisher war es nicht möglich den Abflughafen über den Positionsimport mit zu übergeben. Der Abflughafen kann nun entweder als Fixwert oder aus der Tabelle mit importiert werden. |
|
SumA |
ATLAS SumA: Transportdokument (Art) + Transportdokument (Referenz) im CSV Import einfügen Die Felder "Transportdokument (Art)" und "Transportdokument (Referenz)" stehen im CSV-Import zur Verfügung. |
|
Druck-einstellungen |
Es ist nun möglich die Kombination aus Versandbegleitdokument und Verpflichtungserklärung zusätzlich zu den bisherigen Einstellungen, an eine bestimmte E-Mail Adresse zu senden, damit nicht nur der jeweilige Benutzer diese erhält. Um die Einstellung vorzunehmen wird eine bestimmte Berechtigung benötigt. Sollten die Berechtigung nicht vohanden sein, kann sich der Benutzer zur Administration an das Riege Service-Team wenden. |
|
SCI Interface |
Der Zoll erlaubt bis zu 8 Stellen in der Packstück Nummer unter AES. Bisher konnte dies nicht über SCI importiert werden. Dies wurde nun behoben, sodass es möglich ist 8 Stellen zu übermitteln. |
|
Intrastat |
Ein Fehler hat die automatische Datenübernahme aus einer Einfuhr in die Intrastat verhindert, wenn in der CURREL keine Überlassung vom Zoll übermittelt wurde, sondern erst mit der CUsTax. Dies wurde jetzt behoben. |
Type |
Area |
Description |
DMS |
When creating DMS Import or Export declaration from a Shipment, Scope does now check whether a different Import or Exporter is defined on the Consignee/Shipper of the Shipment. |
|
DMS/NCTS |
When creating an NCTS declaration from DMS Export declaration, the declaration Symbol was incorrectly defaulted with T2. This is fixed now. |
|
DMS |
DMS procedures can now be searched via an article-code or commodity/HS-code using the general search field in DMS Appliance |
|
DMS |
DMS does now produce the Confirmation of Exit form, once the IE599 message arrives on a DMS Export declaration |
Type |
Area |
Description |
Accounts Payables |
Remarks entered on the compensation estimates dialog are now copied to the related charge line and compensation estimate, if an estimate is created |
|
Accounts Receivables |
A configuration option and a permission have been introduced to allow a manual override of the economic date on outgoing invoices |
|
Shipment Editor |
The action “Calculate jobcosting” on the jobcosting tab of a shipment editor is not disabled and blocked due to credit limit, prepayment or cash on delivery shipment blocks anymore |
|
Activity Types |
It is now possible to use multi-selection for deleting entries on the activity type overview to cleanup activity types |
|
Exchange Rates |
Scope now offers the National Bank of Poland (table A) as a source for the automatic import of exchange rates for legal entities with currency PLN. |
|
Exchange Rates |
A special action has been added to the invoice editor in Poland to select and insert an official exchange rate including the table number of the Polish National Bank into the invoice remarks and apply the exchange rate on matching charge lines |
|
Reporting |
The charge type report contains a new column “Cost Center” when grouped by order |
|
Web Services |
A version 3 of the partner web service has been released with the following changes:
|
|
Payment Import |
Scope is now able to import open balances of invoices created by other billing systems via the payment import. As a result the open balance amount of a debtor contains the open balances of invoices known in Scope plus the open balances of invoices not known in Scope. |
|
Quotations |
The quotation validator now validates the incoterm in relation to the conveyance type and shows a warning if an incoterm should not be used with the current conveyance type |
|
Web Services |
The order web service now offers the option to query shipments by their USI identifier |
|
Simple Shipments |
The logic for the action “Calculate jobcosting” has been improved to assign a customs order either to the import or export customs order type |
|
WebCargo Rate Import |
A new configuration option has been added to the products tab on the airline partner profile to create airline buying products automatically during WebCargo or e-Rate imports |
|
Quotations |
The action ‘New from Quotation’ to create new house shipments in the air import master shipment editor has been switched to the new quotation module |
|
Accounts Payables |
Set charge text for manually created charge lines on an incoming invoice |
|
Quotations |
When creating a copy of a quotation the language of the copy will be initialized with the language of the original quotation if the layout is also copied otherwise with the language of the prospect |
|
Shipment Editor |
The taxes set on line level on outgoing invoices have been fixed when using the “Copy invoice to outgoing invoice” context action on the invoices tab of a shipment editor |
|
Payments |
In Mexico a validation error is shown if the payment reference is longer than 100 characters |
|
Quotations |
The quotation validator caches are now properly invalidated after editing a partner |
|
Quotations / Shipments |
When creating a shipment from a quotation, transport orders are now also created when the departure/destination ZIP code is entered on the quotation |
|
Shipment Overview |
The house cost center on the shipment overview Consol (Excel) report has been fixed |
|
Tariffs |
Prevent the validity of imported tariffs from being edited in the tariff editor. This can be done via the context action “Change validity” in the rates import editor for the whole file |
|
Tariffs |
When looking up a tariff the score for a specific UN/Locode match is now higher ranked than the score of a match of the city code of an UN/Locode |