1       Release Details

Release version: UF 39.0

Date of production synchronization server patch: 3rd December 2025 / 18:00 Geneva time

Latest user rights files updated: UF39.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12554

2       Supply

2.1        (US-14656, US-14564, US-14563, US-14561) Improvements linked to the E-validation on POs and INs

A set of improvements related to E-validation introduces additional restrictions on modifying signatures for Confirmed, Closed, or Canceled POs. If a PO uses E-validation, a warning message now clearly explains the steps the user must follow to edit a locked PO.

Additionally, the “Approved By” and “Value” fields have been removed from the IN signature table.

2.2        (US-12585, US-14295, US-14482, US-14483, US-14484, US-14485, US-14486, US-14487, US-14488, US-14495, US-14508, US-14557, US-15045, US-15046, US-15052) New module: Transport & Customs

A new Transportation & Customs Module is introduced with the following objectives:

The module is not active by default and can be enabled per instance via:
Administration → Configuration → Reconfigure.

2.3        (US-14291, US-15050) PO allocation report introduces a line status

Compared to the previous UF version, the PO Allocation Report includes minor changes to column names and introduces a new column displaying the status at the line level.

2.4        (US-14787, US-14547, US-14491) PO unit price deviation PO Vs Catalogue

With these improvements in the PO Catalogue tab, users can now see the positive or negative price deviation per unit in the PO compared to the supplier’s catalogue, when applicable. The deviation is shown at the line level, and the header displays the total percentage deviation between the PO subtotal and the theoretical catalogue subtotal (for catalogue lines only). Additionally, the readability of the PDF PO report has been improved, ensuring that comments are split correctly. The “Date sent” field has also been renamed to “PO Confirmed Date.”

2.5        (US-14672) Update the non-kept local code with a new code when it is merged with a UD code.

When a local code is merged with a UD code (via manual process), the “New code” field in the non-kept PMD is updated with the kept UD code. This action is available in Coordination and will sync down to the projects.

2.6        (US-14600) Improvement to Shipment dashboard default view

In Warehouse → Delivery → Shipment, the existing default “Not empty” filter is complemented with two additional default filters: “Draft” and “Ready to Ship.”

2.7        (US-14570) Order Category Filter added on IR

A new Order Category filter has been added to the Internal Request (IR) list view page. This aligns the IR view with the existing functionality available on PO, FO, and most warehouse documents. The filter is implemented as a drop-down selection, similar to the one used in the Incoming Shipment list view.

Additionally, a new Order Category column has been introduced in the IR list view to improve visibility and sorting options.

2.8        (US-14458) Supplier Catalogues – search bar item code

In Partners → Suppliers → Supplier Catalogue, a new filter by product has been added. This allows users to search for a product code across both active and inactive supplier catalogues.

2.9        (US-14296) Intersection flows – unblock the restrictions on local code

The ticket aligns the behaviour between Intersectional and Intermission flows by allowing the use of local codes in intersectional transactions. With this improvement, the restriction introduced in US-12176 is lifted, and local codes can now be used in Intersectional flows.

When a user tries to validate a PO/FO for an IS Partner containing local products, a non-blocking warning message will appear (one message for all product codes):

“Warning! Line(s) XXXX (line numbers & product codes) contain Local products (which may not synchronise). Please check if these can be replaced with a UniData code, or contact your help desk for further support.”

2.10     (US-14001) Products Likely to Expire Report – AMC Calculation Revision

Several enhancements have been added to Warehouse → Reporting → Expiry → Product Likely to Expire.

A new consumption option, RR-AMC, is now available. When selected, an automatic explanation appears:

“The RR-AMC (Average Monthly Consumption) lets you choose one or more internal source locations, and one or more destination locations so you can view consumption based on specific locations, ECUs or External Partners.”

This note appears only when RR-AMC is selected.

When using RR-AMC, selecting a Source Location becomes mandatory (highlighted in blue). RR-AMC calculations use only the selected source location, and a destination is not required.

The field previously named “Location” has been renamed to “Source Location.”

When the AMC – Average Monthly Consumption option is selected, the Source Location field is no longer displayed.

2.11     (US-13340) Update of Unreserved product Report

In Warehouse → Reporting → Unreserved Stock Report, the report will now show only the lines where the stock level is greater than zero. Previously, the report also displayed lines with negative stock, but these will no longer appear.

2.12     (US-13381, US-14946) Pre-Packing List Export – New Packing Type Selection and Validation

A new improvement allows users to export a pre-packing list that includes all active packing types in the instance. The exported Excel file now contains a drop-down list enabling users to select a packing type, and the dimensions of the selected pack are automatically filled into the corresponding columns.

To ensure data consistency, UniField now blocks the import when a single parcel range contains more than one packing type. In such cases, the following message is displayed:

“Parcel From 1 To 1 contains multiple pack types. Please assign only one pack type per parcel.”

The same message appears if a parcel range mixes assigned and non-assigned pack types.

2.13     (US-12542) RFQ – New Import and Export Buttons

Two new buttons have been added to the RFQ, similar to the functionality in validated POs. For RFQs in the “Sent” status, the existing “Import RFQ” button has been replaced with two buttons: “Import RFQ” on the left and “Export RFQ” on the right. Clicking “Export RFQ” allows users to export the modified RFQ file. Clicking “Import RFQ” enables users to import a file that updates the Price and Confirmed Delivery Date fields, while modifications to other columns are not allowed. The Header “Valid Till” field can also be updated via the import file.

2.14     (US-14978) Issue generating Stock Mission Report

Consolidated Mission Stock cannot be generated when the number of columns exceeds 256. This limitation is linked to the format of the generated XLS report.

A temporary fix has been introduced: the system now blocks the generation of the consolidated mission stock when the number of columns exceeds 255 and displays a clear error message advising the user to generate the MSR per individual instance.

A permanent solution will be delivered in the next release, as it requires changing the report format for both the Consolidated MSR and the standard MSR.

2.15     All Supply tickets integrated in UF39.0

Key	Summary	Detailed
US-14656	E-Validation: Incoming Shipment Order Of Signees with PDF	X
US-14564	E-Validation: Possible to modify Signees on Closed PO	X
US-14563	E-Validation: Correction to PO E-Signature Controls	X
US-14561	E-signature IN – “value” to be renamed “Total Quantity”	X
US-15052	Custom and transport partial reception of ITO: button clear all provokes Fix me	X
US-15046	(US-14557) Duplicated ITO/OTO references in PO linked documents	X
US-15045	(US-14486) Error while trying to create an ITO through IN VI auto-import	X
US-14557	To add a PO ref to Custom and Transport tab	X
US-14508	Custom and transport module: ITO to make custom regim a mandatory field	X
US-14495	Custom and transport module: Standardization of steps	X
US-14488	Custom and transport module: Zone Type; to have only international and Domestic	X
US-14487	Custom and transport module: transport mode to add MSF plane an rename “Air” to “Air Commercial”	X
US-14486	Custom and transport module: Auto VI: International order prefilled header and lines	X
US-14485	Custom and transport module: ITO/OTO Cargo Type to remove Service from Dropdown list	X
US-14484	Custom and transport module: ITO/OTO to rename “Single” shipment flow to “Direct”	X
US-14483	Custom and transport module: to include Transport fees Tab	X
US-14482	Custom and transport module to rename Custom fees	X
US-14295	To introduce info tags in Custom and transport module on Custom Field	X
US-12585	Transport Module – Functional specs 1	X
US-15050	(US-14291) PO Allocation reports display header state instead of line state at line level	X
US-14291	Allocation Report – To Add Line Status	X
US-14787	PO – comment not spleeting in
US-14547	Change Name of PO Date Sent Field	X
US-14491	Tab supplier catalogue	X
US-14696	BUG: Report donation of UF in French with no translation (terms still in English)
US-14672	to update non -kept local code with a new code in case if it is merged with UD code	X
US-14605	“New code” filled in some products in UF	X
US-14600	Improvement to Shipment dashboard default view	X
US-14570	Internal Request: Add Order Category Filter	X
US-14458	Supplier Catalogues – search bar item code	X
US-14296	Intersection flows – unblock the restrictions on local code	X
US-14001	Products Likely to Expire Report – AMC Calculation Revision	X
US-13381	Export Packing – Add the instance’s Pack Types	X
US-13340	Unexpected behaviour for unreserved stock report	X
US-12542	RFQ – new export / import to include header on excel file export	X
US-14916	Error msg not clear for importig ADs to FO
US-14865	Ignoring Concurency pop-up message on RfQ creates extra lines on PO	X
US-14593	Revision of Approved By in the Reception PDF	X
US-14573	Claims: to block manual correction of Claim Reference	X
US-14946	Block import of Packing List when a parcel sequence includes more than one parcel type
US-14945	Parcel numbers are not displayed correctly in SHIP
US-14639	Vertical Integration: Missing Sequence Error E-PPL update of error mesage
US-14978	OCBAF101 – Issue generating Stock Mission Report	X

3       Finance

3.1        (US-14182) Liquidity Balance report from HQ: to see all journals with registers in the selected period

We have developed an adjustment to the report criteria so that a journal is listed if a register has been created for the period or if the balances are not zero.

3.2        (US-14217) Use of periods 13, 14 and 15: to add a configuration with booking conditions

We have developed and implemented the requested enhancement, viewable in the “Companies” menu under the “Configuration” tab.

A new mandatory dropdown field named “Extra Accounting Behavior” has been added. This field becomes read-only once the instance is created, to prevent discrepancies and ensure consistency across instances.

The dropdown includes three predefined options, each corresponding to specific booking permissions for periods P13, P14, and P15:

As this field is read-only after instance creation, changes (e.g., switching from OCB to OCA behaviour) will not be possible via this configuration.

3.3        (US-14629) Functional total value of CV (supplier commitment voucher)

 We have developed and deployed the requested enhancement on the CV form and list views.

• • for OC reporting in EUR
  • for OCG reporting

This improvement aims to enhance visibility.

3.4        (US-14894) OCP – Prevent activation of Employee “not to be used”

We have implemented the requested control in the Human Resources tab.

For employees flagged as “Not to be used”, the system now prevents users with coordination rights from setting their status to “Active”. If such an action is attempted, a warning message is displayed:

“You cannot activate an employee flagged as not to be used.”

 (French: “Vous ne pouvez pas activer un employé marqué comme ne plus utiliser.”)

This measure was introduced to ensure data consistency and avoid unintended reactivation of inactive employee records.

3.5        (US-14849) Addition of track changes to the field “not to be used” in the employees form

We have added the track changes feature to the “Not to be used” field in the employee form.

This enhancement allows for better tracking and review of any updates made to this field, ensuring improved auditability and accountability in employee data management.

3.6        (US-14872) Exportable field Supplier invoice: additional information

We have implemented the requested export enhancements in the Supplier Invoice (SI) module.

If the invoice line is split across multiple analytic dimensions, all elements are displayed with a separator (no percentage shown), ensuring full visibility of the allocation.

These changes are export-only and have no impact on the user interface or manual data entry.

3.7        (US-14923) Adjustment of warning message for freezing closing balance

We have updated the warning message implemented under US-12267 to improve visibility and reduce user errors during period closing.

Previously, the red warning message was displayed above the “Cancel” and “Confirm” buttons, which made it easy for users to overlook the message and mistakenly freeze the balance of the current period while closing the previous one.

To address this, we have:

These changes aim to reduce the risk of accidental actions and improve the overall user experience during period closing.

3.8        All Finance tickets integrated in UF39.0

Key	Summary	Detailed
US-14182	Liquidity Balance report from HQ: to see all journals with registers in the selected period	X
US-14217	Use of periods 13, 14 and 15: to add a configuration with booking conditions	X
US-14629	Functional total value of CV (supplier commitment voucher)	X
US-14649	CC retargeted to other instance not synced with DEST configuration
US-14666	OCP_PH1_COR: Invoice from Supply flow wrongly created in the ISI journal
US-14697	Manual upgrade process : to remove the current warning message related to unbalanced entries
US-14849	To add the track changes to the field NOT TO BE USED in the employees form	X
US-14872	Exportable field Supplier invoice: to add additional informations	X
US-14894	OCP – prevent activation of Employee “not to be used”	X
US-14923	Please displace to the middle of the screen and make bigger the warning message from US-12267	X
US-14972	Financing contracts: python error to fix

4       Non- functional

4.1        (US-15077) Change to AiO to ensure new password is entered

This change means that at the password addition stage of AiO installation, there is no default password already there, meaning user must enter a new password for each field.

4.2        (US-14985) Better visibility for multi-instance servers

This development has 2 components: i)where a server contains multiple UniField databases, where the filter is set so that the URL displays a targeted database (by default), this instance will be displayed by default as the selected instance on the login page.  As only one of the instance on this server will act as the master for the synch server user connection, this “master” instance will be displayed on the login page also.

4.3        (US-14930, US-14905, US-14886) APIs developed for WaCA HQ

APIs have been developed based on WaCA’s request for integration with their planned HQ Accounting system. Tables have been made available to export Local employees, Partners and Journals.

4.4        (US-14936, US-14926) Update on data push linked to SharePoint locations.

These 2 tickets already implemented for OCA have now been released meaning that files are not blocked due to folder layers or zipper folders in destination locations for SharePoint exchanges.

4.5        (US-14107) Upgrade of version PostgreSQL: from 14.19 to 14.20

With this release, the version of PostgreSQL has been upgraded to 14.20.  All instances having a recent version of PSQL will automatically be upgraded. However those with v.9.6 will not be as they require manual intervention.

4.6        (US-14875) URL link for instance/database is case insensitive

This change means that UniField will recognise/accept instance name which is in URL no matter the case (upper case and lower case characters).

4.7        All Non-functional tickets integrated in UF39.0

Key	Summary	Detailed
US-15077	Change to AiO to ensure change of password	X
US-14985	Show database count for aggregation servers with database list filtered by URL	X
US-14936	Auto VI Config update (filepaths / method) for push to sharepoint	X
US-14930	WaCA HQ VI: VI export for Journals	X
US-14926	Back up files to be pushed to sharepoint folder location despite zipped file	X
US-14905	WaCA HQ VI: Test using VI export for Local Employees	X
US-14886	WaCA HQ VI: Test using VI export for Partners	X
US-14875	db field in URL to be case insensitive	X
US-14107	Upgrade of version PostgreSQL: from 14.19 to 14.20	X

Release Details

Release version: UF 38.1

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

Latest user rights files updated: UF38.1 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12551

1       Supply

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

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

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

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

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

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

1.4        All Supply tickets integrated in UF38.1

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

2       Finance

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

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

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

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

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

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

2.4        All Finance tickets integrated in UF38.1

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

3       Non- functional

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

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

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

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

3.2        All Non-functional tickets integrated in UF38.1

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

1       Release Details

Release version: UF 38.0

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

Latest user rights files updated: UF38.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12546

2       Supply

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

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

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

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

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

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

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

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

Also some modifications are introduce in Local codes creation process.

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

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

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

2.3        (US-13333) Merge 2 local codes

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Phase Out Principle (similar to code deactivation flow)

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

Partner (Phase out) in different Configurations

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

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

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

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

The deletion configuration is defined at instance level.

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

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

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

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

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

Additionally, when RR-AMC is selected, an explicit explanatory message will be displayed: “The RR-AMC (Average Monthly Consumption) lets you choose one or more internal source locations, and one or more destination locations so you can view consumption based on specific locations, ECUs or External Partners”.

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

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

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

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

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

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

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

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

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

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

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

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

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

2.16     All Supply tickets integrated in UF38.0

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

3       Finance

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

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

Implemented Behavior:

EoY Revaluation Restriction:

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

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

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

WeFin Automation:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Behavior Implemented:

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

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

This enhancement improves usability and ensures consistency across screens.

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

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

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

Generation of an unposted depreciation entry

Deletion of an unposted depreciation entry

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

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

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

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

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

With this update:

These fields can no longer be edited at project level.

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

This change ensures consistency and prevents unauthorized modifications.

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

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

What We Observed:

Journals were inactivated while entries were still pending synchronization.

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

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

This synch rule has been fixed to avoid this problem.

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

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

What We Observed:

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

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

What We Have Done:

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

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

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

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

Renamed Existing Tab

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

Created New Tab

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

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

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

Content Logic

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

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

These figures are based on actual production data.

Wizard Enhancement

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

Reference Setup

The report includes:

Account codes configured as REVAL in the company settings.

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

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

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

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

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

What Has Been Done:

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

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

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

Export Availability Matrix:

HQ Instance

Coordination Instances

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

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

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

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

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

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

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

What Has Been Done:

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

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

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

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

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

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

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

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

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

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

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

3.18     All Finance tickets integrated in UF38.0

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

 

4       Non- functional

4.1        (US-14173) Upgrade to Python version 3.13.7

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

4.2        (US-14106) Upgrade to PostgreSQL version 14.19

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

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

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

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

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

4.5        All Non-functional tickets integrated in UF38.0

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

1       Release Details

Release version: UF 37.1

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

Latest user rights files updated: UF37.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets:

https://jira.unifield.org/issues/?filter=12543

2       Supply

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

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

2.2        All Supply tickets integrated in UF37.1

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

3       Finance

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

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

3.2        All Finance tickets integrated in UF37.1

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

4       Non- functional

4.1        (US-14500) Aggregation Server landing page

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

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

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

4.2        All Non-functional tickets integrated in UF37.1

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

1       Release Details

Release version: UF 37.0

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

Latest user rights files updated: UF37.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12539

2       Supply

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The following rules apply to the new field: 

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

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

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

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

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

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

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

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

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

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

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

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

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

2.18     All Supply tickets integrated in UF37.0

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

3       Finance

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

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

The report can be issued in PDF and Excel formats.

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

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

After this deletion, we can generate the entries again

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

For register lines:

For Journal Items:

Error messages:

3.9        All Finance tickets integrated in UF37.0

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

4       Non- functional

4.1        (US-14040) Cleaning users_last_login.date

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

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

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

4.3        (US-14124) Cleaning ir_property table

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

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

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

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

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

4.6        All Non-functional tickets integrated in UF37.0

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

1      Release Details

Release version: UF 36.0

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

Latest user rights files updated: UF36.0 can be found here

Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.

JIRA filter for all integrated tickets:  https://jira.unifield.org/issues/?filter=12534

2      Supply

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The new “Qty Received” column will display: 

– 0 if nothing has been received. 

– N/A if no IN is available. 

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

Additionally, column names have been adjusted as follows: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2.14    All Supply tickets integrated in UF36.0

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

3      Finance

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3.13    All Finance tickets integrated in UF36.0

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

4      Non- functional

4.1       (US-13755) Drop column res_users.date

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

4.2       (US-13788) Consolidation of users email columns

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

4.3       (US-14050) Patch to upgrade PostgreSQL version

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

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

4.4       All Non-functional tickets integrated in UF36.0

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

1       Release Details

Release version: UF 35.0

Date of production synchronization server patch: 11^th 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.

JIRA filter for all integrated tickets:  https://jira.unifield.org/issues/?filter=12521

2       Supply

2.1         (US-13166, US-12885, US-11182, US-12727) Electronic Validation: PO restrictions, Signature follow up accuracy, inclusion of Physical Inventory which has new discrepancies PDF

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 2^nd 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.

2.2         (US-12228, US-12912, US-13640) Possibility to add Supplier ranking directly in Catalogue + Track changes added

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 “3^rd 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 “1^st choice”, “2^nd choice” etc until “12^th 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.

2.3         (US-12415) New IR export/import template for Products in Product List

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.

2.4         (US-13332) IN with VI pack “Process to ship” not blocked by Expired goods

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.

2.5         (US-13203) Export FO Follow-up: Addition of line comment

In the extract of Export FO Follow-up report a new column “Comment” which lies between columns “Description” & “Qty ordered” has been added.

2.6         (US-12564) Export FO Follow-up: Addition of line comment

In the extract of Export FO Follow-up report a new column “Comment” which lies between columns “Description” & “Qty ordered” has been added.

2.7         (US-12564) Export Inventory Level: Filter for 0 or negative stock can be applied more widely

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.

2.8         (US-12333, US-12201, US-11803) Picking/Transport documents clearer statuses

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.

2.9         All Supply tickets integrated in UF35.0

Key	Summary	Detailed
US-13731	(US-12201) Picking ticket filters for Available / not available
US-13718	(US-12228) Supplier catalogue ranking	X
US-13705	(US-12885) E-validation” Signatures follow up – extras for consistency.
US-13692	US-13166 E-Validation PO Controls: remove CDD requirement etc	X
US-13690	(US-13649) Fix the display of expiry date in the PI discrepancy report
US-13669	(US-13332) show expired BN/ED in red in IN for this flow
US-13649	(US-11182-12727) Fix the Physical Inventory discrepancies import
US-13640	Add ranking to the Track Changes of the catalogue	X
US-13530	OCA VI: Auto VI new Catalogue import rejected – warning due to inexistant products
US-13332	IN with VI pack “Process to ship” not blocked by Expired goods	X
US-13203	Export FO Follow-up: Add line comment	X
US-13166	[E-Validation] Purchase Order E-signature Controls	X
US-13142	BACK ORDER GENERATED AFTER A FULL RECEPTION
US-12912	Supplier catalogue – having track changes	X
US-12885	E-Validation: “Signature Sub Module” Signatures follow up Improvements	X
US-12727	Physical Inventory (partly E-validation related) New PDF & changes to excel Discrepancy report	X
US-12564	Export Inventory Level – Use of MML filter includes items with 0 stock	X
US-12415	IR : Import lines / Export option with prefilled template of Product List	X
US-12333	Update INT Move Statuses and Form View	X
US-12228	SUPPLIER CATALOGUE Supplier ranking	X
US-12201	Update of Confirmed Status on PICK	X
US-11803	Request for Improvement to the Delivery Order	X
US-11182	E-VALIDATION for Physical Inventory	X

3       Finance

3.1         (US-13465) Accrual management default filtering: draft and running statuses

We have implemented an improved default filter for the accrual list view, displaying only ‘draft’ and ‘running’ statuses by default for greater clarity.

3.2         (US-12530) Import Accruals Lines: Import lines function similar to invoices lines function

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.

Example of import file:

3.3         (US-13322) OCA : Improvement in the liquidity balance report (legal 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:

1. We allowed the report to be exported in PDF format.
2. 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.”
3. We displayed values in EUR, not just the local currency, by adding two additional columns:
   • Closing balance
   • Functional/output value currency
4. We included a sub-total per currency and a general total in the output currency.
5. We renamed the file to follow the format: “Liquidity Balance Period FY Instance yyyymmdd,” e.g., “Liquidity Balance P15 2024 BD_DHK yyyymmdd.”
6. 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.

3.4         (US-13091) Expat import file fail when the column “Contract End Date” has no value

We have fixed a bug to allow the import of expats through “Human Resources” even when the “Contract End Date” column is empty.

3.5         (US-13515) Fixed Asset: Asset Reference field to be editable in Open, Active and Fully depreciated statuses

In the asset form:

3.6         (US-13415) Fixed Asset: synchronization of the asset form from Coordination to the Instance of use

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.

3.7         (US-13262) Fixed Assets International procurement : HQ entries tagged as “assets” (to be done with US-13480)

At the time of validating HQ entries, we improve the process by implementing the following:

• When the asset box is ticked, the mandatory account field is emptied, and the user can only select an Asset Balance Sheet Account in this field.
• When the asset box is unticked, the account field value is replaced by the original account sent by HQ.

---

For validating HQ entries, we do the following:

• For HQ journals, we apply a debit to the expense account and a credit to the regular HQ entries Balance Sheet (B/S) account.
• For ODHQ entries, we apply a credit to the expense account and a debit to the Balance Sheet account.
• A draft asset form is created as part of the process.

It is now possible to change the “Divisor Quantity” field on draft asset created from HQ entry

3.8         (US-13480) Fixed assets: to add account code restrictions on US-13262 Prevent fixed assets on HQ entries

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.)

3.9         (US-13546) Fixed assets: to change statuses draft/open/active/fully depreciated/disposed

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.

Disposed: 

3.10      (US-13321) G/L selector PDF export: Improve the header by adding 2 fields: “currency table” and “output currency”

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:

• Amounts and Currency fields:
  • Currency Table
  • Output Currency

3.11      All Finance tickets integrated in UF35.0

Key	Summary	Detailed
US-13465	Accrual management default filtering: draft and running statuses	x
US-12530	Accruals: Import lines function similar to invoices lines function	X
US-13454	OCA VI Finance accruals: OCA asks to reverse the effect of US-12590
US-13322	OCA : Improvement in the liquidity balance report (legal report)	X
US-13091	Expat import file fail when the column “Contract End Date” has no value	X
US-13515	Fixed Asset: Asset Reference field to be editable in Open, Active and Fully depreciated statuses	X
US-13415	Fixed Asset: synchronization of the asset form from Coordination to the Instance of use	X
US-13262	Fixed Assets International procurement : HQ entries tagged as “assets” (to be done with US-13480)	X
US-13282	Fixed Assets: Cancel button of [disposal screen] brings “an application error has been reported”
US-13390	Fixed assets import file: asset type not localized
US-13480	Fixed assets: to add account code restrictions on US-13262 Prevent fixed assets on HQ entries	X
US-13546	Fixed assets: to change statuses draft/open/active/fully depreciated/disposed	X
US-13422	Fixed assets: To add entry line missing at End of use of an asset form (to set the asset to 0 as “out of the accountancy”)
US-13291	OCA: Remove default destination for header AD Supply – Finance
US-13321	G/L selector PDF export: Improve the header by adding 2 fields: “currency table” and “output currency”	X
US-13646	G/L selector + currency table: use current date for fx conversion
US-13567	OCP Workday / WeFin: store Arcole id and regenerate export on period re-open
US-12517	To remove the not runs with model “account.invoice.create_invoice” for the intersection/intermission cases when the partner is inactive
US-13719	Patch script OCA CoA expense account linked to US-13480
US-13711	OCB vertical interface, matching export, ocb_vi_export_number missing from lines

4       Non- functional

4.1         (US-13192) Additional Product information pulled from UniData: Merged products and Nomenclature family & root and status of Root.

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.

4.2         (US-12409) How to edit major fields on supplier after instance of creation is decommissioned

At coordo level, it is now possible to edit a partner belonging to a decommissioned project

4.3         All Non-functional tickets integrated in UF35.0

Key	Summary	Detailed
US-13644	UD Pull: some UD merged prod reactivated
US-13384	Discrepancies between UF and Windows when monitoring time spent to execute a sql query. To fix UF internal sql monitor
US-13242	OCA Automatic VI : when run PO export job pushed error msg displayed
US-13192	Unidata API : Get all articles + new API for family	X
US-13020	Groups: standard export, “Fields to export” prefilled with empty lines
US-12781	Force auto sync when connecting the connection manager
US-12409	How to edit major fields on supplier after instance of creation is decommissioned	X

1       Release Details

Release version: UF 34.1

Date of production synchronization server patch: 25^th 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.

JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12516

2       Supply

2.1        (US-13135) Bug on figures displayed in certain PDF reports

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.

2.2        All Supply tickets integrated in UF34.1

Key	Summary	Detailed
US-13137	Bug on figures display on FM document (PDF)	X

3       Finance

3.1        (US-13452) Add the UUID check in the permois import V2

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.

3.2        All Finance tickets integrated in UF34.1

Key	Summary	Detailed
US-13452	Add the UUID check in the permois import V2	X
US-13466	OCP_HQ: Liquidity Balance Failed: Traceback (most recent call last)

1       Release Details

Release version: UF 34.0

Date of production synchronization server patch: 11^th September 2024 / 18:00 Geneva time

Latest user rights files updated: UF34.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/?jql=project%20%3D%20US%20AND%20issuetype%20in%20(Bug%2C%20Improvement)%20AND%20fixVersion%20%3D%20UF34.0

2       Supply

2.1        (US-13209, US-12606) Multiple concurrent Supplier Catalogues allowed

Continuing in the direction to encourage use of catalogues, these tickets facilitate catalogues to be more user-friendly by allowing one supplier to have multiple valid catalogues. The main constraint is that the concurrent catalogues must have different products. The dates can overlap or be different. Blocking warning will be displayed if users try to import or create manually new catalogues with duplicate products or if they try to update existing ones with duplicate products. Other modifications included are that now all catalogues will have From & To dates visible at header level and these can be changed in instance where they were created. Previously, where a catalogue had an empty “To Date” this was automatically filled when a more recent catalogue for the same supplier was added. With these tickets there is now no automatic filling of To Data done by system.

2.2        (US-12323, (US-12916, US-11496) New & updated Donation Reason Types and additional filters in Donation report

Initially raised via discussions with Pharma and in order to align more closely with Pharma guidelines as well as operational needs of Supply, a new Order Type (OT) and Reason Type (RT) “Programmatic Donation” has been added to FOs and their associated transport documents. This Order type can be selected in FOs and there will be a non-blocking warning message indicating that goods flow out will be considered as consumption. FO with this OT must have an external partner and the FO can be sourced normally in the OST to any other purchase doc or from stock as per other FOs. Any transport documents (OUT, Pick etc) associated with an FO with this order type will also have the Reason Type “Programmatic Donation” and their goods will be considered to have been consumed, and their quantities will be included in the consumption calculation. This additional Order / Reason type has been added to relevant existing reports.

The Order/Reason Type previously know as “Donation before Expiry” has now been renamed as “Donation to prevent losses”. There is no change to how this OT/RT can be selected or used. All documents with previous OT/RT have been migrated to new name.

The existing Donation report has been updated to include filters for the possible Donation types.

2.3        (US-13345, US-12891, US-13351) Electronic validation modifications & corrections

The electronic validation module continues to be refined and improved with these tickets. In the Supply documents IR, PO and FO, signatures will be allowed to be added only in Draft and Validated status. Other documents remain without this constraint and can be signed no matter their status.

2 corrections have been made so that i)when documents are partially signed and then decision to sign offline is taken, all previous signatures & signee roles are now fully wiped from document. Track changes still keeps a record of these changes. ii) There is now no duplication of roles displayed for when  a document which has its order of signees defined, has an attempt made signee whose role is not the next sequential signee allowed to sign.

2.4        (US-11560) Possibility to merge 2 products (Local & UniData) even if both used

With this ticket, merge of product behaviour is aligned so that for all pairs of products where merge is possible, the merge can be done even when both products have been used. Previously this scenario was possible only for merge of 2 UniData products at HQ. With this ticket merge is possible also at Coordo when both Local & UniData product have been used.

2.5        (US-13037, US-13035) PMD: Modification of product fields at Coordo to not be overwritten by synch + Track changes

With this ticket the following fields in the Product record at Coordo will not have their values overwritten by any synch updates (from HQ etc): “Procurement method”, “SoQ Quantity”, “Field description”, “Purchase description” “Procurement lead time”.

Additionally, for any change to the field “Procurement method” Track changes has been added.

(The relevant User Rights ticket for access is being progressed in parallel.)

2.6        (US-11560) FO/PO created by synch with unrecognised product – more transparency for inexistent products

This ticket aims to ensure PO and FO documents created by synch are more transparent for users when they contain lines for products which do not exist in the instance. When such lines are created in a PO/FO, the “Comment” field will be filled with the code & description of the product according to the other instance, as well as any comment they added to the line. The line will be in red & contain a warning icon, if line pop-up is opened it will direct user (according to the product type) for how to handle situation (subscribe in UniData / see with mission etc). There will be a Not Run message for this case. If product is then created in instance (e.g. Subscribed to in UniData & synched down) then the Not Run will pass and the document line will be updated at next synch. If product remains inexistant user may choose to cancel the line from the PO/FO. Without any recognised product, the document line cannot be processed further.

2.7        (US-11573) Product list can only be modified at instance where created

Development done so that only the creator instance can modify a product list at header or at product line level.

2.8        (US-12520) Cancelled lines to be excluded from Export Pick excel

Exported pick lines will no longer display cancelled lines, the user will only be able to see lines with other stock moves states in the export, which is consistent in case the user needs to import pick.

2.9        (US-12612) “Order Category” added to Export IR/FO Follow-up reports

More filters have been added to both “Export IR Follow-Up” and “Field-order Follow-up” to give better visibility of these documents, the filters are consistent with the relevant IR/FO that contains these fields.

2.10     (US-12896) PO & RFQ – change of currency only possible via button

In both PO and RFQ the user will no longer be able to edit the currency through the “Currency” field, the only option to change the currency will be through “Change Currency” button.

2.11     (US-12955) Additional option for line level filter on order documents

In all the following documents IR/FO/PO a new filter option has been added for the document lines filter. New option: “Show validated only”, when selected will display only lines with validated state.

2.12     (US-12981) Unit Price displayed in IN & SHIP

With this dev, product unit/cost prices are more transparent in INs and Shipping process: unit price of product is now displayed for each line on incoming shipments (INs) and also in Shipments Pre-Packing List (SHIP PPL line pop-up).  How and when these prices can be modified and are calculated remains unchanged, there is just better visibility of them in these documents.

2.13     (US-13084) Correction to Claim flow for lines assigned to incorrect IN

This ticket corrects an issue linked to Claim flows where as soon as a Claim was processed where replacement goods were expected, the Claim created an IN-replacement (IN to receive these goods) but if the original PO on which claim was raised continued to have further lines Confirmed, system was assigning these extra lines to the Claim IN rather than the IN linked to the regular PO flow.

2.14     All Supply tickets integrated in UF34.0

Key

Summary

Detailed

US-13398	Patch script to unmerge products in OCB instances
US-13345	E-Validation: PO Sign Offline: All previous signature info to be wiped from screen.	X
US-13209	(US-12606) Catalogue modifications	X
US-13123	Donation report: Additional filters – Order types	X
US-13037	PMD field “Procurement method” + others should not be overwritten by UniData / HQ updates	X
US-13035	Track changes to be added to PMD “Procurement Method” field	X
US-12520	Cancelled lines should be excluded from Export Pick excel	X
US-12612	To Add “Order Category” to Export IR/FO Follow-up reports	X
US-12934	Patch script to set empty Draft Picks to Closed for Ships to be Dispatched
US-12916	New Order and Reason Type: Programmatic Donation	X
US-12896	PO & RFQ – Change of Currency – only allowed via button	X
US-12891	E-validation: Document statuses to be linked to signatures IR, FO, PO	X
US-12740	Update merge of Local product with UD product functionality – merge should be possible even if both products have been used.	X
US-12955	New Line Level Filter “Show Validated Only” for (IR, FO, PO)	X
US-12606	Supplier catalogue – multiple catalogue same supplier different products	X
US-12981	Show Unit Price in supply (IN & SHIP)	X
US-11573	Prevent deleting lines in Synchronized product lists	X
US-11560	NR “Product Not Found” Change of Behaviour in synched PO/FO	X
US-11496	Reason Type (Order Type): exchange “Donation before expiry” to become “Donation to prevent losses”	X
US-13351	E-Validation: Signature Follow Up – Signee Roles Display Duplicated	X
US-13125	UD: Update on already-created MSL project causing Not Run in UF
US-13084	Confirmed PO lines sent to Claim IN	X
US-13024	To prevent the splitting of product lines with QTY 1 in the IN VI import,
US-12924	Shipment List view not displaying SHIP – correct display
US-12730	Issue with RFQ status / line status inconsistencies
US-12315	Correction of RFQs with “Cancelled” status: lines to be set to “Cancelled” too.

3       Finance

3.1        (US-12438) Fixed assets: To improve the filter in the Journal items of the assets forms : journal + instance (HQ-OCBAF101)

We have improved the filters for the journal items of the assets forms as follows:

3.2        (US-12479) Fixed assets: mandatory to have analytical distribution AD before the status OPEN (and just after status Draft)

It is now mandatory for an asset to have a valid analytical distribution (AD) before it can be set to “OPEN” status. If the analytical distribution is not valid, the asset cannot be moved to “OPEN” status.

If the analytical distribution is incorrect, you will receive an error message, and the asset cannot be moved to “OPEN” status.

3.3        (US-12654) Fixed Asset: inactivation of the functionality

With this ticket we have developed that the inactivation from reconfigure is not allowed if any of the following are present:

If you attempt to inactivate the functionality in those cases, you will receive an error message.

3.4        (US-13050) Homere interface – take employee from the new file staff_l

For the Permois import, we currently import a staff file into Unifield. However, some instances had an additional file, staff_l, which was not being considered by Unifield. In this release, we managed the second file by developing a solution to handle the staff_l file. We ensured that the staff_l file is now also imported into Unifield, alongside the primary staff file.

3.5        (US-13096) PAYE SAGA: Import of payroll entries: to improve the error message when there are already draft payroll entries

For the PAYE SAGA import of payroll entries, we have improved the error message that appears when there are existing draft payroll entries.

Updated Error Message:

“You cannot import payroll entries because there are XX draft expense lines and YYY draft balance sheet lines. Please validate the draft entries or click on ‘Delete draft entries’ to proceed.”

This enhancement ensures clarity and provides actionable instructions for addressing the issue.

3.6        (US-13260) Add the UUID check in the PERMOIS import

In cases where the staff name or one of the three fields (id_unique, id_staff, code_terrain) has changed, the PERMOIS import fails. This issue constitutes approximately 50% of the PERMOIS-related problems reported in Jira. We will address this in the UF34.0 release before revisiting the ticket US-9119.

During the payroll import, we have implemented a check to manage changes across multiple fields. If the employee’s name remains unchanged, the system allows the import to proceed; otherwise, it raises an error stating: “Several employees have the same Identification No xxx (import), zzz (UF).”

Additionally, we have incorporated a new check for the UUID. If either the name or UUID has not changed, the import is permitted to proceed.

3.7        (US-10871) For DPO: to allow Down Payment (specific supply case)

Thanks to this ticket we have allowed the down payments in Direct Purchase Orders DPO.

The flow will be this:

• Create the PO. Validate it. Sync.
• Sync. Create a draft FO. Validate the FO. Source the FO (Proc. Method: On Order, PO/CFT: DPO).
• Check the draft DPO in the Purchase Orders tab. Confirm the DPO.
• Confirm the DPO (no Invoices created; CV is created). Sync.
• Sync. Create the IN.
• Proceed with a Downpayment using the DPO in confirmed status (only confirmed status).

3.8        (US-12137) Intermission: to avoid the creation of a manual IVO and IVI with an inactive currency

With this improvement, we cannot create a manual IVO or a manual IVI with inactive currency at the time of creation:

• Instance A creates an IVO in a currency not active in Instance B.
• Instance A creates an IVI in a currency not active in Instance B.

We have ensured that there is a “not run” when an instance receives an IVI in an inactive currency.

3.9        (US-12283)  FY closing check – check if all active project instances have reported Mission closed status for all periods of the FY

For yearly closure:

Before allowing FY closing of a Coordination instance, check if all active project instances have reported “Mission Closed” status for all periods of the FY.

We must exclude decommissioned projects from this check.

Note that P0 and P16 periods are excluded from the check.

We will have an error message to indicate us this:

3.10     (US-12302) Allow to use multiple AD on CV commitment vouchers (changes made on US-11510 for supplier invoices)

We have allowed the use of multiple ADs on CV (Commitment Vouchers), similar to the changes made in US-11510 for supplier invoices.

It can be done by using the Export CV Lines and the Import CV Lines.

3.11      (US-12732) To be able to delete draft entries in mass in the liquidity registers
 We agreed to introduce the functionality to delete multiple register lines in bulk.

We have implemented here the capability to delete draft entries in bulk within the liquidity registers.

When an import file with 200 lines is mistakenly uploaded, it is currently necessary to delete each line individually.

In the register lines section, users will have the option to select multiple lines. A new button, labeled “Delete Draft,” will be added to the right menu to facilitate the bulk deletion of lines, provided they are in draft status only.

If an attempt is made to delete hard posted entries, a warning message will be displayed, and the operation will be blocked.

3.12     (US-12894) E-Validation: Allow Doc_Creator to Modify Signed Signatures

The proposed improvement allows users with the UR groups Sign_document_creator_supply and Sign_document_creator_finance to remove signees and reassign others across all document types, not limited to Purchase Orders. Users with the Sign_Doc_Creator roles can manage signatures by removing or reassigning signees. Users who have signed a document are restricted to removing only their own signatures, and this action is permissible only in specific statuses defined for signature management. This improvement ensures consistency in signature management across all document types, adhering to defined statuses that control the addition and removal of signatures. Additionally, once a document’s signature process is closed—signaled by clicking the “Close Signature” button and ticking the “Signature Closed” checkbox—no further changes to signatures are allowed.

3.13     (US-13237) Inactive currency to not be available to be used in SI, SR, ISI, ISR, Donation, STV, STR, Customer Refunds and Debit Note

For SI, SR, ISI, ISR, Donation, STV, STR, Customer Refunds, and Debit Notes, we have forbidden the selection of an inactive currency. The development was completed to block the selection of an inactive currency, both with the magnifying glass icon and the “Change” button. Additionally, we implemented a check to prevent opening an invoice with an inactive currency for documents that were already created.

3.14     (US-13264) OCG: To improve the performance in the HQ entries

In the HQ entries, the code was improved to enhance AD (Analytical Distribution) validity calculations, specifically focusing on the compatibility between GL Accounts and Destinations. The same issue was also identified and addressed in payroll lines.

3.15     All Finance tickets integrated in UF34.0

Key	Summary	Detailed
US-10871	For DPO: to allow Down Payment (specific supply case)	X
US-12111	“Entries Data Integrity” Report – error in the not runs when filtering a mission
US-12137	Intermission: to avoid the creation of a manual IVO and IVI with an inactive currency	X
US-12194	Track changes on recurring models and recurring plans
US-12195	Fixed asset management: track changes to add
US-12283	FY closing check – check if all active project instances have reported Mission closed status for all periods of the FY	X
US-12292	“Invoice allocation” report: mock-up to improve  destination column bigger for better visibility of all the characters inside the field
US-12302	Allow to use multiple AD on CV commitment vouchers (changes made on US-11510 for supplier invoices)	X
US-12303	Minor change on export/import invoice line buttons
US-12438	Fixed assets: To improve the filter in the Journal items of the assets forms : journal + instance (HQ-OCBAF101)	X
US-12472	OCP HQ: new vertical integration VI (Interface Unifield><Workday) -go life 01.2025-
US-12479	Fixed assets : mandatory to have analytical distribution AD before the status OPEN (and just after status Draft)	X
US-12548	Prevent to change the code for analytic accounts if they have been already used in JE
US-12654	Fixed Asset: inactivation of the functionality	X
US-12678	Auto booking counterpart for internal transfer – to be able to select only registers from the same instance as 3rd party
US-12732	To be able to delete draft entries in mass in the liquidity registers	X
US-12738	Fixed Assets: to improve the error message in the “generate entries”
US-12894	E-Validation: Allow Doc_Creator to Modify Signed Signatures	X
US-13050	Homere interface – take employee from the new file staff_l	X
US-13090	FO Follow-up Finance report: to add an error message when the beginning date of the filter is later that the end date
US-13096	PAYE SAGA: Import of payroll entries: to improve the error message when there are already draft payroll entries	X
US-13106	On advance returns/ operating advance settlement form = translation to French
US-13137	To allow manual un-rec on entries manually reconciled, if the FXA does not exist and if there is a related NR update (US-13252)
US-13196	OCA CD_GOMA HQ Balance specification report does not go through
US-13237	Inactive currency to not be available to be used in SI, SR, ISI, ISR, Donation, STV, STR, Customer Refunds and Debit Note	X
US-13252	To prevent manual reconciliations of FXA entries
US-13260	Add the UUID check in the PERMOIS import	X
US-13264	OCG: To improve the performance in the HQ entries	X
US-13348	OCB vertical interface. same move numbers for different entry sequences

4       Non- functional

4.1        (US-12597) Prevent duplication of the Admin user

It is now not possible to duplicate the admin user for local user not to have privileges rights

4.2        (US-10865) UR synch after release

User rights will now be fetch by each instance directly from the sync server without passing by the HQ. This will allow instances that patches before HQ to get the user rights without waiting for the HQ to patch and then sync

4.3        (US-12274) user management improvement: to inactivate users which have not been logged in for 6 months

Agreed by all OCs, all users that have not logged in the past 6 months will automatically be deactivated

4.4        All Non-functional tickets integrated in UF34.0

Key	Summary	Detailed
US-12597	Prevent duplication of the Admin user	X
US-10865	UR synch after release	X
US-12274	OCA ICT Request: user management improvement: to inactivate users which have not been logged in for 6 months	X
US-12974	Add the instance level at Sync Server
US-13376	Instance creation config file = add recent new reconfigure features
US-13375	OCB instances – to configure IIL menu for all with patch script
US-12938	WACA OC creation
US-13017	Add Track Changes on Tools automated job import/export configuration
US-13299	Unidata API : fix nomenclature name at creation
US-13344	UF should be able to purge old UD log files for API pull
US-13272	Auto VI: file name not displayed for import in Exception