1       Release Details

Release version: UF 41.0

Date of production synchronization server patch: 17^th June 2026 / 18:00 Geneva time

Latest user rights files updated: UF41.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=12571

2       Supply

2.1        (US-14532) Email notifications for the e-signature workflow.

UniField 41.0 introduces email notifications for the e-signature workflow. With this new functionality, if the instance is configured to be able to send emails it means that when a document requires electronic validation, the designated signee now receives an automatic email alert prompting them to complete their signature in UniField. Notifications follow the cascade signature logic — each signee is notified in turn once the previous signature is collected. Notifications include the document type, reference, and instructions to access the Signature Follow-up screen. A daily consolidated reminder is also sent for any pending signatures with an additional alert when a signature is approaching expiry.

The feature is configurable in Administration >Email> Email Notification for Signatures Configuration per document type and is inactive by default. It applies across all e-validation-enabled document types in both supply and finance modules, including Purchase Orders, Incoming Shipments, Delivery Orders, Supplier Invoices, Cash Registers, Bank Registers, and Physical Inventories.

Email logs are accessible under Tools > Email Logs > Signature Email Logs for traceability.

2.2        (US-15689) PO loan return incorrect RDD at line level

Previously when a loan return was created, the requested delivery date at line level was calculated using days instead of months for the loan duration, while the Delivery tab showed the correct date. This mismatch has been corrected — the RDD at line level now aligns with the loan duration in months, consistent with the Delivery tab.

2.3        (US-15016) Parcel management: removal of strict sequence constraints

Previously, UniField enforced strict parcel sequencing rules: sequences had to start at 1 and be continuous with no gaps. Any deviation — such as a shipment starting at parcel 2, or sending only selected parcels from a larger range — would cause the system to block with an integrity error. This made it difficult to handle real operational scenarios where only specific parcels need to be dispatched or re-dispatched.
As of UF41.0, the strict sequencing rules have been removed: parcel sequences no longer need to start at 1, and gaps between parcel numbers are now accepted. Pack ranges remain available for user convenience, and when a partial number of parcels is processed without manual selection, the system now defaults to selecting from the beginning of the sequence in ascending order.

2.4        (US-15467) Partner/Customer field locked in Pick-Pack-Ship process

The Partner/Customer field in the Pick-Pack-Ship process was previously editable, allowing users to change the destination and risk data inconsistencies. As of UF41.0, the field is read-only — if the destination needs to change, the document must be cancelled and a new FO flow created.

2.5        (US-11652) ECU destination propagated to Pick-Pack-Ship and related documents

When an OUT with reason type “Deliver to Unit” is converted to a Pick-Pack-Ship, the External Consumption Unit (ECU) is now propagated to the PPS header and displayed as the destination location, replacing the previously misleading internal partner reference. The ECU information is also reflected in the Deliveries and IN & OUT reports, as well as in the picking ticket, packing list (PDF/XLS), and freight manifest — giving full visibility of the actual delivery destination throughout the process.

2.6        (US-13201) External Partner -Country field mandatory for external partners

The Country field in the postal address of external partner cards is now mandatory. The behaviour differs depending on context: for new partners, country must be filled before saving; for existing partners in edit mode, the field is enforced only for the address currently visible on screen — other addresses will be validated individually when opened.

Local Market is excluded from this requirement, and country data is synchronised downstream only (not upstream).

This change originally came from a request relating to SDE (single data entry project) in order to facilitate mapping of MSF entities + countries.

2.7        (US-15619) New “MSF Entity” attribute on external partner card

A new “MSF Entity” checkbox has been added to the external partner card, positioned between “Partner status” and “Active.” This attribute allows users to flag whether an external partner is in fact an MSF entity, and when ticked, a mandatory dropdown appears to select the corresponding MSF section (OCA, OCB, OCG, OCP, OCBA, UBUNTU, WACA). The field is available at HQ, coordination, and project level, applies to external partners only, and is excluded for partners of type EXXX (OCB specific partners). All changes to the checkbox and dropdown are captured in Track Changes. This improvement is a prerequisite for the SDE project.

2.8        (US-15633) Export PO Follow-up: inactive partners now selectable

Previously, when generating the Export PO Follow-up report, users could not select inactive or deactivated partners through the Partner/Supplier lookup filter, making it impossible to report on historical POs linked to partners who had since been deactivated. As of UF41.0, the supplier lookup in the Export PO Follow-up report now allows selection of active, phase-out, and inactive partners, and the generated report includes POs linked to all partner statuses.

2.9        (US-15448) Manual correction of the expected receipt date in the header updates the lines, but not the header field

When manually correcting the Expected Receipt Date at the incoming shipment header level, the header field now correctly reflects the new date — previously it remained stuck on the old value.

2.10     (US-14676) UniData automatic product merge at HQ level

When a product code is merged in UniData, UniField now automatically triggers the same merge at HQ level after each UD pull, replacing the non-kept code with the kept product across UniField and synchronising the result downstream — previously this had to be done manually. The automatic merge applies the same conditions as manual merging: the six product attributes (Type, Subtype, Expiry Date Mandatory, Batch Number Mandatory, Main Type, and Default Unit of Measure) must match. Merges between LOG and SRV product types are permitted; merges involving MED products remain blocked. If any of these conditions are not met, the merge is skipped and logged as an error, which can be reviewed and retried via the new menu Tools > UniData > Products Auto Merge;

Successful merges (both manual and automatic) are visible in the existing Merged UD Products Report (Warehouse > Reporting).

2.11     (US-15197) Merge of multiple local codes into the same UniData code

Previously, UniField blocked merging more than one local code into the same UniData code, which prevented database cleaning when duplicate local codes had been created independently over time. As of UF41.0, there is no longer any limit on the number of local codes that can be merged into a single UD code. The standard merging conditions still apply: products must share the same Batch Number and Expiry Date rules and product type to merge without restriction; if products belong to different families but have matching BN/EXP rules, the merge is allowed with a warning message; if BN/EXP rules or product types differ, the merge remains blocked. All merges are captured in Track Changes and synchronised to projects.

2.12     (US-15613) Re-activation of Non-Standard Local code is unblocked

Following the release of UF40.0 the possibility to re-activate NSL code in Valid status was limited only to Administarator UR. With the release of UF41.0 UR Sup_Product_Manager has a right to re-activate NSL Code at coordination level

2.13     (US-15129) MSR and Consolidated MSR export format changed from XLS to XLSX

The Mission Stock Report (MSR) and Consolidated MSR are now generated in XLSX format instead of XLS, resolving the column limit issue (256 columns) that previously caused generation errors on large reports; the CSV export option has also been removed, and report headers are now frozen for easier scrolling.

2.14     (US-14299) State column hidden in OST “Need Sourcing” filter view

In the OST, the State column is now automatically hidden when the “Need Sourcing” filter is active — since all lines in that view are by definition in a validated state. The state column remains visible under all other filter combinations (Sourced, Need Sourcing + Sourced, or no filter)

2.15     (US-13048) Add Items / Remove Items buttons in Kit Composition List

Kit assembly in the field is rarely a perfectly controlled process — components may need to be swapped out, quantities adjusted, or items added based on what is physically available in the warehouse. Previously, UniField offered no structured way to handle these adjustments within an active KCL, forcing users to work around the system. As of UF41.0, two new action buttons — “Add Items” and “Remove Items” — are available directly on the KCL screen for any KCL in Draft or Completed status. “Add Items” lets users select any item (not restricted to TKC content) from a chosen Source Location; “Remove Items” lets users select existing KCL lines and redirect the stock to a Destination Location. Both flows include an expiry date modification step, in line with the existing Substitute Items process.

Beyond the screen-level interaction, every Add or Remove action automatically generates and processes an internal transfer document (INT/KITXXXXX, reason type 15 – Kit), ensuring that warehouse stock levels are accurately updated and the movements are fully traceable. This removes the need for manual workarounds or off-system tracking, gives warehouse teams a clear record of kit adjustments, and keeps the KCL aligned with physical reality throughout the kitting process.

2.16     All Supply tickets integrated in UF41.0

Key			Summary	Detailed
US-15839	(US-12983) Products deactivated by Product Mass Update can have their UF Status changed
US-15835	(US-11652) Exporting the XLS Freight Manifest report on a Ship created from a FO creates an error
US-15826	(US-15619) MSF entity should be inactive for External partner Local market
US-15823	(US-15619) “MSF Entity” data is not properly synced on Partners
US-15822	(US-13201) Country in Local Market addresses is mandatory
US-15816	Processing INs with “saved as draft” data to Ship doesn’t remove this data on the backorder popup
US-15759	SDE: Partial Quantities to process splits UniField OUT/PICK lines
US-15702	Picking Ticket import: Correct message for inexistant line number
US-14532	E-validation: to introduce e-mail notification for the user to sign a document	X
US-15640	BUG: Inconsistency between stock moves and stock card – UF showing diff stock balance
US-15689	PO loan return on a line level pulls incorrect dates	X
US-15016	Pack ID: UniField Parcel Management – Usability vs Reality and parcel_from / parcel_to logic	X
US-15632	Exclude Canceled (UF status Phase-Out) Local Codes from Validation When Selecting External Partner
US-15622	OUT/PICK Track Changes (SDE)
US-15467	Disable Partner/Customer field across the PICK-PACK-SHIP process flow	X
US-15607	(US-15245) Non-admin users can not modify the Partner on a Draft PO
US-15639	“Details” are not Pulled from the source documents for FM.
US-15450	Product Mass Update – Incorrect User Assigned
US-11652	To updated PPS with ECU if OUT converted to Pick	X
US-13201	Partners Zones configuration	X
US-15619	SDE: External Partners New Attribute MSF vs Non-MSF Partners	X
US-15633	Export PO follow-up: Allow report generation on Inactive partners	X
US-15448	Manual correction of the expected receipt date in the header updates the lines, but not the header field.	X
US-14984	Upgrade of SDE to include pack ID
US-15313	C&T ITO – Lines of IN : Having a “state” column
US-14587	SDE: IN Incoming Shipments: APIs etc. (Testing/Dev RB)
US-14676	UniData automatic merge in UniField	X
US-15197	Merge of multiple local codes with same UD code	X
US-13970	IR/FO/PO follow-up to change file name structure
US-12983	Local Product Status change & Deactivation Sync behavior	X
US-15613	Modification to User Rights allowing re-activation of NSL product	X
US-15129	Consolidated MSR/MSR to change the formate of the report from XLS to XLSX	X
US-14299	Remove State Column from OST	X
US-13048	Kit Management: Add/Remove KCL components	X

3       Finance

3.1        (US-14960) Direct Invoice: “Posting Date” and “Register Posting date for Direct Invoice” in Temp status: to make them “editable” within the same month of the register

For Direct Invoices, the fields “Posting Date” and “Register Posting Date for Direct Invoice” in Temp status were made editable when they were within the same month as the register.

Posting Date and Register Posting Date fields

Restrictions

3.2        (US-15072) To add in a tab of the supplier invoice (SI), the field name “Details” from the purchase order (PO)

A new field called “PO Details” was created under the field “Additional Info” in the “Other Info” tab.
This field was populated with the data from the “Details” field of the Purchase Order (PO). The field was successfully created and the data was correctly transferred from the PO. It was added to the list of exportable fields for Supplier Invoices (SI). It was made editable in the following states: Closed, Draft, Open, and Paid.

3.3        (US-15447) Only for the Dec registers: to prevent the closing of a cash register if amounts in “Unrecorded Advances” and ” Unrecorded expenses” not equal to Zero

The previous behavior allowed the closing of a cash register even when amounts in “Unrecorded Advances” and “Unrecorded Expenses” were not equal to zero.
 This could lead to a register and its corresponding period being closed while some entries had not yet been recorded.

This behavior has been corrected.

Implemented Change

Business Rationale

3.4        (US-15481) Finance integrity report: double AJI correction at coo and project

An issue was identified where AJI corrections (REV and COR entries) performed simultaneously at Coordo (COO) and Project levels led to duplicate REV and COR entries, which were not detected by the “Entries Data Integrity” report.

Issue Description

When a Journal Entry (JE) was approved on the Project (e.g., January 2026 with lines 30100 / 66006) and synchronized to Coordo, and the mission period was closed,

If a Cost Center change was then performed simultaneously at both Project and Coordo levels, REV/COR entries were generated and synchronized,

This resulted in duplicate REV and COR entries, which were not flagged by the “Entries Data Integrity” report.

The issue only became visible under specific conditions:

Implemented Change

Controls were introduced to prevent or detect duplicate REV and COR entries generated during simultaneous AJI corrections at Coordo and Project levels.

The Entries Data Integrity report was improved to ensure such inconsistencies are properly identified.

3.5        (US-15498) OCA: Prevent draft instance to block revaluation process

A fix was implemented to ensure that draft instances no longer blocked revaluation processes.

Revaluation was made possible at Coordo level even when instances were in draft status.

Draft instances were excluded from all revaluation checks, preventing them from blocking the process.

This update applied to the following revaluation processes:

3.6        (US-15536) Do not allow to import new rates on closed currency tables

The system was updated to block the import of rates when the currency table was closed.

This prevented newly imported rates from being synchronized to lower levels.

3.7        (US-15609) Combined journal report – export file naming

The file naming convention for the Combined Journal Report export was improved.

Implemented Change

•  “Combined Journals Report XLS”
   “PropInstance_Combined Journals Report XLS_YYYYMMDD”

Example:

3.8        (US-15744) Ubuntu: Vertical Integration file Upfile to D365

Support was provided for the creation of the Ubuntu Vertical Integration file UpfileToD365.

The development was carried out based on the OCA version, incorporating the changes and computations defined in the technical specifications.

Sample files were used to validate the implementation.

3.9        All Finance tickets integrated in U41.0

Key	Summary	Detailed
US-12392	OCBHT127: not runs with model res.currency.rate to solve
US-13993	Fix on intermission flow: use case with commitment vouchers validation and cancellation in INcoming (ENG)
US-14960	Direct Invoice: “Posting Date” and “Register Posting date for Direct Invoice” in Temp status : to make them “editable” within the same month of the register	X
US-15072	To add in a tab of the supplier invoice (SI), the field name “Details” from the purchase order (PO)	X
US-15410	Taxes: to add more decimal digits in the field Amount (8 instead of 4)
US-15432	In the currency parameters: To add a code fix to change the default value + a patch script to change the already created currencies with rounding = 0.
US-15433	No previous fiscal year in WaCA instances
US-15447	Only for the Dec registers: to prevent the closing of a cash register if amounts in “Unrecorded Advances” and ” Unrecorded expenses” not equal to Zero	X
US-15481	Finance integrity report: double AJI correction at coo and project	X
US-15498	OCA: Prevent draft instance to block revaluation process	X
US-15536	Do not allow to import new rates on closed currency table	X
US-15567	DF OCA_HQ : Please synch deletion of the currency rate related to the ticket US-15537
US-15609	Combined journal report – export file naming	X
US-15744	Ubuntu: Vertical Integration file UpfileToD365	X
US-15834	Ubuntu: config file to improve for currency activation and FP analytic account synchonization

4       Non- functional

4.1        (US-15830) Upgraded version to PostgreSQL 14.23

As part of regular upgrades, the PostgreSQL version of UniField has been upgraded to 14.23. All instances which are already on a version 14 will have been upgraded automatically. For instances on older versions a manual intervention is necessary. Details on how to do this are in US-14042

4.2        (US-15761, US-15677, US-15645, US-15499, US-15419, US-15186) SDE APIs

Several APIs have been developed for the SDE (Single Data Entry / SmartScan) project in UniField. These are based on Supply objects Incoming Shipments, Delivery Orders and Picking Tickets. See ticket specifications for more details.

4.3        (US-15729) Traceback from URL hidden

Security measure flagged by OCP / Hack4Value, now if UF instance URL is modified to add a suffix (for example https://176.176.79.99/blablabla ) then no technical information is disclosed.

4.4        (US-14113) New functionality for forgotten password / user login

As soon as an instance receives the UF41 patch, the login screen will change to include 2 additional buttons: “Forgot login?” And “Forgot password?”

When the functionality/button “Forgot login”, is used/clicked on, UniField requests further information from user: email address and (if multiple instances are on the server) the name of the database.

If information submitted matches with a user in the database/instance, UniField will try to send an email to the given email address with the details of the user login associated.

When the functionality/button “Forgot Password”, is used/clicked on, UniField requests further information from user: User login, Email address and (if multiple instances are on the server) selection from the dropdown list of the name of the Database.

Once submitted UniField will check that user profile corresponds to these details and if confirmed will send an email with a Temporary code to given email address.

This Temporary code can then be entered into UniField, in the same “Password management” screen by clicking on the “Add temporary code” button.

In the following screen the Temporary code can be added and the values should be filled by user for their New password and Confirmation of new password. When the “Change password” button is clicked on the user’s password will have been reset.

This resetting of a user password via Temporary code will be logged in the Track Changes for the user profile.

N.B.:In order for UniField to be able to dispatch emails, each UniField instance must have the necessary configuration completed. The menu where the configuration can by made by IT responsible is via menus: Administration > Configuration > Email > Email configuration and requires information specific to that instance / infrastructure.

Even if this configuration had already been completed, this may need to be checked / reset once UF41 has been released.

Users may need to check in their Quarantine/inbox for any emails generated by UniField for this functionality, depending on the sending email address configured by their IT for their instance.

This functionality is not intended to be used by synched users, nor by users who share the same email address with other users in that instance.

4.5        All Non-functional tickets integrated in UF41.0

Key	Summary	Detailed
US-15837	(US-15607) UR: e-validation conflict with reception in and processing PPS
US-15830	PostgreSQL 14.23	X
US-15811	Password reset not to be allowed if multiple users share same email
US-15761	SDE: API Improvements – Header and Lines Status	X
US-15729	Hack4Value report alert about Unifield vulnerability	X
US-15677	SDE: APIs Delivery Order / OUT	X
US-15645	SDE: APIs Picking Ticket	X
US-15613	(US-15452) Modification to User Rights allowing re-activation of NSL product
US-15560	revprox: add options to secure API calls with TLS (for HTTPS)
US-15499	SDE: APIs for synched flow (“project”) INs	X
US-15419	SDE: New format of APIs for SDE work	X
US-15359	Add Track Changes entry for User value “Synchronize”
US-15186	SDE: APIs for Auto VI IN process.	X
US-15074	Modification to PDF template of signature – clarification
US-14113	Users password recovery feature	X

1       Release Details

Release version: UF 40.1

Date of production synchronization server patch: 29^th April 2026 / 18:00 Geneva time

Latest user rights files updated: UF40.1 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=11719

2       Supply

2.1        (US-15694) Fix Order Calculation Import in Replenishment Rules

Issue preventing Order Calculation files from being imported in Replenishment Rules has been resolved. The problem was caused by inconsistencies between the updated export template and import validation checks. Users can now successfully import edited Order Calculation files without format errors.

2.2        All Supply tickets integrated in UF40.1

Key	Summary	Detailed
US-15694	Fix Order Calculation Import in Replenishment Rules	X

3       Finance

3.1        (US-15685) Cash/cheque registers – Register Responsible now copied to the newly created registers

We identified and fixed a bug occurring when creating the new April registers.

Normally, the Register Responsible is copied from the previous month’s registers to the newly created ones. After the fix, the responsible is now correctly copied for all register types (bank, cash, and cheque), ensuring consistent behavior across instances.

3.2        All Finance tickets integrated in UF40.1

Key	Summary	Detailed
US-15685	Cash/cheque registers – Register Responsible not copied to the newly created registers	X

4       Non- functional

4.1        All Non-functional tickets integrated in UF40.1

Key	Summary	Detailed

1       Release Details

Release version: UF 39.1

Date of production synchronization server patch: 11^th February 2026 / 18:00 Geneva time

Latest user rights files updated: UF39.1 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=12563

2       Supply

2.1        (US-15318) Custom and transport module: allowing to have several sub-steps for one step in the ITO/OTO

The system now allows the same step to be used more than once within an ITO/OTO. This makes it possible to record different sub-steps under one main step.

For example, Pre-arrival processing can be added several times with different labels such as Customs, MOH, or MO. Each entry is treated separately but remains linked to the same main step.

This change helps better reflect daily operations when several actions or authorities are involved under the same step.

In addition, ITO/OTO steps can be reused only when the combination of step + sub-step is unique. If the same combination is entered more than once, the system will display an error message and prevent duplication.

2.2        All Supply tickets integrated in UF39.1

Key	Summary	Detailed
US-15318	C&T ITO/OTO : allowing to have several sub-steps for one step in the ITO/OTO	X

3       Finance

3.1        (US-15312) Mass HQ entries validation: Dec + other period: REV is posted in Dec

There was a bug while validating the HQ entries in mass when we had 2 different periods. The periods of the correction were not the correct ones. This has now been fixed.

3.2        All Finance tickets integrated in UF39.1

Key	Summary	Detailed
US-15312	Mass HQ entries validation: Dec + other period: REV is posted in Dec	X

4       Non- functional

4.1        (US-15272) Ubuntu created as an OC on UniField structure

The new OC/OD “UBUNTU” has been created in the UniField structure meaning that we can meet any future request for a new HQ and other instances for this instance to be created and this will be recognised by the synch server.  

4.2        (US-15162) Issue with initial synch during instance create resolved

An issue meaning creation of new instances was halted at initial synch stage if the next_exec_date in the config file was in the past has now be resolved with this ticket.

4.3        All Non-functional tickets integrated in UF39.1

Key	Summary	Detailed
US-15272	Ubuntu: Create Ubuntu on Synch server	X
US-15162	Auto instance creation fails with “Already Syncing…”	X

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

Release Details

Release version: UF 38.1

Date of production synchronization server patch: 8^th October 2025 / 18:00 Geneva time

Latest user rights files updated: UF38.1 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=12551

1       Supply

1.1        (US-14860) Stock card showing incorrect entries on lines

Regression linked to ticket US-12325 released in release UF38 meaning that the balance of historical quantities and current stock quantity on a stock card were not displayed in the correct order. This has now been corrected.

1.2        (US-14880) Parcel comment not visible when added

Regression linked to ticket US-9592 which introduced Pack ID in release UF38 identified by OCA meant that when user added and saved a new parcel comment in a Shipment List, this comment was not visible either onscreen or in PDF. This has now been corrected.

1.3        (US-14882) Phase Out products sourced to ESC

This bug identified by OCB meant that it was possible to source products with status “Phase out” to an ESC type supplier by using the multiple source lines option in the Order Sourcing Tool and then choosing to Source default.

1.4        All Supply tickets integrated in UF38.1

Key	Summary	Detailed
US-14882	BUG: Phase-out codes being sourced to ESC	X
US-14880	parcel coment is not visible on a shipment	X
US-14860	Stock card – the first line is not the one with the stock balance	X

2       Finance

2.1        (US-14870) OCP: GL selector: Not reconciled/Open items at – “an application error has been reported”

Regression due to US-13945 in released in UF38 caused this bug affecting the output of the selection in the GL selector. This issue has now been fixed, and the selection output is working as expected.

2.2        (US-14864) OCBPL101 Import of entries error “charmap” in prod, but in sandbox works

Regression due to Python migration in previous release caused this bug that prevented the import of entries when special characters were present. This issue has now been resolved, and the import can be performed without any problems.

2.3        (US-14827) Automated Vertical integration import: additional fields due to change of SharePoint authentication protocol

Please see non-functional section for a fuller description of this.

2.4        All Finance tickets integrated in UF38.1

Key	Summary	Detailed
US-14870	OCP: GL selector: Not reconciled/Open items at – “an application error has been reported”	X
US-14864	OCBPL101 Import of entries error “charmap” in prod, but in sandbox works	X

3       Non- functional

3.1        (US-14776, US-14827) SharePoint/OneDrive authentication: protocol / additional fields

This was a major issue and is the reason for the intermediate release as was impacting OCs in multiple ways.

Due to a Microsoft/SharePoint decision to change the allowed authentication method, UniField could no longer connect to SharePoint as it previously did. This connection was essential for allowing certain back-ups of UniField instances to be sent to a SharePoint repository as well as for Vertical Integration imports where OCs had configured UniField to pull data for imports such as International Invoice Lines, Expats and HQ entries from SharePoint. With this ticket, new fields are introduced into Tools>Tools>Automated Imports screen so that if the Protocol “OneDrive” is selected additional fields appear and can be filled for the Tenant-id, App-id and Certificate. These are used by SharePoint to verify the connection with UniField.

The equivalent fields are also in Synchronization > Backup > Cloud Backup Config and where values are added for these at HQ for an instance, they are synched to that instance and facilitate the back-ups of that instance to be sent via Direct push to SharePoint protocol.

3.2        All Non-functional tickets integrated in UF38.1

Key	Summary	Detailed
US-14776	SharePoint authentication additional code	X
US-14827	Import DownPrices do not work – error message shown	X

1       Release Details

Release version: UF 38.0

Date of production synchronization server patch: 17^th September 2025 / 18:00 Geneva time

Latest user rights files updated: UF38.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=12546

2       Supply

2.1        (US-14594, US-14517, US-14269) MISC Nomenclature root is unblocked for the use in UniField for Local codes

The ticket focuses on unlocking the use of MISC roots for Local codes.

Please note that the MISC root is archived in UniData. However, due to specific operational flows, SPINCO platform members agreed to allow its use exclusively for Local codes.

If the MISC root is selected for a non-local product, a blocking message will be triggered.

Additionally, with US-14269, a new rule has been introduced: when an archived root is selected in PMD, a pop-up blocking message appears — “You cannot create a product with an archived Root Nomenclature.”

(Currently, this message is only displayed when the user clicks Save / Save+Edit.)

2.2        (US-14166, US-14304) Improvement on Local code creation and the use of Temporary status

With these improvements the use of the product creator Temporary is blocked.

Also some modifications are introduce in Local codes creation process.

When creating a new code at Coordination level the default product creator is set to “Local”;

The system improvements include the following: introducing an immediate blocking message if the entered code contains fewer than 11 characters, with the text: “The code must be between 11 and 18 characters. Please adjust and try again” (note: code creation is already limited to a maximum of 18 characters);

A non-blocking warning message appears at the moment of selecting nomenclature when the selected nomenclature does not correspond to the code (e.g., code CWATZAF0001 with nomenclature ADAPXXXXX), displaying: “Warning: you are about to create a product which does not correspond to the nomenclature, do you wish to proceed?”.

2.3        (US-13333) Merge 2 local codes

The ticket introduces a functionality allowing merging of 2 Local codes. With this release, two Local products can be merged at Coordination level, even if they are in stock or have open transactions. Once the merge action has been performed for the 2 Local products, the selected (non-kept) product will be de-activated in Coordination. After synch, this non-kept product will be de-activated in all Project instances, and any quantities in stock or open or closed transactions will be updated so that the active “kept” product will appear in its place. “New code” field  will be updated with the kept product code in the non-kept PMD.

If 2 Local codes have inconsistencies in Product type/Main type the blocking message will prevent merging of 2 Local codes.
User rights for merging products at Coordination level have been added to the group Sup_Product_Mgr_Coordo.

2.4        (US-13980) UniData UD: additional info about merged, not kept product

If 2 codes were merged at UniData level, in the “non-kept” production UniField, a new code value is pulled through the API. This value will appear in the PMD “New Code” field, and will wipe any pre-existing value in the field. Active track change makes it possible to track updates to the new code field. Please note that merge at UniData level does not indicate the product has been merged at UniField level. All merges in UniField must still be triggered manually.

2.5        (US-13189) HQ tools improvements on Export Stock and pipe Report.

The improvement focuses on enhancing the readability of the Stock and Pipeline report available in Tools at HQ level. When a code is present in stocks and pipelines across multiple instances, the information is consolidated into a single table, making it easier to analyze.

2.6        (US-13354) E-validation Signature Follow Up Cancelled Documents Display

Currently when the TO BE SIGNED filter is ticked documents that are in status cancelled still display for the user to sign.  This ticket changes Signature Follow-Up Screen to ensure that cancelled documents are not displayed under the “TO BE SIGNED” filter.

2.7        (US-12722) E-Validation : drafting signature

The improvement allows importing the ink version of the signature. For more details, please refer to the IT section of the current release.

2.8        (US-12985) Partners management has a new functionality.

The improvement introduces a new way of managing external partners. This tickets support cleaning of the partners at instance level. New De-Activate / Re-Activate Supplier buttons have been added on supplier records.

If open documents for the external partner exists, the partner is set to the status Phase-Out

Users can either manually re-check if the partner can be deactivated, or wait for the new automated daily task that will attempt to deactivate Phase Out partners.

Partners in Phase Out cannot be used for new supplier invoices or new draft POs, but existing validated processes can continue until closure.

Partner activation, deactivation, creation, and phase-out actions remain managed at instance level only.

If the supplier is in status Inactive or Phase Out, it is possible to reactivate them using the Re-Activate Supplier button (same behavior as the De/Reactivate product button).

Phase Out Principle (similar to code deactivation flow)

• When a partner moves from Active → Phase Out:
  • Financial documents:
    • If a supplier is in Phase Out status, new manual supplier invoices or new direct invoices cannot be created.
    • Other operations remain possible: registers, manual journal entries, refunds, reconciliations/unreconciliations.
    • Supplier invoices coming from Supply remain allowed.
  • Supply documents:
    • Processing of opened PO/FO/IN/OUT/PPS linked to a Phase Out partner is possible.
    • If PO is in Draft and the supplier is Phase Out → warning message:
      “The selected supplier is Phase Out. Select another supplier.”
    • Phase Out partners are automatically deactivated when all linked documents are closed.

Partner (Phase out) in different Configurations

1. When External partner is configured as Supplier / Manufacturer / Transporter
   • Draft PO with Phase Out supplier cannot proceed.
   • Draft PO can be cancelled/recreated with a new partner, or partner can be changed directly in the draft.
   • Validated PO and statuses after can continue until closed.
   • New filter introduced: Show Phase Out (alongside existing “Show Active” and “Show Inactive” filters).
   • Reports including partners will continue to display Phase Out and Inactive partners.
2. When External partner is configured as Customer
   • Draft FO for Loan can proceed if the partner is in Phase Out.
   • Draft PO for Loan Return can proceed until closure, even if the partner is Phase Out.
   • Donations and Programmatic Donations with validated FO/PO can continue until closure, even if the partner is Phase Out.
3. When External partner has Mixed Configuration (Supplier + Customer + Transporter + Manufacturer)
   • Validation will be applied per role, following the same rules described above.

2.9        (US-13069) a new feature to delete ESC supplier catalogues with validity dates older than 6 months

The task is available under Tools > Tools > Delete Old ESC Catalogues. It is deactivated by default and if active will run with a default interval of six months between executions.

The functionality will be extended with a new “Specific Partner” field, allowing users to delete ESC catalogues only from a selected supplier. This field is mandatory.

The deletion configuration is defined at instance level.

For visibility, a new sub-menu is introduced at instance level. The list will display:

• Source instance
• Date of deletion
• Number of catalogues deleted

Clicking on a record will show these details plus the Last Execution Message (including the catalogue names).

2.10     (US-14320, US-14475) Historical Consumption AMC/RR-AMC

Since AMC/RR-AMC is calculated based on past months and the current month (Max), the improvement is limiting the selection of months for the AMC/RR-AMC calculation to a maximum of the current month.

Additionally, when RR-AMC is selected, an explicit explanatory message will be displayed: “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”.

2.11     (US-13834) Physical Inventory: Prevent the creation of multiple PIs for the same stock location at the same time

Physical Inventory rules are designed to ensure only one active inventory process exists per location at a time: users cannot open multiple Full, Partial, or Stock Correction inventories simultaneously, nor mix these types for the same location. Multiple inventories of any type are only allowed if their status is Confirmed or Closed. If a user tries to generate a counting sheet for a new inventory while another is already open at the same location (in any status other than Draft, Confirmed, or Closed), a blocking pop-up will appear stating: “Only one Physical Inventory can be open per location at the same time. Please finalize or cancel Physical Inventory [xxx] before creating a new one for this location.”

2.12     (US-13424) A new status Partially processed for Auto-VI

A new state “Partially Processed” was introduced in  auto-VI to indicate cases where some lines were rejected but the import was not in an error state; in this state, the system correctly counted the number of rejected lines and displayed the corresponding error messages from those rejected lines.

2.13     (US-9592) New Pack ID can be used in system

To support introduction of a single pack ID, new information in regards to Single pack ID can be imported in UniField. After import of the e-PL via Vertical Integration the parcel IDs are displayed in the processing screen of the Incoming Shipment including the possibility to filter the content of the IN on specific parcel ids.

When processing the IN to SHIP the parcel ids are promoted to the PPL as it is done with the supplier packing list so that there is no need to re-label boxes and to use the parcel ids.

If the Pack ID was imported for the IN, the corresponding checkbox “P.ID” is ticked in the In Process pop-up window, and users can view the Pack IDs by hovering over the parcel number.

Packing list (PDF/XLS) will also contain information about Pack ID identification after the import.

2.14     (US-14707) Correction of comments in Arabic in PDF

To support deployment and use of UF in Arabic speaking countries PDF was corrected in order to support comments in Arabic language

2.15     (US-14159) Improvement on PO follow up for Direct purchase order (DPO)

When a DPO line is closed, the PO follow-up report will show the full quantity as received and the backorder at 0.

2.16     All Supply tickets integrated in UF38.0

Key	Summary	Detailed
US-14707	OCP_SY Data Fix ARABIC LANGUAGE	x
US-14594	MISC root: unblock the use in Unifield for Local codes	x
US-14507	sync UniData UF ELAESEQT0205	x
US-14475	RR-AMC: to add explanation when selected in Historical consumption	x
US-14426	Users Management: add email column and search box in list view	x
US-14371	Adjust message for warning and blocking messages to avoid scroling	x
US-14320	RR-AMC/ AMC: to block selection of future months in RR -AMC/ AMC	x
US-14304	Local code creation – temporary status	x
US-14269	Local product creation – played nomenclatures	x
US-14166	Local product creation	x
US-14159	PO follow-up for DPO	x
US-13980	UD: additional info about merged, not kept product	x
US-13834	Physical Inventory: Prevent the creation of multiple PI for the same stock location at the same time	x
US-13424	Auto VI: make it visible that line in file was not imported like having the state “exception”	x
US-13354	E-Validation: Signature Follow Up Cancelled Documents Display	x
US-13333	Merge 2 local codes	x
US-13191	Product type: change of description in PMD – non stockable product	x
US-13189	Export Stock & Pipe Report – HQ Tools	x
US-13069	APU Supplier catalogue : Delete the ones that are more than 6 months old	x
US-12985	Partners/ suppliers setting: deactivation (phase-out status)	x
US-12325	Stock Card – display data from newsest to oldest	x
US-9592	e-PL: Add possibility to encode a unique parcel id	x
US-14517	Local Code: MISC root still possible to add	x

3       Finance

3.1        (US-13634) OCA: To make 2 types of currency tables and specific uses

We have added a checkbox to the currency table configuration: “Is for revaluation?”

Implemented Behavior:

EoY Revaluation Restriction:

We restricted the application of EoY revaluation to tables marked as “for revaluation.”

The system now limits the list of available tables to those that are active and flagged for revaluation.

This ensures that OCs not performing revaluation do not need to change their current processes.

WeFin Automation:

We excluded revaluation tables from the automation of actuals in WeFin to avoid incorrect usage.

This setup helps prevent situations where WeFin rates could be mistakenly used for EoY revaluation, which would result in non-correctible entries. The use of designated revaluation tables ensures proper data flow and supports balanced entries.

3.2        (US-13945) OCG_HQ: missing reversing accruals in Trial Balance export as of 31.12 (end year closure)

We have applied a fix to the trial balance export to ensure it correctly accounts for reversing accruals as of 31.12.XXXX, in the context of end-of-year closure.

This adjustment ensures that the trial balance reflects the financial reality more accurately at year-end.

3.3        (US-13954) Accruals not posted but monthly closure possible (“not blocking” warning message already exists)

We have identified an issue where it was previously possible to close a period even if accruals were still in draft status. Although an error message was displayed, it did not block the process.

To address this, we have requested the implementation of a blocking mechanism:

If accruals are in draft, the system will prevent the period from being closed until those entries are posted.

This change is intended to reinforce data integrity during the closing process and avoid inconsistencies.

3.4        (US-14022) Fixed assets: to create an import file in the actions right menu for the “asset reference” data (trigger external ID + Asset code)

We have created an import file accessible from the “Actions” menu in the Fixed Assets module, specifically for the “Asset Reference” data.

This import file allows users to trigger both the External ID and the Asset Code, streamlining the process of asset registration and ensuring consistency in data entry.

3.5        (US-14023) Fixed assets:  button AD from header added in the depreciation tab screen

We have added the buttons “Analytic Distribution” and “Reset AD at line level” to the third tab (Depreciation tab) of the asset form.

These buttons behave in the same way as in the existing screens where they are already available (e.g., SI).

Behavior Implemented:

Analytic Distribution from the header can be modified only for depreciation lines that have not yet been generated (i.e., no JI created).

Only planned entries in the depreciation tab that do not have a JI can be adjusted.

This enhancement improves usability and ensures consistency across screens.

3.6        (US-14024) Fixed Asset: Synch to the “instance of use” the “remaining value”

We have implemented a synchronization between the “Remaining Net Value” field of the asset and its “Instance of Use.”

The update is now automatically triggered whenever the Remaining Net Value is modified due to the following actions:

Generation of an unposted depreciation entry

Deletion of an unposted depreciation entry

Disposal of the asset, which sets the remaining value to zero

This ensures that the instance of use always reflects the most accurate financial status of the asset.

3.7        (US-14354) Fixed assets: at project level: in the assets menu: assets – types and event types must be in read only (no edition)

We have set the menus “Asset Types” and “Asset Events” to read-only at the project level.

Previously, it was possible to edit these fields without any alerts or controls in place. This posed a risk, as these parameters are meant to be managed centrally.

With this update:

These fields can no longer be edited at project level.

All configurations must be defined at HQ level and are now synchronized accordingly.

This change ensures consistency and prevents unauthorized modifications.

3.8        (US-14189) Not runs with model account.move: registers closed and entries blocked at coordo level not going to HQ

We have encountered a situation where no synchronization runs were triggered for the model account.move, due to the inactivation of bank and cash journals before the last entries were synchronized to HQ.

What We Observed:

Journals were inactivated while entries were still pending synchronization.

The system did not alert us or block the process, leading to missed data transfers.

This issue is new to us, as journal inactivation was not previously possible, and therefore such synchronization problems had not occurred before.

This synch rule has been fixed to avoid this problem.

3.9        (US-14427) Operational Advance to employees – PO link field added in Bank and Cheque registers (account 13000)

We have reviewed the behavior of Operational Advance Management regarding the ability to link advances to a Purchase Order (PO).

What We Observed:

In the Cash Register, the system allows linking the advance to a PO.

However, in the Bank and Cheque Registers, this option was not available.

What We Have Done:

We have aligned the behavior across all liquidity registers, ensuring that the PO link is now available in both Bank and Cheque Registers, just as it is in the Cash Register.

This update ensures consistency with the documentation and improves usability for teams managing operational advances.

3.10     (US-14432) Balance specification report – extension to FXA entries

We have completed the following updates to the FXA reporting tool:

Renamed Existing Tab

The current tab of the report has been renamed to “Balance Period Instance.”

Created New Tab

A new tab has been added to the report, named “FXA Period Instance.”

This tab displays monthly entries only (not cumulative), specifically for accounts 67040 and 67050.

The mock-up attached was used as a reference, though not all 67040 entries were included due to length.

Content Logic

The tab includes all FXA entries booked for the reported period.

Amounts are displayed as Debit – Credit (D-C).

These figures are based on actual production data.

Wizard Enhancement

In the selection wizard, the “Top Proprietary Instance” field is now prefilled by default when only one possible value exists.

Reference Setup

The report includes:

Account codes configured as REVAL in the company settings.

Account codes set as default debit/credit for the FXA journal.

This applies regardless of the journal used for booking (e.g., ODM or HR), as manual FXA corrections may be entered under those journals.

These changes aim to improve clarity, consistency, and usability in FXA reporting.

3.11     (US-14504) Balance specification report – displays HQ closed from HQ screen

We have extended the export functionality for the Balance Specification Report to cover additional scenarios beyond the Coordination screen.

What Has Been Done:

The report can now be exported from HQ, including for closed periods, specifically for the HQ instance.

Export is also enabled for inactive proprietary instances, which was previously not possible.

This update ensures that even when a proprietary instance is closed and no longer accessible via Coordination, the report can still be retrieved from HQ.

Export Availability Matrix:

HQ Instance

Coordination Instances

This enhancement ensures continuity in reporting and access to critical financial data, even after instance closure.

3.12     (US-14545) Balance specifications report: display improvement for more clarity

We have made a display improvement in the Balance Specifications Report to enhance clarity.

When the “End of Year” option is selected in the wizard, the FXA tab (Sheet #2) now shows in cell B4 the label:
“Full year export YYYY” (e.g., “Full year export 2025”)
instead of the standard period format.

This change helps clearly distinguish annual exports from monthly ones and improves the readability of the report.

3.13     (US-14565) Partner’s form: track changes for the deactivation and activation of partners

We have added tracking functionality in the Partners form to monitor changes related to the deactivation and reactivation of a partner.

What Has Been Done:

The fields “Deactivate Partner” and “Reactivate Partner” are now tracked.

Any change to these fields is logged, allowing us to follow the history of activation status for each partner.

This update improves traceability and ensures better control over partner status changes.

3.14     (US-13354) E-validation Signature Follow Up Cancelled Documents Display (Refer to the All Supply tickets integrated in UF38.0)

Please refer to the Supply section of release notes for more details on this.

3.15     (US-13424) A new status Partially processed for Auto-VI (Refer to the All Supply tickets integrated in UF38.0)

Please refer to the Supply section of release notes for more details on this.

3.16     (US-12985) Partners management has a new functionality. (Refer to the All Supply tickets integrated in UF38.0)

Please refer to the Supply section of release notes for more details on this.

3.17     (US-14707) Correction of comments in Arabic in PDF (Refer to the All Supply tickets integrated in UF38.0)

Please refer to the Supply section of release notes for more details on this.

3.18     All Finance tickets integrated in UF38.0

Key	Summary	Detailed
US-12316	In the JI: to add total debit – total credit near the total line for “selected lines”	X
US-13153	Code fix_Journal with character (.) has no sdref and cannot be synchronized
US-13634	OCA: To make 2 types of currency tables and specific uses	X
US-13945	OCG_HQ: missing reversing accruals in Trial Balance export as of 31.12 (end year closure)	X
US-13954	Accruals not posted but monthly closure possible (“not blocking” warning message already exists)	X
US-14012	Supplier Commitment vouchers screen in validated CV- put button to distribute AD from header to lines
US-14022	Fixed assets: to create an import file in the actions right menu for the “asset reference” data (trigger external ID + Asset code)	X
US-14023	Fixed assets: to add the button AD from header in the depreciation tab screen	X
US-14024	Fixed Asset: Synch to the “instance of use” the “remaining value”	X
US-14122	Queries created by deleted users are not visible in the Tools menu
US-14189	Not runs with model account.move: registers closed, and entries blocked at coordo level not going to HQ
US-14273	HQ not runs: with model “hr.employee”: to be run without execution
US-14294	Synch update triggered on AD from HQ – AD should not be overwritten
US-14339	Translation to do in the instance configuration (The French version)
US-14369	To enhance the error message displayed when automatic imports fail
US-14396	HQ entry split: issue with rounding to solve
US-14397	OCA Revaluation: put as “default” the last open period – not the calendar period as now
US-14427	Operational Advance to employees – no PO link field in Bank and Cheque registers (account 13000)	X
US-14428	Excel corrupted because text in “reference field” is parsed as a date
US-14432	Balance specification report – extension to FXA entries	X
US-14504	Balance specification report – display also HQ closed from HQ screen	X
US-14545	Balance specifications report: fix in the display for more clarity	X
US-14565	Partner’s form: to add in the track changes the deactivation and activation of partners	X
US-14631	Remove ISAL and IIKD income lines from actuals view for integration to Wefin	X

 

4       Non- functional

4.1        (US-14173) Upgrade to Python version 3.13.7

Minor version upgrade of python from v.3.10.11 to v.3.13.7 this reduces certain vulnerabilities.

4.2        (US-14106) Upgrade to PostgreSQL version 14.19

PostgreSQL version has been migrated from 14.18 to 14.19, ensuring this component supporting UniField remains up-to-date.

4.3        (US-12722) E-validation – possibility to import signature scan

This was a high-priority ticket which means it is now possible for users to import their scanned signatures into their signature space in UniField. This signature can be used in the same way as the previous digitally written signature: when user clicks to sign a document, this signature appears on the onscreen document, and also on the relevant PDF. It can be deactivated and replaced. The original digitally written signature still remains as an alternative option for users if they still prefer this. When adding their signature, user can choose “Type of signature creation” options “importing” (scanned signature) or “drawing” (directly in UniField with mouse etc).  For the import option, the template can be exported, and then user must sign in the designated signature zone. This should then be scanned and saved as*.png, *.jpg, *.jpeg or *.pdf file. This can then be added to the field “Import your signature” by clicking to add attachment.

4.4        (US-14426) Users Management: a new email column and search box in list view

Development requested by Supply to make email usage more user-friendly, a new E-mail column has been added to the list view under Administration → Users → Users. Additionally, new E-mail filter is introduced to make it easier to search for users by their e-mail address.

4.5        All Non-functional tickets integrated in UF38.0

Key	Summary	Detailed
US-14137	Upgrade to Python version 3.13.7	x
US-14106	Upgrade to PostgreSQL version 14.19	x
US-12722	E-validation – possibility to import signature scan	x
US-14426	Users Management: a new email column and search box in list view	x

1       Release Details

Release version: UF 37.1

Date of production synchronization server patch: 13^th August 2025 / 18:00 Geneva time

Latest user rights files updated: UF37.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=12543

2       Supply

2.1        (US-14502) E-signature – signatures not visible after release

UF 37.0 introduced changes to the Incoming Shipment (PDF) signatures that inadvertently altered how the electronic signature is displayed. This ticket aims to restore the correct behavior—ensuring the electronic signature appears on the Incoming Shipment PDF—and to unblock missions already using UniField’s E-Validation feature.

2.2        All Supply tickets integrated in UF37.1

Key	Summary	Detailed
US-14502	E-signature – signatures not visible after release	X

3       Finance

3.1        (US-14654) OCP VI export: Functional rounding only applied after check

The OCP HQ Workday VI export for the report “Monthly export” has been changed so that before UniField rounds/adjusts the Functional credit and Functional debit values to match, it checks first that the relevant Booking currency credit and debit values match. If they do not then no rounding is made on the functional columns. This change will allow OCP users to more quickly identify issues such as duplicate / unbalanced entries which previously were causing issues with closure after integration into workday. There is no change to the way UniField calculates any system values, so no impact on other OCs / exports.

3.2        All Finance tickets integrated in UF37.1

Key	Summary	Detailed
US-14654	OCP VI export: Prevent wrong balance	X

4       Non- functional

4.1        (US-14500) Aggregation Server landing page

In this dev, raised by OCB, a bug in openerp is corrected so that for servers / machines which host multiple instances of UniField, it is possible to specify a domain name for each, and when link is clicked on, only the relevant UF database is displayed on login page.

It is now possible to add in openerp-web-oc.cfg config file, this new directive to filter the list of dbs on the login page.

[openerp-web]
dblist.filter = ‘EXACT’

4.2        All Non-functional tickets integrated in UF37.1

Key	Summary	Detailed
US-14500	Aggregation server landing page filter on database	X

1       Release Details

Release version: UF 37.0

Date of production synchronization server patch: 11^th June 2025 / 18:00 Geneva time

Latest user rights files updated: UF37.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=12539

2       Supply

2.1        (US-14373, US-13955) To define empty Location OST if procurement method from stock

To reduce the potential for data encoding errors that can lead to incorrect picking locations when users are using the Order Sourcing Tool (OST), we are implementing a change regarding the “Stock” warehouse location. This update involves removing the “Stock” location as the default preselection when sourcing items “from stock.” The goal is to decrease the likelihood of mistakenly sourcing goods from the “Stock” warehouse location.

The default location will now be set to empty, rather than defaulting to “Stock.”

Note: Location is a mandatory field. If no location is selected, a blocking message will appear, similar to the behaviour when the procurement method “On order” is chosen. The “Stock” location will remain available in the dropdown list for selection.

2.2        (US-13952, US-13741) Supplier rankings information displayed in PMD / OST

To improve visibility and utilize the new ranking feature for sourcing management at the user level, a new column called “Ranking” has been added to the Order Sourcing Tool. This column displays the line ranking from the selected supplier catalogue (sourced from the product card). If two supplier catalogues exist for the same code/ranking, the supplier with the lowest price is selected.

Previously, suppliers were chosen in alphabetical order when all other conditions were equal.

2.3        (US-14253) Adding a new line in Confirmed catalogue updating a Catalogue

A bug fix allows to update a catalogue in a confirmed status when a new line is added

2.4        (US-14268, US-14216) Adjustment of FO follow-up and IR follow-up generation behaviour

A bug fix addresses the export behaviour of the FO follow-up report and adjusts the column positions. The issue was identified in the previous UF version.

2.5        (US-14084) Loan Return does not allow change of Partner

As the Loan Return PO is created automatically via the Loan flow, and not from scratch. With this correction a change of a partner in a loan return document is not possible anymore.

2.6        (US-13597, US-13263) Layout improvement for big numbers in PDF report Allocation report and Purchase Order

This improvement ensures no overlapping of big numbers in PDF report Allocation report and Purchase order

2.7        (US-14069) Duplication of Direct Purchase order creates a Regular PO

Previously, duplicating a DPO was blocked with an error message. This update enables the duplication of a DPO as a standard Purchase Order.

2.8        (US-11801) Modification of Product Inconsistency report and Product Status inconsistency report

The improvement renames the report from Product Inconsistencies Report to BN/ED Inconsistencies Report. The location of the report moves the report from “Tools” to Warehouse >Traceability (under “Batch Location”). Abbreviation of the report is adjusted to make it easy to read.

A new Standardization level column is introduced in Product Status Inconsistency report. The values pull information from the product card (Standard/ Non-Standard/Non- standard Local).

The report moves from Tools to Product> Reporting (new submenu is introduced under “Product update”)

2.9         (US-11802) Change columns in the report ” Product likely to expire”

Naming of columns is changed to improve readability of the report.

N.B. Columns “Total Quantity Likely to Expire” and “Total Value of Likely to Expire Quantity” excludes qty and value of already expired products.

2.10     (US-13923) Multiple lines AD missing on PO/FO: change of warning message

This improvement enhances the visibility of lines missing Analytical Distribution in PO/FO. A new dynamic pop-up warning message on PO/FO notifies users about lines missing Analytical Distribution:  “Analytical distribution is missing for lines A, B, C. It must be added manually.” 

The warning message dynamically lists only the lines missing Analytical Distribution. If the Analytical Distribution for a line is corrected, that line is automatically removed from the error message.

2.11     (US-13995) Aligning the sequence of signatures in IN PDF

A new column, “Approved by” has been added to the Incoming Shipment PDF. It is positioned after “Received by” and “Controlled by” The French translation has been aligned with standard supply terminology.

2.12     (US-13508) Merge of Local and UniData code changes behaviour for blocking message.

This improvement standardizes the behaviour of warning messages for blocking and non-blocking attributes related to the Local Code/UD Merge functionality. 

When merging Local and UniData codes, if the Main Type differs between the Local Code and UniData codes, users receive an immediate blocking message.

“There is an inconsistency between the selected products: Main Type need to be the same.  Please update your local product Product Type and then proceed with the merge. Products XXXX and XXXX”

2.13     (US-13308) IR: Change name of “Request Date” Field

With this improvement in IR form page “Requested Date” is renamed to “Requested Delivery Date” to align with FO and PO.

2.14     (US-13190) Historical Consumption Report – Include Customer Type Partners in RR-AMC

As part of the Programmatic Donation development, this improvement introduces a new field, “External Partner,” in the Historical Consumption Report when using the RR-AMC function. The goal is to enable AMC extraction for a specific customer or multiple customers. Additionally, “Source” and “Destination” have been renamed to “Source Locations” and “Destination Locations.” 

The RR-AMC will continue to be calculated as usual but will only consider outgoing moves involving the selected partner(s).

The following rules apply to the new field: 

– If an External Partner (Type: Customer) is selected as the destination location, the source location must be either Internal Locations or Cross-Docking. 

– The source location can also be left empty, in which case only movements from Internal Locations and Cross-Docking will be included in the RR-AMC calculation. 

– An External Partner can be combined with an External Consumption Unit as the destination location. 

– If “Other Customer” is selected as the destination and you attempt to select one or more External Customers, a warning message will block this action. 

– Similarly, if “External Customer” is selected as the destination and you attempt to select “Other Customer” a warning message will also block this action.

2.15     (US-13377, US-13353, US-13346) Improvement linked to the E-Validation

This release improves landing pages for Sign-only Users, makes UniField easier to navigate. The role/function titles aligned between the PDF (Incoming Shipment, Internal move, and Delivery Order).

2.16     (US-12270) Introduction of E-validation in Internal Move

The improvement introduces E-validation functionality in Warehouse->Warehouse management-> Internal moves.

2.17     (US-13064) Introduction of E-validation in Physical Inventory

With new improvement E-validation is available in Physical inventory in “Validated”, “Confirmed” Statuses. The signature order in the PDF follows this sequence: Warehouse Responsible, Supply Responsible, and Stock Owner (with the Stock Owner’s signature being optional). If the signature is accepted on validation and the Physical Inventory is set to         Re-count or Regenerate Discrepancy, all E-signatures are removed.
To confirm inventory, the PI must be signed. If no signatures are provided during the confirmation process, a blocking message will appear:

“The Warehouse Responsible role must be a signer in order to confirm inventory. 

If the signature is provided physically, please select ‘Sign Off-line’.”

2.18     All Supply tickets integrated in UF37.0

Key	Summary	Detailed
US-14373	(US-13955) To define empty Location OST if procurement method from stock	x
US-14341	(US-11801) Issues with Inconsistencies report	x
US-14268	Export FO follow-up excel report failing – OCBSL101	x
US-14253	Adding a new line in Confirmed catalogue not updating a Catalogue	x
US-14216	Excel IR Follow Up Formatting Issue	x
US-14146	OCA RR: The Automatic Supply doesn’t work and displays error messages when checking with “specific period only”	x
US-14143	OCA: RR, The “Set Paired Product” functionality is not working in the Segment	x
US-14112	Misalignment of the “Manufacturer” field in the Product Information Interface	x
US-14084	Loan Return Allows change of Partner	x
US-14069	Issue while trying to duplicate a DPO in specific cases	x
US-13998	Error after Import Packing – French version	x
US-13995	to aligne the sequence of signatures in IN PDF	x
US-13989	Possible to select internal locations as Source and Destination for RR-AMC calculation	x
US-13978	Import / Export: Products – template not imported due to Nomenclature issue	x
US-13955	PMD / OST removing “stock” from the default source location automatically preassigned by the system	x
US-13952	Supplier rankings information displayed in PMD / OST	x
US-13923	Multiple lines AD missing on PO/FO: change of warning mesage	x
US-13741	Supplier rankings in PMD / OST ignores validity dates	x
US-13597	Big numbers on PO	x
US-13508	Merge product functionality: Warning Message behavior Blocking V Non-Blocking	x
US-13377	E-Validation: Change to Signee Landing Page	x
US-13353	E-Validation: Role / Function Title Improvements	x
US-13346	E-Validation: User Rights Pop Up When Signee Clicks Save/Edit/Duplicate Buttons	x
US-13308	IR: Change name of “Request Date” Field	x
US-13263	Big numbers on PO allocation report – beyond US-12787	x
US-13190	Historical Consumption Report – Include Customer Type Partners in RR-AMC	x
US-13064	Physical Inventory : Document status to be linked to signature: E-validation	x
US-12270	E-Validation for INT Internal Move	x
US-11802	Change columns in the report ” Product likely to expired”	x
US-11801	Change the name of: Inconsistencies Reports	x

3       Finance

3.1        (US-13520) “Fixed Asset Register”: creation of a new report for audit purposes (in the asset form menu)

A new register for all fixed assets has been created in the screen Asset form, in the right action menu.

The report can be issued in PDF and Excel formats.

3.2        (US-13582) Fixed Asset: to allow to delete generated UNposted depreciation entries in the asset form (same functionality as in the recurring entries)

We can delete the Unposted entries via the button Delete Unposted entries

After this deletion, we can generate the entries again

3.3        (US-13662) Fixed Asset: to add restrictions when we create an asset form from scratch from a JI

We have done a fix in order to avoid errors. We have prevented that the initial line creation when the JI will be on a depreciation Account.

3.4        (US-13716) Fixed Asset: Account code restriction for manual creation at Journal Item level (in the Asset Forms screen) + renaming

The list of Journal Items (JI) available for selection on the manual asset form was restricted to those linked to account codes where “Prevent Fixed Asset on HQ entries” had not been ticked.

This meant that when an account had been tagged as “Prevent Fixed Asset on HQ entries”, the system did not display journal items from that account in the “Journal Item” field of the asset form used for manual creation.

If the checkbox had not been ticked, journal items were displayed for manual asset creation and HQ entries capitalization was allowed.

If the checkbox had been ticked, journal items were not displayed, and the account could not be used for HQ entries capitalization.

It should be noted that asset capitalization accounts were not meant to be ticked, and therefore were displayed in the list of journal items for manual asset creation — serving as a workaround for capitalization of multiple items from HQ entries.

In the “Search: Accounts” screen, the checkbox on the “Chart of Accounts” (COA) section and its corresponding filter were renamed as follows:

• : Prevent capitalization of entries
• : Empêcher la capitalisation des écritures

3.5        (US-14168) Fixed Asset: Colour in blue draft + grey disposed asset form on list view

The draft asset forms are in blue and the fully disposed are in grey.

3.6        (US-13624) Combined Journal report: Bad selection results “exclude journal” ENG

In the combined journal report: we are now able to exclude from the selection the analytic journal ENG. This was not possible before, so it has been fixed with this ticket.

3.7        (US-13801) Internal transfers: to add a new constraint to prevent to change the account code on a counterpart line

There was already a constraint to prevent to change the 3rd party on a counterpart line with a transfer account (US-12678). Here we have added a new constraint to prevent to change the account on a counterpart line.

3.8        (US-13963) Not to be able to select an inactive staff when booking an entry in the cash registers

For register lines:

For Journal Items:

Error messages:

3.9        All Finance tickets integrated in UF37.0

US-14379	Period states not synced up on new instance creation
US-14362	(US-13520) Fixed Asset Register crashes when there is an asset without a related booking currency
US-14332	OCP_HQ workday mapping table to export the Finance VI file for expat users
US-14264	OCBLB101 : error “Let me fix it “screen while consulting List of advance in Bank register
US-14168	Fixed Asset: Colour in blue draft + grey disposed asset form on list view	X
US-14039	OCBSD207: impossible to access to the cash registers
US-13963	Not to be able to select an inactive staff when booking an entry in the cash registers	X
US-13947	Import file for liquidity register is generating multiple lines because we clicked several times on the “import” button
US-13935	French translation in tools menu: importer/Exporter
US-13906	Account Periods: to set Fiscal Year and Period name as read only
US-13902	In the Selector/analytic selector/combine report: to increase the number of digits of the field sequence number to 365 digits
US-13801	Internal transfers: to add a new constraint to prevent to change the account code on a counterpart line	X
US-13782	OCA Code Fix : Import of expat (auto and manual) identification number
US-13716	Fixed Asset: Account code restriction for manual creation at Journal Item level (in the Asset Forms screen) + renaming	X
US-13708	AJI is not updating the currency update if ODM unposted (just updated when the ODM is posted)
US-13662	Fixed Asset: to add restrictions when we create an asset form from scratch from a JI	X
US-13624	Combined Journal report : Bad selection results “exclude journal” ENG	X
US-13582	Fixed Asset: to allow to delete generated UNposted depreciation entries in the asset form (same functionality as in the recurring entries)	X
US-13539	Import Homere: to permit the import of the permois for inactive destinations with no need to tick “allow all cost centers”
US-13520	“Fixed Asset Register”: creation of a new report for audit purposes (in the asset form menu)	X
US-14429	OCP VI Finance: AJI rounding issue in January 2025 (Workday export)

4       Non- functional

4.1        (US-14040) Cleaning users_last_login.date

Since UF34.0 release, based on the ticket US-12274, users created via duplication no longer inherit the last connection date value from the original user. This ticket cleans the historical data = sets users_last_login.date to null for the users whose users_last_login.date is earlier than res_users.created date.

4.2        (US-14046) Last password change of duplicated users + cleaning historical data

Users created via duplication inherit the last password change value from the original user while users created from scratch have last password change equal to create date. This ticket ensures that all new users, including those created via duplication, will now have last_password_change set to their create_date. Moreover it cleans the historical data – sets res_users.last_password_change to res_users.create_date for the users whose res_users.last_password_change is earlier than res_users.create_date and for the users whose res_users.last_password_change is before June 16th, 2021 (when the res_users.last_password_change column was introduced).

4.3        (US-14124) Cleaning ir_property table

Entries related to property_product_pricelist_purchase, property_product_pricelist, property_account_receivable and property_account_payable were deleted from ir_property table since property_product_pricelist_purchase, property_product_pricelist, property_account_receivable and property_account_payable columns in the res_partner table have been modified in US-10652.

4.4        (US-14239) Email configuration allowing emails to be triggered

With this ticket, an adjustment has been made so that with current version of Python version used in UniField, an email can be triggered by UniField. This is a technical ticket as no rules have yet been defined to launch the emails.

4.5        (US-14105) Upgrade of version PostgreSQL: Patch from v.14.16 to v.14.18

With this ticket, the version of PostgreSQL for all instances already on v.14.16 will be updated to v.14.18. This ticket is one of several measures relating to IT security via regular upgrades. For any instances not yet on v.14.16 (e.g. those still on v.9.6) there will be no change as they would still need manual intervention.

4.6        All Non-functional tickets integrated in UF37.0

Key	Summary	Detailed
US-14040	Cleaning users_last_login.date	X
US-14046	Last password change of duplicated users + cleaning historical data	X
US-14124	Cleaning ir_property table	X
US-14239	Email configuration: adapt code for python3	X
US-14148	Possibility to extract translation file via UI of UF
US-14105	Upgrade of version PostgreSQL: Patch from v.14.16 to v.14.18	X
US-13877	Patch application: unable to restart unifield-server

1      Release Details

Release version: UF 36.0

Date of production synchronization server patch: 12^th March 2025 / 18:00 Geneva time

Latest user rights files updated: UF36.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=12534

2      Supply

2.1       (US-13862, US-13476) New warning when document Category inconsistent with the product in document created from scratch ( IN/OUT/INT)

For improved visibility and order accuracy, the Order Category field is mandatory for documents created from scratch (IN/OUT/INT). The default value is empty, and the user can select one of the following options: Logistic, Medical, Service, Transport, or Other.

If a product does not correspond to the selected category, the user will receive a non-blocking warning message.

2.2       (US-13836) New function Export/Import for Delivery order (OUT)

A new Export/Import function has been developed for the Delivery Document (OUT). This function is aligned with the PICK (Export/Import) process and enables users to export and import values seamlessly. It is important to note that the export file includes only available lines and has timestamp to prevent the import of an incorrect file. This is functionality is also key for the SDE project needs.

If the OUT is created from scratch “Convert to Picking ticket” option is blocked by the system with a warning message

2.3       (US-12608) Possibility to add a source document for a newy added line in PO/FO

A bug fix allows adding a source document in PO/FO on a newly added line.

2.4       (US-13832) Phase Out cannot be sourced to PO (External supplier) when sourcing multiple lines

Previously, it was possible to source Phase-out codes to external suppliers when sourcing multiple lines. US-13832 updates the rules to ensure consistency for Phase-out codes across all order source options, whether sourcing a single line or sourcing multiple lines.

2.5       (US-13683) Physical inventory: Explicit message if the Unit of Measure (UoM) or Expiry Date is incorrect at the importation of the Counting Sheet.

When Counting sheet contains value not recognized for UoM, or for ED import is blocked and a clearer warning  message is displayed.

2.6       (US-13590, US-13591) Update of “Export IR Follow-up” and “Export FO Follow-up” reports

To improve comprehension and readability, the “Export IR Follow-up” and “Export FO Follow-up“ Excel reports have been modified. 

A new column, “Qty Received,” has been introduced for sourcing on Purchase Orders. 

The new “Qty Received” column will display: 

– 0 if nothing has been received. 

– N/A if no IN is available. 

– Quantity received if items were received via the corresponding IN. 

Additionally, column names have been adjusted as follows: 

Qty Ordered > UoM > Qty Received > Qty Delivered > UoM > Qty to Deliver 

2.7       (US-13314) Updates in PO – “Supplier Catalogue” Tab

In version UF36 supplier catalogue information visible on PO is modified as follows:

1. is renamed to “UoM.”
2. 1. → “PO Unit Price.”
   1. → “PO Subtotal.”

Additionally, in the PO Action menu, the “PO Lines Mismatch” report is renamed to “PO vs. Catalogue Mismatch.”

The Catalogue Mismatch information is visible to the user only if an active catalogue with a valid date exists. Otherwise, the Supplier Catalogue tab on the PO will not appear.

2.8       (US-12816) New filter “Customer Refence” introduced in Purchase order

To enhance user-friendliness and eliminate the need to switch back and forth to the FO module for the corresponding reference, a new filter, “Customer Ref” (the project PO reference), has been introduced.

This filter has been added between “Source Document” and “Customers.”

2.9           (US-12481) New Details information column in reception/delivery/movement/ Supplier performance report

Following the addition of “Details” field to various docs a new column is added in the following reports:

• Receptions Report: a new column IN Details (details information is pulled from IN)
• Deliveries Report:  a new column Movement Doc Details (details information is pulled from OUT/PPL)
• IN&OUT Report: a new column Movement Doc Details (details information is pulled from IN or OUT/PPL)
• Supplier performance: new column PO Details (details information is pulled from PO)

2.10    (US-12721) New function of Price/ Quantity/ Comment update on Purchase order via import file

When a Purchase Order (PO) is created from an Internal Request (IR) or Field Order (FO), and there is no catalog for the selected partner, the unit price on the PO is based on the average cost price converted from the functional currency.

The UniField 36.0 release introduces a new import function for POs. A new button, “Update Line,” allows users to update the price, quantity, and comments of a line via import. The “Update Line” functionality is available in Draft (-p) status for all supplier types (Internal, External, ESC, IM, and IS). Import can also be performed in Validated (-p) status, but only if the supplier is External. Lines updated via import must correspond to respective statuses.

If a line item is Confirmed, Canceled, Closed, or Validated (for ESC, Internal, IS, and IM partners), the import will ignore that line. If any lines are ignored, UniField provides a clear message explaining which lines were not updated and why.

A user can use the “Update Line” function multiple times while the PO is in Draft (-p) status (or, in specific cases, in Validated (-p) status for external suppliers).

2.11    (US- 12430) Prevent creation of external partner when combination name + city already exists.

A ticket raised by finance preventing creation of the external partner when combination of Partner name + City already exists. Please refer to the Finance section of the release for more details

2.12    (US-12005) Order line with a Product by Nomenclature can be Re-synched between 3 Internal/ Intermission/ Intersection partners

A new improvement enables re-synchronization of the line by nomenclature across three instances. This feature is available for internal, intermission, and intersection flows.

If the order line by nomenclature is sourced to a PO in the third instance, the last instance must assign a product code for PO confirmation to the external supplier.

It is important to note that the assigned code in the last instance must exist in all instances. Otherwise, the nomenclature in the downstream flow will not be updated with the assigned code, resulting in a “Not Run” status.

2.13    (US-13097) IN synch message should not be run w/o execution if PO line not yet confirmed.

Previously, when a sending instance dispatched goods via SHIP, but the receiving instance had a PO line that was not yet confirmed due to inactive code in requesting instance, the system attempted to process synchronization. However, since there was no corresponding IN to update, the system marked the message as “Run” without execution, citing an argument that the update could not proceed because the line was already closed or cancelled. 

With this improvement after activation of the product in requesting instance the run is executed “normally” as if it had waited activation of the product.

2.14    All Supply tickets integrated in UF36.0

Key	Summary	Detailed
US-13957	IN/INT/OUT from scratch; to block modification of Order Category if Draft is confirmed	X
US-13862	Introduce a warning message Category inconsistent with the product in document from scratch ( IN/OUT/INT)	X
US-13836	Delivery Order / OUT: create export / import file	X
US-13832	Phase Out articles can be sourced to PO (External supplier) when sourcing multiple lines	X
US-13683	Physical inventory: counting sheet: When there is an error at import due to unrecognised value in UoM, ED message should be clearer	X
US-13611	Delivery Address inconsistency PPL/SHIP (converted OUT)	X
US-13591	Export IR follow up	X
US-13590	Export FO follow-up	X
US-13585	IR and FO Export Follow Up Log Order Categories Not Working	X
US-13476	Enable Order Category when creating IN from scratch	X
US-13314	Include Supplier Catalogue info in POs – following	X
US-13097	IN synch message should not be run w/o execution if PO line not yet confirmed.	X
US-12816	POs filters – adding “Customer Ref” as filter at header level	X
US-12721	PO Line Item Update via Import	X
US-12608	Strange behavior when adding new lines to PO, and adding the source document	X
US-14080	Impossible to create a RfQ from scratch
US-12481	Receptions and Delivery Report – add Details column	X
US-12005	Resync should allow order lines with nomenclature	X

3      Finance

3.1       (US-11764) Allow inactivation of Department (complementary to US-11587)

In this release, several enhancements were made to the department management system:

These improvements aim to enhance department management and streamline the user experience.

3.2       (US-13543) COA Configuration: add the “destination code” in the “analytic distribution” tab

A new column for the “Destination Code” was added to the Analytical Distribution tab, which is located under Configuration > Financial Accounting > Accounts > Account. This update ensures that the destination code is now visible and accessible for users in the specified section.

3.3       (US-13650) Fixed Asset: In the asset form: to restrict the “asset B/S depreciation account” to an account with “asset” type

In this release, the Asset B/S Depreciation Account in the asset form was restricted to only allow selection of accounts with the type “Asset”. This ensures that only appropriate account types can be used for depreciation, improving data consistency and accuracy.

3.4       (US-13693) Fixed Asset: Make not run update when asset form is received while the fixed assets functionality is inactive

A new “Not Run” update was implemented. When the asset form is received in an instance where the Fixed Assets functionality is inactive, the update prevents the form from running, ensuring that assets are only processed when the required functionality is enabled.

3.5       (US-13894) Fixed Assets: Please filter the screen of generation of entries to “unposted” entries only

The default filter for the Search: Asset Lines screen was set to “Unposted”, ensuring that only unposted asset lines are displayed by default when users access the screen. This improves the focus on entries that still require processing.

3.6       (US-13568) Fixed asset: to add a control to prevent decommission of a prop instance if all assets are not transferred nor disposed

A control was added to prevent the decommissioning of an Instance if assets have not been transferred or disposed of. Since the Instance Decommission process occurs at the HQ level, while the asset form exists only at the Coordination and Project levels, the only way to ensure the asset is not still owned by the decommissioned instance is to generate a NotRun update at the Project or at Coordination level when attempting to change the instance status. This ensures that the decommissioning process can only proceed once all assets have been properly handled.

3.7       (US-13736) Hide the duplicate button in the lines of imported Journal entries JE

A restriction was implemented to prevent modifications to Imported Journal Entries (JE). Specifically, the duplication button was hidden on the line level, ensuring that no changes can be made to the lines in an imported JE.

To clarify, lines in an imported JE are not editable—this means you cannot modify the Credit, Debit, or Account values, nor can you delete individual lines. An imported JE can only be created if it is balanced, and the only way to remove a line from an imported JE is to delete the entire journal entry.

With this update, the system helps avoid a significant amount of data fixes, improving data integrity and reducing manual corrections.

3.8       (US-13703) Import-export IVI lines: to have an error message when the destination is not correct

In this release, when importing IVI lines, if the import fails due to a non-existent destination in Unifield, a clearer error message was added. The message now includes the specific destination causing the issue, allowing users to easily identify and correct the error.

3.9       (US-12443) Inactivation of bank journal conditioned to the inactivation of the related cheques journal

the inactivation of a Bank Journal was made conditional upon the inactivation of the related Cheque Journal. This ensures that a bank journal cannot be inactivated unless its corresponding cheque journal is also inactivated, maintaining data integrity and consistency between the two.

3.10    (US-12430) Partners creation: we can modify a partners form and we can have 2 external partners with the same name and the same city within the same instance

This ticket prevents external partners from being modified so that 2 partners can have the same name and city. If a partner is created with the same name and a different city, it cannot later be modified to have a city which is already used in another partner with the same name, preventing duplicate entries and maintaining data consistency.

3.11    (US-13776) Permois import: to display a clear error message in the case that the column “name” is empty

When performing a Permois import, if the Name field is empty, a clear error message was added. The message now includes the identification number, making it easier for users to identify and address the issue.

3.12    (US-13513) To be mandatory for partners to have at least one of the role customer/supplier ticked at create/edit action

A validation was added to ensure that each Partner has at least one of the roles Customer or Supplier selected. It is now impossible to save a supplier without one of these roles being ticked. If neither role is selected, an error message will be displayed, providing an explanation and guiding users to correct the issue before saving.

3.13    All Finance tickets integrated in UF36.0

Key	Summary	Detailed
US-11764	Allow inactivation of Department (complementary to US-11587)	X
US-13543	COA Configuration: add the “destination code” in the “analytic distribution” tab	X
US-13650	Fixed Asset: In the asset form: to restrict the “asset B/S depreciation account” to an account with “asset” type	X
US-13693	Fixed Asset: Make not run update when asset form is received while the fixed assets functionality is inactive	X
US-13878	Fixed Asset: Search: Asset lines: to correct the format of the 2 totals (func debit and func credit)
US-13895	Fixed Asset: to remove the menu Generate Asset Entries and Import Asset Entries at project level
US-13894	Fixed Assets: Please filter the screen of generation of entries to “unposted” entries only	X
US-13568	Fixed asset: to add a control to prevent decommission of a prop instance if all assets are not transferred nor disposed	X
US-13691	Fixed assets: to update the wording in the activate the fixed asset configuration (following the changes of release UF35)
US-13968	Fixed assets: fix to do in the asset inactivation (reconfigure)
US-13736	Hide the duplicate button in the lines of imported Journal entries JE	X
US-13703	Import-export IVI lines: to have an error message when the destination is not correct	X
US-12443	Inactivation of bank journal conditioned to the inactivation of the related cheques journal	X
US-13401	Partial reconciliation at project while full reconciliation at coordo
US-12430	Partners creation: we can modify a partners form and we can have 2 external partners with the same name and the same city within the same instance	X
US-13776	Permois import: to display a clear error message in the case that the column “name” is empty	X
US-13648	Restrict the accounts in the Product Categories import to “donation” or “asset” accounts types depending on the column
US-13976	Product categories import file: account restriction to fix in column H (asset B/S Depreciation Account)
US-13513	To be mandatory for partners to have at least one of the role customer/supplier ticked at create/edit action	X
US-9993	To fix the Journal Items Track Changes in the form view: the option is there but no results are displayed
US-11953	To improve the performance of the Journal Items search view
US-13988	OCP VI Finance: prefix zip file by reopen
US-14004	OCP Workday projects: additional requests

4      Non- functional

4.1       (US-13755) Drop column res_users.date

Since UF34.0 release, based on the ticket US-12274, last login of the users is kept in the users_last_login table instead of the res_users table. To avoid confusion, the column date was deleted from the res_users table.

4.2       (US-13788) Consolidation of users email columns

The email column in the res_users table was not populated. Instead, the column in the table res_partner_address is used for keeping email addresses of the users. To avoid confusion the email column in the res_users table was deleted.

4.3       (US-14050) Patch to upgrade PostgreSQL version

Triggered by a security concern raised by OCA, this release contains a patch which will automatically upgrade all servers which are currently on PostgreSQL version.14.10 to version 14.16. 

N.B.:This will not change the version of any servers which are still on any version of PostgreSQL prior to v.14.10 (there is a manual process required to be performed as documented in US-14042).

4.4       All Non-functional tickets integrated in UF36.0

Key	Summary	Detailed
US-13755	Drop column res_users.date	X
US-13788	Consolidation of users email columns	X
US-14050	Patch: Upgrade instances on PostgreSQL v.14.10 > v14.16	X