1. Release Details
Release version: UF 31.0
Date of production synchronization server patch: 6th December 2023 / 18:00 Geneva time
Latest user rights files updated: UF31.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=12491
2. Supply
2.1 Streamlining of Reason Types used in INs from scratch, migration from RT “Other” for INTs and OUTs (US-7168) (US-7169)(US-10518)
The Reason types (RTs) for INs from scratch have been reduced. For future INs from scratch which are created: the dropdown list offers only 3 RTs now (1 Internal Supply, 4 Return from unit, 5 External Supply). This is to encourage users to follow the correct process.
Previous INs from scratch with RTs no longer existing have been migrated to relevant current RT to be consistent with this improvement.
Additionally previous OUTs and INTs with RT “14 Other” were replaced by a more accurate and suitable RT
2.2 (US-11653) “Reference” search field added to Partners
In the “Partners” Functionality, a new search field has been created for “Reference” and it will be displayed in all Partner search windows in different documents like FO, PO, IN, RFQ, Tender & OUT.
2.3 “Details” field addition and modification across Supply order and transport documents. New field in PPL for Parcel Comments (US-11739) (US-11827) (and OUT), (US-11835) (US-11741) (US-12149)
With these tickets, several improvements have been made to different documents in ordering, procurement and warehousing functionalities, specifically to harmonise the “Details” information:
IR : New “Details” field has been created in the IR Header, same way of processing as FO, and any value entered in IR will be transferred to OUT (or Pick if converted).
OUT: New “Details” field has been created in the OUT Header transferred from the IR, not editable (Only editable in case of OUT FS).
PO: “Details” field already exists in PO but will be populated from the source document (FO or IR) and will continue to be editable until the PO validated.
IN: New “Details” field has been created in the IN Header, and will pull from any value entered in the same field in the linked PO. It is not editable in IN (Only editable in case of IN FS). And “Origin” field in IN FS has become inactive.
PICK: New “Details” field has been created in the PICK Header transferred from the FO or from IR when linked OUT converted to Pick, not editable.
PACK: New “Details” field has been created in the PPL Header transferred from the Pick (Not editable)- The field which was previously in the PPL “Description” has been removed and replaced by field “Parcel Comments” and this is editable, both fields are appearing in the packing list pdf of the ship object. As with previous field, any value in the field Parcel Comments is visible for this PPL in the SHIP.
INT: New “Details” field has been created in the INT Header transferred from the IR or IN from scratch, not editable (Only editable in case of INT FS – Draft status). And “Origin” field in INT FS has become inactive.
2.4 (US-11745) Creation of OUT from scratch to ECU no longer possible
In the Delivery Order / OUT from scratch, it is no longer possible send goods to an External Consumption Unit. It is now impossible to select own instance and at line level it is impossible to choose External Consumption Unit, error Message will be displayed. Goods can still be sent to an ECU if the flow is initiated by an Internal Request, or via Real Consumption.
2.5 (US-11844) Issues resolved with quantity duplication in Shipment and Donation certificate, (US-11852) (US-12088)
The issue of having duplicate quantities in PPL and Donation certificate has been solved in this release. The main issue was related to packs being returned from shipments and then re-added back to the shipment again. Also the status of the Returned shipment line (Pack) in the pop-up of returned lines has been fixed to be “Returned” not “closed”.
2.6 (US-11904) Supplier column added in Export IR Follow-up
In the Excel export of IR Follow-up, New “PO Supplier” column has been added to the report to be consistent with Export FO Follow-up report.
2.8 (US-11660) Icon removal from List view of Draft Shipments
In “Draft” Shipments, the icon “+” to process shipments from List view of shipments has been removed, shipment can still be processed in the form view of “Draft” Shipment.
2.9 (US-11792) Removal of Intermediate Cancel window in OUT/Pick
To increase the efficiency of processing by reducing unnecessary steps, and to be more user friendly, when cancelling an “OUT” or “Pick”, the intermediate pop-up screen to double confirm the action of cancelling the move has been removed in this release.
2.10 All Supply tickets integrated in UF31.0
| Key | Summary | Detailed |
| US-12149 | Field for (Parcel) comments to be maintained in PPL | X |
| US-12091 | Allow IN from Scratch from ESC when IIL are Active | |
| US-12088 | DONATION CERTIFICATE BUG | X |
| US-11904 | Add Supplier in Export IR Follow-up | X |
| US-11852 | Line status in ship pop up has incorrect status | X |
| US-11844 | Quantity Duplication in Shipment | X |
| US-11835 | Add “Details” field to INT | X |
| US-11827 | Add “Details” field to IR (and OUT) | X |
| US-11792 | Remove Intermediate Cancel Window | X |
| US-11745 | Prevent Creation of OUT from scratch to ECU at Line Level | X |
| US-11741 | Add Details, Comments and Notes in Packing | X |
| US-11739 | Transfer Details from IR/FO/PO to OUT/Pick/IN | X |
| US-11660 | Page should be updated automatically during Shipment Creation in Dashboard View | X |
| US-11653 | Add “Reference” search box to Partners | X |
| US-10518 | Missing migration of moves with reason type “Other” | X |
| US-7169 | Update Reason Types for IN from scratch | X |
| US-7168 | Reduce number of Reason Types for INs from scratch | X |
| US-12200 | (US-5563) Issue while manually validating a Claim | |
| US-12193 | (US-11741) “Description” header was not renamed in the Ship’s Freight Manifest Excel | |
| US-12183 | (US-12149) PPL Parcel Comments field should not pull from Details field | |
| US-12061 | Change of Supplier on IN from scratch leads to incorrect warning | |
| US-12051 | Possibility to create a Pick from scratch | |
| US-11877 | Update Track Changes translation for merged products | |
| US-11860 | Correct Typo in Periodical Forecast Report Search Box | |
| US-11714 | Unable to validate RFQ when adding new lines that are missing line numbers via import |
3. Finance
3.1 (US-11026) Reporting: “Field Balance specification report”
We have created a new report called the Field Balance Specification Report. The report will be in the menu of Legal reports as follows:
The report can be done by period and we can select the details of entries reconciled in the last period or the total of entries reconciled in later period:
The report can be created at HQ and at coordination level just for instances that are a coordination,
The report will show the active accounts codes with outstanding balance of some balance sheet accounts.
There will be a balance accounts summary and after this we will have the details of the balances of the outstanding accounts.
Details: List on the report the following entries:
- => Unreconciled entries within the period to report: Entries which are posted before or at the end of the period to report and at the time of export of the report still not reconciled. E.g. Report Mar 2023 = Entry posted before and including 31 Mar 2023 and are not reconciled at the date of export of the report.
- => Entries which are posted before or at the end of the period to report and are reconciled with some legs of the reconciliation posted later than the period to report. E.g. report Mar 2023. Entries posted in Feb 2023 and reconciled with entries posted in Apr 2023.
For the December report, we will show the list of entries booked before the end of December and that are reconciled with entries with posting date in P13, P14, or P15 or later.
For the P13 report, the report will show the entries booked until the period P13 and that are reconciled with entries with posting date in P14 or P15 or later.
3.2 (US-11355) New CC import behavior in Tools/Import-Export/Finance: 2 imports, one for creation and one for mass updates
In the menu Tools, Import/Export and then submenu Finance: there will be 2 imports, related to cost centers: one will be used for the initial creation of cost centers and the other one for mass updates of cost centers.
The current cost center import will become “cost center creation mapping”: no change as from now.
and we will create a new import for mass cost center updating called: “cost center updates”: the new one.
3.3 (US-11510) Importing Multiple Analytical Distribution Lines in Unifield on draft invoices (SI)
Before, it was possible to import Analytical Distribution (AD) by line when we have only one Cost Center (CC) and one Destination account for 100% of the distribution.
With this improvement, it will be possible to add multiple Cost Centers and/or Destinations in the same line.
The proposed method for importing multiple ADs is by separating each percentage, cost center and destination with a semicolon (to differentiate the different values).
Remember that changes can be done only when the invoice is in draft status.
Example:
You have to select “Export Invoice Line” and you will see the excel report:
3.4 (US-11525) To implement a filter in the journal list: manually created and automatically created (created at instance creation)
On the journal list from Accounting>configuration>financial accounting>journals>journals
We have created 2 filters with the options:
- Automatically created (journals that are created at instance creation)
- Manually created
3.6 (US-11950) Fixed assets management
The fixed assets functionality has been developed in UniField. This functionality is to rely on Finance responsibilities only. Finance will be responsible to get information from Supply and Logistic in order to record Fixed Assets events, trigger depreciations in the right instance and to follow Assets movements from one mission to another.
Fixed assets, also known as long-lived assets, or property, plant and equipment, are items in physical form that:
- are held for use in service of organizational activities, or for administrative purposes; and
- are expected to be used more than once (not consumable); and
- are expected to be used during more than one year period; and
- can uniquely be tracked and monitored; and
- are with value greater than a defined materiality amount
For MSF, it applies only to tangible items.
As per principle of flexibility, Fixed Assets won’t be pre-identified in the system. Each OC will define out of the system what they do consider as Assets. It will be a manual action that will set an item as a Fixed Asset.
When to trigger the recording of the fixed asset in the Balance Sheet?
- While validating an invoice: It will be possible to set an invoice line / Items as Fixed Asset => invoice line triggers accounting entries in balance sheet instead of expenses.
When do we trigger the fixed asset form creation?
- When the items are defined as Fixed Assets and the invoice is validated, an Asset form will be created in draft status.
When does the asset form is set as “in use” and start to be depreciated?
- It will be a manual action done in the Asset form. There will not be an automation linked to Supply stock movements.
- Depreciations method will be linear only and on monthly basis, included in the monthly closure checks.
- Useful life will be defined in each Asset Type at HQ so OCs can set different life time for the same asset type.
- It will be possible to propose several life time for the same Asset type, defined at HQ so missions can only choose the life time proposed in the asset form
- Note that within the same OC, missions can only choose what has been set in the Asset Types.
- There will be 7 different asset types (with also the option to create some new manually at HQ)
Acquisition:
- Through invoice: goods that will be manually set as “assets” in the invoice will be booked in the Balance Sheet. An asset form will be created to monitor and follow the assets events. When asset forms will be created, they will be linked to the invoice that triggered the asset form and will take the unit price of the invoice.
- Manually: it will be possible to create an asset form from scratch where all mandatory values will need to be filled, including the value and currency. Mainly for International orders where no invoices are created or when an asset is transferred to another mission
Disposal:
- Once the asset is open/running (depreciated), several reasons for disposal before or after the end of life will trigger different accounting entries depending of the reason to offset the value in the balance sheet including calculation of gain (loss) on disposal.
3.7 All Finance tickets integrated in UF31.0
