This document contains descriptions of new features in Basware Purchase-to-Pay 17.11 and its maintenance releases.
Module(s): Purchase
Feature ID: ALUSTA-27867
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
Now it is possible to define default coding row data to manual budgets. Once a budget is manually selected in a requisition draft, the corresponding default values of the budget will be retrieved and the existing values will be overwritten. If the default value is empty, the existing value is not overwritten. For instance, the selected budget can state a specific account code related to its purchase type. The same coding is copied to all lines/splits in the requisition.
The values are given as codes without a lookup list. There is no lookup list validation in the requisition draft, so if the codes are invalid, the approval process validates them. The fields are account code, cost center code, project code, and invoicing dim code 1-10.
Module(s): Purchase
Feature ID: ALUSTA-24675
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
In EHF Order response, the seller may propose changes to quantity, delivery period, price, or replacement item. Now Basware P2P can receive an EHF order response with a replacement item. When the seller accepts an order with changes, the order response code «30» must be sent on order header level to the buyer.
Module(s): Purchase
Feature ID: ALUSTA-27977
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Purchase order PDF encryption settings now allow copying text from the document.
Module(s): Purchase
Feature ID: ALUSTA-17545
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
Now it is possible to select if budgets are used as dynamic or manual budgets per tenant. With manual budgets, the budget creator states to which users the budget is available. The budget users can select the budget in P2P Purchase in requisition draft - if the budget is active and not expired. Once the user has selected the budget, all requisition lines go to that same budget. The user can still change the budget or release it before sending it to process. During requisition approval process or order process, the manual budget cannot be released or changed, but lines can be added/deleted depending on process boundaries. To change or release the budget, the requisition must be recalled or returned to owner. The requisition states the budget consumption bar in the user interface, and in budget management, the corresponding manual budget states the budget consumption lines in requisition (pending) and order process (reserved, spend) phases.
Module(s): Purchase
Feature ID: ALUSTA-17546
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Now it is possible to set organization to the header data as well as state the inheritance to lower organizations when creating a manual or dynamic budget. In P2P Purchase’s Budgets, the budget visibility, management (creation and editing), as well as activation is tied to the organization that the budget is addressed to and the user has rights for. In the Workplace client, the user also has only those budgets available that include the organization the user is purchasing to.
Module(s): Purchase
Feature ID: ALUSTA-13677
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
Now users are able to view from P2P order history if order sending has succeeded, so that they know if any further action is required from the buyer to ensure that the supplier receives the order.
Module(s): Purchase
Feature ID: ALUSTA-26886
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Purchase requisition search function has been enabled in the Edge client. A user can now search for their purchase requisitions and requisition tasks and filter the requisition based on free text, organization, and date. If the user has the “View your organization’s purchase requisitions” user right, the user can search also all other requisitions in the organizations the user has rights for. The user is not able to open the documents but can see the status, current recipient, purpose, organization, date, document number, and gross total of the requisitions.
Goods receipts search function has been enabled in the Edge client. The user can now search for goods receipts and goods receipts tasks and filter the requisition based on free text, organization, and date. The user is not able to open the documents but can see the status, purpose, organization, date, document number, and gross total of the goods receipts.
Module(s): Invoice Automation
Feature ID: ALUSTA-11596
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
Now the system can perform an advanced invoice coding row validation and a lookup list validation during the header review, header approve, admin approve, row review, and row approve activities. This helps making sure that the invoice coding rows are valid when the user performs the review or approve action on an invoice.
This new feature needs to be configured in use in the Configuration Tool. By default, this feature is disabled.
Module(s): Invoice Automation
Feature ID: ALUSTA-28258
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
To enable better mobile usage the invoice image is now opened to the current window from the icon.
Invoice image can still be opened in another tab clicking the correct item in the menu that opens when you click the secondary mouse button.
Module(s): Match Orders
Feature ID: ALUSTA-5787
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Previously Basware P2P limited the amount of purchase order numbers in the invoice header data. This restriction is removed. Now users are able to add, modify, copy, and delete purchase order numbers with a similar dialog that was already earlier available for delivery notes. In Edge, the values can be copied over from a spreadsheet. Now it is also possible to match an invoice with larger number of purchase orders if necessary.
Module(s): Invoice Automation
Feature ID: ALUSTA-18464
Release: P2P 17.11
Feature Implementation: Basware consultant work is needed
Search results are not automatically loaded any more, this is behind a parameter.
Module(s): Analytics
Feature ID: ALUSTA-30197
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Tableau server version is upgraded to 10.3.2
Module(s): Analytics
Feature ID: ALUSTA-22442
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
A new dashboard, Supplier Quality, has been created under Procurement workbook tab to replace the previous version of the same dashboard.
The Supplier Quality dashboard is designed for analyzing the performance of the suppliers with enhanced focus on products ordered and various quality measures.
Supplier Quality view allows users to assess the relevance of different suppliers within supplier categories, which can be also analyzed starting from the products ordered.
The suppliers can be weighed either based on their purchase volume and value or through multiple dimension options.
Module(s): Invoice Automation
Feature ID: ALUSTA-27893
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Now it is possible to change notification email settings for tasks, discussions, and announcements on the User settings page in Edge.
Module(s): Invoice Automation
Feature ID: ALUSTA-26616
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Now it is possible change the login password and approval password on the User settings page in Edge.
Module(s): Invoice Automation
Feature ID: ALUSTA-26617
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Now it is possible to change the language and region on the User settings page in Edge.
Module(s): Invoice Automation
Feature ID: ALUSTA-26613
Release: P2P 17.11
Feature Implementation: Feature is in use automatically
Now it is possible to define a default approver on the User settings page in Edge.