Observed issues and known errors

The main challenges observed are:

• Incorrect extraction of header and line charges from PDFs. Definitions of header and line charges vary by supplier and depend on each supplier’s individual invoice format.
• Incorrect extraction of purchase order or delivery numbers. Some suppliers use labels that are not covered by the current standard prompt and must be explicitly defined.

When OCR results are not as expected, updating the prompt for the relevant entities is often the most effective solution. This requires creating a new version of the Document Processor Flow and enhancing the prompt with clearer instructions and quality assurance rules to better control the output. Ensure to test the new version of the IDP Document Processor Flow thoroughly before setting it to active.

Occasionally, failure messages appear in the logs, typically due to:

• Incorrect process configuration during solution deployment
• Missing or incorrectly configured user arguments

See User arguments for Invoice Processing.

In rare cases, users can submit documents from Review Center without providing required information, such as an item code.

When this occurs:

• RPA cannot process the document.
• The process flow breaks.
• The document does not reappear in Review Center.

To resolve this issue:

• A system administrator must access the API Gateway.
• Retrieve the document details. You can locate the document in the API Gateway from the document ID, which is available in the execution log. Alternatively, you can find it by using the use case ID for M3InvoiceProcessing.
• Update the document by setting visibility = true and reprocessing = false. After the settings are changed, the document becomes available again in the Review Center. The user can then add the missing information, such as the item code, and reprocess the document.

If the line charge amount for line type 5 - Line charge in the Gross price (GRPR) field in 'Supplier Invoice Batch. Open Lines' (APS451) is rounded to two decimal places, even though more decimals are sent in the LoadSupplierInvoice BOD, you can enable a feature toggle to allow up to six decimal places.

To activate this feature toggle, open 'Feature List. Open' (CMS975) and select the Feature active check box for Feature ID 3640684.

RPA logs provide detailed information from the start to the completion of each job. You can retrieve these details from the log file located in the Logs folder within the configuration folder.

Log file details:

• File name:JobsResults[yyyymmdd].txt
• Path: configurationFolder\Logs

The path to the configuration folder is defined by the RPA user argument configurationFolder.

For each run, the RPA process logs this information:

• Start time
• Number of documents processed
• Download file paths and file details
• Processing results for each file
• Number of successfully processed files
• Number of files that failed processing
• End time

If the process runs in attended mode and exceptions occur, you can also check the logs in these locations:

• C:\ProgramData\Infor\RPA\TrayAssistant\Logs
• C:\ProgramData\Infor\RPA\Runtime\Logs

Apply these tips to help prevent common errors:

• Authorize IONAPI and Microsoft Office 365 in RPA Management > Manage > Authorization.
• If you run RPA in unattended mode, verify that the device status is Connected in RPA Management > Manage > Devices.

The Related Information widget in M3 shows the documents stored in Infor Document Management (IDM) based on context matching. If the required context values are not available on the screen, the document is not displayed even if it exists in IDM and was processed correctly.

If the ProcessContentDocument BOD does not update IDM, or if required attributes are missing or incorrectly mapped, IDM cannot associate the document with the M3 supplier invoice.

The widget cannot display the document if one or more required Business Context fields are:

• Not populated in IDM
• Not visible or available on the M3 screen

This table lists the identified issues, what to check, and the corresponding solutions:

Issue	Cause	Solution or verification
The incorrect invoice document is displayed in the Related Information widget.	Incorrect or missing Business Context Model in Infor Document Management for the selected M3 program and panel.	In Infor Document Management, select Control Center > Configuration > Business Context Model and search for the relevant M3 AP or GL program under the M3_SupplierInvoice document type. Verify that a correctly configured Business Context Model exists for the program and panel. For supplier invoices, the context model's XQuery must include additional key fields than the accounting entity (company/division) and the supplier invoice number to ensure the system can uniquely identify each invoice document. You can download the standard context models for the M3_SupplierInvoice document type from KB3643459 and import them or use them for comparison. See Configuration of M3 to display invoices in Smart panel.
The invoice document is not displayed in the Related Information widget for a specific AP or GL program, but is displayed in others.	Incorrect or missing Business Context Model in Infor Document Management for the selected M3 program and panel.	See the solution or verification for the incorrect invoice document displayed in the Related Information widget. If a correctly configured Business Context Model exists for the program and panel, verify that all fields referenced in the context model XQuery are available in the list view or panel. For 'Supplier Invoice Batch. Open' (APS450), you must add the Correlation ID (CORI) field to the view. Before the invoice reaches status 90 in APS450, not all attributes are updated in IDM, and CORI is required to locate the invoice document in IDM.