Exception Handling
When PO Line Price Change automation fails due to an error, the failed Purchase Order document record is moved to Data Lake and is displayed on these tabs of the Review Center screen in the RPA Management application:
- Missing Information: This tab displays Purchase Order documents with the MISSINGINFORMATION status. A Purchase Order document is set to this status when the automation process is unable to extract any of the mandatory fields from the Customer Purchase Order document, such as PO number, Item number, Vendor details, or Ordered date.
- Need Action: This tab displays Purchase Order documents with the NEEDACTION status. A Purchase Order document is set to this status if one of these conditions is met:
- The Ordered Date in the document does not match the Ordered Date value for the PO in SyteLine.
- The Effective Date in the document matches the Effective Date value for the vendor contract in SyteLine.
- The UOM value in the document does not match the UOM value in SyteLine.
- The Use PO Change Order parameter on the Purchasing Parameters form is set to Sometimes.
- The status of the PO Change Order for the PO is Finalized.
- Items listed in the document are not available on the PO records of SyteLine.
- Failure: This tab displays Purchase Order documents with the FAILURE status. A Purchase Order document is set to this status if:
- The document is other than the Purchase Order or Vendor Contract.
- The Amend Ordered PO checkbox is not selected on the Purchasing Parameters form.
- When the file size is more than the maximum file size.
- API, IDP or any application fails.
Note:
- If these records are corrected by the user, RPA reprocesses the price change documents in the next workflow run.
- Users can switch between the automations on the Review Center screen to view the related exceptions.