Purchase Order Status Updates are sent by systems using cXML. The specification for the StatusUpdateRequest is detailed here, along with a sample.

See Documentation Topics:

Purchase Order Status Update Integration

Integration Logs

Overview

The BuyerQuest platform is able to receive Purchase Order Status Updates (StatusUpdateRequest) from other systems.

The specifications for these status updates are described here and can be further referenced in the cXML specification found at http://xml.cxml.org/current/cXMLUsersGuide.pdf.

Integration Configuration

This integration is configured in the Admin Control Panel at SYSTEM ADMINISTRATION > Settings and Configurations > Manage System Configurations > PROCURE > PO Integrations > Inbound cXML PO Integration.

1. To enable PO Status Updates, set Accept cXML PO Status Updates to Yes.
2. Choose to Enable Purchase Order Validation with Yes or No.
3. The Sender's Identity must be specified if either of the above fields are set to Yes.
4. The Sender's Shared Secret must be specified for the integration of the Purchase Order Status Update or Validation.

The Status Update Request will be authenticated using the values from the Sender's Identity and Shared Secret.

Purchase Order Status Update Log

The Purchase Order Status Update Log is available in the Admin Control Panel in INTEGRATION LOGS.

Purchase Order Status Update Request

The Purchase Order Status Update Request specification is included here:

PurchaseOrderStatusUpdate11.9.xlsx

cXML Status Update Request

Sample Inbound cXML Message from Third Party to BuyerQuest

<?xml version="1.0"  encoding="utf-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.033/cXML.dtd">
<cXML   timestamp="2019-08-015T16:34:28-07:00" 
payloadID="459853158454--78954319574654654654@10.11.128.013">
     <Header>
          <From>
               <Credential domain="DUNS">
                    <Identity>2839102938</Identity>
               </Credential>
          </From>
          <To>
               <Credential domain="NetworkID">
                    <Identity>BuyerQuest</Identity>
               </Credential>
          </To>
          <Sender>
               <Credential domain="NetworkID">
                    <Identity>MVEMJSUN/Identity>
                    <SharedSecret>384jfd9yh5</SharedSecret>
               </Credential>
               <UserAgent>ERP System</UserAgent>
          </Sender>
      </Header>
     <Request>
          <StatusUpdateRequest>
               <DocumentReference payloadID="PO-000001"/>
               <Status code="200" text="OK" xml:lang="en-US">Fully Received</Status>
          </StatusUpdateRequest> 
     </Request>
</cXML>

cXML StatusUpdateRequest Response Specifications

When the system receives a StatusUpdateRequest, the system verifies the received payload id as a valid BQ PO Number in the system.

The BuyerQuest system verifies that the received Status is one of Partially Received, Fully Received, Invoiced, or Closed. If it is not one of the specified statuses, a 403 Incorrect Status message is sent to the third party.

If the Purchase Order exists in the system and the Status value received is valid, a 200 OK message is sent to the third party system.

Sample BuyerQuest Response Message

The response message from BuyerQuest system conforms to the sample below.

<cXML payloadID="9949494" xml:lang="en" timestamp="1999-03-12T18:39:09- 08:00">
     <Response>
          <Status code="200" text="OK"/>
     </Response>
</cXML>

Status Codes Used in BuyerQuest Responses