This article describes the behavior, mandatory services, and necessary configurations in Basware P2P for enabling electronic order responses to XML orders (UBL 2.0).
When sending electronic business documents, both the sender and the receiver must be known and must be unique within the business network, like Basware Commercial Network (BCN). For this purpose, Basware P2P uses Identifiers, also known as Party Identifiers.
The customer, or buyer organization, must have the BCN service E-orders and E-invoice receiving to enable e-ordering. Buyers can request the service from the Basware Support Portal.
The supplier must have the BCN service Invoice Key-in and PO Flip to send order responses to the buyer. Buyers can create campaigns in Basware Portal to invite suppliers to register for the service. If the buyer is using SmartOrders, then the supplier does not need to register for Basware Portal. Instead, the link in the purchase order email will take the supplier to a limited version of the BCN service where the supplier can perform the same order response actions.
Check identifiers in Basware P2P
Check that the correct identifiers are configured for buyers and suppliers.
To check the buyer identifier:
To check the supplier identifier:
Check the scheduled task in Basware P2P
Order Responses are fetched by P2P from BCN by using a scheduled task called "ImportPurchaseOrder". Check that this task is configured correctly for your system:
There are two different types of order responses:
Order Response Simple - must not contain line data details
Order Response (Full)
|The Payment term field is emptied when the order response is processed in P2P||
When the order response is processed by P2P, the payment term is resolved by payment term name and organization element ID. Ensure that payment term names are unique within each company.
|The Tax code field is emptied when the order response is processed in P2P||
When the PO is sent to a Basware Portal supplier with Tax %, it is possible that the tax code includes also Tax2 % (e.g. EU purchases from another EU country). Basware Portal does not support Tax2 %. When the PO reaches Basware Portal, the normal Tax % is cleared due to Tax2 %.
If supplier does not add the correct Tax % on the order response, this will result in an Order Change as the Tax Total becomes zero. There are mandatory pre-processing routines in Basware Network to remove the Tax2 % from Basware Network orders which must be implemented to ensure that the Tax % is not emptied.
|Order response processing fails in P2P, according to the purchase order History||This issue is most likely caused by errors in order response data and needs to be investigated by Customer Services.|
|The purchase order is not updated with the correct status and no entries show in the purchase order History||
First, follow the instructions above to check the Buyer and Supplier Identifiers. Those are the ONLY methods P2P uses to recognize the buyer and supplier.
If those are correct, This issue is most likely caused by errors in order response data or configuration and needs to be investigated by Customer Services.
If you're using RestAPI connections, the only method to recognize is the Purchase Order Number. In this case, you must have a unique PO number for every PO.