Release Details

Release version: UF 30.1

Date of production synchronization server patch: 27^th September 2023 / 18:00 Geneva time

Latest user rights files updated: UF30.1 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=12487

Supply

(US-11974) MML – PO Confirmation with “process anyway” not allowed – UF request Fin_Budget group profile & (US-12011) Issue with MML PO Confirmation if Supplier internal

This issue, linked to the new functionality of MML meant that users could not confirm certain POs. POs affected were those containing products (MED) which did not conform to MML. Issue was due to the extra popup which was added to check if user wanted to confirm PO despite the MML non-conforming product(s). This has now been corrected and the user rights were adjusted for this to work correctly. Other issues found also linked to MML / Confirmation with POs to ESC and Auto VI import were also corrected.

(US-11956) Patch script to correct to POs with traceback issue due to prod by nomenclature

This issue was a side effect of US-11563 in UF30. This meant that certain POs displayed a traceback meaning they could not be viewed or processed due to their containing products by nomenclature and having source document of FO or IR for External CU. These POs have been fixed via a patch script.

(US-11920) To ignore Returned shipments from the list of open shipments when deactivating partners

With this ticket, the inconsistency of Returned type Shipments has been corrected so that all levels at line level share the Returned status too. This issue was blocking the de-activation of Partners and causing issues with decommissioning of instances so this has been resolved.

All Supply tickets integrated in UF30.1

Finance

All Finance tickets integrated in UF30.1

Release Details

Release version: UF 30.0

Date of production synchronization server patch: 13^th September 2023 / 18:00 Geneva time

Latest user rights files updated: UF30.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:

Supply

(US-10748) MSL & MML in UniField

Medical Standard Lists (MSL) and Medical Master List (MML) are now integrated into UniField. The data from the lists are managed in a UniData Medical Standard List tool at HQ level outside of UniField. Data added to this tool will automatically synchronize into UniField. Although there are some cases of LOG products in MSL/MML, these lists are intended for Medical products.

An MML submenu was added to the Products tab in UniField version 29.0 to synchronize data from UniData to UniField. This submenu is now visible in

MML Products: The Medical Master List (MML) is a list of products which are OC Validated. Some MML Products are restricted to a specific mission or project. These products are included in the MML but Restrictions and Use Comments are noted.

MSL Projects: This list will show a list of MSL projects linked to that mission. It is possible to activate and deactivate MSLs on this page. Once activated, the MSL is automatically updated by any change made to it in the MSL tool.

MSL Products: All products in any active MSL Project are listed in this submenu.

The product details for individual products have also been updated. OC Validation has been added to the “Information” tab to show that the product is Validated on OC level. There is also a new “UD OC Validation” tab in each product datasheet.

Use Comments are shown in this tab along with information about Mission or Project Restrictions. Additional information about whether the item is included in the MML or MSL is also shown in this new tab.

An MSL Non Conform report has been added to the Action Menu of MML Products to show the medical products in stock that are not included on the MML/MSL. Sometimes a project or coordination will order on behalf of another instance, even if the products don’t exist on the shipping instance’s MSL. These items which will be shipped to another partner are only shown on the report if the “Include in-pipe quantity” box is ticked.

A column showing whether items are included on the MML/MSL list has been added to supply documents (IR, FO, PO, IN, OUT, etc). The lines with products that are not included in the MML/MSL will be red. There will also be a notification at the header of the document. Last, a pop up warning will appear when validating or confirming a purchase for any items that are not included in the MML or MSL. None of these types of alert levels is blocking: it is possible to continue to process document/line, even if the product isn’t on the MML.

(US-11369) Import AD Multiple Lines on draft PO and FO

It is now possible to import multiple Analytical Distributions on the same PO or FO line. The process to import multiple ADs is the same as the process to import one AD (by exporting, modifying then importing the template found on the page).

If only one Cost Center and Destination are used on a PO or FO line, the format of the template looks the same as it has in past versions of UniField. In this release, multiple Cost Centers, Destinations and Percentages can be added to the template by separating the values with a semicolon (;).

To be able to import the document, the numbers in the Percentage column must add up to 100 and the total number of semicolons in the Percentage, Cost Center and Destination columns must be the same.

(US-11534) Auto save line quantities when adding multiple lines

Previously, if a user entered a quantity in the Add Multiple Products popup, the quantity would only save if the user clicked on . If they clicked on the next line without saving, the quantity entered changed back to zero.

Now, quantities entered in any ‘Add Multiple Lines’ screen (FOs, IRs, POs, RfQs, Tenders, Catalogues, INs, INTs, OUTs, Real Consumption, TKC, KCL, and Initial stock inventories), will be automatically saved when clicking on another line.

(US-11563 & US-10783) Allow PO to have Multiple Destination Locations

Destinations in a Purchase Order indicate where the products should be received (Input for items to be stocked, Cross Docking for items to be delivered out and Service/Not Stockable for specific products).

It is now possible to have multiple destination locations in the same PO. Previously, the Destination Location was managed at header level so it had to be the same for all lines in a PO. This could cause problems when a merged PO had IRs/FOs with different destinations. A new “Destination Location” field has been added at line level so that items can be received in the correct Destination Location in the IN, even if some items will be delivered (Destination = Cross Docking) and others will be stocked (Destination = Input). This field can be viewed in the Purchase Order Line’s pop up view. It is only possible to have one Destination per line.

The same PO can have different Line Destinations on different lines. The Destination field in the PO’s Delivery tab will show all of the destination locations included in the PO, based on the different Line Destinations.

(US-2411) Add status column to OUT document

In this release, a “State” column has been added to the PDF of the Delivery Order to make it easier to distinguish between Available and Not Available lines in an OUT.

(US-11181 & US-11787) E-VALIDATION for FO/OUT/Pick

It is now possible to electronically validate/sign three new supply documents: Field Orders, Delivery Orders and Picks. If E-validation is activated, these modules will each have an additional Signature tab where users can manage signatures and / or sign documents. The process to sign electronically is the same as the signature process for other supply documents (Internal Requests, Purchase Order, Reception,…)

The total quantities at the time of signing are shown in the e-validation line. To make it easier to compare the quantities when validated to the printed document, Total Quantities have been added to the OUT, IN and Pick PDF documents.

To allow e-validation of Picks, there is now a signature box at the bottom of the Pre-Packing List. The quantities shown in this document will be the Total Quantity if nothing has been picked or the Picked Quantities for closed Pre-Packing Lists.

Signatures can be added at any time. In case a signature was added to a document that was only partially processed (creating a new document), a warning message will appear, indicating that the signature needs to be added to the new document. The signature will remain in the original document.

(US-11636 & US-11433) Added filters/ fields in Export PO Follow-Up

Several improvements have been made to the PO Follow Up Report. New columns have been added to the Excel document to show the Order Category, Priority and “Source Creation Date” (the creation date of the IR or FO that is linked to that PO line). It is now possible to filter the report based on these new columns.

Additional filters have been added to the Report configuration page making it possible to view only certain Order Types or Categories. If no box is ticked, all lines will be shown.

All Supply tickets integrated in UF30.0

Finance

(US-10874) Improvement Internal transfer: auto booking of counterpart (in the same instance)

We have improved the internal transfers within the same instance.

1 – A counterpart is created at temp/or direct hard posting of the initial entry. The creation is at first posting of initial entry only. We have an icon for visual purposes, to advise about the link between the initial entry and the counterpart.

2 – When we edit/delete the initial entry (in temp status) and the counterpart entry (in draft or in temp status) : there will not be updates:

• Initial entry in temp status: allow edit/delete. No update to counterpart entry.
• Counterpart entry in draft or temp status: allow edit/delete. No update to initial entry.

3 – It is not allowed to manually reconcile entries if there is a counterpart at project level or coordination. There will be an error message.

4 – When the counterpart or initial is deleted, the link will be break. At that time, manual reconciliation is possible.

5 – When the reconciliation is undone, the link is broken and it is allowed to manual reconcile back with various lines without link.

6 – To keep a coherence, automatic reconciliation will be for both same or different currency.

7 – Only do Full reconciliation. Don’t proceed to partial reconciliation when amounts don’t match:

• Reconciliation same currency: Full reconcile when amounts debit/credit match.
• Reconciliation same currency: When amounts debit and credit do not match, do not allow reconciliation and as consequence, break the link. Allow lines to be reconciled with entries without link. This covers also the use case when there is no debit or no credit (both lines in the same sides of the booking).
• Reconciliation different currency: always reconcile as the amounts will never match due to UF rate vs local rate difference. Any difference will be FXA as per current behaviour.

8 – Reconciliations are manually un-reconcilable = that means they are tagged as “manual” even if system does it automatically

BEHAVIOUR TABLE BETWEEN INITIAL AND COUNTERPART BOOKING

(US-11130) OCBHQ to have in the Combined report and JI and AJI exports the accounts mapped: “HQ system accounts” at project level

For the instances that will import accountancy entries from UF in their local accountancy application, OCB has a mapping of the accounts.

They requested to have the option to select accounts mapped in the reports Selector, Combined Journals Report, and in JI and JE.

In the Selector and in the Combined Journal Reports we have now the possibility to add accounts that are mapped in: Accounting>Config>Accounts>Account mapping:

• Accounts mapping is now synchronized down.
• There is new tick box “Display HQ system accounts mapping” in the company for, “Configuration” tab, when ticked.
• HQ mapping is displayed on JI, AJI list views.
• HQ mapping is exported in Selectors and “Export Search result”.
• HQ mapping is displayed on Selectors in accounts field.
• New extended filter “HQ System Account” on JI and AJI.

(US-11289) Search: Supplier and customers screens: to remove the field “Journal” and to replace it with “booking currency” field filter

In the menus Customers and Suppliers we have added the Booking Currency field.

Some examples here for suppliers:

(US-11303) Accruals: to add a filter by number in the “Search: Accruals Management” screen

In the accruals search view, we have added a filter by number.

(US-11311) Bank and Cash registers created in a special period: to prevent!

We have done several changes in order to ensure that:

• Only regular periods are shown in the [period] field of the registers. This is the case if we navigate this field.
• When changing the date of opening to a December date, in case December period is not open => an error message is shown like when the period is not open:

• When changing date of opening to December date, the extra accounting periods are not displayed as option, even one of them is in open status.

(US-11548) For IVO and for IVI: to put in the list all accounts with type regular, expenses, payables and receivables (as in the Supplier Invoices)

For IVO and IVI, we have allowed the accounts that are now in the SI header and we have removed the regular equity accounts and  the accounts with the type for specific treatment “Down Payment” /”Operational Advance”  (in OCA account number 13610 and in OCB, OCP, OCG account number 13100).

(US-11601) IIL auto import configuration in UF HQ_OCA

OCA have requested support for the configuration of automatic import of IIL (International invoice lines) from SharePoint to UF HQ_OCA.

(US-11715) OCG: Automated import setup and testing for destination (daily import) 2

OCG has requested support to setup the automated import for destination in our HQ OCG sandbox.

All Finance tickets integrated in UF30.0

Non- functional

(US-11484) Prevent Modifying Proprietary Instance Fields as Soon as It Is Used

Proprietary instances have always been created with all fields editable but once the instance is used in journal entries the code, level and Parent should not be changed. This release disables the ability to edit these 3 fields completely. As seen in the screenshot below, these fields will be read only for all users including administrator.

(US-11602) To Have a Pop-Up Asking for The E-Mail Address.

The UF30.0 release will include a pop-up prompting users to input their email address. This will not be a mandatory field so users can proceed to login without inputting their email address. However, the pop-up will continue to be displayed up to a maximum of 3times until 4^th December 2023. After this, the user can still provide the email address in the following ways:

• In the preferences menu at the top right corner of the UniField application window as seen below.

• Upon password expiry, the change password dialog box will have the email address field displayed. The email field will not be mandatory so one can proceed to change password without it.
• With user_manager rights directly in the user objects

Please note: For synchronized users, the email field can only be filled in at HQ using admin user or other user with access to managing synchronization whitelist.

(US-11616) Remove Block on Patch Application If CC For FO/PO Ref Is Not Set.

Instances with no cost centre for FO/PO reference set could not upgrade to new version of UF as seen with the release of UF29.0 in US-11613, US-11627 and US-11635. Instances were stuck at upgrading modules until the FO/PO cc was data fixed. The UF30.0 release removes the block on patch application for such instances. Instances without the cost centre for FO/PO reference set can now upgrade to newer versions of UniField.

(US-11668) Prevent Deletion of Synchronized Users and Allow Recreation by Sync If Deleted.

All users with user_manager access group were able to delete synchronized users on the coordination and project levels. This improvement now ensures that a deleted synchronized user is recreated by sync after deletion. In addition to this, in the linked user rights ticket US-11691 we have removed deletion rights from user_manager access group. Only activation and deactivation will be possible. Any attempt to delete a synchronized user will return error message: Cannot remove a synchronized user.

(US-11734) To Auto Activate International Invoice Lines (IIL) On New Instances For OCA

The current process of activating IIL for existing instances is manual through the Reconfigure menu in Administration tab. This improvement ticket ensures that IIL is automatically activated for all new instances in OCs that desire it. In this specific case for OCA, their auto install config file template is now set to:

Activate International Invoices Lines = Yes 

If another OC desires to have IIL already activated for new instances, we shall update their auto install template after formal request via Jira.

All Non-functional tickets integrated in UF30.0

Release Details

Release version: UF 28.1

Date of production synchronization server patch: 5^th April 2023 / 18:00 Geneva time

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

Supply

(US-11297) Order in Sync Instance Missing

The changes made in US-10180 made it mandatory to fill the Order in Sync Instance field in FOs in order to validate added lines.

It was not mandatory to fill this field for FOs created before release 28.0, so this field is empty for field orders created before the last release. If any lines in the FO have this field filled, it must be filled for any added lines, including lines which have been cancelled and resourced.

This change ensures that it is possible to Cancel & Resource PO, IN and Pick lines with FOs that have at least Order in Sync Instance filled when the resourced line was not.

(US-11176 & 11146) Allow KCL for perishable items to be added to INs and OUTs

Ticket US-7603 made it possible to enter a KCL reference in INs, Picks and OUTs. Of these documents, only the Pick could add a KCL reference for items that were managed by batch number or expiry dates. This change ensures that the KCL reference items managed by BN/ED can be added to OUTs and INs.

All Supply tickets integrated in UF28.1

Finance

(US-11252) ADVANCE MANAGEMENT: Correction of US-10279 – show all advances button”

After this development, we are able to settle advances from one register in another register. This is very important for settling bank or cheque advances which are 99.99% of the case settled via cash register.

We have a default checked button to display ONLY entries from that specific register. When the button “ONLY THIS JOURNAL” is activated, it shows advances from the register we are in. If it is not selected, we show all advances from all registers as follows:

• when we are at COORDO level, we can see the open advances of all registers, all periods, of all instances, in the same currency, which are not yet settled, and which are in Temp or Hard posted status.
• when we are in a PROJECT level, we can see the open advances of all registers, all periods, in the same currency, which are not yet settled, and which are in Temp or Hard posted status.

All Finance tickets integrated in UF28.1

Release Details

Release version: UF 28.0

Date of production synchronization server patch: 15^th March 2023 / 18:00 Geneva time

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

Supply

(US-7598, US-7603, US-10562) Changes to Kit Composition Lists

With this release there are several changes to Kit Component Lists (KCL) and how their components and expiry dates are tracked and managed.

A ‘Kit’ column has been added when processing KCL, Kitting Orders, PICK, Pack, Ship, Delivery Orders and Real Consumption to make it possible to identify which kit is being processed. It is not mandatory to identify a KCL in the ‘Kit’ column, but when one is chosen, the kit being processed will be linked to the document that’s being processed. This information will be shown on the related documents.

When a Kit is processed in an OUT, the KCL will be automatically set to Status “Closed” when it is sent out of the instance. If a KCL has kit as a component, the component KCLs will also automatically be set to Closed status when the top KCL is closed.

If the kit has components that need to be managed by Batch Number/Expiry Date, these fields will be mandatory in the KCL for the kit and its components.

(US-7957) Improved usability in the OST

Several changes have been made to make the Order Sourcing Tool more user friendly. It is now possible to click on column header to sort by Requested Delivery Date.

A new link has been added to the Action Menu when a line is selected in OST which displays all POs that contain this Product.

Last, in the Supplier pop-up that opens after clicking the magnifying glass, suppliers that have an active catalog which contain selected item are displayed in green at the top of the list.  

(US-8454) Upgrade of FO, RFQ, Tender for consistency

In this release, the functionality of Field Orders, Requests for Quotation and Tenders has been updated to make them more easily editable and to make line level information more easily viewable.

Previously, Field Orders and RFQs could only be modified in the pop up screen. In the current release, there will be 2 icons to the left of each line to allow the 2 different modes of edit: a “Pencil” icon to edit directly in the line, and a “doc” icon to open line in pop-up. Clicking anywhere on the line will allow the line to be edited in line-mode. In addition to being editable at line level, it will now be possible to add lines by Nomenclature in FOs and RFQs. The process for adding products by nomenclature in these documents will follow the same steps as the current functionality for POs.

Header information for FOs, RFQs and Tenders have been updated to make the naming more consistent, and to ensure that pertinent information is shown in each document.

(US-9495) Re-sync between internal partners

The Re-sync functionality that allows orders to be synchronized to a third (external) UniField instance has been expanded to allow synchronization to a third internal instance. This means an order can be created at a project, synched to Coordination and the Coordination could then send the order (by sourcing the FO to a PO) to another project in the same Mission. Transport documents will work in the same way as previously: each order document will have a corresponding transport document for the goods flow. The “Re-synch” mechanism is limited to 3 UniField instance partners and not more.

The functionality for DPOs remains the same; this Order Type can only be issued to External suppliers. This means that DPOs can only be created in the final instance with the second instance as the Consignee/Delivery partner. This is where the IN for these goods must be received. For the original requestor to receive the goods, the second instance must use the Pick/Pack/Ship mechanism to send goods.

Diagram 1: 2 possible DPO flows

1. The order is initiated at project1.1, and order sent to Coordo1, who sources to project1.2 in the same Mission. Project1.2 can source the order onto a DPO to an external/ESC partner. The delivery flow (red arrow) starts with External/ESC partner and goes directly to the middle internal partner Coordo1.
2. The order is initiated at project1.3, and order sent to project1.2, who then source to their project1.1 in the same Mission. Project1.1 can source the order onto a DPO to an external/ESC partner. The delivery flow (red arrow) starts with External/ESC partner and goes directly to the middle internal partner proj1.2

*Only some possible flows are displayed, however bother internal and DPO flows are equally valid for any combination of flows between 3 internal partners of same mission.

(US-9874) Improvement on the LOAN flow documents’ naming

An additional Order Type has been created for processing Loans. When processing INs, POs and FOs for loans, “Loan Return” has been added as a reason type. When the “reminder” document is automatically generated by the system, the system will automatically add the reason type “Loan Return” to this document and all transport documents which follow.

(US-10180) Adding new lines in synced FO – Order in Sync Instance

Each FO line created by synchronization is linked to the original request in the field “Order in synced instance”. If a line is added to a synchronized Field Order, the line will be red and it will not be possible to validate the FO until the line is linked to an original request from the requesting instance.

It is now possible to link an added line to the original request by opening the FO pop up and selecting the order in the mandatory Order in Sync instance field:

With this change, the added lines will be able to enter the stock or be included in the OUT for delivery following the reception the goods.

(US-10585) Merge 2 UniData products functionality

In previous versions of UniField, if two products that are active in the HQ instance are merged in UniData, the items had to be manually deactivated and merged. This could only be done when there were zero stocks in all instances and no open transactions for this product.

With this release, two UniData products can be merged at HQ, even if they are in stock or have open transactions. Once the merge action has been performed for the 2 UniData products, the selected product will be de-activated in HQ. After synch, this product will be de-activated in all Coordination and Project instances, and any quantities in stock or open or closed transactions will be updated so that the active “kept” product will appear in its place.

There are 2 new reports which display products which have been merged; one accessible at HQ and one at instance level (Coordination and Project) displaying Products which have been merged.

User rights for merging products at HQ have been added to the group Sup_Config_HQ.

All Supply tickets integrated in UF28.0

Finance

(US-6710) New Cost center (CC) import behaviour in Tools/Import-Export/Finance:

We have done an improvement in the export/import file be able to import the cost centers for their creation. This is import is just for the creation and not to update the cost centers that exist already un the system. If we import a cost center already in the system, the hole file will be rejected and we will get an error message:

CCs with a “Top prop instance” to be tied with but with no target instance will reject the whole file as target is mandatory for each CC.

All file is accepted or nothing.

The new import file will have 4 new fields :

How to do the extract of the new improved file:

Go to Tools > Tools > Import/Export > Finance.

Filter “Object to Import/Export” by “Cost Center”.

Under “File export” click on “Export empty template”, you will get extract with the following headers:

Example:

(US-7624) Remove the possibility of partial import for automatic import of international staff (employees) (let possible ONLY the TOTAL import)

In the menu Human Resources, Import Expats: We have removed the possibility of partial import for automatic import of international staff (employees).

The import must be total or rejected if the file contains errors.

CASE 1: If there is no error at all:

• If the file is “processed” ==> it will have all the employees displayed.
• If the file is “rejected” ==> nothing will be displayed.

CASE 2: If there is one or several errors:

• the file is “rejected” ==> it will have all the employees displayed – because all of them has been rejected!).

There will be an ERROR column. If the column is not empty, it means that the employee contains an error to correct.

The error message that will be on the rejected file: “THE EMPLOYEE DOES NOT HAVE AN ID NUMBER AT LINE X”.

CASE 1: If there is no error at all:

• If the file is “processed” ==> it will have all the employees displayed.
• If the file is “rejected” ==> nothing will be displayed.

CASE 2: If there is one or several errors:

• the file is “rejected” ==> it will have all the employees displayed – because all of them has been rejected!).

There will be an ERROR column. If the column is not empty it means that the employee contains an error to correct.

The error message that will be on the rejected file: “THE EMPLOYEE DOES NOT HAVE AN ID NUMBER AT LINE X”.

(US-9215) Intermission/intersection: IVO/IVI Change the fields name from “reference” to “description”

IVO (Intermission voucher out):

Go to Accounting > Customers > Intermission Voucher OUT> Invoice

No more “Reference” field, now renamed as “Description”

IVI (intermission voucher in):

Go to Accounting > Customers > Intermission Voucher IN > Invoice

No more “Reference” field, now renamed as “Description”

(US-10279) Open advances: When clicking on “Open advance” button from a given register: filter of the list of open advance per journal code of the register where we are

Go to: Accounting/Registers/Bank registers

Select a bank register.

Go to “List of Open Advances” in this bank register.

You arrive to this screen: Search: Open Advances – BA010 – BDT

(before this development, we had not the journal name)

When clicking on [open advance] button from a given register – filter the list of open advances per the journal code of the register where we were:

(US-10353) Selector (GL and combined): to add a new checkbox “Exclude inactive journals” with also the filter journal inactive date.

We have created a new checkbox “Excluded inactive journals” and also a date on the G/L Selector and Combined Selector:

(US-10410) Combined journals reports: allow multiple sequence numbers on the selection

In the Accounting/Selector/Combined Journal Report we are now allowed to add multiple sequence numbers to search “Combined journal reports”:

(US-10652) Improvement of the Supplier list (Search: Suppliers): to add 3 additional filters

Go to partners, Suppliers/Suppliers and add after Partner type and zone 3 additional filters:

• purch default cur: purchase default currency
• cur acc rec: currency accounts receivable
• and acc pay currency accounts payable

(US-10653) To improve the Liquidity Balances report: to be able to select from the HQ all the liquidity balances (Coordo and project)

At HQ level, go to Accounting/reporting/legal reports/liquidity balances:

==> Now we have the possibility to select all missions at once in the liquidity balance report: coordinations and projects.

==> The result is sorted by instance code and journal code.

(before this development we could select all coordinations -so we had the liquidity balances of the coordinations at once – but we could not select the projects, so we didn’t have the liquidity balances of the projects).

(US-10838) To add additional error messages in the Export/Import invoices in case of import of wrong or empty destination or funding pool

In the Export/import invoices, we have added additional error messages in case that we import a wrong or an empty destination or funding pool:

Example:

(US-10850) OCG Vertical integration: modification of the formatted data file: department column (exception to the CD1 mission)

We have done a change in the formatted data file exported from UF (to be imported in D365) as follows:

• for any accounting line that does have a cost center, the department field should be the first three characters of the cost center (ie: in the instance MX1, if cost center is MX101, department is MX1, if cost center is MX301, dpt is MX3).

• for any accounting line that does not have a cost center (ie: balance sheet accounts), department should be the name of the instance (in the instance MX1, dpt is MX1.

This change has been applied to all OCG missions, with the exception of CD1 where a specific development was made and should not be updated.

(US-10897) In Tools: To add the field “Phone” in the excel file of “Suppliers”

In Tools (XML File)

Go to Tools > Tools > Import/Export > Supply

From “Object to Import/Export” select the object “Suppliers”

==> we have added an additional column with the field “Phone”:

All Finance tickets integrated in UF28.0

Release Details

Release version: UF 26.0

Date of production synchronization server patch: 14^th September 2022 / 18:00 Geneva time

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

Supply

(US-10168) Lookups for headers and constants should be case insensitive

This improvement ticket is to ease the importing job in UF, it is now acceptable for all Supply imports in UniField to have inconsistent cases, e.g., UoM “pce” instead of “PCE”, or “Pce” instead of “PCE”, file will be recognised and imported.

(US-10051) Accurate naming / addition for product codes XMLID / MSFID

This ticket is to improve the accuracy / visibility of background product id codes:

• In Tools>Object Query > Products

Possible search field has been updated so that it is now named “MSFID” (previously it was named “hidden field for UniData). It is also now possible to search for additional field “SDref”.

• In Product PMD>Action menu>View Log:

i) existing label “Internal module data ID” is now renamed to “SDref”
ii) existing label “UniData xmlid_code” is now renamed to “xmlid_code”

• In Product PMD>Action menu> Export

User can search for field MSFID, and MSFID is not possible to be changed by users via import or update products menus (should not be possible to update MSFID of product via import (MSFID should ONLY be added/changed by by UniData)

• Log to show if the MSFID of a Product has been changed has been added to track changes In Product PMD>Action menu> Track Changes

(US-10010) Avoiding Local products import at Project

This improvement ticket is to avoid the issue of users accidentally creating or updating products in project-level instances. In this release below sub-menus are no longer accessible in projects:

• via menu Products > Import products> import products
• via menu Products > Import products> update products
• via menu Tools > import / export > Supply
• via menu Tools > automated imports > Products

(US-10008) Disable tick box “Cross Docking”

This improvement ticket raised by OCA, to prevent user from changing the destination location on the PO level. Users can still do the change in the IN level. In the PO, the tick box “Cross Docking” in the tab “Delivery” is not visible anymore for users.

(US-9968) Blocking the creation of EPREP in Intermediate stock location

Improvement ticket raised by OCB, to stop the creation of “EPREP” location under the “Stock” category, system prevents such a location being created if name includes word “eprep” and a message is displayed to stop this action:

(US-9962) VI: If E-Packing IN > PPS import cannot be done (forced availability/negative stock) clearer message

Improvement ticket raised to avoid previous issues found by OCB. In the flow of ordering, sourcing, and importing E-packing VI import into IN with the option to pick & pack after, if one of the products is already “forced” as “Available” in an unrelated OUT from the same location (Crossdocking), the import could not be processed. With this dev, system will now check at IN import (if IN>P/P/S) that products do not have a negative available stock in CD location, and if so, the import will be blocked and product code / qty displayed in warning message. Same check done for all types of VI IN import.

(US-9744) Remove PI C/S check on line reference.

Improvement ticket raised by OCB, to avoid any duplication in Physical Inventory. At import of Counting Sheet, system will no longer check the line reference in file at import of counting sheet.

System will keep the check of Product / BN / ED, duplicate lines, and match imported Prod/BN/ED, add new lines, etc.

(US-9509) Product UniField Status after re-activation of product.

Improvement ticket raised by OCG, to ensure the consistency for UF Product Statuses when a product is manually re-activated. At manual re-activation, the product’s “UniField Status” should change accordingly. In the case of UniData products, the UF Status should be updated based on its “UniData Status” and “OC Subscription”.

• For HQ, ITC and ESC products at HQ: If product re-activated, then UF Status automatically set to “Valid”
• For Local products at Coordo: If product re-activated, then UF Status automatically set to Valid
• For UniData products at HQ: If product re-activated, then the following is the result:
• If Product is OC Subscribed = FALSE, then UF status > No change (remains Archived or Phase out)
• If Product is OC Subscribed = TRUE, and:
• UD Status = Forbidden then UF status > No change (remains Forbidden)
• UD status = Archived then UF status > No change (remains Archived)
• UD Status = Valid / Outdated/Discontinued then UF status > set to Valid

(US-9229) New Reason Type for OUTs: Deliver Unit

Improvement ticket raised by OCA, to improve the analysis of stock movements and to ensure greater consistency. With this ticket a new Reason Type (RT) is introduced for stock movements towards External Consumption Units. The default RT on any OUT or (converted) Pick to an External CU is now “Deliver Unit”. This new RT can also be selected in an OUT from scratch (although Default RT remains “Deliver Partner” for this). For both Picks and Outs, the RTs at line level will now be consistent with header level RT. The RT “Other” can no longer be selected.

Previous documents (Picks and Outs) have been migrated to conform to the RT logic as follows:

“Deliver Unit” for all OUTs created for IR with Ext CU.

“Deliver Unit” for all Picks created (via converting OUT) for IR with Ext CU.

“Deliver Partner” for all OUTs and Picks created for FO to customer.

“Consumption Report” for all OUTs created via a Consumption Report.

These documents have had their RTs at line level adjusted to be consistent with header level RT

(US-8966) Cancel / C&R multiple lines to be consistent with single lines in IR/FO/PO

This improvement requested by OCB, ensures Cancel and C&R of lines is consistent in IR/FO/POs. It is possible now to cancel / C&R multiple (Draft/validated) lines, in Draft-p / Validated/ Validated-P IR/FO, and also in POs with supplier type ESC or external, (It is not possible to Cancel / C&R validated lines in PO with Internal/Intermission/Intersection type suppliers if they are beyond “Draft” status).

(US-8864) Export Inventory Level lists batches with no movement in the selected period

Improvement ticket raised by OCA, to improve the Export Inventory Level report, in case the checkbox “Include products with stock <= 0 with movements in the last months” is ticked, and X months is selected, report generated will include Products and their EDs/Batches which are in stock or have had movements in the last X months, and exclude the ED/batches which have not moved in the defined value X months and are not in stock.

(US-8428) Physical Inventory – Planned Inventory vs Stock Correction

Improvement ticket raised by OCB, to improve options for inventory management, in the Physical Inventory, the checkbox for “Full inventory” is replaced by a mandatory drop-down list with below options:

• Full inventory count (planned),
• Partial inventory count (planned)
• Stock correction (unplanned).

If 3rd option is selected “Stock correction (unplanned)”, only the “Add” button displays to allow products to be added. The button “Products selection” is not displayed.

Drop-down list values of (Inventory Type) options can be changed as long as no products have been added yet.

The rest of the functionality stays as per before.

(US-7323) Add Product search field for INs etc and PMD Action menu links

This Improvement ticket was raised by OCG. For more consistency and to extend the searching possibilities, an additional search field for “Products” has been added at header level in the List View for each of these documents: IR, FO, Tender, RFQ, INs, INTs, Outs, Picking, PPL, so as to behave like that existing in POs list view.

Also, in the Products/PMD Action menu, links to see the relevant documents for selected (ticked) product have been added. Links displayed are: Field Orders – Internal Requests – Purchases- RfQ’s – Tenders – Incoming Shipments – Internal Moves – Delivery Orders – Picking – Packing.

(US-5190) Remove possibility to split Draft FO lines

This improvement ticket is to avoid several issues caused in the past leading to NRs and wrong data, and means it is now not possible to split FO lines directly in FO in Draft status. Other functionalities allowing split in FO lines at a later stage (OST, PO, IN etc) remain as before.

(US-3694) Product sheet: Display inventory level from all locations

Improvement ticket raised by OCA, to update the calculation of Real stock and Virtual stock displayed for products so that more locations are taken into account. The calculation of Real/Virtual stock now includes the product Qty in the following locations: LOG/MED in main stock AND all configured Internal locations (Intermediate stock and Internal consumption units). AND E-Prep internal locations. It (still) does not include any transition locations (such as Input, Packing, Cross-Docking etc). The revised stock calculation is displayed in the below menus:

• Product Data sheet – a) list view and b) form view
• Search screen for products – ie pop up when selecting products from other transactions (e.g. IR, PO, FO, Tender, RFQ, OUT) having the calculation of the value for Qty “Real Stock” and “Virtual stock”.

Improvement corrections on reports (US-10296, US-10222 & US-7388)

The last 3 improvement tickets to increase the efficiency of UF reporting and for more consistency,

• Bug solved to correct the CDD/EDD in “IR Follow-up per location” report.
• Performance improved for the times’ needed to export “FO follow-up per client” report, selecting IR in order ref no longer possible in this report to decrease the time since there is another dedicated report for IRs doing the same checks.
• “IR follow-up per location”: For more consistency, in the “IR follow up per location” in case of cancelled lines in Delivery out, report is now more accurate and consistent in display of “Qty to deliver” and in displaying “INT Ref.” where relevant. please refer to ticket “US-7388” for more details.

All Supply tickets integrated in UF26.0

Finance

3.1 (US-10241) Get an additional column with the register codes in the list of the Register creation wizard

In the register creation wizard (the path is Registers/Register Creation), we have added a new column named “JOURNAL” that will contain the register code:

3.2 (US-10205) OCA: To sync up the HQ Entry if the CC is not targeted

There is a new behaviour for the cost centers: if the instance at HQ level is targeted with the cost center XX02, but the parent instance is not targeted with the XX02 cost center, now it is possible to synchronize the HQ entry down with the cost center XX02 to the parent instance.

3.3 (US-10115) Code fix for Journal entries: use case with AD KO to avoid: to prevent the edition/change of the AD on a “system” JE

In this dev we have unable the edition/change of an AD on a “system” JE. The “Save” button in the wizard is in grey, so it is not possible to use it. So now it is not possible to update the AD through the “Form” view.

To check this you can:

• Go to Accounting > Registers > Cash register.
• Click in “New” and create a direct entry as expense and temp post.
• Go to “Journal Entries” > “Journal Entries”
• Click on “check box” of the temp posted entry.
• Click on “Form” view:

• Click on the “Analytical Distribution” line. It will open a new window named “Analytic distribution”.
• Click on “Save” and you will see that it is in grey so the command is not active.

3.4 (US-10090) OCB proposal: quick update in Recurring Entries module for management of Fixed Assets

A new Analytic journal DEP has been created in order to use the recurring entries module for the management of the fixed assets.

This is optional per OCs. OCA will not use that for the moment.

• Go to Accounting > Configuration > Analytic Accounting > Analytic Journals
• The Journal code is named DEP, the Journal Name is Depreciation, and the type is also named Depreciation:

The process to create a depreciation entry follows these steps:

• Go to Accounting >Configuration > Financial Accounting > Accounts> Accounts, activate the GL codes for the accumulated depreciation (example code 21200 for the Non-Medical Equipment).
• Go to Accounting > Periodic processing > Recurring entries > Recurring models.
• Click on the button “New” to create a “Recurring Model”
• Go to Recurring Plan and create a “New” Recurring Plan by selecting the Recurring model previously created in the Recurring Model screen.
• Go to “Generate entries” and click on “Generating entries”: it will create entries with the “Journal code” DEP.

3.5 (US-9730) PAYE_UNIFIELD and PAYE_SAGA Import: request to have all the import error messages at once

When we import the payroll file in Unifield, the file import can be unsuccessful because of errors in the import file. Before this dev, we had the first error message, then when it was corrected, we had the second message and so on.

In this request we have requested to have all the wrong messages at once. Here is an example:

• go to accounting/Payroll/employee update: import permois file
• go to accounting/payroll/Import payroll: proceed to the import of the Payroll File.

==> the import is not possible because many errors have been detected. As requested in this dev ticket we have all the error messages at once, and not one by one.

3.6 (US-8954) Entries data integrity report – report header to improve: to add additional fields.

We have improved the Data Integrity report by adding additional fields to the report header in order to have a better visibility of the filter done.

The path to see this report is this: Go to Accounting > Reporting > Generic Reporting > Entries Data Integrity.

Now after improvement the header columns are these:

Some examples of the new header after dev:

3.7 (US-8169) Partners and selectors: issues with inactive partners

In this development we have fixed these issues:

• In the GL selector => The search filter works now also for partners that are inactive. This is to enable the search at HQs, where all partners are inactive.
• For the Journal Items and for the journal entries => The filter active/inactive have the option active by default but give the possibility to select inactive partners too. This will be useful at HQs, where all partners are inactive.

3.8 (US-8088) The “Funding Pools” finance report from Tools needs to be reviewed following the dev of US-7243.

The release UF19 changed the behaviour in the Funding Pools by adding two new fields in the parameters: “Allow all Cost Centers” and “Select Accounts Only”.

According to this, the new Tools Finance report “Funding Pools” has to take into account these new two fields, so we added the columns J and K in the report corresponding to Allow all Cost Centers and Select Accounts Only.

To see the Funding Pool finance report, please follow this path: go to Tools/Import/Export/Finance and choose Object to import/Export: Funding Pools

3.9 (US-8003) UR: Write access to [Responsible] tab of project register in Coordination.

In this dev we have added a window action menu in the right panel of registers called “Modify register responsible”: we have given the rights to this window action only to Fin_coordo group. A wizard is displayed to add or to remove users from the responsible field. The results update the responsible tab in the register.

3.10 (US-7819) Advance return wizard: show the third-party liquidity journal if account code type is “internal transfer”.

We have corrected a behavior in the system and now:

• for “Internal Transfer (same currency)”, we are able to select all the liquidity journals in the same currency except the current journal itself (it is not possible to do a transfer to yourself).
• for “Internal Transfer”, we are able to select all the liquidity journals in another currency.
• Now we have the third party to allow the booking of the entry. It corresponds to the Journal code.

3.11 (US-7790) Data Integrity report VI: add not runs on register lines, account.move,account.move.line, AJI objects

“Not runs” help us to spot problems so we have added the “not runs” on reg.lines, account.move,account.move.line, analytic.account.move objects in the data integrity report as per below:

3.12 (US-7209) Improvement in the “local expenses” report.

This report had performance problems in the past that made it unusable. In order to avoid this, we will not be able to select all the instances at once.

To see this:

• Log into HQ instance
• Go to Accounting > Reports > Generic Reporting > Local Expenses
• It will open a new window “Local Expenses”. Now the default “Cost Centre” is empty. You can not choose the cost center OC (all instances at once).

3.13 (US-6392) OCP Employee Ledger and Employee Balance.

Two new reports have been created for employees following the partner ledger and balance model.

We can see the reports here: go to Accounting > Reporting > Legal Reports > Accounting Reports. We have a new menu called “Employees” with two sub-menus “Employee Ledger” & “Employee Balance”:

Employee Ledger:

This report is an analysis done by employee. It is a report containing one line per employee representing the cumulative credit balance.

Go to Accounting > Reporting > Legal Reports > Accounting Reports > Employees > Employee Ledger:

We will have several possibilities to do our selections using the filters.

Employee Balance:

To see this new report, we go to Accounting > Reporting > Legal Reports > Accounting Reports > Employees > Employee Balance:

We will have several possibilities to do our selections using the filters.

It’s optional to tick on “Only active employees”.

All Finance tickets integrated in UF26.0

Non- functional

(US-10141) Check that database dump is fully loaded during restore.

As seen in US-10140 and US-10117 pg_restore can be stopped before the end of the process. This results in a psql schema with missing data: indexes, foreign keys…. etc which on the web application displays the server as stuck on updating modules with no end.

This release adds a check at login to ensure that indexes and foreign keys are OK, and if not, prevent login and sync. This means that restore will be executed as a single transaction wrapping the emitted commands in BEGIN/COMMIT. This ensures that either all the commands complete successfully or exit-on-error.

Below is the error displayed in the case of a failed db dump restore

We have also added a warning message on the restore window to inform the IT user to wait to be automatically redirected to the login screen once restore process is completed.

(US-9984) Internal partner and instance creation/decommission to automatically inactivate the internal partner in the decommission process

Prior to this release: When an instance is inactivated, the internal partner stays active in the partner instances. This behaviour is corrected in this release to ensure consistency. The inactivation of a proprietary instance at HQ also triggers the inactivation of the internal partner via sync.

This improvement also ensures that:

• If there are open/ongoing supply documents on the partner (no proper cleaning before inactivation), NotRun message msf.instance is generated when the inactive status from HQ is synced down to the instance. This means the inactive status will not be received by the “decommissioned” instance as well as the linked internal partner.

All open documents linked to the target instance for decommission must be closed and synched to clear the NR message msf.instance. Once NR is cleared, the inactive status of the prop instance and internal partner is received by all the mission instances.

All Non-functional tickets integrated in UF26.0

Release Details

Release version: UF 25.0

Date of production synchronization server patch: 15-June-2022 / 18:00 Geneva time

Latest user rights files updated: UF24.1 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=12420

Supply

(US-9766) IR aligned to PO in warnings / IR, PO & FO blocks on high qtys

This ticket aligned the warning messages in the IR to the ones in the PO/FO, and also added some extra checks to avoid excessive digits for Qty / amounts which previously had caused issues. Now for IRs, FOs and POs, adding a line with Qty more than 10 digits is not allowed and warning message is displayed. For IRs, line-level check is made on result of the Quantity x Unit Price that it does not exceed 10 digits, and also for IRs at document level there is a check if total amount/value has more than 15 characters. Warning messages are displayed for all of these cases.

(US-9727) Export inventory level: Do not include batches with qty <> 0 with product list as filter

This ticket raised by OCA, for the inventory level export, when a location and a specific product list have been chosen, and in case there is a product with many batches and zero stocks, reports will exclude the batches with 0 stocks and include one line for the product with zero qty.

(US-9656) Phase Out product should be possible in FO

This ticket raised by OCA to assure that FO with external and internal customer could have “Phase out” products added/validated, and the check for sourcing external or internal will be in OST.

(US-9639) Kit: Substitution / Dekitting when component prod values changed BN/ED attributes

This improvement requested by OCG, will enable the processing of KCL De-kitting or Substitution for products with BN/ED attributes which have changed. Now there is an extra button “Update products whose BN/ED attributes have changed” which appears in KCL processing window. When button is used, any affected products will have their BN/ED info removed, or have default BN/ED info added (as per original ticket ). Action only updates products in this KCL window.

(US-9604) Performance improvement: PO / FO Validation / Confirmation

This ticket raised by OCB, to improve the system performance and decrease the time needed in PO validation/confirmation, and for applying the CDD on all lines, especially for the POs which consists of many lines.

(US-9467) RR: export empty template in the Replenishment Segment

This request raised by OCB, is to enable users to export improved template from an empty RR Replenishment Segment. Now if user exports excel (via Action menu) from an empty Replenishment Segment, the export template has 5 empty lines. These can be filled in the normal way to import lines onto the Segment.

Menu: Warehouse > Replenishment Rules > Configuration > Replenishment Segment

(US-9466) RR: Round up Projected view figures

This improvement raised by OCB, to decrease the digits of the months of supply and projected months in the Replenishment Rules Inventory Review excel export:
The values in the following columns are now rounded to 2 decimal places:

• months of supply (RR-AMC)
• months of supply (RR-FMC)
• Projected MX (month)

(US-9373) Do not allow Output locations as Destination

OCA requested this improvement to remove the output locations (Output, Packing, Shipment, Distribution) from the destination location in the INT from scratch, to avoid any inconsistent data in these locations, and to be consistent with the IR’s destination locations as well as including Quarantine and Destruction.

(US-9190) Backorder filename tab issue after the e-PL importation Vertical integration

This improvement requested by OCB, means that in the Incoming shipment from ESC, which is updated through the e-PL importation, in the Notes tab, any “filename” relates only to files imported on the specific IN which was updated by import. Back order INs without direct VI import should have this field blank.

(US-9173) Inconsistencies in location name MSF Customer

This ticket raised by support team after noticing that some instances in different sections contain created / configured locations with the same name “MSF Customer” as the default location. With this ticket, all those manually configured locations which have the same name or some variation of name of MSF Customer location have their location(s) changed to “Other_MSF_Customer”, and then users can de-activate the locations which are not in use.

(US-9070) IN line at project cancelled due to Coordo split & partial cancel

This important ticket was raised by OCA, and had previously led to many issues with incomplete/incorrect flows as the splitting of a line and then cancellation of one part of a split line led to all of the line in other document or instance being cancelled. This has now been resolved for all of the Test cases outlined in ticket.

(US-8451) RR: Allowing same product in multiple segments

This ticket, raised by OCA introduces more flexibility into Replenishment Rules Replenishment Segments, and means that one product may be present across several segments belonging to the same Location Configuration as long as the product does not have an active value (FMC/Min Max or Auto Supply) in overlapping periods. When a product is active in one period of an RS, any other RS in which it is present must have the value “0” for this period. A product can be present in up to 3 active Replenishment Segments belonging to the same Location Config, and these Segments can have different types of RR applied. Having the same product in multiple RSs implies that all of the RSs involved must have the “Specific Periods only” checkbox ticked if the RR types are either Auto Supply or Min/Max, as was developed in US-8449 and implemented in release UF24.0

N.B. Please see Finance section of Release Notes to see further details of US-6475 ticket of addition of VAT corner to POs. and US-8567 also treatment of intermission partners.

All Supply tickets integrated in UF25.0

Finance

(US-9800) To add an additional count LINE column on the supplier and customer Commitment Voucher screens.

In the Supplier Commitment Voucher screen and in the Customer Commitment Voucher screen, we added the “Line count” column between “source document” and “currency”.

Go to Accounting >Commitments > Customer Commitment Vouchers /Supplier Commitment Vouchers

(US-9355) Changes in the “Open Invoices” Report (suppliers right action menu) – to add draft invoices and other

In the accounting/Suppliers/and submenus Supplier Invoices, Supplier Direct Invoices, Supplier Refunds, Intersection Supplier Invoices, Intersection Supplier Refunds, Donation, Intermission Voucher In), we have amended the content of the report named “Open Invoices”. The main issue is the addition of the drafts.

The new name is “Pending Invoices “. In French; “Rapport de factures en attente”.

It is placed in the right menu of the screen, with the other reports.

• For the Supplier invoices: we will have the open invoices before and the draft invoices after (drafts in light grey in order to distinguish Draft from Open).
• For the Donations: we will have the open and draft donations of the Open fiscal year + the donations in draft.
• For the Intermission Vouchers IN: we will have the Intermission Vouchers IN of the Open fiscal year + the IVI in draft.
• For the Stock Transfer Vouchers: we will have the Stock Transfer Vouchers of the Open fiscal year + the STV in draft.

Example:

(US-9213) Intermission/intersection: remove the step “missing information” IVI/ISI/ISR

When validating an IVI, ISI or ISR (Intermission Voucher IN, Intersection Supplier Invoices or an Intersection Supplier Refund), the user was asked to retype the total amount of the invoice. In the case it was not done, there was an error message, and the process was blocked.

This step did not have any added value and create an unnecessary step in a long and lasting process flow, so this step has been removed.

(US-8890) Intermission / Intersection: black color of the STV lines instead of blue

In order to align the behavior of STV invoice lines to the IVO or SI lines, we decided to put the lines in black (and not in blue).

(US-8607) Set the first day of the current month at [active from field] when creating a new analytic account or a new GL/account

Now, when you create a new GL Account or a new Analytic Accounts the field “Active from” will have by default the first day of the current month.

(US-8567) Do not allow to activate the intermission partner when an internal partner already exists with the same name

When activating a partner type intermission, the system will check if the same name exists in the internal partners; if yes, the system will not allow to activate the partner (regardless of the status of the internal partner and whatever the letter case) and we will have an error message as follows:

(US-8023) In the analytic journal items please add the journal ACC (accruals) in the “Journal type” filter

In Accounting/configuration/analytic accounting/analytic journals : the accrual journal was tagged to the journal type named “GENERAL”. Now the journal type “GENERAL” has been renamed to journal type “ACCRUAL”.

When opening a new Analytic Journals form, the type selected by default was “General”. Now it will be “Purchase”:

(US-7961) To allow to settle one advance in cash or bank register, even it has been originally booked in a cheque register.

Before, if an operational advance was created through a cheque register, it was not possible to close it through a cash nor bank register and we received a warning message “The register journal is not compatible with an advance return.”

Now after this improvement, it is possible to settle an advance created in a cheque register through a cash or a bank register.

(US-7857) Button filters on AJI: Engagements and ENGI journals

Some improvements have been done in the filter buttons naming and in the searching options regarding AJI.

We go to Accounting/Journal Entries/Search: Analytic Journal Items:

• If we toggle on search button “ENGAGEMENTS”, the result of the search will be the journal code column with “ENG” only.
• If we toggle on search button “ENGI”, the result of the search will be the journal code column with “ENGI” only
• If we toggle on both search buttons “ENGAGEMENTS” and “ENGI”, the result of the search will be the journal code column with both “ENG” and “ENGI”

We have also changed the order of the filters and the name of one filter:

• BEFORE
• 
• AFTER: The filter ORDERS has been renamed to SALES and replaced at the end of the filters
• 

(US-7791) To update the HR information needed by UF to run payroll and third party: to remove values:

This improvement was done in order to assess the GDPR compliance of UF, given the facts below: we synchronized databases between continents in and out of EU and everyone having the Fin_HR group could access to the info.

In this improvement:

• we deleted from the database the “not used” personal information from the staff list.
• and we changed the import of the permois by not taking a list of fields anymore. This is the list of the fields that will not be retrieve anymore from the permois to Unifield:

3.12 (US-6475) VAT corner for the PO – like VAT corner for SI

In this improvement we created a tax part in the PO (the same part as we have already in the Supplier invoice).

Go to PURCHASES > Purchase Management > Purchase Orders:

• Click Edit “yellow pen” any PO
• Click on tab “invoices”
• The new part has been added at the bottom, after the Down Payments and it is named “Taxes”:

To consider below points:

• The new box “Taxes” is available for External PO only.
• If relevant, there is a new button on PO footer to remove the taxes at line level.
• Adding a tax line or removing it, will affect in the total amount of PO.
• SI Tax corner is populated from the PO Tax box.

(US-5722) Accruals Management improvements release

We have done new improvements in the accrual functionality in terms of display and we have also added a new option: we can use more than one expense account in the accrual lines.

These changes have made the functionality user friendly.

Here you can visually see some of the improvements:

Go to Accounting > Periodical Processing > Accruals management > It will display “Search: Accruals Management”

We renamed the status from: draft, posted, partially posted and cancelled

to: Draft, running, done and cancelled.

The new search options: 2 new buttons have been created “ONE TIME ACCRUALS” and “REVERSING ACCRUALS” as below, to search by toggle on/ toggle off:

We can also search by filters as below:

Here we have the new display of the screen “Search: Accruals Management” linked with the columns related.

Note that name of the column “Status” changed to “State”.

The display of the Accruals Management screen has also changed as follows:

Go to Accounting > Periodical Processing > Accruals management > Click on “New”

• Screen for the Accrual type One Time Accrual

• Screen for the Accrual type Reversing Accrual

• Example with data:

We have now two tabs (instead of one before): Accruals and Journal Items:

1. Tab named Accruals: which include the below columns:

• The pencil (to edit only at draft status).
• Line number.
• Description of the line: it will be reported in the AJI and JE
• Reference
• Expense account.
• Analytic distribution at line level.
• Accrual amount.
• Functional amount
• And the X button to delete in draft status
• The state (draft, running, done or cancelled)

1. Tab named Journal Items: Including all accruals lines of the transaction (Expenses, Payables and receivables) as below:

In the right action menu, we have renamed the actions to “Post Accruals” and “Post Accrual Reversals” and we have also added the track changes:

All Finance tickets integrated in UF25.0

Non- functional

(US-9815) Create a link button to the User Manual Online.

Following the release of UniField documentation online, we have created a link inside UniField to the user manual. The icon has been added to the top right corner next to the Home button. Clicking on this icon will open the documentation site https://doc.unifield.org/, in a new tab.

A banner has been added to alert the users of this new feature. The banner will disappear once the user clicks on any menu.

(US-9736) Users Filter: Show not Synchronized

A new filter [SHOW NOT SYNCHRONIZED] has been added to the Users search menu to allow one to search for only non-synchronized users. Previously, it was only the Active, Inactive and Show synchronized filters.

All Non-functional tickets integrated in UF25.0

Release Details

Release version: UF 24.1

Date of production synchronization server patch: 27-April-2022 / 18:00 Geneva time

Latest user rights files updated: UF24.1 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=12413

Supply

In this intermediate release, the following tickets are included:

(US-9849) UD: Correction of product synch if Standardization level changed

This ticket corrects the issue found whereby products changed from NSL (Non Standard Local) to NST (Non Standard) / STD (Standard) were keeping their old behaviour and remaining inactive at Mission level. With this change, when UniData send any combination of updates including this change to standardisation level, any product which is STD or NST should now be active at Coordo & Project. This ticket also corrects products which already had this issue due to past UD updates.

(US-9833) Prevent addition of new lines on pick

This ticket corrects issue found so that it is no longer possible to add new lines onto a Picking Ticket. In the past this issue implied need for Data Fixes but this will no longer be the case.

(US-9826) prevent removal of Partner address due to IN maniplulation

This issue which caused multiple issues with sourcing and shipping was a regression introduced with changes of US-9021/US-9219. It meant that if a user created an IN from scratch, added a partner, changed the Reason Type to “Return from Unit” and then added the the Ext Cu, then the address of the original partner added (same as that of creator’s instance) was automatically removed, which prevent actions such as those listed above from being completed. This has now been corrected.

(US-9637) Export Inventory Level change to format to allow generation

This issue was flagged by OCG as they were unable to access the generated Export Inventory Level due to the generated file being too large to store on the database. With this ticket, the format of the report has been changed to native xlsx, meaning it should be possible to access this report.

All Supply tickets integrated in UF24.1

Finance

(US-9818) UR: User with User_Manager is not able to export the list of staff + department field

Users with the User_Manager profile are now able to export the list of staff and department field.

(US-9813) Possibility to inactivate journals (UF24): last fix to do in the new functionality

We discovered after the release UF24 a bug to be fixed for some use cases of inactivation of journals. The part of the code used to “get the last register” doesn’t work properly, so the register checked is not always the right one (that means that in the instances that could inactivate journals, the balances must be checked manually because for now we can’t rely on this automatic check). With this ticket this bug has been fixed.

Remember that to use the functionality you go here:

Go to >Accounting/configuration/financial accounting/journals/journals:

We have created the 2 filters Active and Inactive to do filters.

And then when you enter into the journal, there is a new field box to tick (Active Journal) or unticked (Unactive Journal)

All Finance tickets integrated in UF24.1

Release Details

Release version: UF 24.0

Date of production synchronization server patch: 16^th March 2022 / 18:00 Geneva time

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

Supply

(US-9219) IN from scratch, field Ext. Unit mandatory if RT is Return from unit

An improvement implemented for the IN from scratch: when user wants to choose “Return from Unit” as a Reason type, Ext. C.U becomes mandatory to be filled, this is to be consistent with check already done if products are added via import.

(US- 9361) Historical Consumption report – AMC per location, Adjusted AMC

As raised by Pharma, the following changes to the Historical Consumption report have been developed:

It’s possible now to select a new Consumption Type “RR-AMC”. This will be the 3rd option and the other 2 options remain. When this 3rd option is selected, it is possible to select one or multiple Source Locations and one / multiple Destination locations. This means it will be possible to see consumption for a specific location or group of locations or see consumption to a specific destination location or set of destinations. Source location(s) must be internal but destination location(s) can be internal or external.

When 3rd option (RR-AMC) is selected, there is a checkbox named “Display Adjusted RR-AMC”. When selected, the report will take into account and show the adjusted AMC based on any stock outs / substitution for products recorded via a recorded “Stock Out” with selected period. When the 3rd option RR-AMC is selected, it is still possible to see and use the “Remove negative AMCs” as before meaning no negative AMC figures (due to returns) will be displayed.

 (US-9359) Physical Inventory new export

As per request from Pharma, a new excel export named “Closed Inventory” is available from Physical Inventory when in Closed Status via the Action menu.

• Similar to the Discrepancy report but with additional information: any counted qty which does not result in a discrepancy will also appear in this report.

(US- 9354) No validate reception button for DPO to ESC

Improvement for consistency requested by OCP, for the DPO Flow, when DPO (coming from FO sourced to external partner) is done to an ESC, it’s possible now to confirm the reception at line level (and so close the line).

(US-9266) New Reason Type for INTs: Internal Return

Improvement requested by Pharma and necessary for the RR-AMC report modification described above: a new Reason Type now exists for Internal Movements (INTs). This can be selected manually in the INT, and there is no change to the default RTs proposed by system.The INTs with “Internal Return” will be treated in the same way as INs with RT “Return from Unit” when there is calculation on the RR-AMC of a specific location.

(US-9129) IN: PDF displays cancelled lines

Improvement requested by OCA, a change to the PDF of Incoming Shipments has been implemented: PDF will no longer show any lines which have been cancelled. Closed and Available lines will still be displayed.

(US-8955) BN/ED added to the Receptions & Deliveries Reports

Improvement requested by OCA, to extend the Receptions/Deliveries Reports by the two following columns: Batch Number / Expiry Date

(US-8867) (E-Validation) IR PDF signatory changes

Improvement in preparation for E-Validation development to update the signatories displayed for the IR PDF in Eng and in Fr: They now contain “Technical Responsible” FR: Responsable Technique and “Supply Responsible” FR: Responsable Approvisionnement

iii)Remove “Storekeeper” (the space for the other 2 above can be increased)

(US-8862) Page number and Document references are missing

Improvement requested by OCB, for the PDFs of IR, INT, & OUTs, all pages now contain the page number and the document reference as for the first page of each document.

(US-8843) Claim: Message to clarify that product/batch/ED not on doc

Improvement requested by OCA, in processing the Claims, when batches/Expiry Dates of products being returned are different to those received. Warning message displayed will be more accurate: (Prod/BN/ED not available in the IN/OUT)

(US-8699) Estimated DD on PO, reports to update

Improvement raised to ensure reports aligned with dev already made in US-8076 where an additional date field “Estimated Delivery Date” or EDD was added to the PO.

(US-8660) (Automated) VI: Display freight name in “Ship Reference”

Improvement requested by OCA , affecting Incoming shipments, meaning the “Ship Reference Field” will now be updated when this value is filled in IN/EPacking Vertical Integration (VI) file. This will not impact how this field displays for INs which are updated by synch. An additional filter on “Ship Reference” at header level for the IN list view has been added.

.

(US-8608) IR additional search/view on Location Requestor

Improvement requested by OCB, search field “Location Requester” has been added to the Internal Requests (IR) List view and is also reflected in same via by additional column there.

(US- 9603, US-9517) Import of AD into Draft PO/FO

Two requests from OCB, with these it is now possible to import Analytical Distribution directly into a Draft PO/FO at line level. Only 1 AD (1 Cost Centre and 1 Destination) can be added onto each line. The action to export / import templates are both via the “Import AD” button.

In the import file, only the AD values will be imported. No other information can be modified or added via the import file. Percentage must be “100%” and system will check that Line number and Product Code match those of onscreen PO.

If there is already an AD added in onscreen PO, exported template will show this. If at header level there are multiple ADs added, the exported template will show percentage value as “Mix” and ADs will be blank. In the case that there are already ADs in the onscreen PO, it is possible to remove (delete) them by importing the file with blank AD values. However if there are multiple ADs at header level and export and import have “Mix” as percentage value, then the values will remain if AD fields are blank. At import, there is a check that AD values exist, but the main/secondary check will remain after import, when line/PO/FO is validated.

(US-8449) RR: Min/Max and AutoSupply validity dates added

Improvement to Replenishment Rules (RR) functionality requested by OCA, affecting the RR Product Segment and Inventory Review. In this RR product segment:

>The RR types Min / Max & AutoSupply can now be applied with specific validity dates, in the same way as was already the case for RR type Order Cycle.

>The default is that validity periods are not applied for Min/Max & AutoSupply but they can be applied by ticking onscreen checkbox “Specific periods only” or changing value in import/export of Segment. If unselected, values other than 1st column cannot be filled / are not accepted at import.

>Import/export of Segment now has multiple columns to allow for these values: “Min / Max 1” “From” “To”, Min / Max 2″, “To” etc.

For the Inventory Review: 3 columns which display Min / Max and Auto Supply values, are replaced by just one column “RR Type” which will display the RR of that Segment: “”Order Cycle” “Min/Max” “Auto Supply”. The columns at end of the report which previously showed FMC values for each month “RR-FMC M0 Aug” have been renamed to “RR value M0 Aug” to reflect relevant value for any of the 3 RR types.

(US-8122) Consolidated MSR : improvement

Improvement raised by OCP for the Consolidated MSR Dates: Last Update value to be added at header of export.

(US-4642) Creation of and conversion to EPREP locations

Improvement requested by OCG and raised and supported also by Pharma for EPREP Locations:

i)All newly-created configurable locations which have “Eprep” type selected will be flagged automatically as of “EPrep” type, a check will be made at creation that the name contains the word “Eprep” in Eng / Fr.

Pre-existing intermediate locations, can be converted into being “Eprep” according to user rights via the menu:

Supply Configuration>Warehouse configuration>Regular Warehouse Management>Convert Intermediate Stock to Eprep

Once a location has been created as Eprep type or converted to it, this cannot be reversed. The EPrep type of location now is reflected as a sub type of location under Configurable Locations in the warehouse structure, and appears in pink as per previous dev (US-9044) to apply colour coding to location types. MSReport has an additional column which shows EPrep stocks qties.

(US-9143) OCA : Patch script to automatically set AD destination to OPS

As per OCA’s request, exceptionally there will be a Patch script included in this release to change AD Destination to OPS for all Validated POs to ESC type suppliers across all OCA instances.

(US-9391) Patch script to rename incorrect references in INs and INT

A second patch script is to be included to rename INT and IN documents which have incorrect prefixes ( ”PICK/XXX”). They will have the correct document prefix added in front of their existing reference (so IN/PICK/XXXXX ) to allow for traceability. The issue causing this problem has been solved via US-9312.

All Supply tickets integrated in UF24.0

Finance

(US-7563) Possibility to inactivate GL journals

In the [Accounting/configuration/financial accounting/journals/journals] screen, we have created a filter with [active] or [inactive] status on the header of the journal list for activation and inactivation of the GL journal.

The standard display is [active]: Only active journals are displayed in the standard display screen. Registers related to inactive journals are not listed anymore on the register creation screen on [accounting/registers/register creation].

In the Journals we have the field Active:

The [inactive] journals cannot be used anymore in the interface:

• • as third party of an entry
  • to book a manual journal entry
  • We cannot import a file to the journal from manual journal entry, or into a register for register lines should check the active status of the journal code seen in the import.

The creation of a journal with the same code as an inactive journal it is not allowed.

We have added in the exportable fields the [Active] status in the export of the list of journals.

The conditions to allow the inactivation will be:

1. For liquidity journals, before allowing the inactivation check:
2. all registers have been closed
3. all manual journal entries have been posted
4. the balance of the last register is zero

We will receive error messages as the following one:

• For non-liquidity journals: all entries have been posted on the journals.

The activation-deactivation will synchronize to the other instances. We will prevent the deactivation if there are draft, or temp posted entries / documents. For the GL journals that have been deactivated, we will show the correction wizard in AJI and JI.

We have added the field “Active” in the Journal Track Changes.

We will not allow:

• The selection of inactive journals in the invoices
• The duplication of JE and invoices on inactive journals
• The re-opening of a register on an inactive journal
• The selection of inactive journals in the Recurring Models
• The inactivation of a journal if a Recurring Plan which isn’t “Done” uses it
• The selection of a Recurring Model on an inactive journal, in the Recurring Plans
• The duplication of a Recurring Model on an inactive journal / of a Recurring Plan using a Recurring Model on an inactive journal
• The selection of an inactive Bank Journal in the Cheque Journal form
• The selection of inactive journals as Refund Journal in the Refund Wizard
• The Refund Type “Modify” for the invoices booked on an inactive journal

Reporting

• We will not show the registers related to inactive liquidity journal in the [liquidity position report]
• We will show the inactive journals in the [liquidity balances] report as far as there have been movements within the period considered in the report. So, the related line won’t be displayed on the condition that the journal is inactive, and the “Starting Balance”, the “Movements”, and the “Closing Balance” are all 0.00.
• We have added a new column in the [liquidity balances] report: [Journal Status].
• (US-9708) In the reports “Trial Balance”, “Partner Balance”, “General Ledger”, and “Partner Ledger” the inactive journals will be displayed in red.
• (US-9698) In the Search views of the invoices, we have done a standard search view, with a filter hiding the inactive journals by default.

(US-8896) Intermission/Intersection: synch rule when the account code on STV/IVO is not available/active at client level

We have changed the synchronisation rule of balance sheets at STV lines between 2 sections using different sets of balance sheets (B/S) accounts. Before this change, UF synchronized the lines booked in B/S, as far as the account codes used were the same. OCA balance sheet numbers are completely different than other OCs.

When an ISI or IVI is created at synch time, the account on each line is taken from (by order of priority) the related CV line if any, else on the product or product category, else directly from the account used on the line in the other instance. In case the account is not found or is inactive, the related line is created without account and is displayed in red (until the account is set). The lines concerned are listed in the related “Synch Message Received” which appears as “Partially Not Run”.

It is not possible to validate the invoice if the accounts are still missing.

This should be the only use case (UC) where invoices can be created with “empty” accounts. Therefore, it is not possible to create an invoice by duplicating another invoice with missing accounts: all the accounts must be filled in first.

(US-9241) To remove the “merge lines by account” functionality from invoice objects where it is available (SI and ISI)

We have removed the “merge lines by account” functionality.

(US-9214) manual STV/IVO synch check box and (US-9331) Synch check box of manual STV/IVO when created from duplicate

US-9214: Intermission/intersection: manual STV/IVO synch check box:

1. if the partner chosen is intermission/intersection, the check box is ticked.
2. if the partner chosen is not intermission/intersection, the check box is Unticked:
3. when the user creates a partner, the user clicks on [validate] button, we will always make a check to ensure the consistency between type of partner at [partner] field and [synch] check box.
4. if the partner is not intermission/intersection and the synch check box is active, we will not allow to validate. Error message: ” You are not allowed to synch an invoice to this partner. Please remove the tick from the check box “sychronization” from the tab Counterpart invoice”.

(US-9325) Add a filter button named “OPEN FY” on STV/IVO/ISI/IVI

We have added a filter button named “OPEN FY” on STV/IVO/IVI/ISI screens.

The Fiscal year to consider is the FY of the posting date.

The following statuses are considered as NOT open: draft, mission closed and HQ closed.

This filter button “OPEN FY” is ticked by default.

When the filter button “OPEN FY” is unticked ==> all objects are displayed.

When the filter button “OPEN FY” is activated:

1. we can see all draft invoices (whenever their posting date).
2. we can see all invoices if their posting date is in the FY Open.
3. we can see just the cancelled posting date in the FY Open and the invoices with NO posting date.

(US-8985) Intersection: To add the legal entity names in the STV PDF print out form

In accounting/customers/STV and then in the first tab “invoice”, we are talking about the report pdf named “print invoice” only related to the STV (intersection flow).

1. We have added the legal name of the supplier (in the pdf is in the first line on the left) and of the customer (in the pdf it is in the first line on the right).
2. The legal name was not currently in the system, so we have added a field containing this information in the “Partners form”.

The field legal name is placed below the field “Name”:

(Note: when we create an instance, the instance must also be created as an internal partner).

It has been decided that the legal name will appear in the pdf document for all partner types (because there are still intersection instances that are not using Unifield)

1. If the legal entity name is not available in the system, it will be empty.
2. The second line is the Name and this remains the same.

(US-8870) Intersection: To be able to identify where the partner has been originally created “instance creator”

In the Suppliers form we have created a new field “Instance Creator” in the tab “General”.

We have added this field in all partners type synchronisation rules.

We have also added this field in the export action menu.

All Finance tickets integrated in UF.24.0

Non- functional

US-9570 Automate Interval Number to 12 in all OCB instances

This change is only for OCB instances as they requested to set the automatic sync to only run 2 times before office hours. As the auto sync interval must always match the auto patch interval, we included a patch script in the UF24.0 release to implement this change for only OCB instances.

US-9456 Change sync rule 413 and improve display of JI/JE/AJI

Failed datapush at OCBHQ, (Data Push create: OperationalError: out of memory). The memory error was raised when the instance tried to compute the sync rule #413 to sync JI (account.move.line).

The rule was created in 2012 for the pilot 0.4 used to flag a JI as corrected but currently only posted JI can be corrected so the domain is not needed anymore. We therefore changed the rule to ensure that with this release:

• Performance during sync is improved
• Display of JI/AJI/JE has been largely improved. This will largely benefit all OCs (HQ) users

US-9423 Checks on sync instance configuration

Checks on sync instance configuration will ensure register actions in the instances leading to wrong sync groups as seen in US-9412 are prevented. The checks in question have been implemented in the sync server at instance validation to ensure:

• A coordination must have exactly 4 groups of each type (Mission, HQ + Mission, Coordinations and OC), all in the same OC,
• A project must have 3 groups: Mission, HQ + Mission, OC. All in the same OC.
• The HQ + Mission group used on an instance must contain the parent instance
• The Mission group used on a project must contain the parent instance

Otherwise, the instance validation is denied.

US-9256 Include Continuous backup info in the Sync Version Instance Monitor

For all versions of UF23.0 and below, the report Administration/HQ Monitor/Version Instance monitor available at HQ only includes info regarding cloud back up. With the UF24.0 release, new columns as below have been added to accommodate continuous backup info too:

• Backup type
• basebackup_date
• rsync_date

US-9160 Add new account (Donation) to Product Synch rule

The Donation account has been added to the product sync rule. Users in the past have not been able to add this account at field level. Even if, they attempted to add it at HQ, it was not synched so there was no way for it to be filled at mission level as seen in US-9106. This release fixes this. Donation expense account once filled at HQ will be synced down.

US-9693 Version Instances Monitor: add OS and Architecture

Following this release, The Windows version information and the architecture (32-bit vs 64-bit) of UniField servers will be added to the Version Instances Monitor.

All Non-functional tickets integrated in UF24.0