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.
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. Users can access this result screen directly from the Receipt Interface screen using this navigation path: .
This table shows the list of exception messages and its occurrences.
| S.No | Message | Category | Attachment or creation scenario | Scenario description |
|---|---|---|---|---|
| 1 | Unable to match POR for packing slip attachment | Error | Attachment | 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 | Creation | This exception occurs when the receipt creation flag is disabled and no Purchase Order Receipt exists in the system at the time of processing. |
| 3 | Extracted packing slip information does not align with PO line details | Error | Creation | This exception occurs when the receipt creation flag is enabled, but while creating Purchase Order Receipt lines, the extracted packing slip details do not match the corresponding items in the Purchase Order. |
| 4 | The system is unable to retrieve the company value based on the Ship-To address | Error | Common Process | 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: 10 MB | Error | Common Process | This exception occurs when the uploaded document exceeds the maximum allowed file size of 10 MB for RPA processing. |
| 6 | UOM in the packing slip doesn't match the line item: "+_itemID | Error | Attachment | 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 | Attachment | 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 | Attachment | 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 | Common Process | 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 | Common Process | 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. |