Release Details

Release version: UF 29.0

Date of production synchronization server patch: 14^TH June 2023 / 18:00 Geneva time

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

Supply

(US-8455) Request to introduce a “Loan Certificate” in PPS and OUT

With this release, a Loan Certificate will be available in the Action Menu for all INs and OUTs (Pick/Pack/Ship and Delivery Orders). The certificate will only show the lines in the document that pertain to the Loan or Loan return.

If there is a Loan and a Loan Return in the same SHIP, it will be possible to select the document you want to view. When selecting the document that you wish to view, it is possible to choose to see the Total Value of the Loan. By default, no value will be shown.

The project’s name in the documents will be based on the name submitted by HQ. Any changes required to the name shown cannot be modified at project or coordination level.

(US-8361) Free gift certificate text alignment with donation certificate

A Certificate of Donation has always been available in UniField, but it has been added to the action menu for all SHIP and OUT for better accessibility. This certificate will be available for all Reason Types, not just ‘Donation.’

Previously it was possible to view Gift Certificates and Free Gift Certificates. This change harmonizes the names and shows the Free Gift Certificate in any place where the Gift Certificate was shown in the past. This document is now also available in the action menu for all SHIPs and OUTs.

(US-11141, 11462) Prevent new lines from being added on Validated POs that sync to a supplier

Lines from Cusomer Purchase Orders that have been validated have never synchronized to the Supplier instance, since the second instance may have already started to process the order. Despite this limitation, it was possible for the requesting instance to add lines to the PO even though the added lines would never be visible in the FO in the supplying instance.

In this release, it is no longer possible to add lines in the requesting instance once a synchronized PO is validated. The add line button is no longer visible once the PO is validated if the PO is sent to the supplier by synchronization (Internal, Intersection, or Intermission orders). All new lines must be added in the Field Order or Purchase Order of the Supplying instance and will synchronize to the Requesting Instance.

(US-10580) Alignment of IN pdf “Line Number” and “Qty Confirmed” to the PO

In past versions of UniField, the line numbers shown in the PDF version of an Incoming Shipment always started from 1, where the line numbers in the form view were linked to the PO’s line numbers. With this release, the line number shown in the Reception PDF will match what is shown when processing the IN.

The quantities shown in Incoming Shipments are also being updated to provide more insight on backorders and quantities in the original orders.

The Qty Confirmed column in the IN will now show the quantity that was confirmed in the PO, even if some of the original quantity has already been processed, same for qty in the IN from scratch, confirmed qty will show the quantity that was confirmed in the IN from scratch.

The Qty backorder column will now reflect the open backorder (the qty confirmed minus qty received from all IN lines linked to that line of the PO/IN from scratch).

(US-10563) Add fields in PO lines allocation report

The “Allocation Report” has been updated to show two new pieces of information:

• Requestor: The allocation report will now show who requested the line, whether the request came from an FO or an IR. Previously this column was called ‘Partner’ and only showed the requestor when the request was an FO.
• Comments: Any comments included in the Purchase Order for the line will now be shown on the PO allocation report.

(US-11218) VI PO import job stops due to checksum

During Automated Vertical Integration, UniField checks to make sure that a file isn’t a duplicate. If it is, the import is stopped, even if there are new non-duplicate import files to process. With this release, UniField will continue to process remaining VI files, even if another file processed was a duplicate file.

(US-10126) Split IN lines VIA manual VI, Duplicate ordered QTY and update QTY to process

When processing an IN via manual vertical integration, the quantities to process are taken from the import file. To prevent replacing the correct import data with order information from the PO, the top 3 buttons (Copy All, Clear All, Import IN) in the IN process screen have been removed.

(US-8968) To introduce a “Returned” status for completely returned SHIPs

Until this release, the statuses available for processed Shipments were ‘Dispatched’ and ‘Received,’ even if all lines in the order were returned. With this release, a new status ‘Returned’ will be available for shipments Replaced “Cancelled” State:

If all lines in a SHIP have been returned, the document status will be Returned. The status of shipments where all lines were returned before this release have been changed from Dispatched to Returned.

The status of all lines that have been returned in a SHIP will be changed from Closed to Returned.

A dropdown menu has been added to SHIPs to make it easier to only view relevant line statuses:

(US-9022) Allow modification of Estimated and Actual Ship Dates on Ships

Previously the Actual Ship Date in a SHIP could not be manually modified and the shipment’s Expected Ship Date could only be modified when the state is Draft.

With this release, it will be possible to modify the Expected and Actual Ship Date fields until the shipment is dispatched (Validated). Sometimes shipments are sent before or after they are validated, so now there will be a pop up allowing the shipper to select the date the shipment was actually dispatched. Once a shipment is dispatched, the Ship Date fields cannot be modified.

(US-10752) Products: Prevent change of Product Type (Stockable > Service etc)

Users at HQ can change the Product Type for UniData products and these changes will synchronize down to all coordination and project instances. At coordination level, changes in Product Type will synchronize down to projects for local codes. If an item is in stock and then the Product Type is changed to Non-Stockable, the product could be stuck in stock without being able to be delivered.

Now, a check will be done using data from latest MSR. If an item is in stock/Pipelines in any linked instance, the Product Type cannot be changed.

(US-10923) Prevent resubscription of NSL that have been unsubscribed in Unidata

OCs can choose to unsubscribe to Non Standard Local (NSL) codes in UniData and this change in subscription will be reflected in UniField. Previously, it was possible to reactivate these NSL codes in coordination, even if it was unsubscribed by HQ.

Now, when an NSL product has been unsubscribed by the OC, it cannot be activated at mission level unless the product code is resubscribed.

(US-11000) Magnifying glass to search for orders in the OST does not show lines from IRs

In the Order Sourcing Tool, the magnifying glass in the Order field previously only showed references from Field Orders. With this change, it will also be possible to search for sIR references using the magnifying glass.

(US-11177) Add ability to search for batch numbers with magnifying glass for KCL

Previously batch numbers for kit components managed by batch number/expiry dates had to be entered manually when creating a Kit Composition List (KCL).

Now, the magnifying glass functionality has been added when selecting batches for Kits so that users can view all available batches for a given kit’s Component .

(US-9157) RR: Better differentiate OC exports

The names for the Replenishment Rules export files have been updated to be more clear. The new document names are:

Previous Name	New Name
Order Calc	Order Calc Excel Export
Order Calc (only lines with warning)	Order Calc Excel Export (only lines with warning)
Export Draft Consolidated OC Lines	Draft Consolidated OC Lines
Export Consolidated OC all status	Consolidated OC Lines – All Statuses

A warning Message will be displayed in case of trying to import an incorrect file type:

“Error: Wrong format: Order Calc Excel Export template must be used”.

All Supply tickets integrated in UF29.0

Key	Summary	Detailed
US-8455	Request to introduce a “Loan Certificate” in PPS and OUT	x
US-8361	Free gift certificate text alignment with donation certificate	x
US-11141	Prevent new lines from being added on Validated POs that sync to a supplier	x
US-11462	(US-11141) Prevent new lines from being added on Validated POs to Internal Intermission Intersection Partners	x
US-10580	Alignment of IN pdf “Line Number” and “Qty Confirmed” to the PO	x
US-10563	Add fields in PO lines allocation report	x
US-11218	VI PO import job stops due to checksum	x
US-10126	Split IN lines VIA manual VI, Duplicate ordered QTY and update QTY to process	x
US-8968	To introduce a “Returned” status for completely returned SHIPs	x
US-9022	Allow modification of Estimated and Actual Ship Dates on Ships	x
US-10752	Products: Prevent change of Product Type (Stockable > Service etc)	x
US-10923	Prevent resubscription of NSL that have been unsubscribed in Unidata	x
US-11000	Magnifying glass to search for orders in the OST does not show lines from IRs	x
US-11177	Add ability to search for batch numbers with magnifying glass for KCL	x
US-9157	RR: Better differentiate OC exports	x
US-11340	[Physical Inventory] Include accurate decimal values instead of rounding down in discrepancy reports
US-11015	No statuses for some items lines in Export IR/FO Follow-up
US-11140	Add Link to RfQ Reference when Sourcing to RfQ
US-11184	French translation improvement for IN print out – « contrôlé par »
US-10880	Claims: Claim from scratch from IR ext CU strange behaviour
US-11268	[RFQ] Update RFQ button once RFQ is sent
US-11450	Product track changes attached to the wrong product
US-11465	(US-8968) Main Shipment becoming Returned when it should not
US-11471	To fix the QTY confirmed and backordered qty calculation in the IN from scratch
US-8371	PO: UF refuses to change unit price
US-11524	[9022] Actual Ship Date should be Today’s Date in Pop Up, but it defaults to previous Actual Ship Date
US-11528	To fix the qty confirmed in the IN from scratch

Finance

(US-10858) Electronic Validation: Inactivate signature when user is inactivated

After this improvement, we will get automatically the signature inactivated, when the user will be inactivated.

The aim is to prevent that old signatures could be used when the profile is reactivated later.

(US-10991) Electronic Validation: Improve the error message when the user has a signature, but he is not allowed to sign a document

We have improved the error messages for this use case: the user has the signature, but the user is not allowed to sign the document. In this case, the user tries to apply his/her signature on the object and the old error message was “Operation denied”. We have adapted the message to put it clearer.

The error message has been changed as follows:

“You are not in the list of users allowed to sign this document – please contact the document creator”.

“Vous n’êtes pas dans la liste autorisée à signer ce document – merci de contacter le createur de document”.

(US-11199) Electronic Validation: signature follow screen up for “document creator”: to remove the default filters [my signature] and [to be signed]

In Unifield, go to: Administration/Users/Signature/Signature follow-up: we have removed the default filters [my signature] and [to be signed]. After user’s experience we have considered that it was not pertinent.

(US-11349) Electronic Validation: “signature follow up” exporting option (excel and pdf)

We have created two “Export” action menus from the Signature follow up screen:

• Export to Excel
• Export to PDF

Go to Administration, Users/ Signatures Follow up, go to the right menu Actions and select “export search results”.

The idea is to apply some filters using the existing filtering method above the screen and to be able to export the list in Excel/PDF.

The content will be the information of all the columns that we have on the current “signature follow-up” screen.

The use of this: when we need to quick check which documents/objects have been signed in UF, we can export the report and provide to auditors/control etc.

(US-10807) Users: filter based on the “department code”- drop down list

In Administration, Users: “Search: Users” there was an inactive filter named “Company“. It has been now renamed as “Department” and it will be used to have the Department information.

Remember that to populate the department field, you need to go to the menu Human Resources => Configuration => Human Resources => Departments.

(US-10820) OCB: Sub-cost center validity date greater than parent cost center validity date, no import in CODA: to add an error message

We have added an additional check for cost centers parametrization:

In the case that the Sub cost center validity date is greater than the parent cost center validity date ==> we have added a warning error message.
“the sub-costcenter validity date is greater than the parent cost center validity date”.

(US-10835) International Invoice Lines – ESC ERP (European Supply Center ERP)

To develop the Finance Cost price *, we have created the International Invoice Lines module to synchronize down the International Invoices Lines extracted from ESC ERP to the requestor instances. This is to get the real paid prices from the ESCs for International orders.

* Finance Cost price: the product finance cost price will be calculated based on invoices and no more on POs.

This module intends to:

• Allow a downstream flow from UniField HQ instance to missions’ instances, called International Invoices Lines.
• With information extracted from the ESCs’ ERPs and imported in UniField HQ instance.
• International Invoices Lines are a more detailed information of HQ Entries/Invoices placed by ESCs to OCs related to International orders placed by missions to ESCs, where information of a product line level / Purchase Order Line level are available, especially invoiced prices.
• Match International Invoices Lines with reception of International Orders in UniField so prices of International Invoices Lines can be used to value the average Finance Cost price of a product.

Principles :

The Module is not compulsory to use and will be in the reconfigure (Manage International Invoices Lines) and access managed via user rights.

IIL imported at HQ will sync to the instance where the CC is ticked as PO/FO Reference to ensure IIL are available either at Coordo or project that placed the International Orders.

In case of DPO to ESCs, the CC of the receiving instances will have to be entered in the IIL instead of the CC of the instance that placed the order.

If ESC entries are not found at time of reception triggering the creation/validation of the ESC invoices, invoices prices will be populated by the Purchase Order prices.

ESC entries can be monitored at HQ regarding their status (status will sync up from mission to HQ).

(US-10904) Final status of in kind donation: from OPEN status to new status DONE/TERMINE (it is not a renaming)

We have done some improvements on the in kind donation functionality:

– We have created the button called: “Set as done” (“Terminer” in French version).

– we have also created the Status Done (Terminé in French). The status OPEN will not exist anymore.

(US-10921) IVI / IVO / STV / ISI: to add the Counterpart Invoice Number search field

We have added the “Counterpart Invoice Number” field on the IVI / IVO / STV / ISI search views and to display it in the list views.

(US-11005) To prevent FO / PO creation if “Cost center picked for PO/FO reference” is empty

We have prevented the FO / PO creation if the “Cost center picked for PO/FO reference” is empty:

We have also put an error message:

English message: “add the cost center picked for PO/FO reference”

French message : “rajouter le centre de coût utilisé pour la reference PO/FO”

(US-11046) Costing methods: standard price to remove + Patch script to correct products with the wrong costing method

We have removed the option Standard price, as MSF used just the option Average price.

We have done a patch script to correct the products with the standard price.

(US-11103) Manual journal entry: available journals: to remove the not used journal with code REV

The REV journal is no more available for manual journal entries.

All Finance tickets integrated in UF28.1

Key	Summary	Detailed
US-10799	ELECTRONIC VALIDATION: To create a submenu in the Users with the Signatures (List, Follow-up and My Signature)
US-10858	Electronic Validation: Inactivate signature when user is inactivated	x
US-10991	E-validation: Improve the error message when the user has a signature, but he is not allowed to sign a document	x
US-11199	E-validation: signature follow screen up for “document creator”: to remove the default filters [my signature] and [to be signed]	x
US-11349	E-validation: “signature follow up” exporting option (excel and pdf)	x
US-6976	Remove the translation option from the analytic accounts
US-8443	OCA_VE_COOR Unbalanced entry after synch – causing failure of test auto Finance VI in from HQ.
US-9702	Code fix for Journal entries: use case with AD KO to avoid
US-10629	Partners form: purchase default currency and field order default currency
US-10755	Selector saved queries/templates: to be able to delete them at once (to do with the user right ticket US-11328)
US-10807	Users: filter based on the “department code”- drop down list	x
US-10820	OCB: Sub-cost center validity date greater than parent cost center validity date, no import in CODA: to add an error message	x
US-10835	International Invoice Lines – IIL module – ESC ERP	x
US-10904	Final status of in kind donation: from OPEN status to new status DONE/TERMINE (it is not a renaming)	x
US-10915	OCB VI – vertical integration – Changes to the interface file (to add additional columns) to adapt to the new HQ system
US-10921	IVI / IVO / STV / ISI: to add the Counterpart Invoice Number search field	x
US-10996	Entries Data Integrity at project: remove coordo Unbalanced reconciliations
US-11005	To prevent FO / PO creation if “Cost center picked for PO/FO reference” is empty	x
US-11022	Accrual – Edition of the third party on draft ACC to empty is not reflected in the list view + patch script
US-11046	Costing methods: standard price to remove + Patch script to correct products with the wrong costing method	x
US-11103	Manual journal entry: available journals: to remove the not used journal with code REV	x
US-11348	Allow editing entry line with if the line contains character (° )
US-11399	OCA_MM_MYAM: DF: Target instance of CC did not synched to the field
US-11410	OCB VI vertical integration: to add the db-id for journals (account_journal.id)
US-11444	French Translation: Cash request into Demande de fonds

Non- functional

(US-11254) Python3: patch file too large to store in database

This improvement is in preparation for the python3 migration. In the UF28.1 and all earlier versions of UF, the patch file retrieved from the sync server by the instances is stored in the database. However, when we tested this procedure to migrate from python2 to python3, it returned an error when allocating memory to output buffer. To fix this, we changed the patch file to be stored in the filesystem under a new folder: “C:\Program Files (x86)\msf\Unifield\Patches”

Please note that the new patches folder will not be visible with this 29.0 release. It will be created with the next patch/release when the new patch is applied. The patch file to migrate py2 to py3 will be approximately 100MB and should not heavily impact the disk space on the C drive.

(US-9958) Time out for inactivity

Currently, there is no automatic log out when users are not using UniField. This poses some IT security risks. This release implements a 1hour timeout activity which was agreed upon by both Supply and Finance as acceptable for the business. The user will be notified 15mins before automatic logout.

(US-11232) Unidata API: Display Mission/Project Restriction and OC validation

We have extended the integration with UniData and UniField. As a result, some of the fields from UniData are now visible in UniField as well.

On the Product level, in the ”Information” = > “Status” section, the following fields are newly visible:

• “OC Validation” checkbox
• “Devalidation Date” or “Validation Date“ (depending in whether the product is OC validated or not)

A new tab on the ”UD OC Validation” has been created. You will find there all ”Mission Restrictions”, ”Project Restrictions” and ”MSL” in which the specific product is listed. The ”Code” field is the instance code that has been mapped to the specific mission/project/MSL restrictions. Please note that if the Mission/Project restriction has not been mapped yet, the field will remain empty.

(US-10885) MSL: prepare prototype call to MSL API

We have integrated the MSL data into UniField. This enabled us to show all the published MSL projects in UniField as well as all the products listed in these projects which are also present and active in UniField.

You will find new submenus in the ”Products” menu:

• MML Products – The submenu lists all the products, that are active in UniField and are also OC Validated for the given OC in UniData. You can also see, whether the product is MML or MSL Valid. MML Valid means that for the given product, there are either no restrictions for the products in UniData or these restrictions apply to the proprietary instance, or coordination instance. MSL Valid means that MSL project applies to the proprietary instance. The ”MML Valid” filter serves as a quick filter to see only MML Valid products. Please note that on the HQL level, ”MML Valid”/”MSL Valid” fields are always empty as MML restrictions and MSL projects only apply to Coordination/Project level instances.
• MSL Projects – The submenu lists only relevant MSL Projects for the proprietary instance. Which project is relevant depends on the instance level. For the HQ instances, all published projects within OC are displayed. On the coordination level, only published projects mapped to the proprietary instance or its children are displayed. On the project level, published projects mapped to the proprietary instance + projects of its coordination + all children of its coordination are displayed.

You can click on each project to see the specific products that are listed under this project.

To see the specific products in the ”MSL Products”, you need to activate the specific project first. You can do so by clicking on the green button positioned on the right side. The project can also be deactivated at any time. By default, all projects are deactivated.

• MSL products – all products listed in the relevant MSL projects are listed in this submenu. Each MSL project must be activated first in the “MSL Projects“ object. By default, only products listed in the MSL Project mapped to the proprietary instance are displayed. If you wish to see the products listed under another MSL project, you need to choose them in the “MSL Valid for instance” filter. Again, you can only choose from projects, which are already activated in UniField.

In the ”Tools” -> ”Unidata” => ”MSL Projects with no link to UF” you will find all unmapped MSL projects. Also, these unmapped projects will appear in red font in the “MSL Projects” submenu.

All Non-functional tickets integrated in UF29.0

Key	Summary	Detailed
US-11254	Python3: patch file too large to store in database	x
US-9958	Time out for inactivity	x
US-11232	Unidata API: Display Mission/Project Restriction and OC validation	x
US-10885	MSL: prepare prototype call to MSL API	x

Release Details

Release version: UF 27.0

Date of production synchronization server patch: 7^th December 2022 / 18:00 Geneva time

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

Cross-functional

(US-9406) Electronic Validation

A new functionality which has been developed in this release is that of Electronic Validation. This has been developed for both Finance and Supply with requirements raised by OCA (Finance) and OCB (Supply), with the aim of providing users with the ability to sign key documents online which will reduce the need for signatures on printouts and give improved traceability of the signature process for each document.

This functionality will only be available if it has been configured to be active at instance level (in the instance which wishes to use E-validation), via the Reconfigure menu.

If there is no change to the Reconfigure settings, it will not be possible to access or use the E-validation functionality (users will see no change).

Once E-validation has been activated in the Reconfigure, each user who should have access to the functionality (e.g. because they will need to sign documents or should manage part of the online signature process) will need their User Profile to be configured to allow for this (to be managed in the same way as user rights are currently).

In the User profile, the checkbox “Enable Signature” should be ticked, Start date and End date can be filled (or can be left as default settings as from today without an End Date) and the relevant Signature user groups must be added to the profile:

Sign_user = for user who needs to sign documents (either Finance or Supply)

Sign_document_creator_supply = user who decides who should sign each Supply document, can decide to Close signature part of Supply documents and has visibility of documents for follow up.

Sign_document_creator_finance = user who decides who should sign each Finance document, can decide to Close signature part of Finance documents and has visibility of documents for follow up.

For users who need to manage the signature process and be able to sign they will need more than one of the groups added.

Once a user has had the Signature enabled on their User profile, they need to add their signature. This can be done either by filling in the pop-up which they will see when they next log in to Unifield:

Or by going to the submenu which will now appear to help manage their signature in Administration>Users>My Signature.

(This submenu screen can also be used later for if user wishes to replace or delete their signature)

Once the E-validation functionality has been activated, users will be able to manage signatures and / or sign for the following documents: Supply: Internal Request, Purchase Order, Incoming Shipment, and Finance: Supplier Invoice, Donation Invoice, Bank reconciliation, Cash reconciliation, Full report.

Each of the above documents will now have an additional tab for signatures.

A user can only sign a document on which they have added as “allowed to sign”.

The button “Manage Users allowed to sign” can only be used by a user who has specific document_creator user right.

The default and optional Signatures (right panel) are based on the signatures already displayed in the relevant PDF of that object.

When a user that has been added as allowed to sign then signs the document (using the tick box icon ), their signature will be displayed on the object Signature tab, and also in any relevant PDF of that document. Track changes of document will also record any signatures added, removed or changed.

For users who have specific rights, they will be able to see the “List of Signatures” (Administration>Users>List of Signatures) which also has a PDF in the Action menu

And a “Signatures Follow up” screen (Administration>Users>Signatures Follow up) is available, in a limited capacity, depending on rights, to allow users to follow up which documents are assigned to them for their own signature, or for those with further rights, which documents are assigned to other users for signature.

Supply

(US-10798) Product field: “Controlled Substance” value: P2 – Psychotrop 2

New request from OCBA-HQ Medical data steward, due to new value which has been created for field “Controlled Substance” attribute in PMD of UniData: P2 – Psychotrop 2. This value should now be available in UniField Products to allow for UD linkage to work. When it is selected for a product, it will behave in same way as for any another value selected in Controlled Substance field – ie in all transport docs (PICK, OUT, IN etc) and reports which have the “CS” checkbox or column.

(US-8749) (US-10777), (US-8749) LOAN report displays new status Cancelled & (US-10403) correction of Loan report for External Partner flow

Improvement requested by OCB for Loans report, to show consistent statuses for PO/FO lines in loans report (column R) with documents, means the following:

• Where original loan has been dispatched but for return of loaned goods, PO/FO documents lines are cancelled (no returns) – line status in report is Cancelled (new status).
• Where PO/FO document lines are closed (complete flows – complete or partial goods quantities returned) – line status in report is Closed.
• PO/FO documents lines are open (pending returns) – line status in report is Open.
• PO/FO documents to external partner, goods received and returned, lines status in report is Closed.
• Where no stock movement (IN / Out) has been done and PO/FO document lines to external/internal partner are cancelled (no ships nor returns) – no line displayed in report.

There has also been a correction to the report for a specific flow to External Partner.

(US-8386), (US-10766), Renaming of reports “PO Follow-up per supplier” and “FO Follow-up per client” & report location changes

Improvement requested by OCA to rename IR/FO/PO follow-up reports and to change their locations so that they are all under the “Reporting” submenu as per below:

• Original “IR follow up per location” is now named “Export IR Follow-up”
• Original “FO follow up per customer” is now named “Export FO Follow-up”
• Original “PO follow up per supplier” is now named “Export PO Follow-up”

US-9394, US-10721 Modification of Physical Inventory Adjustment Types and new field Sub Reason Type

Improvement requested by OCG, in Physical Inventory – Discrepancy report, now for the “Adjustment type”, only 2 options are available, “Discrepancy” and “Other”, it is no longer possible to add or import other options. There is an additional (new) field, also at line level “Sub Reason Type” which is optional to fill in. This field can only be used if “Adjustment Type” is “Discrepancy”. “Sub Reason Type” allows the following options to be selected from the dropdown list or they can be imported. This new field can be changed until the PI is Closed and will appear in all reports:

i)Encoding Error

ii)Process error

iii)Picking error

iv)Reception error

v)Batch Number related error

vi)Unjustified/Unexplained error

(US-10600) RR: Real Stock in Inventory review + Order Calc takes into account all projects & (US-10554) RR: Coordo cannot access project Expiry date info

Corrections raised by OCB for the Replenishment Rules (RR) functionality: When RRs are configured in Coordo and include synced locations in projects, after computing data on all levels , in the Inventory Review report and Order Calculation, the system will now consider the expiry dates of the stocks in Coordo along with those in the configured project locations, and will no longer consider stocks from projects which were not included in the Location Config of that RR.

(US-10598) Addition of Service product to Regular PO from FO no longer possible.

Improvement to avoid having service products in crossdocking location: User will now be blocked from adding a service product to a regular PO created from a synced FO, a blocking message will be displayed in this case. It is still possible for user to add Service type product to a DPO (Direct Purchase Order).

(US-10596) Automated VI E-PL of IN message & check on forced availability in stock correction

Improvement to solve the issue of failed automated import of E-PL in IN due to negative/forced inventory of relevant product in crossdocking location. In the case where there is an import of IN via VI which includes direction to P/P/S goods directly, if those goods are already forced “Available” on an unrelated Out/Pick document (meaning they will be “Unavailable” for the Out/Pick doc linked to E-PL IN) there will be a blocking message “There is not enough stock in Cross Docking which can be allocated to process XXXX with a quantity of XXX” . This message / block of process will only be displayed for the case of POs from FOs for which the IN to PPS option has been selected, and no longer for cases of INs of POs which are from scratch or which come from IRs.

The same checks are done for manual VI IN import.

(US-10587) Reason Types in PPS & OUTs for Loans & Donations correction.

Correction raised by OCB, to fix the reason type in P/P/S & OUTs for Loans & Donations, now all picking documents (Picking, PPL, Packing, SHIP and Out) Reason Types will correspond to RT of preceding order document and adhere to the following rules:

FOs:

– where FO has Order Type “Regular”, Pickings now have RT “Deliver Partner”

– where FO has Order Type “Donation before Expiry”, Picking docs now have RT “Donation before Expiry”

– where FO has Order Type “Standard Donation”, Picking docs now have RT “Standard Donation”

– where FO has Order Type “Loan”, Picking docs now have RT “Loan”

IRs

– for IR to External CU, picking docs now have RT “Deliver Unit”

(US-8684) KIT: Partial qty removal of one component/line & (US-10579) Addition of “Completed” Status Filter in TKC and KCL

Improvement to ease the management of KITs. In the Kit Composition List (KCL), the option to substitute (remove lines and add others in their place), products is now more flexible meaning it is possible to remove a partial quantity of an existing line (previously it could only be the full quantity). This means that in the KCL Substitution pop-up, the field “Qty” will be modifiable for products being removed.

Also another improvement to be more user-friendly, a new filter “Completed” has been added to both Theoretical Kit Composition (TKC) and Kit Composition List (KCL).

(US-10491) Synch Messages: Automatically set to “Run without execution” for Not Runs from INs processed before SHIP sent

As per agreement with OCs, this improvement ticket means specific types of Synch Messages which were “Not Run” will now be Run automatically without execution. The aim of automatically running them is to reduce the amount of Not Runs in the system which need to be manually run (the flows themselves cannot be treated as already closed/processed). The type of Not Runs which will be treated in this way are for the Use Case:

Project (or other requesting instance) process an Incoming Shipment (ignoring warning message) for which the Coordo (sending instance) has not yet processed/sent the SHIP. Then when Coordo do send the SHIP, this creates a Not Run message since it cannot update a Closed / already treated IN.

This type of Synch message (Run without Execution) can be identified by searching for the following in the Synch Messages screen:

Method to Call. “stock.picking.partial_shipped_fo_updates_in_po”

Execution Messages starts with “Exception: Unable to receive Shipment Details into an Incoming Shipment in this instance as IN” .

(US-10369) IR follow up perf improvement

Improvement to decrease the time needed to export IR f/up per location report, time required to export this report has been reduced by around 3 times less than before.

(US-10193) SYS filter in Internal Move label made more accurate

Improvement requested by OCB, to be more logical for users, in list view of Internal Movements “INTs”, the filter button named “SYSTEM INT” has been renamed to “NON-SYSTEM INT”, no other change has been made to this functionality.

(US-10067) (US-10068) Change to how taxes can be added to POs

There has been a change to the way the taxes can be added to POs, please see Finance section for more details

(US-7434) Track changes added to OUT & PICK

Improvement to add Track changes in the Action Menu > under links, to Delivery Orders (OUTs) and Picking Tickets (Parent & Child pickings) to make more user friendly and to get the information easily for analysis.

The track changes will show same information as was already displayed in Track Changes of INs.

N.B.: See below in IT section for explanation on new Supply User group with possibility to add to white list (for synched users)

All Supply tickets integrated in UF27.00

Key	Summary	Detailed
US-10812	[US-10475] Extra space in Sup_Config_HQ group name
US-10802	UR: E-Validation change to User Rights for view of Signatures Follow up screen
US-10798	UD: PMD controlled_substance: extra value: P2 – Psychotrop 2	X
US-10787	E-VALIDATION: “Signatures Follow up” data protection. View screens supply / finance
US-10777	(US-8749) Extra check on Loan report	X
US-10768	Electronic Validation corrections / adjustments
US-10766	The files exported from the 2 reports “Export IR Follow-up” excel and pdf export. & “Export FO Follow-up” excel export. do not have the same titles like the name of the reports	X
US-10721	Impossible to import a Sub Reason Type on the Physical Inventory’s discrepancy lines
US-10600	RR: Real Stock in Inventory review + Order Calc takes into account all projects	X
US-10598	Addition of Service to Regular PO from FO should not be possible.	X
US-10596	Automated E-PL of IN was failed with error (There is not enough stock in Cross Docking which can be allocated)	X
US-10587	RT in P-P-S & OUTs for Loans & Donations needs correction	X
US-10579	Kit Management – Add “COMPLETED” Status Filter in TKC and KCL	X
US-10567	OCBCD100: RR-AMC do not show consumption
US-10554	RR: Coordo cannot access project Expiry date info	X
US-10522	To improve error message when importing CS which includes not existing products in PI
US-10491	Synch Messages: Set to “Run” without execution for NR IN processed before SHIP sent	X
US-10480	UR: Prevent Local finance user to create intermission / intersection partners at mission level
US-10475	Synchronize user from HQ is not possible for supref HQ user
US-10403	Loans report: remains Open PO to External Partner	X
US-10369	IR follow up perf improvement	X
US-10193	SYS filter in Internal move works in opposite logic than in other applications	X
US-10068	To prevent to add taxes on line nor on header on External PO with Order Type In Kind Donation
US-10067	To avoid the possibility to add taxes at line level in the PO for internal suppliers (internal flows)
US-9406	Electronic Validation	X
US-9394	Modification of Physical Inventory Adjustment Types and Comments	X
US-8749	LOAN report to show status Cancelled for cancelled lines	X
US-8684	KIT: Partial qty removal of one component/line	X
US-8386	Rename reports “PO Follow-up per supplier” and “FO Follow-up per client” & report location changes	X
US-7434	Add track changes to OUT & PICK	X

Finance.

3.1 (US-6844) Intermission / intersection flow: Counterpart invoice status filter on IVO/IVI/STV/ISI.

We have added new filters to show the states of the counterparts for the following transactions:

• Stock Transfer Vouchers
• Intermission Voucher OUT
• Intersection Supplier Invoices
• Intermission Voucher IN

3.2 (US-9142) Add in Interface the total of Output Amount/Output Credit and Debit when Output Currency is selected in Selector.

The improvement has been done in both search results: “Analytic Journal Items” & “Journal Items” interfaces that are created from the selector search screen.

Please to see this, go to Accounting / Selector/ G/L / Selector and then select in the Selector the field “Display in output currency “with a currency.

Both “Analytic Journal Items” & “Journal Items” interfaces will appear with two columns and their totals “Output amount” & “Output curr.”:

• Total output amount at the end in the entries interface when using the Analytic selector
• Total Output Credit and Output Debit at the end in the entries interface when using the G/L Selector

3.3 (US-9271) Full report: add the correction lines when using Wizard of correction on return of advance expenses.

The improvement is in the extract of the “Full Report” from the registers. When the correction of the analytic distribution belongs to an advance line (expenses) through the “Analytic Distribution Items” interface, the extract of the “Full Report” will show both lines “Corrected” and “Reversal”:

3.4 (US-9301) Possibility to get the product code and quantity of the expense in the JI (Journal Items) and AJI (Analytic Journal Items) export.

The improvement is done in the Export data excel file through both interfaces “Journal Items” and “Analytic Journal Items”.

Now we can get the Product code and the quantity available in the Export of JI and AJI of each entry, line by line.

3.5 (US-9357) Donation’s improvements miscellaneous: filters, journals, fields.

There have been additional improvements for the donation’s functionality:

Go to Accounting > Suppliers > Donation:

• The default search of the donations is the “Draft” state:

• Below the 3 states of donation filters, we have added a new filter named “Fiscal year”, to allow to filter by year:

• The only journal available is now the IKD journal -In kind donations- (it is not possible to select the ODX journal in manual. This ODX journal will be used just for automatic entries):

3.6 (US-9389) Commitment Voucher CV: to set up “export CV lines “and “import CV lines” like for the supplier invoices (to do with US-9732).

We have done an “export cv lines” report and an “import cv lines report” (as the ones that we have developed for the supplier invoices in the ticket US-9732).

• We have created two new buttons in the “Commitment voucher lines” tab named: “Import CV Lines” and “Export CV Lines”.

• The “Export CV Lines” includes 10 columns: 4 columns are editable which are “Account” plus the analytic distribution columns.
• Each line has its own ID defined in the column “Internal ID”.
• In the case that a line of the commitment voucher has been split in several lines, the AD will be empty. We will have the word “SPLIT” in the column “Analytic distribution”. The 3 last columns Cost Center, Destination and Funding Pool will be empty.

• We can export the information, change the data and import the file with the data in Unifield. The import fails in case one of the main components do not match: “CV Number, Currency, Supplier, Source Document and CV Type“: an error message will be shown:

3.7 (US-9588) The filtering for the periods 13, 14, 15 and 16 (extra accounting) is not correct in AJI on ENGI (international commitments).

The display of “ENGI” lines in the “Analytic Journal Items” interface has been corrected.

The ENGI will be seen in the filter of the ordinary periods (Jan-Dec).

3.8 (US-9732) Extend to AD the Export/Import invoice lines (to do with US-9389).

We have improved the excel file by adding the analytic distribution:

• The exported file “Export Invoice line” has been improved by adding 4 additional columns: Analytic Distribution, Cost Center, Destination and Funding Pool).
• If the invoice line has been split, we will have the word SPLIT in the excel file and the analytical distribution will be empty.
• If we try to import incorrect values (cost center that does not exist, mandatory values not reported…), the import will fail, and we will have error messages that will help us to correct the errors and to import again the file.

3.9 (US-9770() and (US-10780) OCA: Closing of Period 15 and end of year REV: to add checks and warning messages.

UF has the functionality to revaluate a/liquidity every month, b/liquidity end of year (using a currency table) and c/regular balance end of year (using a currency table).

OCA is using this option.

REV is happening at Coordination instance only – it can be applied once and not correctable.

REV is optional. If an account code for REV is set at company configuration, an instance type coordination could not be closed without REV being processed for a defined list of periods: Jan – dec. We did not include extra accounting periods.

This improvement request is to add P15 in the list of months where we do a revaluation and to add warning messages in case of not respect of the procedure.

The current list of periods to be revaluated is January to December. Those periods have only a/ liquidity every month revaluation.

In Period 15 we have to do the revaluation in 2 steps:

B/ liquidity end of year and c/ regular balance end of year (in both cases it is compulsory to use a currency table).

This improvement has added to P15 2 revaluation checks and additional warning messages:

(EoY: End of Year revaluation)

1. No EoY revaluation run = no warning message.

2. Liquidity EoY has been done => “EoY Revaluation of liquidity has been done”.

3. B/S EoY has been done => “EoY Revaluation of B/S has been done”.

4. Both has been done ==> “Both EoY Revaluation have been done”.

3.10 (US-9869) To be able to identify where the LOCAL staff has been originally created “instance creator”.

We have added a new field in the Employees tab indicating the instance where the employee has been created. The field is named “instance creator of the employee”.

We have added in the export report (in the right action menu), the field “Instance creator of the employee” and the field “Company”.

3.11 (US-9941) To add a filter button named “ACTIVE INSTANCES” in the “Search: Period States” interface

Go to accounting / configuration / financial accounting / periods / periods

1. We have added a new button called “Active Instances” to filter only the Active Instances.

2. This button “Active Instances” will be selected by default.

3.12 (US-10067) To avoid the possibility to add taxes at line level in the PO for internal suppliers (internal flows).

We have disabled the possibility to add taxes at line level in the PO for internal suppliers (internal flows).

3.13 (US-10068) To prevent to add taxes online nor on header on External PO with Order Type In Kind Donation.

We have disabled the possibility to add taxes at line level nor on header on External PO with Order Type In Kind Donation.

3.14 (US-10073) How to inactivate liquidity journals from decommissioned instances in an easy way.

At coordination level, it is now possible to inactivate the journals of a decommissioned/deactivated project.

3.15 (US-10124) To allow the import PAYE_UNIFIELD even if Destination and Cost centers in the file are not compatible.

UniField will allow the import of the Paye Unifield file even if the combination of cost center and destination is not active. But in this case, a warning message will appear:

The incorrect payroll lines will be reported as invalid and there will be no update of the analytics on staff with error.

The correct payroll lines will be reported as valid and there will be the update of the analytics on staff without error.

3.16 (US-10181) Improve the booking of Entries linked to down payments function: use the PUR journal.

The improvement in the column “Journal Code” in the “Journal Items” interface.

When an account code is configured “type for specific treatment = down payment”, the down payment entry in the register needs to be linked to a confirmed PO. The entries related will appear in “Journal Items” interface as below (example):

1. “13100 – Advances Done To Third Parties with PO” recorded in the liquidity journal will appear under the journal code of the liquidity journal.
2. All other lines related created automatically from the reconciliation will be booked in the “PUR” journal.
3. Below you have an example:

3.17 (US-10237) Selector saved query list view: add creation and last edit date/editor fields.

This is an improvement in the “Selector” at saved queries for “GL Selector”, “Analytic Selector” and “Combined Journals Report “.

We have created three additional columns:

• CREATION DATE
• LAST EDIT DATE
• LAST EDITOR

3.18 (US-10262) To block the possibility to create a Journal if the currency parametrized is not active.

The improvement blocked the possibility to select an inactive currency during the creation of a new journal.

Now with the creation of a new journal, if an inactive currency is selected, you will receive a popup message with “WARNING Currency is inactive” and you will not be able to save.

3.19 (US-10480) UR: Prevent Local finance user to create intermission / intersection partners at mission level.

The possibility to create intermission / intersection partners at mission level has been blocked for the groups of users below:

• Sup_Demand_Manager
• Sup_Purchase_Manager
• Sup_Purchase_Officer
• Sup_Store_Keeper
• Sup_Supply_Config
• Sup_Supply_System_Administrator
• Sup_Warehouse_Manager
• Fin_Config_Coordo
• Fin_Config_Project
• Fin_Config_Full

3.20 All Finance tickets integrated in UF27.0

Key	Summary	Detailed
US-6240	Change of Color codes for HQ entries: validated (to black) and split lines (to green)
US-6844	Intermission / intersection flow: Counterpart invoice status filter on IVO/IVI/STV/ISI.	X
US-7719	Remove the space at beginning and at the end of the “journal code” and “journal name” object when saving.
US-7852	Report the third party “code” and not the third party “description” in the Analytic Journal Items interface.
US-8065	Default [destination] could not be displayed in the AD wizard of the Direct Invoice.
US-8672	In the register import file, technically allow this special character “…”
US-9142	Add in Interface the total of Output Amount/Output Credit and Debit when Output Currency is selected in Selector	X
US-9259	Impossible to validate a direct invoice (DI) after having deactivated the original destination.
US-9271	Full report: add the correction lines when using Wizard of correction on return of advance expenses	X
US-9279	Advance settlement wizard: to make AD screen a pop up on top of the advance settlement wizard.
US-9301	Possibility to get the product code and quantity of the expense in the JI and AJI export.	X
US-9357	Donations improvements miscellaneous: filters, journals, fields.	X
US-9389	Commitment Voucher CV: to set up “export CV lines “and “import CV lines” like for the supplier invoices (to do with US-9732).	X
US-9588	The filtering for the periods 13, 14, 15 and 16 (extra accounting) is not correct in AJI on ENGI (international commitments)	X
US-9732	Extend to AD the Export/Import invoice lines (to do with US-9389).	X
US-9770	OCA: Closing of Period 15 and end of year REV: to add checks and warning messages.	X
US-9809	AD check on HQ entries not correctly applied: check on both parametrized account code and Cost centres of the Destination.
US-9842	To remove the white space in the beginning and end of the identification number of the international employees.
US-9869	To be able to identify where the LOCAL staff has been originally created “instance creator”.	X
US-9941	To add a filter button named “Active Instance” in the “Search: Period States” interface.	X
US-9999	Accruals: to change the default display ACC in the list view.
US-10067	To avoid the possibility to add taxes at line level in the PO for internal suppliers (internal flows).	X
US-10068	To prevent to add taxes online nor on header on External PO with Order Type In Kind Donation.	X
US-10073	How to inactivate liquidity journals from decommissioned instances in an easy way.	X
US-10105	Invoice object default display + Commitment vouchers (CV) in list view: draft State on the top
US-10124	To allow the import PAYE_UNIFIELD even if Destination and Cost centers in the file are not compatible.	X
US-10181	Improve the booking of Entries linked to down payments function: use the PUR journal.	X
US-10214	Pending Invoice Report to fix: not to add the temp posted register entries for direct invoices (draft DI).
US-10228	Payroll entries shown as Valid without AD (analytic distribution): behaviour to be changed! they must be Invalid.
US-10237	Selector saved query list view: add creation and last edit date/editor fields.	X
US-10262	To block the possibility to create a Journal if the currency parametrized is not active.	X
US-10443	OCG_LB1_COO: Cheque paid in May appears as unpaid in July : code fix to exclude FXA entries from later period check.
US-10480	UR: Prevent Local finance user to create intermission / intersection partners at mission level.	X
US-10586	Patch script: to turn all one-time accruals manually reconciled in status Running to status DONE in OCA and OCB prod instances.
US-10780	End of year REV on P15: change warning messages.	X
US-10787	E-VALIDATION: “Signatures Follow up” data protection. View screens supply / finance.	X
US-10819	To add product_id and quanity in account_move_line sync rule 412

Non- functional

(US-10662) Error: No valid Time zone detected: Disable time zone field on user preference and user form.

The timezone field on user preference and user form has been removed for all users. This fixes the bug that was causing application error when timezone is set on a user profile. The standard openERP behaviour when timezone is set on a user profile is to:

• Detect the system Timezone
• Change time displayed on the User Interface to apply the rule: database time – system timezone + user timezone

Most of the time OpenERP is unable to detect the system timezone on Windows so the default UTC timezone is set.

This release removes the timezone drop down menu from Users and Settings to prevent this behaviour. Only the database time and system timezone will be taken into account.

(US-10475) Synchronize user from HQ is not possible for supply referent HQ users

Prior to this release, only the group Fin_Config_Full had access to the synchronization whitelist. We have created a new group Sup_Config_HQ only at HQ level for supply to independently manage the Supply synchronized users.

(US-10604) To improve the performance of the HQ entries import

The performance of the HQ entries import has been improved. A progress bar and state of the import has been added. The state will show status: In progress, Done or Error if import fails with the reason for the failure displayed. See finance part of the release notes for the functional details

All Non-functional tickets integrated in UF27.0

Key	Summary	Detailed
US-10662	Error: No valid timezone detected: Disable timezone field on user preference and user form.	X
US-10475	Synchronize user from HQ is not possible for supref HQ user	X
US-10604	To improve the performance of the HQ entries import	X