1 Release Details
Release version: UF 37.0
Date of production synchronization server patch: 11th 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 | |
