.1 Release Details
Release version: UF 32.0
Date of production synchronization server patch: 13th March 2024 / 18:00 Geneva time
Latest user rights files updated: UF32.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=12500
.2 Supply
.2.1 (US-12171) Correction of Picking percentage calculation status
This improvement is to solve the issue of misalignment of FO “Picked” percentage status with what has been shipped. The Picked status percentage now reflects the correct percentage of picked which ignores C&R/cancelled lines.
.2.2 (US-11907 & US-12339) Correction of Eprep stock locations category location & cleaning
This improvement complements what was developed in US-4642, as it was agreed that “EPREP” stock locations are categorized under the Parent Location “Stock”, and “EPREP” should no longer be a “Location Category” itself. This ticket is to ensure consistency in the system: the location category “EPREP” has been removed from drop-down lists in the “search stock locations” pop-up which appears in various screens, this was done after cleaning-up and correcting the Eprep stock locations of all OC instances.
.2.3 (US-12076) Addition of Track changes in RFQ
Track Changes has been added to the “RFQ” Request for Quotation Object in the Action menu to ease and improve the continuous tracking of changes on the RFQs and to be consistent with other supply objects.
.2.4 (US-11957) Export Inventory Level – additional advanced filters
In the Export Inventory Level report, more search options have been added to the advanced filters to get more precise reports, so “Specific Product list” and “Specific Product family” are now included. Both search filters were added also to the List view as well as appearing in the list view columns.
.2.5 (US-12335) Prevention of gaps in INT references due to duplication of SYS-INTs
In Internal Moves users used to be able to create an INT from scratch via duplicating a SYS-INT, and this behaviour created a gap in the INT serial numbers. This issue is solved now with this improvement, the new INT that results from duplication a SYS-INT appears in the list view of INTs and is correctly numbered.
.2.6 (US-12167 & US-12582) Correction of Sourcing possibilities for FO with service type products to PO/RFQ/Tender
Service products coming from FO must be sourced through a “Direct Purchase Order” (DPO), therefore the use of “Regular purchase order” was not allowed. In this release, the use of “Purchase List” type has been stopped also, and a blocking message is displayed. Similarly, when an FO containing a service product is sourced via either RFQ/Tender and is then processed to create a PO, the same rule is now applied – the PO created will automatically be a DPO.
.2.7 (US-10701) Prevent of Cancellation of parent Pick if subpicks in progress still
This issue was faced by several users before: previously it was possible to cancel the main pick when subpicks were not all closed. This was achieved by users performing several conversions of the Picking tickets to OUT and vice versa. This resulted in users then being unable to cancel or process any sup-picking ticket/PPL linked to that Picking. This issue is solved now and users can’t cancel the main picking in any way while any picking tickets are in progress. A blocking message is displayed.
.2.8 (US-12115) “Details” field PO to be concatenated where multiple source docs
To continue the development that has been implemented in US-11827, in the case where multiple IRs/FOs are sourced onto 1 PO, all the “Details” fields from the multiple source documents will be pushed to the PO with a semicolon separator, up to the limit of 86 characters.
.2.9 (US-12248) Prevention of multiple tabs allowing Supplier change and inconsistent currency
The issue, caused by user having multiple tabs open on a PO while editing it has now been resolved. It is not possible now for users to make changes in supplier/currency when they open multiple tabs and make changes on different tabs.
When user tries to make changes on different tabs at the same time, a blocking message will be displayed:
.2.10 (US-11845) Alignment of Price rounding displayed in Donation Certificate
For more consistent and accurate data, Product unit prices in the Donation certificate have been rounded to 5 decimal places and the Total to 2 decimals. This corresponds to the FO/PO way of decimal rounding.
.2.11 (US-12100 & US-12616) PMD “Stock by Location view” and MSR Correct display of Virtual stock for Direct Purchase Orders
Direct purchase orders’ validated/confirmed lines quantities will now be excluded from Virtual stock calculations in the Product PMD “Stock by Location” and also in the Mission Stock report (MSR). The quantities will not be displayed since instances issuing DPOs will never receive them in stock.
.2.12 All Supply tickets integrated in UF32.0
| Key | Summary | Detailed |
| US-12616 | MSR should not display virtual stock for Validated or Confirmed Direct purchase order | X |
| US-11845 | Align Price in Product File and Donation Certificate | X |
| US-12582 | Sourcing “Service” product coming from FO to Tender/RFQ should be possible and to continue procurement to PO “Direct purchase order” type should be created | X |
| US-12339 | To clean-up OCP instances, to correct the Eprep stock locations category | X |
| US-12335 | To fix the issue of having SYS-INT created manually by users and causing a gap in the INT List view | X |
| US-12248 | Prevent multiple tabs allowing Supplier change and inconsistent currency | X |
| US-12231 | Let Me Fix in SHIP when generating Freight Manifest excel | |
| US-12197 | (US-3843) PO line quantity doesn’t decrease after a claim | |
| US-12171 | Correct Picking calculation status – ignore Cancelled-r lines | X |
| US-12167 | Sourcing FO to PO type Purchase list should not be possible for Service type product | X |
| US-12115 | “Details” field in IR and FO pushed to PO to be concatenated where multiple source docs | X |
| US-12100 | PMD “Stock by Location view” should not display Virtual stock for Direct Purchase Orders | X |
| US-12076 | To add Track changes in the Action menu of RFQ | |
| US-11957 | Export Inventory Level – Advanced Filters | X |
| US-11907 | Location Category: EPrep | X |
| US-10701 | SHIPment blocked from being processed (convert pick> Out > pick + cancellation) | |
.3 Finance
.3.1 (US-12590) and (US-12371) OCA and OCB vertical integrations
We have improved the vertical integration file for OCA and OCB.
Please note that the import files for each OC are different, and each file is tailor-made for each OC depending on their needs and their HQ system.
.3.2 (US-12344) To be able to change the status of a period from open to draft (when there is no JI)
Following several errors that required data fixes, we have changed the system’s behavior. It is now possible to change the status of the period from ‘open’ to ‘draft.’
This change will only be possible if no data has been encoded or registered (no JIs or registers in draft created).
Access to this feature is granted to HQ super users with the group Fin_Config_Admin_mission only.
.3.3 (US-12173) E-validation OCA pilot findings – New requests (id2, id3, id10, id11, id6 et id4)
The e-validation functionality continues to be improved. We have implemented some useful changes in this release as follows:
• id2. We have renamed the button “Delete Signature” to “Inactivate Signature”
• id3+id10: We have merged the 2 sub-tabs “Manage users allowed to sign” and “Signatures” in each signature tab to create only one tab named “Signature” with a mapping of users added to each role/function.
o We have kept the button “Manage Users allowed to sign”
o A pop-up appears when the mapping between users and role is to be defined
o In rows, we have the Role/Function
o We have introduced a new column for “Users” and a magnifying glass. For each role, a user has been defined, and only these users will be able to sign.
o We have added a new column called “Backup.” The same user can be added to two roles, and for one of these roles, they will select “Backup” because they are replacing another person.
o In the PDF, when the “Backup” field is selected, the replacement role for the backed-up position will be indicated.
• id11. We have added the Legal name of the active signatory in front of the position when the document creator is adding users who are allowed to sign.
• id6. The signature users registered in the current period are automatically inherited by the next period’s register until they are removed. This behavior mirrors that of the “register responsible.
• id4. Close signature” – We have added a message: “You are about to block the signature on the document. This action is irreversible. Are you sure?
.3.4 (US-11897) To be able to close the month only if the registers corresponding to all active journals are created
We can now close the month only if the registers corresponding to all active journals are created, opened or closed for this period.
If we attempt to close a register and the journals are not created, an error message will be displayed:
.3.5 (US-11868) Reflect in Full Report Correction 6**** to B/S via correction wizard
We have enabled the ability to change an expense account to a balance sheet account via the accounting correction wizard. This change is now also reflected in the Full Report of the related register entry.
.3.6 (US-11800) Rename “Donation” to “Donation Received” and to “Donation reçue en nature” (French)
For a better understanding we have changed the name of donations.
.3.7 (US-11269) To prevent changing the G/L accounts on a liquidity journal linked to a “non-draft register”
We can no longer directly edit the G/L account of the liquidity journal linked to a non-draft register (open or closed).
However, when the first register of the journal is not yet in the open state, you can still edit the G/L accounts.
.3.8 All Finance tickets integrated in UF32.0
.4 Non- functional
.4.1 Migration to Python 3
In this release, we are finally migrating the full UniField code from Python 2 to Python 3.10.11. This is to ensure UniField Python code remain up to date, preventing risks of obsolescence for the tool.
.4.2 (US-11587) To have a pop-up asking for the field “department” and (US-12294) Pop up to make the Email Field Mandatory in Unifield
We have implemented a pop-up that prompts the user to fill in their email address and department.
We can have errors if the email is not from msf or invalid.
:
We will also store this information in the preferences:
.4.3 All Non-functional tickets integrated in UF32.0
| Key | Summary | Detailed |
| US-11587 | To have a pop-up asking for the field “department” | X |
| US-12294 | Pop up to make the Email field Mandatory in Unifield | X |
| US-12607 | When you change the language of the UF Instance via “Edit Preferences”, it does not change immediately, only after log out/log in it changes | |
