12-5-2024
Chartering VIP Only
In Voyage Estimator, fixed issue where Head Fixture CVEs would not be reflected in the P&L.
Bug EN-61987
12-5-2024
Veslink Voyage Reporting VIP & IMOS
Fixed an issue preventing Report Designer from properly getting Alias port data.
Bug EN-61904
12-5-2024
Chartering
The issue where Time Charter Broker Commission was generated for lumpsum offhire occurring outside of the broker commission period in the contract has been fixed.
Bug EN-61825
12-4-2024
Operations VIP & IMOS
An issue related to off-hire reverse bunker quantities in reporting has been resolved.
Bug EN-62030
12-3-2024-r2
Operations VIP & IMOS
With CFGSelectLinkedPortCallInOpsInvoiceDetails enabled, the port selection menu could display incorrect port options if there are multiple cargoes with different loading and discharge ports. This has been fixed.
Bug EN-61816
12-3-2024
Trading IMOS Only
With this release, preliminary Invoice Total amounts in Base and Currency can be selected as columns in the Create Trade Settlement Invoices List.
Story EN-61021
12-3-2024
Operations VIP & IMOS
The Bunker Requirement Import and Update XML now supports Pre-Test Viscosity, Post-Test Viscosity, and Bio and Fossil Fuel Factors.
Story EN-60839
12-3-2024
Veslink Voyage Reporting
The System Config page now contains a new setting in the Forms Section (veslink.com/#operations/veslinkConfig/).
"Within SOFs, allows selection of cargo type All. This applies a given activity to all cargoes that exist on that leg". To use this setting, turn it on, then reset master data. If using offline forms, you must download new forms; for Onboard, you must run bulk replication. No action is required for API submission.
With this setting enabled, offline/Onboard SOF forms will now default to cargo type "All" instead of the usual "Select..." dropdown option. For voyage legs with multiple cargoes, an SOF submitted against that leg with "All" selected in the Cargoes column will generate the relevant cargo activity for all cargoes in that voyage leg. If desired, leg cargoes can be manually excluded by creating a separate cargo activity of the same type and manually selecting the desired cargo.
For API submission, if this setting is turned on, cargo activities with no cargoName will apply to all leg cargoes. Individual cargoes can be manually excluded for a given activity in the same manner as described above.
Story EN-56420
12-2-2024
Data Center Settings VIP Only
Resolves an issue with the Class Societies module permissions. If you encounter an access issue with Class Societies, please work with your security admin to verify you have the correct permissions for the module.
Bug EN-62620
12-2-2024
Chartering VIP & IMOS
Address Book information output in the cargoSaleExport and tcExport XML messages now includes the vendorCrossRef field.
Story EN-62318
12-2-2024
EU ETS
Previously, if a port with non-zero emissions was changed to a passing port, which don't have emissions, that port would display zero emissions in the Voyage Manager but still showed the previous emissions in Report Designer. This is now fixed.
Bug EN-61931
12-2-2024
Operations
In an AR final statement, if the paid line item is AP, the sign was wrong. This has been fixed.
Bug EN-61817
12-2-2024
Journals IMOS Only
Previously, when using multiple company codes, period validation could be evaluated incorrectly during Journal Entry save. This has been fixed.
Bug EN-61726
12-2-2024
Invoicing & Payments
Some tax items were mistakenly counted toward cargo total %. This has been fixed.
Bug EN-61575
12-2-2024
Trading
Previously, CO2 trading exposure could have been incorrect in the scheduled trading snapshot. This has been fixed.
Bug EN-61427
12-2-2024
Berth Scheduling VIP & IMOS
When splitting or inserting a cargo on a voyage, the default berth activity rules will now apply.
Story EN-60714