Release Details

Release version: UF 23.0

Date of production synchronization server patch: 8^th December 2021 / 18:00 Geneva time

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

Supply

(US-9044) Change to Stock locations display

As per request from Pharma, the view of stock locations has been changed. In all views, the name of the location “Quarantine before scrap” has been changed so it is now “Expired/ Damaged /For Scrap”, and its parent location has been renamed from “Quarantine” to “Quarantine / For Scrap”. In the “Location Structure” screen (Warehouse>Inventory Management>Location structure) and in the “Search Stock Location” window (which appears when user must add a location to a document e.g. to choose the “Location requestor” in the IR, stock movements etc), different types of location appear in different colours.

Location colours are: Internal Consumption Units and Intermediate Stocks: Blue; External Consumption Unites: Green; Input and Cross docking: Purple; MED, LOG and Stock: Grey, Expired / Damaged / For Scrap: Light Orange; Quarantine (analyze): Dark Orange.

For all locations which were previously displayed with their location path, this has been removed and only the name of the Location is displayed.

(US-8452) Replenishment Rules: Outdated FMC removal + Segment export

As per request from OCA, a new button has been added to Replenishment Rules (RR) Replenishment Segment screen called “Remove Outdated FMCs”. It can only be used when the Replenishment Segment is in Draft status, and the type of RR is “Order Cycle”.

When clicked it will remove any FMC values and their dates for any FMC which is wholly in the past. FMCs which are valid will be moved to the left to fill any removed ones.

Also the name of the file which is exportable from the RR Replenishment Segment has been corrected to display “SEG_ XXDBXXXXDATE”.

(US-1128) Theoretical Kit Composition (TKC) import for creation

As per request from OCG, when creating a new Theoretical Kit Composition (Products>Kit Management>Theoretical Kit>Theoretical Kit Composition), it is now possible to choose an existing TKC and import its products directly into the new TKC. The new TKC can have products from existing TKCs added multiple times, and then these products can be removed or more added directly in the screen.

(US-8972) IN synched to receive Inactive product and message

Now when an IN receives an update via synch from a sending instance, containing a product which is not active in the receiving instance, the IN is still updated (to Available Shipped) and there is a warning on the relevant line(s) indicating issue with product. Line(s) containing inactive product cannot be processed until product is activated.

(US-8433) VI: IN simulation screen more accurate

As requested by OCB, now when a Vertical Integration (VI) import file is imported onto an Incoming Shipment and file does not contain all lines in original IN, in the simulation screen, the change “CHG” flagged is now “Ign” meaning line not in import file is ignored. Previously the CHG column showed “Del” (Delete) for these lines, which was inaccurate.

(US-8794) Correction on products to allow correct UR control of Active status

Development has been made which means User Rights can now be used to correctly control products which should be able to be Activated/Deactivated, depending on the Product creator, Standardization Level and level of instance (HQ, Coordo, Proj).

Of the Products which descend from HQ to Coordo, only the ones which have UniData as Product creator and which are “Non-standard Local” can be de-activated at Coordo, and this by a user with appropriate User Rights.

(US-9176) Claim: IN of returned goods uses wrong Source Location

The ticket raised by OCA to resolve a BUG, when products are returned by claim, now the IN of the returned products bears the name of the partner, and in the stock move reports of the returned items, it shows the MSF supplier in the source location and not the stock therefore, there is no negative stock of the product due to this transaction, previously, the name of the partner was not shown in the IN, the location of the source was a stock, resulting in a negative stock of the returned item.

(US-9147) RDD field in Validated PO should not be modifiable

New improvement for validated purchase orders which is consistent with previous improvement US-8076 “Management of PO 2 RDDates Estimated Delivery Date”. After validation, users will not be able to change RDD anymore at header or line level. Via VI, any change to the RDD will be reflected in the EDD line level, without changing the original RDD (this remains unchanged and is as per previous ticket).

(US-8951) Synched INs: warning if Cancel line & Track changes update

New improvement for Synced incoming shipments between instances, A non-blocking warning message will appear for processing or cancelling any line in the INs linked to synchronised flow with Available status, and in Track changes reports, correct status for IN (Available, Available Shipped, Available Updated) appears.

(US-8923) PPS: not possible to return packs from Sub-Ship

A Bug has been solved, users can now return packs from the sub-ship, after picking/packing lines to draft shipment, processing partial packs to sub-ship, adding more packs from the remaining packs to sub-ship, and then it is possible to return packs from sub-ship, and add parts of the packs to sub-ship again.

(US-5357) Product Nomenclature Status to be received from UniData

An extra field has been added to receive the Nomenclature “status” from UniData.

The aim of this improvement is to prevent UniField users from creating new products with obsolete Nomenclatures.

UniData already manages the status of Nomenclatures and sets those which are no longer Valid to Archived. Now this field is present also in Nomenclatures in UniField.

Before any update is received from UniData, the default Nomenclature status for products in UniField is valid. For any Nomenclature status which is updated to “Archived” by UniData linkage, any existing product with this Nomenclature can still be used, but no new product can be created using Archived Nomenclature. The Nomenclature status is visible on Root level of Nomenclatures.

N.B.: The equivalent development on UniData side to send status via linkage is due in release early next year so no update to UniField for these values is expected before then.

(US-8847) Inconsistent/missing status label in Delivery Order PDF

The ticket raised by OCA to fix a BUG, in the Delivery Out PDF, the State is now compatible with the correct status of the delivery out, Dispatched and Received status appear now correctly in the pdf.

(US-8732) RR: Improve pipeline synchronization to project

On OCA’s request for new improvement, for purchase orders synchronized between instances, date changes to Validated supplier POs even if PO lines status does not change, now are synched to project/requesting instance and appear in the pipeline report, such as in EDD/CDD changes in validated/confirmed POs.

All Supply tickets integrated in UF23.0

Finance

(US-7929) Whenever REV/COR are generated, their posting date must be within the same FY as the posting date of the original entry.

In this ticket we have put in place a new generic rule: the possibility to correct the transaction only when the posting date of the transaction is in the same fiscal year of the original entry posting date.

For example:

• Initial document date in 2020.
• Initial posting date in 2021.
• FY 2020 closed and FY 2021 open.
• Correction with posting date in 2021.

==> In this situation we can correct the transaction in 2021, as the correction posting date is in the same fiscal year of the original entry posting date.

(US-8459) OCG: Funding Pool and financing contracts: to add new filters.

We have added a new filter:

Go to Accounting/Grant management/Financing contracts/ tabs Funding pools and tab Reporting lines:

Funding Pools analytical account => In the Search Account/Destination view (click Add in the tab Accounts/Destinations), we have added a new filter ‘Analytical Destination Account’ as a free text (no magnifying glass) so search can be based with text.

Financing Contract => in the reporting line tab, when adding Account/Destination, add a new filter ‘Analytical Destination Account’ as a free text (same as for FP)

(US-8585) Intersection: create a specific journal and new name for SI from intersection flow.

A new improvement has been done in the intersection flow by the creation of a specific journal ISI (Intersection Supplier Invoice) and a new name for the invoices coming from an intersection flow (ISI Intersection Supplier Invoice).

By the past, all invoices received from an intersection partner were created as Supplier Invoices.

For the refunds:

• The Stock Transfer Refund (STR) correspond to the STV refund and it will stay in the existent journal SAL.
• The Intersection Supplier Refund (ISR) correspond to the ISI refund and it will stay in the new created journal ISI.

The new ISI in the new journal ISI (new) has the similar behaviour to the SI on Intersection partners currently (same menu, same buttons, same filters…). Only exception: everything related to taxes is removed.

STR (new) are generated at STV refund time, with POSITIVE amount (just the sense of the JI/AJI will change). They can also be manually created (no check whether the amount is negative or not). Their behaviour is similar to the one of the Customer Refunds currently (they appear in the same menu, have the same buttons, the same filters…).
They DO NOT replace the Customer Refunds which are kept as they are (but not generated via STV refund anymore).

ISR (new) are generated at ISI refund time, with POSITIVE amount (just the sense of the JI/AJI will change). They can also be manually created. Their behaviour is similar to the one of the Supplier Refunds on Intersection partners currently (they appear in the same menu, have the same buttons, the same filters…). Only exception: everything related to taxes is removed.
The Intersection partners will be removed from SI and from SR: the SI and SR currently linked to Intersection partners will still be named “Supplier Invoices” and “Supplier Refunds”, and won’t be moved to the new menus, as they use different journals (so different Entry Sequences).

STR and ISR are not synced.

• STV can be refund cancel and modify (no refund refund).
• ISI can only be refund cancel if the counterpart invoice status is in closed state (no refund modify / refund possible).
• STR and ISR have no refund button possible.

(US-8839) Customer Commitment Vouchers from Field Order – Intermission/intersection.

In UF22 we did the CV linked to the PO to intermission and intersection partner type at the requester side. The objective is now to generate a CV from the provider side so credit of expense are triggered via CV when the FO lines are confirmed.

When related to intermission and intersection provider partners, they often have to purchase goods externally before to ship them to the requester instance.

During the time the supplier instance buy the goods and ship the goods, they generate expenses that are on behalf of the requester that are only offset when the shipment is triggered and the draft client invoice (STV or IVO) are validated.

This functionality tends to generate credit of expenses in the engagement accounting entries (positive Analytic Journal Items) in between the field order is confirmed and the time the credit of expenses are generated when the invoice is validated.

The function is optional and defined in the reconfigure menu. Indeed, not all OCs will use this functionality and within each OC, only instances that are playing the role of regional supplier shall fully benefit from this functionality. Other instances that sometimes play the role of provider will decide to use it or not.

(US-8845) Inactive cost centers block update of Incoming Shipment

The update of an IN/Incoming shipment will not be blocked if the linked cost centres/destinations are not valid. However, in this case, it is not possible for the user to validate the SI unless a Finance user modifies the cost center/destination and sets it to an active one.

The use case that we correct was this one:

• HQ1C1: PO validated to HQ1C2, AD: HT101 / OPS, sync
• HQ1C1: set HT101 and OPS as inactive
• HQ1C2: source FO to stock or PO, P/P/S, sync
• HQ1C1: no more NR to confirm the PO, IN is available shipped

(US-8900) STV’s invoice Excel Export – Equivalent of IVO’s Invoice Excel Export (intermission/intersection).

You will be able to have a new excel file called “Invoice Excel Export” from the STV in order to follow the flow. This file exists already for the IVO.

Go to: Accounting > Customers > Stock Transfer Vouchers > select STV line > go to the right menu “Reports” and you will find the “Invoice Excel Export” report.

Details of columns:

Column A: Document number: As documents are in the same page we will give a number per document to distinguish them. Ordinal number of the document as per selected STV. Ex. there are 3 STV selected, the numbers would be 1, 2, and 3.

Column B: Line number: Number of the line on each STV. In the same example below, if the 1st STV has 3 lines, the 2^nd^ has 2 and the last 4, the numbers on this column would be 1,2,3 (related to 1^st STV) ,1,2 (related to 2^nd STV), and 1,2,3,4 related to the last STV.

Column C: Product: fill the product code related to the line. Leave empty or write FALSE when the product code is not filled for the manual STV.

Column D: Description: Description of the line in the STV.

Column E: Quantity: quantity of the line in the STV.

Column F: UOM: Unit of measure of the line in the STV.

Column G: Percentage: 100% if the line is not split or percentage of the analytic split if line split.

Column H: Unit price: unit price as it is on the STV line. In booking currency.

Column I: Sub-total: subtotal of the line as what is it in the STV In booking currency.

Column J: Account: account code of the line in the STV.

Column K: Cost center: Cost center of the line in the STV.

Column L: Destination: Destination on the line in the STV.

Column M: Voucher number: SAL number of the voucher. In case the voucher is not posted leave blank or fill FALSE.

Column N: Voucher status= status of the voucher (invoice object: draft, open, paid, closed).

Column O: Posting date: posting date of the STV.

Column P: Ship#: Number of the shipment generating the STV. Leave blank or fill FALSE for manual STV.

Column Q: Partner: the partner visible from the header of the STV.

Column R: FO number: number of the FO source of the process as it is seen in the supplier and customer sections. Leave blank or fill FALSE for manual STV.

Column S: PO number: Number of the PO to external partner in order to buy the goods. Leave blank if sourced from stock. Leave blank or fill FALSE for manual STV.

Column T: Counterpart invoice number: as per on the counterpart invoice tab of the STV.

Column U: Counterpart invoice status: as per on the counterpart invoice tab of the STV.

Please note that the Funding Pool is excluded from the list.

All Finance tickets integrated in UF23.0

Non- functional

US-8367 Add the version to the UR files exported from Tools

New improvement when working on URs, we need to extract the files from Tools, then update them and import them in the sync server for release into productions.

The system will automatically add the current version (same as version next to log out button) when exporting UR files from Tools. As we can see below:

Access_Controls_List_Export_UF20.0rc3_20210304.

To perform this action: Go to Tools > Import/ Export > Non-Functional > choose Object to Import/Export > Export all data

US-5357 Product Nomenclature Status for Unidata linkage

The ticket is both supply and IT and already described in supply section above.

US-9217 OCP-NE1-COR admin account unable to view Hardware id

This ticket raised by OCA resolves a bug in the French version of UniField when accessing the entity ID. When the user logs in with the admin account to a French instance, the user is not able to see the entity ID, just the value of the last update. As you can see in the example below:

This issue is resolved in this 23.0 release. Admin users should now be able to view and access the entity Id as seen in the French instance example OCP_NE1_COR below:

Go to synchronization > Maintenance > Entity ID:

The result of this action:

All Non-functional tickets integrated in UF23.0