Contents

• 1 Introduction
• 2 Procurement
  
  • 2.1 Users can update emailed purchase orders from Purchase Professional Tools
  • 2.2 Improved document details view for Purchase Professional Tools
  • 2.3 Purchase requisition data enrichment for order data
  • 2.4 Users cannot add HTML files as attachments to purchase documents
  • 2.5 Validation for contract imports - Contract numbers must be unique for the same supplier within an organization
  • 2.6 Expressions enabled for all price fields when using Order REST API

2.1 Users can update emailed purchase orders from Purchase Professional Tools

Module(s): Purchase
Feature ID: ALUSTA-76054
Release: P2P 21.10
Feature Implementation: Feature is in use automatically

Users of Purchase Professional Tools can now update an individual purchase order if changes have been made to the order. The action is available from the Procurement dashboard and from the document details view. Update is not available as a batch action. 

After clicking Update, the user can select whether the changes were initiated by the buyer or the supplier, leave a comment about the update, and select whether to send the updated purchase order to the supplier. 

2.2 Improved document details view for Purchase Professional Tools

Module(s): Purchase
Feature ID: ALUSTA-81524
Release: P2P 21.10
Feature Implementation: Feature is in use automatically

Users of Purchase Professional Tools can now enjoy an improved details view for purchase documents. The view allows users to see more information at one time and navigate the document information using tabs, in the same way as the List and details view layout on the Procurement dashboard.

The new details view includes many document actions, but some actions are not yet available. If you don’t see the action that you want to perform, click the link in the informational banner. You can access all of the possible actions from the legacy document details view.

History has also been added to the list of available tabs in the Procurement dashboard and the document details view. 

2.3 Purchase requisition data enrichment for order data

Module(s): Purchase
Feature ID: ALUSTA-83464
Release: P2P 21.10
Feature Implementation: Basware consultant work is needed

anyERP data enrichment can now be used to enrich the purchase order information on purchase requisition drafts. The enrichment updates fields like payment terms, contract number, order sending method, and goods receiver (updates with a single receiver only). Data enrichment can update these fields for each purchase order to be created from a purchase requisition draft. 

2.4 Users cannot add HTML files as attachments to purchase documents

Module(s): Purchase
Feature ID: ALUSTA-85087
Release: P2P 21.10
Feature Implementation: Feature is in use automatically

Users can no longer upload HTML files in Basware P2P for security reasons. Previously, if users tried to add HTML files with security concerns as attachments to purchase documents, a confusing error message was shown to the user. We have added a clearer error message so that users better understand this limitation.

2.5 Validation for contract imports - Contract numbers must be unique for the same supplier within an organization

Module(s): Purchase
Feature ID: ALUSTA-85418
Release: P2P 21.10
Feature Implementation: Feature is in use automatically

When importing contracts into Basware P2P, the import data is now validated to ensure that no contracts for an organization have the same contract number and supplier. If two contracts for an organization have the same contract number and supplier, they are considered duplicates and cannot be imported. 

It is possible to import contracts with the same contract number and supplier if they are imported to different organizations.

2.6 Expressions enabled for all price fields when using Order REST API

Module(s): Purchase
Feature ID: ALUSTA-85498
Release: P2P 21.10
Feature Implementation: Feature is in use automatically

When using the Order API to send purchase orders, expressions can now be executed for the following fields: data.documentLines.allowanceCharges.amount, data.documentLines.allowanceCharges.baseAmount and data.documentLines.lineExtension.amount. Expressions can enable features such as rounding for these price fields.