Overview

In certain cases, customers may face an issue where a Purchase Order (PO) does not appear in Basware AP, even though it has been sent successfully via API.
This article explains how to verify whether the PO was sent correctly and how to identify potential issues in the data flow.

Root Cause

This issue typically occurs when the PO Header and PO Order Lines are not sent in the correct sequence.
If the Order Lines are sent before the Header data, the system cannot associate them with the correct Header, causing them to remain in temporary database tables.

 

Resolution Steps

1. Send PO Data in the Correct Sequence

• Always send the PO Header first, followed by the associated Order Lines.
• Use the POST method for both requests.

 

2. Verify PO Header Data

• Use the GET method to retrieve and verify the Header details.
• Ensure you use the correct External Code to pull the Header data.
  (Example: GET /api/order/{externalCode}

3. Verify PO Line Data

• Similarly, verify the PO Line details using the appropriate GET method.
• Compare the data with the expected line-level information.
  (Example: GET /api/orderlines/{externalCode})

 

4. Check “lastUpdated” Field

• Review the “lastUpdated” timestamp at the end of both:
  • The Header data, and
  • The Order Line data.
• This helps confirm that both header and line records were sent and processed properly in sequence.