1 Release Details
Release version: UF 36.0
Date of production synchronization server patch: 12th 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:
- is renamed to “UoM.”
- → “PO Unit Price.”
- → “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 |
