Exception handling

To ensure transparency and operational control, the solution includes a dedicated Receipt Automation Result screen in FSM for monitoring, reviewing, and managing automation outcomes.

This screen serves as the central exception management and audit dashboard for the Packing Slip Attachment Automation.

To access this result screen, go to Receiving > Lists and Reports > Receipt Automation Results.

Result screen layout

The screen provides this information:

  • Visibility into each automation run (Run Date)
  • Summary-level success and failure counts
  • Line-level transaction details
  • Clear failure reasons for exception cases
  • Hyperlinks to Purchase Order numbers, allowing users to directly navigate to the PO record
  • Hyperlinks to Purchase Order Receipt numbers
  • Hyperlinks to the attached packing slip document, so users can view the document directly from the result screen, which is useful when reviewing failed scenarios

These navigation links eliminate the need for manual searching within the system and significantly reduce investigation time.

Header-level grouping

Results records are grouped based on the Company in the header. This grouping provides a company-wise view of all automation results, making it easier for users operating in multi-company setups to review outcomes.

Records for which the AI cannot determine a Company appear under the configured default Company. This company is configured while deploying the solution.

Run-level alert indicator

If an RPA run is interrupted by an unexpected technical error, a red alert icon is displayed beside the run status, along with a message that describes the interruption inside that line.

Users can drill into the record to view the status of packing slips in a specific run.

Line-level status

Users can open a record to view the status of a specific run.

This table shows the statuses which are displayed at the line level.

Status Description
Success The packing slip has been successfully attached to the receipt.
Failed The packing slip failed to attach to the receipt, for example, due to a receipt mismatch, a quantity mismatch, or an item mismatch.
Not Processed The RPA cannot process the packing slip due to reasons, such as the file is password-protected, the file size exceeds the permitted limit, or the PDF quality is below the required threshold.
Reprocess A previously failed record has been prepared for reprocessing.

Handling failed records

For records in the Failed status, users can perform manual reprocessing:

  1. Open the failed record from the Exception Handling screen.
  2. Click the All Purchase Order Receipts tab.

    This tab displays all Purchase Order Receipts for the Purchase Order.

  3. Select the correct Receipt Number to which the packing slip must be attached.
  4. Save the record.

After you save the record, the status changes from Failed to Reprocess. During the next RPA run, the record is picked up automatically and the packing slip is attached to the specified receipt.

If you do not want to wait until the next RPA run, use the Move Attachment to Receipt button.

  • Click this button to immediately move and attach the packing slip to the specified receipt.
  • The status is updated accordingly. You are not required to wait for the next scheduled run

Accessing the packing slip documents

Users can access packing slip documents in these locations:

  • For records with a Failed status, users can view the document in the Exception Handling screen.
  • For records with a Success status, users can view the document in the Receipt Comments section.
  • For records with either status, users can access the documents from the Related Information in-context widget.

This table shows the list of exception messages and its occurrences.

S.No Message Category Scenario description
1 Unable to match POR for packing slip attachment Error This exception occurs when the RPA is unable to identify a fully matched Purchase Order Receipt (POR) for the uploaded packing slip document.
2 Cannot attach packing slip: Purchase order receipt not found Error This exception occurs when the RPA is unable to find the respective purchase order receipt.
4 The system is unable to retrieve the company value based on the Ship-To address Error This exception occurs when the AI model is unable to determine the Company value based on the Ship-To location address extracted from the packing slip.
5 File size exceeds the permitted limit: 20 MB Error This exception occurs when the uploaded document exceeds the maximum allowed file size of 20 MB for RPA processing.
6 UOM in the packing slip doesn't match the line item: "+_itemID Error This exception occurs when the Unit of Measure (UOM) in the packing slip differs from the UOM specified in the Purchase Order Receipt for the respective line item.
7 Quantity in the packing slip doesn't match the line item: "+_itemID Error This exception occurs when the Quantity in the packing slip does not match the Quantity recorded in the Purchase Order Receipt for the respective line item.
8 Item in the packing slip doesn't match the line item: "+_itemID Error This exception occurs when the Item listed in the packing slip does not match the Item specified in the Purchase Order Receipt for the respective line item.
9 Unsupported file format Error This exception occurs when the uploaded packing slip document is in a file format that is not supported by the RPA.
10 Missing mandatory fields in the packing slip Error This exception occurs when the uploaded packing slip document does not contain essential information required for processing, such as PO Number, Ship-To Address, Item details, or Quantity.