Common Use Cases for Acknowledge Purchase Order
Here are the common use cases for Acknowledge Purchase Order:
Common Use Cases |
Description |
---|---|
Accept a Purchase Order |
|
Reject a Purchase Order |
|
Acknowledge a Purchase Order, Accept, or Reject Each Line with No Changes |
|
Acknowledge a Purchase Order with Changes |
|
Line Change
You can use an acknowledgment with an acknowledgment code value in the lineChange code list to communicate a price change, part number correction, UOM change, quantity change or date change.
You must provide one of these values in the payload when the acknowledgment code
value is in the lineChange code list, else the message is skipped:
- UnitPriceAmount - If a non-negative numeric value is provided in the payload for a line change, the purchase order is updated.
- SupplierItemNumber - When a SupplierItemNumber is provided in the payload for a line change, the supplier item number can be updated on the PO line if the feature Correct the Supplier Item Number on Purchase Orders is enabled. Otherwise, you need to create a descriptive flexfield for B2B Part Number Correction, which will be populated with the corrected part number.
- UnitOfMeasureCode - When a UnitOfMeasure is provided in the payload for a line change, the descriptive flexfield (b2bAckReviewRequired) on the PO header is set to One or more lines have acknowledgment comments and the UnitOfMeasureCode provided in the payload is mapped to the flexfield (b2bUOMChange) on the PO line.
- OrderQuantity - The purchase order is updated when positive decimal numbers are provided.
- PromisedShipDate, or PromisedDeliveryDate - The PromisedShipDate or PromisedDeliveryDate is updated when a date change is provided in the payload and it is as expected by the Buyer Managed Transport setting on the PO, otherwise the descriptive flexfield is updated.