1       Release Details

Release version: UF 39.0

Date of production synchronization server patch: 3rd December 2025 / 18:00 Geneva time

Latest user rights files updated: UF39.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12554

2       Supply

2.1        (US-14656, US-14564, US-14563, US-14561) Improvements linked to the E-validation on POs and INs

A set of improvements related to E-validation introduces additional restrictions on modifying signatures for Confirmed, Closed, or Canceled POs. If a PO uses E-validation, a warning message now clearly explains the steps the user must follow to edit a locked PO.

Additionally, the “Approved By” and “Value” fields have been removed from the IN signature table.

2.2        (US-12585, US-14295, US-14482, US-14483, US-14484, US-14485, US-14486, US-14487, US-14488, US-14495, US-14508, US-14557, US-15045, US-15046, US-15052) New module: Transport & Customs

A new Transportation & Customs Module is introduced with the following objectives:

The module is not active by default and can be enabled per instance via:
Administration → Configuration → Reconfigure.

2.3        (US-14291, US-15050) PO allocation report introduces a line status

Compared to the previous UF version, the PO Allocation Report includes minor changes to column names and introduces a new column displaying the status at the line level.

2.4        (US-14787, US-14547, US-14491) PO unit price deviation PO Vs Catalogue

With these improvements in the PO Catalogue tab, users can now see the positive or negative price deviation per unit in the PO compared to the supplier’s catalogue, when applicable. The deviation is shown at the line level, and the header displays the total percentage deviation between the PO subtotal and the theoretical catalogue subtotal (for catalogue lines only). Additionally, the readability of the PDF PO report has been improved, ensuring that comments are split correctly. The “Date sent” field has also been renamed to “PO Confirmed Date.”

2.5        (US-14672) Update the non-kept local code with a new code when it is merged with a UD code.

When a local code is merged with a UD code (via manual process), the “New code” field in the non-kept PMD is updated with the kept UD code. This action is available in Coordination and will sync down to the projects.

2.6        (US-14600) Improvement to Shipment dashboard default view

In Warehouse → Delivery → Shipment, the existing default “Not empty” filter is complemented with two additional default filters: “Draft” and “Ready to Ship.”

2.7        (US-14570) Order Category Filter added on IR

A new Order Category filter has been added to the Internal Request (IR) list view page. This aligns the IR view with the existing functionality available on PO, FO, and most warehouse documents. The filter is implemented as a drop-down selection, similar to the one used in the Incoming Shipment list view.

Additionally, a new Order Category column has been introduced in the IR list view to improve visibility and sorting options.

2.8        (US-14458) Supplier Catalogues – search bar item code

In Partners → Suppliers → Supplier Catalogue, a new filter by product has been added. This allows users to search for a product code across both active and inactive supplier catalogues.

2.9        (US-14296) Intersection flows – unblock the restrictions on local code

The ticket aligns the behaviour between Intersectional and Intermission flows by allowing the use of local codes in intersectional transactions. With this improvement, the restriction introduced in US-12176 is lifted, and local codes can now be used in Intersectional flows.

When a user tries to validate a PO/FO for an IS Partner containing local products, a non-blocking warning message will appear (one message for all product codes):

“Warning! Line(s) XXXX (line numbers & product codes) contain Local products (which may not synchronise). Please check if these can be replaced with a UniData code, or contact your help desk for further support.”

2.10     (US-14001) Products Likely to Expire Report – AMC Calculation Revision

Several enhancements have been added to Warehouse → Reporting → Expiry → Product Likely to Expire.

A new consumption option, RR-AMC, is now available. When selected, an automatic explanation appears:

“The RR-AMC (Average Monthly Consumption) lets you choose one or more internal source locations, and one or more destination locations so you can view consumption based on specific locations, ECUs or External Partners.”

This note appears only when RR-AMC is selected.

When using RR-AMC, selecting a Source Location becomes mandatory (highlighted in blue). RR-AMC calculations use only the selected source location, and a destination is not required.

The field previously named “Location” has been renamed to “Source Location.”

When the AMC – Average Monthly Consumption option is selected, the Source Location field is no longer displayed.

2.11     (US-13340) Update of Unreserved product Report

In Warehouse → Reporting → Unreserved Stock Report, the report will now show only the lines where the stock level is greater than zero. Previously, the report also displayed lines with negative stock, but these will no longer appear.

2.12     (US-13381, US-14946) Pre-Packing List Export – New Packing Type Selection and Validation

A new improvement allows users to export a pre-packing list that includes all active packing types in the instance. The exported Excel file now contains a drop-down list enabling users to select a packing type, and the dimensions of the selected pack are automatically filled into the corresponding columns.

To ensure data consistency, UniField now blocks the import when a single parcel range contains more than one packing type. In such cases, the following message is displayed:

“Parcel From 1 To 1 contains multiple pack types. Please assign only one pack type per parcel.”

The same message appears if a parcel range mixes assigned and non-assigned pack types.

2.13     (US-12542) RFQ – New Import and Export Buttons

Two new buttons have been added to the RFQ, similar to the functionality in validated POs. For RFQs in the “Sent” status, the existing “Import RFQ” button has been replaced with two buttons: “Import RFQ” on the left and “Export RFQ” on the right. Clicking “Export RFQ” allows users to export the modified RFQ file. Clicking “Import RFQ” enables users to import a file that updates the Price and Confirmed Delivery Date fields, while modifications to other columns are not allowed. The Header “Valid Till” field can also be updated via the import file.

2.14     (US-14978) Issue generating Stock Mission Report

Consolidated Mission Stock cannot be generated when the number of columns exceeds 256. This limitation is linked to the format of the generated XLS report.

A temporary fix has been introduced: the system now blocks the generation of the consolidated mission stock when the number of columns exceeds 255 and displays a clear error message advising the user to generate the MSR per individual instance.

A permanent solution will be delivered in the next release, as it requires changing the report format for both the Consolidated MSR and the standard MSR.

2.15     All Supply tickets integrated in UF39.0

Key	Summary	Detailed
US-14656	E-Validation: Incoming Shipment Order Of Signees with PDF	X
US-14564	E-Validation: Possible to modify Signees on Closed PO	X
US-14563	E-Validation: Correction to PO E-Signature Controls	X
US-14561	E-signature IN – “value” to be renamed “Total Quantity”	X
US-15052	Custom and transport partial reception of ITO: button clear all provokes Fix me	X
US-15046	(US-14557) Duplicated ITO/OTO references in PO linked documents	X
US-15045	(US-14486) Error while trying to create an ITO through IN VI auto-import	X
US-14557	To add a PO ref to Custom and Transport tab	X
US-14508	Custom and transport module: ITO to make custom regim a mandatory field	X
US-14495	Custom and transport module: Standardization of steps	X
US-14488	Custom and transport module: Zone Type; to have only international and Domestic	X
US-14487	Custom and transport module: transport mode to add MSF plane an rename “Air” to “Air Commercial”	X
US-14486	Custom and transport module: Auto VI: International order prefilled header and lines	X
US-14485	Custom and transport module: ITO/OTO Cargo Type to remove Service from Dropdown list	X
US-14484	Custom and transport module: ITO/OTO to rename “Single” shipment flow to “Direct”	X
US-14483	Custom and transport module: to include Transport fees Tab	X
US-14482	Custom and transport module to rename Custom fees	X
US-14295	To introduce info tags in Custom and transport module on Custom Field	X
US-12585	Transport Module – Functional specs 1	X
US-15050	(US-14291) PO Allocation reports display header state instead of line state at line level	X
US-14291	Allocation Report – To Add Line Status	X
US-14787	PO – comment not spleeting in
US-14547	Change Name of PO Date Sent Field	X
US-14491	Tab supplier catalogue	X
US-14696	BUG: Report donation of UF in French with no translation (terms still in English)
US-14672	to update non -kept local code with a new code in case if it is merged with UD code	X
US-14605	“New code” filled in some products in UF	X
US-14600	Improvement to Shipment dashboard default view	X
US-14570	Internal Request: Add Order Category Filter	X
US-14458	Supplier Catalogues – search bar item code	X
US-14296	Intersection flows – unblock the restrictions on local code	X
US-14001	Products Likely to Expire Report – AMC Calculation Revision	X
US-13381	Export Packing – Add the instance’s Pack Types	X
US-13340	Unexpected behaviour for unreserved stock report	X
US-12542	RFQ – new export / import to include header on excel file export	X
US-14916	Error msg not clear for importig ADs to FO
US-14865	Ignoring Concurency pop-up message on RfQ creates extra lines on PO	X
US-14593	Revision of Approved By in the Reception PDF	X
US-14573	Claims: to block manual correction of Claim Reference	X
US-14946	Block import of Packing List when a parcel sequence includes more than one parcel type
US-14945	Parcel numbers are not displayed correctly in SHIP
US-14639	Vertical Integration: Missing Sequence Error E-PPL update of error mesage
US-14978	OCBAF101 – Issue generating Stock Mission Report	X

3       Finance

3.1        (US-14182) Liquidity Balance report from HQ: to see all journals with registers in the selected period

We have developed an adjustment to the report criteria so that a journal is listed if a register has been created for the period or if the balances are not zero.

3.2        (US-14217) Use of periods 13, 14 and 15: to add a configuration with booking conditions

We have developed and implemented the requested enhancement, viewable in the “Companies” menu under the “Configuration” tab.

A new mandatory dropdown field named “Extra Accounting Behavior” has been added. This field becomes read-only once the instance is created, to prevent discrepancies and ensure consistency across instances.

The dropdown includes three predefined options, each corresponding to specific booking permissions for periods P13, P14, and P15:

As this field is read-only after instance creation, changes (e.g., switching from OCB to OCA behaviour) will not be possible via this configuration.

3.3        (US-14629) Functional total value of CV (supplier commitment voucher)

 We have developed and deployed the requested enhancement on the CV form and list views.

• • for OC reporting in EUR
  • for OCG reporting

This improvement aims to enhance visibility.

3.4        (US-14894) OCP – Prevent activation of Employee “not to be used”

We have implemented the requested control in the Human Resources tab.

For employees flagged as “Not to be used”, the system now prevents users with coordination rights from setting their status to “Active”. If such an action is attempted, a warning message is displayed:

“You cannot activate an employee flagged as not to be used.”

 (French: “Vous ne pouvez pas activer un employé marqué comme ne plus utiliser.”)

This measure was introduced to ensure data consistency and avoid unintended reactivation of inactive employee records.

3.5        (US-14849) Addition of track changes to the field “not to be used” in the employees form

We have added the track changes feature to the “Not to be used” field in the employee form.

This enhancement allows for better tracking and review of any updates made to this field, ensuring improved auditability and accountability in employee data management.

3.6        (US-14872) Exportable field Supplier invoice: additional information

We have implemented the requested export enhancements in the Supplier Invoice (SI) module.

If the invoice line is split across multiple analytic dimensions, all elements are displayed with a separator (no percentage shown), ensuring full visibility of the allocation.

These changes are export-only and have no impact on the user interface or manual data entry.

3.7        (US-14923) Adjustment of warning message for freezing closing balance

We have updated the warning message implemented under US-12267 to improve visibility and reduce user errors during period closing.

Previously, the red warning message was displayed above the “Cancel” and “Confirm” buttons, which made it easy for users to overlook the message and mistakenly freeze the balance of the current period while closing the previous one.

To address this, we have:

These changes aim to reduce the risk of accidental actions and improve the overall user experience during period closing.

3.8        All Finance tickets integrated in UF39.0

Key	Summary	Detailed
US-14182	Liquidity Balance report from HQ: to see all journals with registers in the selected period	X
US-14217	Use of periods 13, 14 and 15: to add a configuration with booking conditions	X
US-14629	Functional total value of CV (supplier commitment voucher)	X
US-14649	CC retargeted to other instance not synced with DEST configuration
US-14666	OCP_PH1_COR: Invoice from Supply flow wrongly created in the ISI journal
US-14697	Manual upgrade process : to remove the current warning message related to unbalanced entries
US-14849	To add the track changes to the field NOT TO BE USED in the employees form	X
US-14872	Exportable field Supplier invoice: to add additional informations	X
US-14894	OCP – prevent activation of Employee “not to be used”	X
US-14923	Please displace to the middle of the screen and make bigger the warning message from US-12267	X
US-14972	Financing contracts: python error to fix

4       Non- functional

4.1        (US-15077) Change to AiO to ensure new password is entered

This change means that at the password addition stage of AiO installation, there is no default password already there, meaning user must enter a new password for each field.

4.2        (US-14985) Better visibility for multi-instance servers

This development has 2 components: i)where a server contains multiple UniField databases, where the filter is set so that the URL displays a targeted database (by default), this instance will be displayed by default as the selected instance on the login page.  As only one of the instance on this server will act as the master for the synch server user connection, this “master” instance will be displayed on the login page also.

4.3        (US-14930, US-14905, US-14886) APIs developed for WaCA HQ

APIs have been developed based on WaCA’s request for integration with their planned HQ Accounting system. Tables have been made available to export Local employees, Partners and Journals.

4.4        (US-14936, US-14926) Update on data push linked to SharePoint locations.

These 2 tickets already implemented for OCA have now been released meaning that files are not blocked due to folder layers or zipper folders in destination locations for SharePoint exchanges.

4.5        (US-14107) Upgrade of version PostgreSQL: from 14.19 to 14.20

With this release, the version of PostgreSQL has been upgraded to 14.20.  All instances having a recent version of PSQL will automatically be upgraded. However those with v.9.6 will not be as they require manual intervention.

4.6        (US-14875) URL link for instance/database is case insensitive

This change means that UniField will recognise/accept instance name which is in URL no matter the case (upper case and lower case characters).

4.7        All Non-functional tickets integrated in UF39.0

Key	Summary	Detailed
US-15077	Change to AiO to ensure change of password	X
US-14985	Show database count for aggregation servers with database list filtered by URL	X
US-14936	Auto VI Config update (filepaths / method) for push to sharepoint	X
US-14930	WaCA HQ VI: VI export for Journals	X
US-14926	Back up files to be pushed to sharepoint folder location despite zipped file	X
US-14905	WaCA HQ VI: Test using VI export for Local Employees	X
US-14886	WaCA HQ VI: Test using VI export for Partners	X
US-14875	db field in URL to be case insensitive	X
US-14107	Upgrade of version PostgreSQL: from 14.19 to 14.20	X