Release Details
Release version: UF 33.0
Date of production synchronization server patch: 12th June 2024 / 18:00 Geneva time
Latest user rights files updated: UR.33 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=12507
Supply
.1 (US-11135) PO to display any discrepancies with Catalogue
With this ticket, users will have immediate information about the conformity of their PO to the Supplier Catalogue. Every PO will now display additional information about the adherence of the PO’s products to a Supplier Catalogue. Where the PO’s Supplier has no valid Catalogue (a Catalogue for the same Supplier in the same currency which is active, Confirmed and with valid dates), this will be displayed in the “Purchase Order” tab of the Purchase Order as “No valid catalogue”.
Where there is a valid catalogue for the same Supplier as is in the PO, the conformity of the PO product lines will be checked and the adherence will be displayed on this same tab as a percentage:
Adherence is calculated on number of lines which conform / total number of lines in PO.
In the case that there are lines which do not conform (so adherence is less than 100%) there will be a new tab displayed: “Supplier Catalogue” and this will display adherence for lines which do not match and lines (Products) which do not exist in the catalogue, as well as information for each of the lines which has a mismatch, and the reason for the mismatch. Reasons for mismatch can be due to differing Unit Price and Order qty.
There is also the possibility to export the lines which have a mismatch.
The adherence information on the PO is automatically refreshed (rechecked) each time the PO is viewed or the new tab is clicked on.
There is no change to the behaviour of the PO lines in other tabs – this new development does not update the prices or quantities on the PO, it only displays whether they conform to the Supplier Catalogue or if not, why.
.2 (US-12716) POs & FOs for Intermission and Intersectional flows flag non-UniData products
In order to encourage users to only use UniData products for order flows with Intermission and Intersection partners, at validation of PO / FO, the system will now check and raise a non-blocking warning message if for Intermission PO/FO any Local products are included, and for POs/FOs to Intersectional partner the system will raise a blocking warning message if any Local, ESC or ITC products are included.
.3 (US-11908) PO lines to have additional filter for ESC status
POs with an ESC-type Supplier will now have an additional filter on lines so user can select to see if they have been Confirmed by ESC or not. Possible filter statuses are: ESC Confirmed, ESC Unconfirmed and (default) Show all. This filter can be used independently or together with the standard lines status filter.
.4 (US-12489) E-Validation: in IR, FO, PO & IN the order in which signatures can be added is fixed.
For the Supply documents IR, FO, PO and IN, the order in which signees can add their signature is fixed in the order of appearing roles, so the first must sign before the next person has access to sign. Each user can still unsign in the normal way, and it is still possible for the Signature_creator group to remove certain roles from needing to sign. The system will check at addition of each signature that user is either i) the first signee or if not that ii)the signature above has been filled before allowing user to sign.
.5 (US-12359) Improved visibility of imported/exported files for configured automated Vertical Integration.
With this ticket, the names of imported and exported files will now be visible in the Job reports, and can be searched for using the newly added filter. This was developed to allow for better traceability for the Supply auto VI flows (used by OCA) for PO export, Confirmation and also update of IN via E-Packing list, but the functionality allows this visibility for all automated import/exports so Finance will also benefit from this improvement.
.6 (US-12367) Export IR Follow up report: new “Details” field added
Since the “Details” field was added to multiple Supply documents recently, it has now been included in the IR follow up report so as to give better visibility for these documents. This is consistent with the relevant PO and FO reports which already contain this field.
.7 (US-12033) Tender comparison to reflect any change in RFQ quantity.
It is possible when filling in the RFQ with Supplier details to change the product quantity. Previously this change was not visible at the comparison stage in a Tender, so now, when the Tender “Compare RFQs” button is clicked, in the resulting comparison pop-up screen there are additional columns added to show the Supplier Quantity as well as the original Tender quantity. Any discrepancy for this is displayed in red. The same elements are displayed in the excel “Comparison RFQ” in the action menu.
.8 (US-12719) PMD: New field “HS Code” added to UniData products
This new field HS code (Harmonized system) will now appear in all UniData products in the Specific info tab. Where there is one, value will be pulled from UniData and synched down to all instances below.
.9 All Supply tickets integrated in UF33.0
| Key | Summary | Detailed |
| US-12367 | Export IR Follow-up – add IR Details column | X |
| US-12716 | In PO/FO with Intersection / Intermission partner only UniData products allowed | X |
| US-12845 | MSR update at merge of products for newly created project. (Instance ID missing) | |
| US-12489 | E-validation: Fix order of signatories on Supply docs: IR, FO, PO, IN | X |
| US-12704 | Product Nomenclature – translate “Root” to “Racine” instead of “Origine” | |
| US-12586 | PMD Product: Track changes to include entry for change of Root | |
| US-11908 | ESC Confirmed Lines Filter on PO | X |
| US-12359 | Identification of the VI import job | X |
| US-12584 | IN coming from synced flow (DPO) via VI E-PL, to remove the “warning msg” when in status “Available updated” | |
| US-12719 | UniData: PMD Products – HS code – new field | X |
| US-12742 | Active status change at Coordo on NSL product merged to be synched | |
| US-12033 | Tender: Rfq comparison to reflect change of Supplier Qty | X |
| US-11135 | Include Supplier Catalogue info in POs | X |
| US-12613 | Supplier can be changed in validated PO in case of of opening 2 tabs | |
| US-10750 | OST Source Lines – Cancelling item after changing the stock location | |
| US-12817 | IR import template has an issue with “Order Category” in import template | |
| US-12251 | MSL: incorrect values for Product Count column in the export | |
| US-12147 | Synch does not update the product’s default description (US-1567) | |
| US-12976 | OCA: All ESC Supplier Catalogue VI failed in all instances since last release | |
| US-13025 | Issue with SoQ Rounding button on PO |
Finance
.1 (US-12927) In the “search: Employees” screen: to add a filter with the field UUID
In the “search : Employees” screen: we have added a filter with the field UUID. The UUID is already in the employees form).
UUID: unique employees identification number.
.2 (US-12844) E-Validation: PO Sign Offline: wrong behaviour
The e-validation functionality continues to be tested and improved. During testing of e-validation on the PO, it was discovered that it was possible for a signee user to electronically sign a PO that is marked “Signed Off Line”.
Additionally, in this scenario the PO remained visible on the signee users Signature Follow Up list. This should not be the case in this scenario.
These 2 points have been corrected in this release.
.3 (US-12690) Position not updating in the Human resources tab when importing PERMOIS
When loading the Permois file and then the Paye saga file, we noticed that the job position in the UF Human resources tab was not updated. This wrong behaviour has been corrected in this release.
.4 (US-12653) Fixed Asset: not to display the assets menu if the system manage fixed assets is not ticked
The fixed assets functionality is a choice. The OC can use it or not. So after this improvement, we will not display the Assets menus unless the check box is ticked in the reconfigure: “Does the system manage Fixed assets?”. This is with the aim to avoid confusion in the users.
Path for the reconfigure: ADMINISTRATION > Configuration > Parameters > Reconfigure:
.5 (US-12645) Fixed Asset: improvement of the duplication of an asset form
The duplication of asset forms has been improved. Now the following fields will not be updated:
Example of a duplication:
.6 (US-12595) Fixed Asset: Add [EXTERNAL ASSET ID] field in the asset form (to do with US-12440)
When we go to Accounting > Periodical Processing > Assets > Asset Form: We will see a new field called “External Asset ID”. The external asset id corresponds to the asset code from the external log tool.
.7 (US-12440) Fixed Asset: Fixed assets – to import list of assets with value 0 in the fixed assets module (to do with US-12595)
When we go to Accounting > Periodical Processing > Assets > We have added a new menu called “Import Asset Entries”: we will be able to import assets into the system.
When the file contains errors, it will not be imported. We will have the details of these errors in a message that will facilitate the correction to import the file with success.
Some errors examples:
.8 (US-12267) Freezing register balance during the month: add additional check box with a warning message
We have added a check box with a warning message “Are you sure you want to freeze closing balance while the previous period is still open?”
To tick “OK” means that the user is freezing the end of month balance of a period register, while the status of the previous period is still open.
.9 (US-12470) Fin_Config_Coordo could not inactivate journals from decommissionned instances
We have allowed the group Fin_Config_Coordo to inactive journals from decommissioned project instances. This is to allow to clean up “old instance’s registers” that we did not clean before decommissioning.
.10 (US-12256) Open advance list for users with limited access to the registers.
Now we have all open advances on the register’s currency, regardless of wherever it has been booked. As it is important to be able to settle an advance from other register.
.11 (US-12029) To prevent the closure of a project register at coordo level if we have draft entries at coordo level from this project register (creation of a new not run!)
Do not allow closing of a project register when there are still draft entries from this project at coordo level.
The project will close, but after sync, we will have a not run at coordo level about the project register status: “not possible to accept the closure status as at coordo there are still draft entries from the project”.
The not runs will disappear when we delete the draft entries or if we treat them at project level (by reopening the register at project level).
Example of not run message:
.12 All Finance tickets integrated in UF33.0
| Key | Summary | Detailed |
| US-12927 | In the “search : Employees” screen: to add a filter with the field UUID | X |
| US-12844 | E-Validation: PO Sign Offline : wrong behavior | X |
| US-12690 | Position not updating in the Human resources tab when importing PERMOIS | X |
| US-12653 | Fixed Asset: not to display the assets menu if the system manage fixed assets is not ticked | X |
| US-12645 | Fixed Asset: improvement of the duplication of an asset form | X |
| US-12641 | Fix to do in the customer’s search menu: when the “Customers” button is un-ticked, we must see non-customers partners | |
| US-12595 | Fixed Asset: Add [EXTERNAL ASSET ID] field in the asset form (to do with US-12440) | X |
| US-12589 | Accounts parameters: to change the label of internal transfer in the type for specific treatment (account 14130) | |
| US-12470 | Fin_Config_Coordo could not inactivate journals from decommissionned instances | X |
| US-12440 | Fixed assets – to import list of assets with value 0 in the fixed assets module (to do with US-12595) | X |
| US-12350 | Manually created journal filter shows “system” journals (EOY and IB) that are automatically created | |
| US-12267 | Freezing register balance during the month: add additional check box with a warning message | X |
| US-12260 | Remove duplication button on Direct Invoice line on register screen | |
| US-12256 | Open advance list for users with limited access to the registers | X |
| US-12226 | After the release of the assets module: to remove the possibility to use DEP journal in the recurring entries module | |
| US-12074 | GDPR – Remove from the staff track changes the fields removed in the ticket US-7791 | |
| US-12029 | To prevent the closure of a project register at coordo level if we have draft entries at coordo level from this project register (creation of a new not run!) | X |
| US-11865 | YE_COOR_OCA: 18620 register entry without third party YE00-BA006-230177 | |
| US-11456 | To see ALL the closed journals in the liquidity report, even the one that have been inactivated |
Non- functional
.1 (US-12826) UniData: Switching UniField pull from the UniData API
The integration of Unidata data in UniField was executed via Unidata linkage. The linkage worked as a push mechanism. Once the product was updated/created in UniData, the updates/creations were also pushed to UniField.
Since release version UF33.0, a new type of integration is implemented. The UniData data are received via the UniData API called by UniField daily. There is no functional impact in UniField from the regular user’s perspective, however, a few submenus have been introduced to enable better monitoring of the Unidata Pull. Also, the products are no longer matched on product codes, but on MSFID (=unique product ID generated by UniData). Therefore, the multiple truth issues should no longer occur.
All of them are located on Tools -> UniData -> UniData linkage errors:
UniData Linkage errors
In case the data pull was not successful for a specific product, the product will be displayed in this sub-menu table. Here, you can also find the MSFID of the product and the text taken from the log explaining the cause of the error.
¨
UD Products incompatible with OC values
The submenu lists all products for which the value of attributes differs from the OC default value.
OC default values (see below) are set in UniData and they are not directly returned by the API. Thus, if a new product is created the OC default value is taken instead and never updated afterwards. However, the OC default values can be later changed (which is rare) or created afterward but the product won´t be updated anymore.
Therefore, the table in the submenu lists all products, where there is a discrepancy between the actual value and the current OC default value.
OC Default Values
Some of the attributes pulled from UniData have default values set and they are not returned by the UniData API. The default values are based on Nomenclature.
Each OC can however set their own OC specific value in Unidata as well, such as Procurement Method or Expire Date Mandatory.
The table displays all OC default values currently set in UniData.
.2 (US-12867)) UniData: Display msfid & Create msf Id filter
Since the Unidata pull matches the product on MSFID, it can be convenient to search the product by its MSFID.
A new filter is displayed in the product menu enabling a quick search. The MSFIDs in the filter need to be specified as a range.
Also, the MSFID is now visible in the “View log” action field.
.3 (US-13019)) UniData pull: Fit / Function / From values
This is a purely technical ticket. Fit/Form/Function values are not returned by the API by default, thus additional needed to be created for these values.
.4 (US-13034)) Justification code: Add new values
2 new justification codes were introduced in UniData which are currently not mapped in UniField. To display these values as well, they needed to be added to the mapping table.
The new codes are the following:
.5 All Non-functional tickets integrated in UF33.0
| Key | Summary | Detailed |
| US-12251 | Product count corrected in MSL projects export | |
| US-12826 | Integration Unidata data is now executed via UniField pull | X |
| US-12867 | New filter and display of MSFID | X |
| US-13019 | Technical ticket related to UniData pull | X |
| US-13034 | 2 new values for justification codes | X |
