12-3-2021
Chartering
In the past, if we updated a cargo through an import, that would reset previously-set liner expenses. Now we preserve previously-set liner expenses.
Bug EN-40044
12-3-2021
Financials
Added a new P&L Calc Option called “Capitalize and Amortize Costs Prior to Performing Period” to the Monthly Accruals form which will allow capitalization and amortization of costs incurred as a result of fulfilling a contract prior to the performing period of the contract, and after the nomination date.
When selected, the costs incurred between the Nomination Date and the Start of the First Load port will be capitalized and then amortized over the performing period as defined by the Start of First Load to the end of Last Discharge on the voyage. The amortization will happen as a percentage of the performing period completed on the accrual date. Costs incurred during the performing period will not be affected by this option.
This option will be selected by default when CFGDefaultPnLCalcCapAmortContractFulfillmentCosts is enabled. It requires additional business rules to be added to account for the journals generated from this logic using the following prefixes: "CAP", "AM", "EXP" and "CM" for capitalized costs, amortized costs, costs expensed to the period and all other journals respectively.
When selected, the costs incurred between the Nomination Date and the Start of the First Load port will be capitalized and then amortized over the performing period as defined by the Start of First Load to the end of Last Discharge on the voyage. The amortization will happen as a percentage of the performing period completed on the accrual date. Costs incurred during the performing period will not be affected by this option.
This option will be selected by default when CFGDefaultPnLCalcCapAmortContractFulfillmentCosts is enabled. It requires additional business rules to be added to account for the journals generated from this logic using the following prefixes: "CAP", "AM", "EXP" and "CM" for capitalized costs, amortized costs, costs expensed to the period and all other journals respectively.
Story EN-39861
12-3-2021
Trading
Previously, index linked TCI contracts with applied market value concept and their related cargo contract had incorrect exposure days. This has been fixed.
Bug EN-39518
12-3-2021
System Performance
Filters on Receivables Summary views were inconsistent between removing and reapplying the filter, and loading from another view. They are now consistent and accurate.
Bug EN-38826
12-3-2021
Operations
Before, Laytime Claims with multiple cargoes having the same counterparty were missing fields, such as Cargo Group and Cargo LOB, in the Claim List. Now these fields are populated with the information from the first Itinerary line containing a cargo in the Laytime Calculation.
Bug EN-37592
12-2-2021
System Performance Desktop Only
Fixed an issue where upgrading the IMOS database schema to v346 or above would result in an error on pre-2016 versions of SQL Server.
Bug EN-40052
12-2-2021
Distances & Maps
Coordinates updated for ports Cherry Point and Port Angeles Pilot Station
Bug EN-39991
12-2-2021
Distances & Maps
Fixed routing for Nakpo and Satsumasendai
Bug EN-39972
12-2-2021
Operations
When CFGDuplicateActivitiesForCargoesAndBerths is enabled, berth-only voyage template port activities will now populate correctly in voyages when more than one berth-only activity is present in a voyage template.
Bug EN-39268
k8s-12-1-2021
Trade Hub
Enhanced date-time picker for Laycan Range. User can no longer select dates that are in the past, and are also provided the option to select any date up to 2 years from the current day.
Bug EN-39900
12-1-2021
Chartering
In Voyage Estimator, fixed an issue where percent-based overage and deadfreight were not properly accounted for in the breakeven freight calculation or reverse TCE calculation.
Bug EN-39675
12-1-2021
Analytics VIP Only
Previously, adding the Voyage Leg Summary table to the Voyage table in the Report Designer might have led to missing voyages in the report. The issue has been fixed.
Bug EN-38361
Powered by Automated release notes for Jira