Release Details

Release version: UF 22.0

Date of production synchronization server patch: 15-September-2021 / 18:00 Geneva time

Latest user rights files updated: UF22.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=12383

Supply

(US-8646, US-8584, US-8432, US-8560) Changes to Products & how they are synched

With this release there are several changes to products to improve their alignment and also for user-friendliness.

For products with the type ESC, ITC, HQ, if they are deactivated in the higher instance (HQ level for all except Local products, which would be de-activated at Coordo level) this de-activation is synched to all lower instances. This was already the case before. However, previously, where a product in the lower instance was still in use (Stock / in an open document), the product could not be de-activated and there was no Not Run synch update. With this change, the de-activated product will automatically be set as UF status “Phase out” meaning that if a product can be de-activated by synch, it will be. If product cannot be de-activated by synch, it will remain Active, but status will change to Phase Out, and there will be a Not Run synch update. These 2 changes should help users identify where such a case has occurred. This is consistent with how UniData products already behave.

Where a product is de-activated in a higher instance, and in the lower instance the product is not in any open document or in stock, but it is in a product list, now its existence in a product list will no longer block its deactivation. Product will be de-activated, and it will be possible to see in the product list “Old products” tab, that this product was removed.

For the case of synched flows between Instances with different products (e.g. Intermission or Intersection), for the case that a PO or FO is created by synch and includes a product which does not exist in the receiving instance, there is now a message onscreen on the relevant document (PO or FO) warning the user that a product code could not be created. As with before, there is still a Not Run created, and the message on this has been made clearer.

(US-8520) New Import into IN from scratch

An improvement for Pharma, there is a new import file with specific checks for INs which are created from scratch (i.e. not linked to a PO) and which are for returns from external consumption units. There is a specific button for this import (see screenshot) and before the file can be imported, the header fields “Ext CU” and “Reason Type” and of course “Expected Receipt date” fields must be filled. Reason Type must be “Return from Unit”. The import file has a specific format, but the same checks are made as for the original import lines functionality.

(US-8280) IN Physical Reception date field change

As initiated by OCB, the already-existing “Physical Reception date” field on Incoming Shipments (INs) has been moved to appear on the pop-up “Products to process” displayed once the “Process” button has been clicked.

Any date entered here and then processed with lines will appear in Closed IN in the “Additional Info” tab. As per before, if no date is entered here when processing the IN, the Actual Reception date will be taken for this field.

(US-7927, US-8076) Modification to PO RDD date management & pipeline

Previously, a second RDD field “Requested Delivery Date (modified)” had been added at header level to POs in order to manage the updated delivery dates from suppliers for lines which were not yet confirmed. With this ticket, the 2^nd Requested DD is renamed to “Estimated Delivery Date” (EDD). As well as being present at header level, this field has also been added at line level, and is visible onscreen directly in POs, and in FOs it is visible only in line pop-ups. The line level can be filled manually or pushed from the header level field. There is no change to the format of the Vertical Integration PO import and export files. The date value is synched in the same way as the original RDD value was.

Labels for the other dates have been modified to be consistent with the naming, “Delivery Requested Date” has become “Requested DD” etc and also in the OST the original “Estimated DD” label has been changed to “Calculated DD” with the same value, so as not to be confused with the term in POs.

There has also been work done to align how the pipeline and its dates are displayed in different screens and reports, taking into account that Validated PO lines are considered as pipeline.

(US-8014) New AMC report not showing negatives

As requested by Pharma, a parallel report has been developed in the Historical Consumption report. Warehouse>Reporting>Consumption Reports>Historical Consumption

There is a new checkbox which appears when Consumption Type is “Average Monthly Consumption”. The checkbox “Remove Negative AMCs” has a fuller explanation below it, and when ticked, the “Historical Data report” can be generated which does not show any negative AMCs at the month level, and the “Entire Period AMC” is based on the figures shown for each month. When the checkbox is not ticked, a similar report can be generated showing the figures as per the regular calculation for AMC (including negatives), and it is still possible to view the (original) onscreen version for this via the View Historical Data button.

(US-8719, US-8558, US-9028) Replenishment Rules changes

Some improvements and corrections made to the Replenishment Rules include: The Inventory Review report excel export had had grouping added to its columns to make it more readable. These can be expanded and contracted.

It is now possible to add a value of “0” for FMC values for any status of product

When UI is viewed in French, the comma character “ , “ is accepted to indicate a decimal place.

(US-8944) Migration of Local Products to new Thermosensitive codes/values

As per the mapping agreed by Pharma, and already implemented by UniData for UniData products, all Local products in UniField which had old Thermo values have been migrated to the new equivalent Thermo values. No active ITC, ESC and HQ products had old Thermo values, so none needed to be migrated.

(US-8364) Display of Physical Inventory Counting Sheet

In the Physical Inventory, when adding products, it was already possible to specify system should add products with movements in the last X months. With this change, the number of months specified to add products can be used to filter and display also the batches of the added products based on this timed selection. Where user has added products specifying products with movements in the last 5 months, this would be the default option ticked in the new checkbox on the “Generate Counting sheet” pop-up (see below) and only batches which have been moved in the last 5 months will be displayed in the counting sheet.

If this checkbox is unticked, the original product selection remains unchanged, so all products with movements in the last 5 months will be displayed, but all of their batches will be displayed even those which were last moved several years before.

If the checkbox “only count lines with stock different than 0” is ticked, the new checkbox cannot be ticked. All previous displays of the Counting Sheet are still possible.

For the case that multiple additions of products were performed, the system will propose the greatest number of months used during the additions.

(US-8175) Forced reception, Not Run management & New Not Run type

With this ticket there is a correction to specified flows where lines in a project IN belonging to a synched flow have been manually changed (e.g. cancelled) by a user, without waiting for the synch to update the IN, and then the Coordo has sent the line.

In order for the update by synch of the other lines in the IN to not be blocked, a new type of Not Run synch message has been created. It is called a “Partially Not Run” meaning the message itself was run for the document (so the IN has been updated with all lines where possible), but the flagging of Synch message as “Partially Not Run” indicates there were problematic lines in the document which could not be updated.

This type of Not Run is automatically displayed in the Message Received Monitor in the same way as standard Not run messages, but its line is displayed in Orange rather than Red, and there is a specific filter button for this type in the header.

This type of Synch message has a button “Set as Totally Run” to allow user to set to fully Run in order to remove from this filter on the dashboard:

All Supply tickets integrated in UF22.0

Finance

(US-7903) Request to have Commitment vouchers linked to the PO with Inter-section / intermission partner types

Operational centers have agreed to implement commitment vouchers for intersection and intermission flows.

• All Funding Pools are allowed in the Commitment Vouchers “Automatic – Intersection” and “Automatic – Intermission” (i.e. we don’t restrict to PF only).
• We will use the AD directly from the PO for the invoices generated by synch (so for these invoices, we will not use the AD of the CV).
• When we synch and the synch creates IVI /SI, we use the account of the CV (this account can be modify in the CV that have a status draft).

Behavior to take into consideration:

• CV will still be deducted from amount of IVI or SI until the CV full amount is reached.
• CV will be set to done if total amount is reached, whatever the state of the PO, the remaining backorders / invoices to come.
• CV will be set to done once a IVO/STV is validated and if the PO or PO line is in closed state (even if the amount of the CV is not reached).
• CV will not be set as done once a IVO/STV is validated and if the PO or PO line is not in closed state and the total amount of the CV is not reached.
• CV will not be set as done in case the PO or PO line becomes closed after reception and if no IVI or SI are validated at a later stage (cancel invoices).
• In case a line is added on the FO of C2, no added line on the CV of C1 for consistency.
• Pushed FO from C2 to C1, no CV are created at C1.

(US-7449) The AD of the CV and SI lines will be the one of the PO

We have changed the way AD is calculated in Invoice and in CV. The objective is to align PO/Invoices and CV aligned on the PO analytical distribution behaviour:

Please be aware that the CV in progress that were created before this change will keep the former behaviour, the improvement is just for the new POs and their CVs (this improvement is not retroactive).

Some notes:

• When transferring AD from PO to Invoice, system use the product as linked object (note that it is not possible anymore to delete products coming from PO in invoices).
• When transferring AD from PO to CV, system use the product as linked object.
• It will not be possible to delete product lines in CV but it will be possible to change the account code in draft status (not in validated status); for manual CV the account code is editable at validated status (current behaviour).
• AD will be per product in SI and CV the same as it is in POs.
• Each CV line or SI line will generate AJIs according to the AD of the line, AD being the one from the PO.
• The updates between SI and CV will be based on the product line and not anymore – based on the account code.

(US-9003) Set all Intermission partners with the functional currency (EUR / CHF)

We noticed there were some intermission partners that have another currency than the functional currency while only functional currency is allowed for Intermission partners so we proceeded with a patch script to set all intermission partners with the functional currency.

All Finance tickets integrated in UF22.0

Non- functional

(US-9026) Invalid date in a wizard pop-up generates a Pink Screen

Since UF21.0, an invalid date value into the date field for example inputting an invalid physical reception date when processing an IN would return a pink screen. The UF22.0 release fixes this by returning an invalid date error message instead of the pink screen.

(US-8869) Remove stocked internal files from IR (doc) import

As reported in US-8853, all files used to import IRs are being retained by the database. This causes abnormal growth of db size. With the UF22.0 release, import files will be deleted automatically after a successful import since these files are not needed or available functionally.

(US-8866) Add the last update sequence pulled next to hardware id

When the Core team is updating the hardware id of an instance, we have to ensure also that the “Last update sequence pulled” at the sync server corresponds to the last update sequence pulled” at the instance level. This is to ensure that the restored dump is the correct one to avoid any missing/discrepancies of data. We have noted several incidents following a request for hardware id update where we found out that the backup restored is not the latest one.

In this release, we have added the last update sequence pulled next to the hardware id in the sub menu “Entity id”. This field is read only and is updated after each sync. This will ensure that when requesting hardware id update, requesters will copy the hardware id as well as the last update sequence pulled to ensure it matches with the sync server.

(US-8865) Huge Sync Message to Process Blocks Synchronisation

Huge sync messages to process for example a PO with 1000+ lines would block synchronisation due to memory error. The UF22.0 release fixes this issue.

(US-8776) Code fix to remove the tag on users created by duplication

Duplicating a synched user in a coordination or project instance has been retaining the synced flag on the duplicated local user. With the 22.0 release, the sync flag is removed when a sync user is duplicated. The login field of a synced user in coordination or project cannot be changed either (only read, no write access/edit)

All Non-functional tickets integrated in UF22.0