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