Release Notes 2025-Q4

Problems solved

---

General

Error resolved: Insufficient memory

Solved error regarding insufficient memory occurring when adjusting the calculation quantity for a sales order based approached from a blanket order.

Error resolved: email body text longer than 10 lines.

When adding email body texts with more than 10 lines, an error occurred on line 10 when sending the email.

My sent tasks information is incorrect.

The filter on the tile with my sent tasks was incorrect. As a result, only your own, open tasks that you created were sent.

---

Finance

Document Cost Relation table was not cleared when deleting calculations.

When deleting a cost calculation, the cost summary was not always deleted.

Displaying cost price/sales price per unit in item entries incorrectly.

Cost price and sales price per CU were not calculated correctly.

Error resolved: Item charge assignment in purchase invoice

Error message resolved occurring upon assignment of charges directly to purchase invoice lines.

---

Sales

Pallet requirement not transferred from shipping address to order

The pallet requirement field from the shipping address was not transferred to the sales order.

---

Supply Chain

Calculation of ERD (Estimated Receipt Date) incorrect

The calculation of the ERD was not always correct. An option was added to work with expected dates or actual dates. The expected receipt date on a line was not always updated correctly if the time to warehouse was unknown.

Volume in m³ is not calculated

Volume calculation was only working with cm³ unit of measure. Correction made to have volume calculated based on m³.

Error retrieving text lines for preferred manufacturer

When retrieving the standard purchase text with a link to the manufacturer, an error was likely to occur because the manufacturer table was being used instead of the SmartTrade Manufacturer table.

Entering ‘Transport time to destination’ adjusts the ETA entry point.

If the transport time field was filled in while ETA entry point field already contained a value, ETA entry point field was still adjusted.

Vendor texts not transferred to purchase order

Linked vendor texts were not transferred to a newly created purchase order in all situations.

Corrected prices per CU in item entries.

The price per CU was calculated incorrectly, the price was multiplied when it needed to have been divided.

Split purchases across multiple transport orders

When dividing a purchase order (line) across multiple transport orders, data was not retrieved correctly in all cases. Quantities from a previous order (booked quantity) were not considered. Furthermore, the status of a purchase related transport order was not updated after booking if the status table was not filled in.

The container count on the purchase overview was incorrect.

If no container was linked to a purchase order, the sum of all containers was displayed in the fact box, while it should have been 0.

Error resolved: missing container settings

Import EDI met foute EAN

Corrected: EDI import of correct EAN.

Import EDI zonder GTIN

Corrected: EDI import includes GTIN.

---

Traceability

Assembly item on purchase, no lot creation

When releasing a purchase order containing an assembly item, (if configured) a lot number was created for the purchase line. However, an assembly order is also created later with a lot number, resulting in duplicate entries.

New lot must be assigned the correct colour immediately.

When creating a new lot number, the default status for a new lot is now checked in the status table. Status including colour is then applied to the new record.

---

 

EDI

EAN number is empty when processing message to order

When processing an EDI message to a sales order, the correct GTIN code was not always transferred to the sales order.

EDI message does not contain external document number

When importing EDI messages, the external document number was not always retrieved due to inconsistencies in EDI message structure.

EDI does not import reference number

When importing some EDI order files, the external reference number was missing because it is sometimes located in a different location in the BGM line.

EDI with 14 characters cannot be entered as a GTIN per unit

It was not possible to enter a 14-character GTIN code, although this should be possible when, for example when printing an ITF14 barcode.

Error when posting a manually entered EDI order

When posting a manually entered EDI order whose dispatch advice should be sent as a DESADV message, an error occurred due to a missing line number.

---

Extended text

Item text lines not transferred from assembly item to component

When converting an assembly item to component lines, the corresponding extended text lines were not included to be transferred.

Recommended links