NEXT 202405 - January 2024
Release date: January 31, 2024
About this release
Data export in information requests
It is now possible to export the data of an information request. You will receive an .xlsx file containing a tab with data for each part (name and address details, contact persons, etc.)
Dun & Bradstreet middleware
The Dun & Bradstreet connection has been expanded with middleware functionality. You can now use your own endpoints to check, for example, whether you already have the data available elsewhere, to save costs.
General
Bugfixes
- Various text corrections have been made.
- Various layout corrections have been made.
Vendors
New
- [Information requests] It is now possible to export the data of an information request. You will receive an .xlsx file containing a tab with data for each part (name and address details, contact persons, etc.). To do this, use the 'Export all' button in an information request.
- [Information request] You can view survey results while assessing an information request. By default, the order is now first sorted by 'Heading order' in ascending order and then 'Question order' in ascending order.
- When you start an Information Request from the supplier details (Add+ button after opening a supplier) you now have the option to select an (information request) template.
- [Supplier Data Portal] The forms related to contacts in the Supplier Data Portal and when reviewing requests now take into account the field settings available in Admin > Vendors settings > Personalization > Contact fields visibility.
- [Supplier Data Portal] The supplier detail fields in the Supplier Data Portal and when reviewing incoming requests now have comments that can be entered in Admin > Vendors settings > Personalization > Visibility fields.
- [Supplier Data Portal] Supplier Data Portal requests where you as a user have to complete a workflow task are now shown on the Start Center under 'Workflow tasks'.
Bugfixes
- The 'Operation Log' tab in the supplier details now shows Supplier Data Portal requests related to the opened supplier again.
- [Information request] When you manually add a product while assessing an information request, the custom field values were not always correctly copied. This has now been corrected.
- It was not possible to delete E-Signing requests that were only linked to a supplier and not to a contract. This has now been corrected.
- [Information request] An issue where, in specific situations, contract product fields were not always transferred from the information request to the contract upon approval, has been solved.
Admin
New
- [Supplier Data Portal] In the 'Accepted Vendor Change' and 'Rejected Vendor Change' emails (Admin > Vendors settings > Vendors notifications) the following tokens can now be used: [VL:LASTWORKFLOWUSER] and [VL:LASTWORKFLOWCOMMENT]. The first shows the name of the last workflow user in the workflow, the second shows the comment that the user entered when approving or rejecting.
Bugfixes
- In the user overview with active users (Admin > General settings > Users), column 'External ID for SSO' did not show the correct value, this has now been corrected.
- The year 2024 has been made available as a filter option in the locations below:
Admin > Spend settings > Data bundling > Connect vendors
Admin > Spend settings > Data bundling > Combine vendors
AP Automation
New
*Infor LN CE connection live
The Infor LN CE connection has been launched. For more information, please contact the Account Manager.
*Added new fields to the accrual report
- The following fields have now been added to the export of the accrual report: Scan date, Registered, Posted, Released, Procurement number and Order type.
- In addition, extra columns have been added to the list view ('created by' and 'posting period start date') of the ongoing cost overview, so that it can now be seen who generated the report and what the start date of the booking period is concerned.
*PO lookup possible at line level
From now on it is possible to search at line level with the PO lookup.
Open the 'Select order number' screen by clicking on the icon in the header of the invoice and clicking through to 'show open orders'.
- Search for the 'PO Lookup' using the filter icon next to 'PO lookup'
- The order number with the searched for PO lookup in the line is shown. The line can be viewed via the + icon.
*The OpenAPI documentation has been improved
The OpenAPI documentation has been improved in the following areas:
- PurchaseOrder has valid documentation
- Fixed types and enums have been added
- Readability has been improved (punctuation, new lines, code blocks, and pattern format).
- Request examples have more realistic data.
JD Edwards
For the Polish localization it is necessary to be able to note units on coding lines with two decimals. From now on, this has been made possible in the standard solution for all JD Edwards customers.
SAP
*From now on it is possible to include the planned additional costs (ZHAN) on logistics invoices.
Infor LN & Baan
If dimensions under a general ledger account are not in use but are included in the import, they will be ignored from now on. As a result, dimensions that are not in use are now no longer editable.
Fixes
General
- When an invoice was opened in Coding by Accounts Payable, it was not possible to edit the invoice header directly. This has been resolved.
JD Edwards
If no purchase order was found on a line during the import, this resulted in an error. From now on, the system will skip the record and log a 'purchase order not found' warning.
Baan
Fixed an issue whereby the Gsplit validations were also applied to invoices where this was not applicable.
Procurement
New
Search by bundle name
From now on it is possible to search by the bundle name.
- Under 'Setup' → 'bundles' it is possible to create or edit a bundle and give the bundle a name.
- It is possible to search by name on the bundle via the search bar or via 'Products'.
*Note, this might contain additional configuration and possibly involves extra costs. Ask the Account Manager for more information.