• The quantity used for calculating the actual value of a shipment may not be the same as the line quantity due to for instance additional contaminations of the shipment. The quantity corrections (both negative and positive) are based on the contract line quantity and percentages. Each quantity correction will be registered separately and each can have one or more price components linked to it. Examples may include moisture, oil, fat, debris etc.
• The shipment may contain multiple price defining components in various, previously unknown, ratios. In these cases the price is not calculated by starting with a base price, but the individual elements. Their quantities and prices define the value per element to be summed up to get the total value of the shipment. Each element will have a percentage and quantity correction level reference in order to calculate the absolute quantity of the element. Secondly each element will also have its individual pricing structure using the full capability of component pricing.

To complete the element pricing functionality we have already planned to release two more updates:

• Step pricing This is a valuation type that enables the setup of a table with multiple steps/ranges returning a price (correction) based on an attribute value.
• Integration with AQS The element pricing solution allows for manual updates of the percentages for the quantity corrections and price calculations. The logical next step is to integrate this with AQS test result values as both share the batch attributes as a common ground.

Enhancements in this release

Change to use of Outright/Fixed on CX contracts – Market price (Section 2.2.2)

There is a change on Outright/Fixed CX contracts. Technically the Market price fields have changed for the benefit of having an editable Premium. This has a few implications for the use of use Outright/Fixed CX contracts, regardless of whether you use the Premium field or not. This concerns the following:

• The editable Premium functionality itself.
• A conversion job that is always required.
• The fact that integrations may be impacted.

The new functionality is the Editable premium functionality: there is now an editable Premium on the CX contracts that have the Contract type “Outright”, both with or without a Period. This means the default valuation types “Outright” and “Fixed” in our standard setup.

To create the functionality, technical changes have been made to the Market price field. Old CX contracts will no longer seem to have a Market price. This issue can be repaired by running theconversion job “Commodity exchange contract market price update” to correct existing Outright/Fixed CX contracts. This will correct the Market prices. It is always required if Outright/Fixed CX contracts exist.

The functionality of Editable premium is quite simple: on Outright/Fixed contracts, a value can be entered on a +New contract and other versions of the edit screens. Just like all the other fields, the Premium will no longer be editable once the CX contract is settled.

The Data entity DycoTrade commodity exchange contracts has been updated to capture the fields. Integrations that use the data entity should be tested. Integrations that use a project customized data entity will likely require changes because Market price is a new field.

Enhancement credit note creation for contract lines with net amount (Section 2.2.3)

With the functionality of element pricing, the calculated price is presented as a net amount on the contract line. For the unit price, no unit price is set. In standard purchase orders and also for purchase contracts, it’s possible before posting the purchase invoice to either change the unit price or change the net amount. In the latter case, when changing the net amount, automatically the unit price will be removed. The invoice will be posted against the changed net amount. The changes made when posting the purchase invoice, however, will not be changed on the order/contract line. When crediting the invoiced order or contract line, for the full total quantity, the total invoiced net amount of the invoiced is used a credit amount. However, when crediting a partial quantity, also the full net amount is used on the created credit line. It such a case, based on the partial quantity, the user need to determine what the applicable credit amount needs to be. For the purchase and sales contracts an enhancement has been made that in case only a net amount is available when invoicing the contract line, which is always the case for element pricing, based on the partial quantity, the applicable credit amount for the quantity is calculated. This will be applicable for both purchase and sales contract lines. Similar to this computing functionality, also for other posting forms (e.g. prepayments, provisional, product receipt, picking list, packing slip etc.) enhancements have been done to calculate the correct net amount based on a partial quantity.

Enhancements Settlement contract functionality (Section 2.2.4)

In this release small enhancements of the settlement contract functionality have been released:

• Improved validation message regarding intercompany contract; user is now in an earlier stage informed.
• Updating the settlement price in the settlement contract requires a refresh before the calculation is updated; this refresh is not needed anymore to have the settlement price updated.

Enhancements Advanced quality functionality (Section 2.2.5)

In this release small enhancements of the settlement contract functionality have been released:

• Allow changing sequence on sample process cycle + apply logic on sample itself; changes in the sequence of the various process statuses are now possible and correctly presented on the sample according to this new sequence.
• Updated logic for 'Refresh specifications' option on Sample; the functionality executed with the ‘Refresh specifications’ button is being improved. The re-apply of the set-up of the item attributes is working consistently.

The DycoTrade Release notes for version 10.0.39 can be found here.