Date of production synchronization server patch: 11th 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.
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.
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.
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.
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.
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.
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.
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.
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.”
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.
In Warehouse → Delivery → Shipment, the existing default “Not empty” filter is complemented with two additional default filters: “Draft” and “Ready to Ship.”
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.
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.
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.”
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Date of production synchronization server patch: 8th 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
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.
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.
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.
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.
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.
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.
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.)
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?”.
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.
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.
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.
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.
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
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.
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).
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”.
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.”
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Date of production synchronization server patch: 13th 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.
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.
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.
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.
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.
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.
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.
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.
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.
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”)
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.
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.
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”
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.
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).
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’.”
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 assetshas 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
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.
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).
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.
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.
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.
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.
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.
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
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.
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.
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)
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).
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
Date of production synchronization server patch: 15th January 2025 / 18:00 Geneva time
Latest user rights files updated (no change): UF35.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.
An issue has been identified in the Analytic Selector filter, which previously ignored the case of a second Journal Item correction. A fix has been done in this release.
A bug was detected while using the accruals functions. It was not possible to post entries, and an error message was displayed. This issue has been fixed in this release.
This ticket was included so as to avoid Synch Not runs being created on newly created instances. The User Rights group sign_document_creator_supply (only used when E-validation module is active) should no longer create this issue.
Date of production synchronization server patch: 11th December 2024 / 18:00 Geneva time
Latest user rights files updated: UF35.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.
Several improvements to the E-Validation module are included in this release. Now, for Purchase Orders which have an external Supplier, the system will make several checks before allowing users to sign. These checks are that: PO has lines, lines have quantity, price and AD. This check is done at the point when signees are being added to the PO.
The action of locking the PO means that no PO fields at header or line level can be edited with the exception of the Estimated and Confirmed Delivery dates EDD & CDD). It is still possible to Validate and Confirm the PO and its lines.
In a PO which is “locked” there is a 2nd new button which appears “Remove signatures to unlock PO”. When this button is displayed the other button to “lock” will not appear and vice versa.
As the name suggests, if used, the “Remove signatures to unlock PO” will remove any signatures currently on the PO and make the PO editable again. , Both the lock and unlock buttons can be can be used only by users who have the “Sign_document_creator” user rights group.
Physical Inventories are the latest transaction to be made available in the E-validation module. The PDF report which will display all signatures is the (new) Discrepancies PDF. This report can be accessed only once the discrepancies in the PI have been generated (which matches with pre-existing excel for discrepancies), however the PI can be signed in any status. The pre-existing Excel report of discrepancies has also had some formatting changes.
Several improvements have also been made to the “Signatures follow up” screen. These include the way Supply documents are displayed (full name of document + initials for Supply documents for example “Purchase Order (PO), the “user” field selection now only shows users who have sign rights, the column name “Document name” has now been changed to “Document ID” document statuses are now displayed more accurately (.e.g POs which are “Closed” are now displayed as such), the header filter button “Open” has been renamed to “Unsigned” so that the signing status is clearer.
Please see specific tickets for more detail on these changes.
To continue in the direction already initiated in previous releases to make catalogues more useful and used, it is now possible to add a ranking directly on a catalogue, either at header or at line level. Each new catalogue must have a ranking, which must either be added by the user when the catalogue is Confirmed, or for catalogues which are created via synch or auto VI import, a default “3rd choice” ranking is automatically assigned but can be changed. When a new line is added directly to an existing catalogue, this new line must have its own ranking assigned unless there is already a ranking at header level. The ranking options have changed to have a clearer naming, so they are now “1st choice”, “2nd choice” etc until “12th choice”. Where Suppliers already have a ranking with an old value (e.g. “0”) in the Product record, these remain unchanged unless a new catalogue is added. The Tender process will now no longer automatically assign a ranking to the supplier selected in the Tender process. It is still possible to modify / add a new ranking directly in the product PMD. The Order Sourcing Tool will prioritise the new rankings, and will propose according to this hierarchy.
It is now possible to see Track Changes for Catalogues which are for external suppliers. This is available via the Action menu in an excel format. This includes entries for any changes to the rankings of the catalogue & its lines.
This improvement requested by OCA allows for users to export a list of a product list in a format which can be imported into an IR (Internal Request).
The new export “Export Product List IR Excel” can be accessed in the IR List view Action menu (without any IR being selected).
In the intermediate pop-up, the user can select an exiting Product list and then generate the IR template including these products.
In order to import this list, it is necessary to be in an IR which is in Draft status and for which the header information has already been filled.
The import can be made via the Action menu of an IR in form view by clicking on “Import Product List IR Excel”. This action / import can be performed several times if user wishes to import a file more than once due to different product lists etc being added.
In this improvement for the VI (Vertical Integration) flows when an IN import file has pack details and also expired goods is possible to “Process to ship” even BN is expired. Previously the import was blocked for auto VI.
In this improvement for the VI (Vertical Integration) flows, when an IN import file (E-Packing List) has pack details and also expired goods is possible to import and “Process to ship” even if a Batch Number has expired. Previously the import was blocked for auto VI.
Previously in this report, the checkbox “Include products with stock <= 0 with movements in the last months “ disappeared when certain other filters were applied such as addition of an MML. Now this checkbox, together with its conditional field for months can be applied more widely.
With this ticket, Picking List, Picking Ticket, Internal move and Delivery Order documents now have clearer naming for their statuses and header filters. Where their status was previously “Confirmed” this is renamed to “Not Available” with the relevant header filters which correspond. Header filters on Pickings will now display Picking Tickets or Picking Lists and can also display according to line level status – Available will display all Pickings with at least one line available. There has been change to the default status filter buttons applied for these documents to increase user-friendliness. The PDF of the OUT document has also been minimally revised to make better use of space.
We have implemented an improved default filter for the accrual list view, displaying only ‘draft’ and ‘running’ statuses by default for greater clarity.
We have implemented the Import Lines function to work similarly to the Invoice Lines function.
The import of accrual lines will now be used only for creating new accrual lines, not for updates.
We have ensured that the column names in UF are used as the column names in the import file:
Description
Reference
Expense account
Accrual amount booking
Cost center
Destination
Funding pool
Additionally, we have ensured that: Cost center, destination, and funding pool control for analytical compatibility as usual, and the import function allows comma-separated splits, as in the invoices/commitments import. Finally, we have frozen the header in the report.
We requested a PDF version of the Liquidity Balance report, which was previously exportable only in Excel from the accounting report.
The changes implemented included the following:
We allowed the report to be exported in PDF format.
We added a header that includes the date and time of export, the instance code, the page number and total pages, as well as the report header and name: “Liquidity Balance Report.”
We displayed values in EUR, not just the local currency, by adding two additional columns:
Closing balance
Functional/output value currency
We included a sub-total per currency and a general total in the output currency.
We renamed the file to follow the format: “Liquidity Balance Period FY Instance yyyymmdd,” e.g., “Liquidity Balance P15 2024 BD_DHK yyyymmdd.”
We added an option to select a currency table and display the currency.
We also added the possibility to generate the report in a display currency without selecting a currency table. For reports generated over multiple periods without a chosen currency table, each month’s own currency rate is applied.
In the asset form, we created a new field called “Instance of use”. This new field is populated by default with the instance where the asset is being created. If the asset needs to be transferred, the field will be updated to reflect the instance where the asset is being transferred to. Only the coordination (coordo) will have the ability to change this field.
To restrict the “instance of use” field, it is now limited to active UF proprietary instances, and selections are only available within the mission (excluding intermission and intersection transfers).
Once the “Instance of use” field is available, we will synchronize the asset form in the Open status (where the asset code is present) to the instance specified in this field.
When an asset is transferred from one project to another, based on the “Instance of use” field, the asset form will be synchronized in Open status with the remaining value. The instance from which the asset is transferred will have the event type “Transfer to Asset Owner,” which will be treated as a disposal-type event, similar to a sale. The receiving instance will have the asset form in Open status.
Regarding fields on the asset form:
A. Transferred Fields: These include the “Header”, “Asset Form” tab, and “Event” tab.
B. Manageable/Editable Fields: Only the receiving instance will be allowed to add events and edit the “Comment” and “Traceability” sections in the main tab.
Draft Status: No synchronization; all fields are editable.
Open Status: The analytical Distribution needed; the form gets synchronized to the “Instance of use” The following fields are editable: asset reference (serial number, brand, type, model, year) and account codes.
Running Status: The analytical Distribution is needed; only the “Asset Reference” fields are editable.
Closed Status: No further changes are allowed.
C. Depreciation: Depreciation can only be done by the COO and will be visible at project level.
In Accounting/Configuration/Financial Accounting/Accounts/Accounts, the core team has confirmed the possibility of implementing the manual configuration on the Chart of Accounts, available only for account codes of type “Expense”, to restrict accounts codes for fixed assets on HQ entries.
Under “Accrual Account”, we have added the following option: “Prevent Fixed Assets on HQ Entries”.
Error message: “The account 6xxxx could not be capitalized” (Note: “6xxxx” refers to the account code of the selected line.)
We have put in place the following statuses for the fixed assets: draft/open/active/fully depreciated/disposed.
Draft:
This status is applied when an asset is generated from SI or HQ entries(we will see this at the bottom of the asset form).
It can be deleted when manually created. If it was a mistake from HQ entries or comes from an invoice, it should be marked as “Disposed.” So it has to be put into Open and then “Dispose”:
Open:
This status allows synchronization and filtering to begin depreciation (by clicking “Compute Lines”).
When the asset is validated in the asset form, clicking the “Open” button generates the asset code, and the asset becomes “Open.”
We can either compute the lines or delete them.
The “Cancel” button has been replaced by the “Dispose” button (similar to the one used for the “Running” status).
The “Delete Lines” button has been retained.
Active (previously named “Running”):
This status is applied when asset entries are generated as “Posted” or “Unposted.”
The “Dispose” button has been kept.
Fully Depreciated:
The asset’s useful life is over, but the asset is still in use. It remains on the balance sheet.
When exporting the PDF of the selector search result, it includes the instance name, report date, list of account codes, list of journals, and status – these fields are all necessary.
We have added the following details to the header for better precision when generating the report:
With this development, Unifield is now able to find and pull information from UniData API so that UniField users can now see which products have been merged in UniData.
UniField now pulls all Product Nomenclature levels of Family and Root from UniData to UniField. For Root nomenclatures which are archived, this status “Archived” is now visible in UniField. Account codes from Families are now taken from UniData and used to update product categories in UniField.
The UniData Sync Report now contains additional information too.
Date of production synchronization server patch: 25th September 2024 / 18:00 Geneva time
Latest user rights files updated: UF34.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.
This issue, spotted by OCG was a bug affecting the display of certain figures on PDFs such as Freight Manifest in the SHIP, the Destruction report and the PO merged report, meant that the figures were obscured due to overlapping, and this was caused by a change to how the figures were rounded, and is linked to previous migration of python version. This has now been corrected and these reports are now displayed correctly.
We have added an additional check for the import from Homere to Unifield: If the name, code terrain and id staff are the same in PERMOIS and in UF, but 2 records exist in UF, add also a check on the uuid and allow the import of Permois if it matches.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
