Guidelines for troubleshooting the integration
Use this information to identify and resolve common issues that may occur during invoice processing immediately after the solution is deployed in a tenant. Follow the guidance to diagnose problems and complete the required setup.
Most fixes are one‑time configuration tasks. After you complete them, the same issues should not recur unless the solution is modified or moved.
If a failure occurs later, long after deployment, you can use this guide to trace how far the process ran successfully and where it failed.
To troubleshoot effectively, you must have access to and basic knowledge of Infor ION, Infor Enterprise Collaborator (IEC), Infor Document Management (IDM), and Infor M3 Accounts Payable.
Invoice not found in M3 'Supplier Invoice Batch. Open' (APS450) or accounts payable
You may encounter a situation where a supplier invoice document is received and processed successfully by the RPA automation flow, but no invoice is created in 'Supplier Invoice Batch. Open' (APS450)
Use the step‑by‑step checks to identify where the process stopped and what you need to verify to resolve the issue.
This table shows the possible issues between Review Center or RPA and ION:
| Issue | Cause | Solution or verification |
|---|---|---|
Missing LoadSupplierInvoice BOD in ION OneView after the invoice has been processed by RPA or in Review Center. |
Required ION connection points are missing or inactive | Verify that the IMSfromRPAStudio and IMSfromRPAAgent connection points exist and are active. Ensure that the Document tab for both connection points includes LoadSupplierInvoice set to Send from Application. |
| Data flow is missing or inactive | Required ION data flow is not configured or activated | Verify that the M3InvoiceProcessing data flow exists and is activated. |
This table shows the possible issues between ION and M3:
| Issue | Cause | Solution or verification |
|---|---|---|
LoadSupplierInvoice BOD exists in ION OneView, but the invoice is not available in 'Supplier Invoice Batch. Open' (APS450) |
LoadSupplierInvoice document is not added to the Infor M3 connection point. |
Ensure that the Document tab for the Infor M3 connection point includes LoadSupplierInvoice set to Receive in Application. |
| Processing error in ION | Errors occurred during BOD processing | In ION, select and click the Error BODs tab to verify whether errors are logged and then, resolve them. |
| Invoice stopped in Enterprise Collaborator | Error occurred during IEC processing | In Enterprise Collaborator Administration, go to Messages and verify errors related to the M3_SupplierInvoice_Load_In agreement. |
Invoice document not displayed in Related Information widget
After the invoice status is set to 90 ‘Updated in APL in 'Supplier Invoice Batch. Open' (APS450) and the invoice is added, for example, to (APS205) in table FPLEDG, the programmatic event PGM_SupplierInvoice_FPLEDG is sent. This event is picked up by Event Hub (EH) and Event Analytics (EA).
The event triggers the publication of a SyncSupplierInvoice BOD, which is sent to ION. This BOD contains key fields such as the supplier, invoice number, invoice year, and voucher number. These fields must be updated in Infor Document Management.
In ION, an XSLT mapping transforms the SyncSupplierInvoice BOD into the ProcessContentDocument BOD required by Infor Document Management.
The corresponding invoice record in Infor Document Management is then updated with these key fields and attributes. This information links the invoice in M3 with the invoice document in Infor Document Management, allowing the invoice image to be displayed in various M3 programs.
See Configuration of M3 to display invoices in Smart panel.
Use the step‑by‑step checks to identify where the process stopped and what you need to verify to resolve the issue.
This table shows the possible issues between M3 and ION:
| Issue | Cause | Solution or verification |
|---|---|---|
| The supplier invoice document is not displayed in the Related Information widget in any Accounts Payable program. | Infor Business Context is not published. | Set H5 to publish Infor Business Context. |
| The supplier invoice document is not displayed in (APS450). | The Correlation ID is not included in the list view in (APS450/B). | Add the Correlation ID (CORI) to the list view. |
| The supplier invoice document is not displayed in other AP programs, but is visible in (APS450). | The invoice status in (APS450) is not 90 – Updated to APL. | Correct any errors and ensure the invoice has status 90 - Updated to APL in (APS450). |
| The invoice has status 90 - Updated to APL but is not found in Accounts Payable, for example, in (APS205). | The invoice was not transferred to Accounts Payable due to erroneous transactions. | In 'Trans Work File. Restart Erroneous Jobs' (GLS037), correct any errors and update. |
| The invoice was stopped in Infor Enterprise Collaborator. | If the invoice exists in AP, for example, in (APS205), check whether a successful message exists or an error is logged for the M3_SupplierInvoice_Sync_Out agreement in Enterprise Collaborator Administration. |
|
No message exists for the M3_SupplierInvoice_Sync_Out agreement, |
The SyncSupplierInvoice BOD is not activated for the company and division. |
Ensure that SyncSupplierInvoice BOD is enabled for the correct company and division in M3 BOD Processor administration. |
The SyncSupplierInvoice document is not added to the M3 connection point in ION. |
The document is not configured for the connection point. | Ensure that the Document tab for the Infor M3 connection point includes SyncSupplierInvoice set to Send from Application. |
The SupplierInvoice BOD is not sent from M3. |
Filtering or routing rules in Event Analytics block the message. | Ensure that no filtering or routing rules prevent the SupplierInvoice BOD from being sent. Verify that the rules M3BODs_SupplierInvoice > PGM_SupplierInvoice_FPLEDG and FPLEDG_UPDATE_SupplierInvoice are active. |
| Events are not processed. | Event Hub or Event Analytics is not running. | Check the Event Hub log file. |
This table shows the possible issues between ION and IDM:
| Issue | Cause | Solution or verification |
|---|---|---|
The ProcessContentDocument BOD is not added to the Infor Document Management connection point. |
The document is not configured on the connection point. | If a SyncSupplierInvoice BOD exists in ION but no ProcessContentDocument BOD, ensure that the Document tab of the daf connection point includes Process.ContentDocument and is set to Receive in Application. |
The data flow M3_SupplierInvoice_to_IDM is missing or inactive. |
The data flow is not imported or activated. | Ensure that M3_SupplierInvoice_to_IDM exists in ION Data Flows and is active. |
| Supplier invoice attributes are not updated in IDM. | An error occurred in IDM. | If the ProcessContentDocument BOD exists in ION but attributes are not updated, run the Health Check in IDM Control Center for ION and IDM. Check the Infor OS Grid status report for errors. |
| The Supplier Invoice document type is missing or incorrectly configured in IDM. | The IDM document type does not match the delivered standard. | Ensure that the document type M3_SupplierInvoice exists and includes all required attributes and configuration. Download the document type from KB3643459 and compare. |