1 Release Details
Release version: UF 38.0
Date of production synchronization server patch: 17th 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.
- Financial documents:
Partner (Phase out) in different Configurations
- 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.
- 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.
- 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 |
