Date of production synchronization server patch: 07-July-2021 / 18:00 Geneva time
Latest user rights files updated: UF21.0 can be found here with record of changes 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.
This issue, raised by Pharma, meant that it was no longer possible to import line information into an OUT (Delivery Order) created from scratch. This was caused by US-8010 released in UF20. This is now corrected so the import is now working.
(US-8795) VI import on PO Stock Take Date check
This issue raised by OCG and linked to US-8638 meant that when a VI import in XML format was done either manually or via Auto VI on a PO, for new lines added via import a Stock Take Date could be added which was after the PO Creation date. This was not conforming to the expected range of STDate and meant the PO lines were then blocked after. With this ticket, the check is done on the STDate in import file, a warning is raised and line not imported if STDate is not conforming. It is still not mandatory to add a Stock Take Date on new lines, and in the case there is no STDate, then the system will take the same date as the creation date of the PO.
(US-8650) Check on Inactive products at document level > line level
This issue raised by multiple OCs, was due to the system making a check at document level that all product lines contained Active products. There were many cases where a document contained a now Inactive product, and the line for this product was closed, but due to this check the other lines in the transaction were being blocked from progressing. The check has now been transferred from being at document level to the specific line(s) being processed. This means that Inactive products in already processed (closed) lines will no longer block the processing of lines with Active products in the same document.
All Supply tickets integrated in UF21.1
Finance
(US-8810) OCG_XX1_COO : not runs with model: dest.cc.link (due to VM duplication; disaster recovery test)
Due to a OCG IT Virtual Machine test recovery, OCG HQ has been duplicated, creating sync issues between the fake and the production HQ, creating not runs on the combination destinations and cost centers in several missions. This ticket fixes the not run.
All Finance tickets integrated in UF21.1
Non- functional
(US-8753) Set admin password in UF to “never expire” by default
Following improvement in password policy US-7019 (UF21.0 release), all production passwords were set to expire every 6months with the exemption of sync users and unidata users. In this UF21.1 patch, we added admin user accounts to the short list of users set by default to “Password never expires”. This means that when the 6months elapse, administrator accounts will not be prompted by the system to change password.
Date of production synchronization server patch: 5th May 2021 / 18:00 Geneva time
Latest user rights files updated: UF20.1 can be found here with record of changes 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.
(US-8539) Product de-activation mechanism on split documents
When a user/synch tries to de-activate a product, the system will check if it was in stock or in any open document, and if so, the de-activation would be blocked.
The issue flagged by OCA was that if the document was an old FO or PO and was split (with a suffix -1, -2 or -3) because it was created & processed pre-SLL (Ticket allowing status to be different at line level), then the de-activation of a product in one of these documents was blocked even if the line/document was Closed or Cancelled. With this ticket, the system will no longer block for the case of these split documents, so the product can be de-activated if it meets the originally defined criteria.
(US-8436) Change to Direct Purchase Order linked documents
In UF20 release, the tickets US-7617 & US-7552 were included which meant that when Incoming Shipments (INs) linked to a Direct Purchase Order (DPO) are processed or cancelled at requestor (project) instance, the details of this reception/cancellation are synched up to the DPO instance.
OCG identified that this was not always the case, and specifically for when an FO was sourced to multiple DPOs the linked IN information was not correctly synched up. With this ticket, this issue is corrected so that in the case of an FO being sourced to multiple DPOs, each of these will have a separate IN created at project to ensure the accurate data is synched back.
For FOs sourced in this way between UF20 and UF20.1 (this release) a separate ticket, US-8554 has been created to ensure correction of these flows via Data Fix after this release.
(US-8389) Block moves to Virtual locations via INTs
This issue identified by OCB was that users could create Internal Movements (INTs) from a stock location to a virtual location (such as “Inventory Profit &Loss”) therefore bypassing the correct procedures such as doing a Physical Inventory to adjust stock levels. This has now been corrected and is no longer possible.
(US-8349, US-8185) Claims issues
These 2 issues meaning that VI auto IN import was blocked due to Claim in progress, and there being an unclear Not Run synch message when a Claim was raised and then closed in the same instance before it was synched to the Supplier instance have now been corrected. The VI auto import is no longer blocked in this case, and for the second, the Not Run synch message now clearly communicates the issue with related document Ref.
(US-8200) IN processing issue
For a specific user case, when the Outgoing Transport document had been processed with a quantity already in stock (Crossdocking) in advance of the ordered quantity being actually received via the Incoming Shipment, the VI import of this Incoming Shipment was blocked. This has now been corrected.
All Supply tickets integrated in UF20.1
Finance
(US-8535) OCA: Automated VI – export to HQ system error message
To fix an error message linked to OCA automated VI, we have added a configurable pause in the process between the generation and the push of the VI files to the sftp server.
All Finance tickets integrated in UF20.1
Non- functional
(US- 8487): Certificate Renewal Issues
Certificate renewal issues were identified in some instances due to a failure in the auto-renewal. These instances were forced to renew certificates manually because the revprox code that automatically renews certificates on instances failed. This is due to a bug introduced by US-8158 and the new LE authority causing revprox not to consider the certificates as certomat ones. This bug is fixed and resolved in this release.
Date of production synchronization server patch: 16-June-2021 / 18:00 Geneva time
Latest user rights files updated: UF21.0 can be found here with record of changes 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.
With this ticket comes an improvement in usability allowing users to select multiple lines directly in the IR/PO/FO or still to use the same pop-up window as before to select products for either Cancel or Cancel & Resource.
(US-7590, US-7597) Kit improvements on KCL status & comments
In these 2 tickets raised by OCB, the system now displays the status of each of the Kit components via Products>Kit Management>Kit Composition List, along with some filter buttons for each of these statuses.
In the Kit Composition list, when using the Substitute Item functionality it is now possible to see the comments linked to each KCL line, and in the substituting items, it is possible to keep the same comment as per the line removed or also to add a new comment for the replacing line.
(US-8320) Phase Out status products can be shipped out
This is a modification linked to previous alignment of UniData and UniField status of products (US-7158). UniData products with “Phase Out” status can now be consumed and sent out of the instance. This includes donations and regular outs to internal, external, intermission and intersection partners as well as Real consumption.
Now there is a check at processing PPL and SHIPs that the partner’s delivery address exists/is active, and warning to change this if not. There is also a warning on the Partner file if user tries to delete an address which is currently used in a PPS open document.
There is an addition to the PPS flow to complement US-5859 which limits the modification/addition of packs to being done in “quick flow” in the Draft Shipment so that it is not possible to ship more parcels than exist in shipment.
(US-8194, US-7816) Sourcing/POs – Local market & Service product
Some modifications so that if “Local Market” supplier is selected in the OST, the type of PO will automatically be switched and created as Purchase List. This can be manually changed back if needed.
When an FO with a Service product is sourced to a Direct PO, it is now no longer possible to change the DPO to a regular or purchase list type PO.
(US-8372) Supply documents product price, non-acceptance of comma
When User Interface (UI) is in English, unit price fields in documents IR, PO, FO, IN, Product cost revaluation and Initial Stock Inventory will no longer accept comma “,”. Only full stop/period “ . “ will be accepted as decimal marker. No change to how French UI works or to any imports.
Two improvements to the Replenishment Rules functionality, both affecting the Replenishment Segment. It is now possible to fill in up to 18 FMC values per line/product, which gives a longer planning horizon if needed. For FMC dates, when the calendar button is used to enter them, the calendar displayed will no longer show a default of “today’s” date but rather, the date of the column entered previously in order to minimise clicks for user to select future dates.
(US-7941) Vertical Integration: Auto VI multiple ESCs possible
For automated Vertical Integration, both import and export for Supply (PO, IN and Catalogue) it is now mandatory to define the specific ESC supplier for each job. This means that auto vi jobs can be active for multiple ESC Suppliers, one job for each supplier and each action.
As requested by Pharma, extra columns will now be displayed in the IN&OUT and Receptions reports, and the Receptions report will now show INs created from scratch (not from PO).
Reports FO follow-up per Client and PO follow-up per supplier will also have extra columns. The Export Stopped products report is now renamed to Export Phase Out products, and will no longer display inactive products.
(US-4653, us-8162) Stock Take Date improvement & IN correction
It is now not possible to change the Stock Take Date on POs which are validated or a status after. The STDate after PO validation can only be updated by the Synch in the case of a synched flow. For products added on POs sourced to external Supplier (e.g. to ESC) then new lines will accept a STDate if date value is on/before PO creation date. Split lines will automatically take date of original line.
The issue raised where lines in Incoming Shipments (INs) could not be cancelled due to system checking Stock Take Date of POs which for historical reasons were not conforming to expected STDate. This has now been corrected.
(US-8554, US-8630) Direct Purchase Order corrections
In previous release, US-7617 meant Direct Purchase orders can now be closed/cancelled by synch when project/receiving instance process/cancel the Incoming Shipment. In a follow up ticket US-8436 on an intermediate release, the behaviour of INs was changed to allow for FOs split across multiple DPOs. However the DPOs created in this way between the 2 releases remained not being updated correctly by the synch. This ticket acts in the same way as a Data Fix would to allow the Not Run messages to be executed across all instances with this issue so the DPOs receive the correct updates.
In a second ticket, the flow where a DPO was created and then a line was split and then confirmed was corrected so that at project/requester instance, the PO split line is no longer displayed as Draft status but in Confirmed status to match its DPO counterpart.
Correction made to internal moves (INT) allowing only virtual location of “Destruction” to be selected as destination location. Other virtual locations were previously made inaccessible for this in US-8389.
Another issue corrected is that where an IN is processed for expired goods, the chained INT linked to it will automatically be processed in the normal way and expired goods will arrive at destination location.
All Supply tickets integrated in UF21.0
Finance
(US-7295) Deactivation date of Destination/ Cost Center combination in UF.
In this ticket we have added the activation and deactivation date of the combinations of destinations / cost centers.
Additionally to the checks on the activation dates of Destination and Cost Center individually, system will also check the activation dates of their combinations.
The display of this combination inactivation date will be in the Destination Analytic Account configuration in the Cost Center (CC) tab. It can be filled manually.
There is the possibility to fill these dates by import via Tools.
All parametrization is always done at HQ level.
(US-8295) Improvement in Kind Donation functionality
New functions have been added to the In Kind Donations functionality as below:
1. Do not allow to delete with the red x the IKD lines as far as the IKD is from supply.
If IKD comes from supply (regardless of the partner types): allow to create additional lines which are editable and that can be deleted.
Allow to delete/edit lines when IKD is manually created.
2. We did a new cancel button on IKD like on STV/IVO when we have a donation in draft. The object is not removed, just greyed. Similar to STV/IVO the object and details is visible but not useable.
3. We created the split function in IKD.
If we try to split a line with 0 amount we will be blocked (also via de wizard).
If we want to split an invoice that has one line amounted 0, it will be possible just if we delete this line.
4. Now we can change product, account, quantity, unit price and description from a donation coming from a supply flow. ==> we frozed the donor, the source document, the product and the quantity fields of a donation coming from a supply flow.
5. We created the import-export functionality as the one created for the supplier invoices in 2020: “Import Invoice Line / Export Invoice Line”.
The field “notes” that is in a tab of the invoice lines of a SI/IVI/IVO/STV will be also available in the excel spreadsheet.
6. There were no changes in the behavior of the ODX journal nor in the “duplication” behaviour: If the donation comes from a supply flow the source document will not be copied if we duplicate the document. If the donation is manual, the source document will be copied if we duplicate the document.
(US-7876) Track changes on currencies and currency tables
We implemented the track changes on currencies in these screens:
the editions of every field, including the changes on the rates.
on the currency tables we can track:
the creation of the currency table
the editions of the code, the name, the state, the addition and deletion of currencies
to see the changes on a currency itself: click on the button on the right of the currency line.
(US-8001) CODE FIX: Don’t generate REV and COR when correction on FP on HQ entries using the correction wizard.
We did a code fix to correct a wrong behaviour: If the AD (analytical distribution) of an HQ entry is edited using the correction wizard to change either its Funding Pool and/or its Free1/2 account, REV/COR entries were generated, whatever the period state. This is not the case anymore, no REV/COR entries are generated.
(US-8094) Track Changes in HQ Entries
Thanks to this ticket, we will trace:
the fields used as headers in the list view of the HQ entries.
the transition to “Validated” (the tag on which the filters To Validate and Validated depend), so that we can spot when the HQ entries have been posted.
the split and unsplit of entries. Note: lines coming from a split will be identifiable because the “Original HQ Entry” will have a value for these lines (contrary to the “original” lines).
the analytic reallocation
the change of the account
(US-8208)Whenever a VI export is made, a message is stored in the logs with the filename and the database name
Whenever a VI export is made, a message is stored in the logs only (i.e. nothing is displayed in the interface) with the filename and database name. Logs are visible under Administration => Reporting => Audit => Client Logs.
This applies for these reports:
OCP matching export
Export to HQ system (OCP)
OCB matching export
OCB matching export Access Interface
Export to HQ system (OCB)
Export to HQ system (OCB) Access Interface
Example of log:
All Finance tickets integrated in UF21.0
Non- functional
(US-7019): Password policy best practices
Following a request to improve the UniField password policy, the following best practices have been integrated in this release as follows:
Unifield user password has been enhanced with the following requirements -> 8 Characters : 1 capital letter, 1 number, 1 special character.
Expiration of passwords: Users will be forced by the system to change their passwords every 6 months after their last password update. This rule will not apply for:
production sync users, generic sandboxes, and testing environments (runbots and VMs for core team and dev)
Administrator user
UniData users
NB: After the release, all users in production (including admin) will be prompted to change their passwords at login.
Each OC IT referent will be responsible for changing passwords for the synchronised users (synchronization white list) at HQ except for the apm user which will be updated by core team. Below is a screenshot guide on where to find the synchronisation white list in UF.
(US-8172): Most secure/efficient ways for auto clean-up of UF DB backups
The current 20.1 and older versions of UF allowed for failed backup files to be valid and kept which consumes disk space. This issue is fixed in this version 21.0. UF will no longer keep failed backup files (all dumps that complete with a non-zero exit code will be considered as a failure by the system). The failure generates a report of an empty KO file in the “Get Backup Files” view
(US-8403): UF All-In-One setup may corrupt pre-existing PostgreSQL configuration files if not ending with new-line
The postgres configuration file was being corrupted causing postgres service to stop. This was due to an erroneous appendage of lines in the postgres.conf file. UF21.0 fixes the issue by adding a new line break before the parameters added by UF in the config file.
The decision and process to destroy any product should be in adherence with your OC procedures. In UniField, the destruction process will usually be done in two steps. The first step will move the goods to quarantine. The second step will move the goods from quarantine to the “Destruction” location.
One of the likely triggers for this will be when a supplier claim has been created, and the decision has been taken to scrap the product. See previous section and LU on claims for details.
If the product being scrapped is not linked to any claim, it will still have to be moved out of the internal warehouse location to quarantine. This will be done through an Internal Move (INT) as explained in the previous section.
In order to complete the process of scrapping a product (second step), it is necessary to create an Internal Move to move the goods from quarantine to the “Destruction” location. Again, an appropriate “Reason type” should be selected on the INT.
Internal Move to destroy products
Note that it is possible to skip the first step and directly destroy products (i.e. moving them from stock to destruction via an INT) but this is not an advised process.
Following the development of the “Receptions report” (see section above), this new report mirrors this latest report by gathering all together all the major information regarding processed deliveries.
The report should only export lines from OUT(and OUT-CONDO) which are in the state Closed or Delivered and from SHIP which are in the state Dispatched or Received.
Go to:Warehouse / Reporting / Deliveries Report
Select any filter you need among the following: Date from; Date to; Partner; Source location; Product Main Type and/or Destination Location.
The “Move Analysis” functionality is another tool which allows investigating on all movements.
Go to: Warehouse / Reporting / Moves Analysis
Move Analysis
Clear the current filters by clicking on the “Clear” button.
Use filters and “Group by” options to select which movements you want to see and how you want to see them.
Click on the “Search” button.
The “IN & OUT Report” (previously named “Export Moves analysis”) is producing a similar report based on several selection criteria but the report is generated in Excel.
Go to: Warehouse / Reporting / IN & OUT Report
1.Click on the “New” button.
2. In the selection screen, enter parameters for the movements selection:
a)By date: even though it is not mandatory and performance has been increased, it is still recommended to use this filter set on movement’s date.
b)Advanced filters such as Partner, Product, Product list,BN or ED can also be used
c)Specific location can be selected: you have the option to select one, several or no location.
If no location are selected and the “Only display standard stock location” box is ticked, then movement between non-standard locations such as Input; Cross Docking; Packing, Shipment, Distribution and Quarantine will not be displayed.Note that even Deactivated location can be selected.
d) Reason type
IN & OUT Report
3. Click on the “Generatereport” button.
4. Open the Excel file via the action menu.
IN & OUT –Excel report generated
Please note that the “Total stock after movement” is done for all instance in case no location is selected while it will be per location-s selected if a/some location-s are selected (if several locations – quantities will be aggregated). The location will be indicated between brackets under the column header of “Total Stock…”.
This functionality focuses on Picking, Packing and Delivery Orders (PICK/PACK/OUT). It may be used to see which products have been /are being delivered. According to the filters applied, the user can search by products, but also by partner, which could be useful to see what has been or is due to be delivered to a specific project.
Go to: Warehouse / Product Moves / Deliver Products
Deliver Products
The system will by default show all deliveries which are in progress. Clear this default selection by clicking on the “Clear” button.
Enter your selection criteria (partner, product,…).
This functionality allows to analyze Incoming Shipments. It can for example be used to see if a particular product has arrived or is expected to arrive.
Go to:Warehouse / Product Moves / Receive Products
Receive Products
The system will by default show all receptions which are expected / in progress. To search for a specific product, clear all applied filters by clicking on the “Clear” button.
In the “Product” filter, enter the product on which you wish to investigate.
Click on the “Search” button.
Receive Products
The system shows all Incoming Shipments where this product is involved.
This functionality can also be useful for the warehouse officer to see all deliveries which are due to arrive today, thanks to the “Today” filter which will display INs expected today.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
