Monitoring and Troubleshooting

Feature Overview

Every time the Intercompany app makes a web service call between companies — sending an order, syncing a confirmation, or transferring a posted document — it writes a record to the IC Interaction Log. Each entry captures the exact timestamp, the user who triggered the action, the web service method that was called, the full SOAP request and response payloads as downloadable XML files, a plain-text summary of the response, the source and target IC partner codes, the outbox transaction the call relates to, and the HTTP status code returned by the remote server. A status flag of OK or Error makes failed calls immediately visible. The log is read-only and accessible from the Tell Me search or directly from the IC setup area, so support staff and administrators can review the full communication history between companies without leaving Business Central.

Document Relations provide a cross-company audit trail that links each IC outbox transaction to the resulting posted document on the Supply Company side. When the Sales Company releases a sales order, the Intercompany app places an outbox transaction in the IC outbox. Once the Supply Company processes that transaction and posts a shipment, the resulting document number is stored in the IC Document Relation table against the original transaction number, IC partner code, and sales line reference. This means you can start from a sales order line in the Sales Company and trace exactly which posted shipment on the Supply Company side was generated by that order — even across different Business Central environments. The chain is: sales order line → IC outbox transaction → IC inbox transaction at the Supply Company → posted shipment (or invoice), with the Document Relation record holding the final posted document number.

Two additional surfaces complete the monitoring picture. The IC Sales Order Fact Box, visible directly on the sales order, shows at a glance the IC partner code, vendor order number, purchase order status, IC status, and intercompany flag for each sales line — so a user can assess whether an order has been successfully transmitted without leaving the sales order page. The standard Business Central Change Log, surfaced through the IC Change Log Part, records field-level changes to IC-related records and answers the question of who changed what and when. Together these four surfaces — the Interaction Log, Document Relations, the IC Sales Order Fact Box, and the Change Log — give a complete picture of the state of any IC transaction.

Key Facts

Getting Started

The steps below describe a typical investigation, starting from the first symptom (an order that does not appear to have reached the Supply Company) and working through to resolution.

Step 1 — Check the IC Sales Order Fact Box on the sales order.
Open the sales order in the Sales Company and locate the IC Sales Order Fact Box on the right-hand side of the page. Verify that the IC Partner Code is populated, the Intercompany flag is set, and that the IC Status and Purchase Order Status reflect the expected state. If IC Status is blank or the Vendor Order No. is missing, the transaction may not have been sent at all.

Step 2 — Establish the outbox transaction number.
Open the IC Outbox or Handled IC Outbox Transactions list and filter by the sales order number using the External Document No. field. Note the transaction number — you will use this to cross-reference in the Interaction Log. If the transaction is still in the outbox and has not been moved to Handled, the web service call may not have been attempted yet.

Step 3 — Open the IC Interaction Log.
Search for "IC Interaction Log" using the Tell Me function or navigate directly from the IC setup. The log is sorted by Entry No. descending by default, so the most recent calls appear at the top.

Step 4 — Filter by IC partner and date.
Use the filter pane to narrow the log to the relevant Target IC Partner Code and an Interaction DateTime range covering the time the order was released. You can also filter by Outbox Transaction ID using the transaction number found in Step 2 to find the specific call.

Step 5 — Identify failed calls.
Look at the HTTP Request Status column. Entries marked Error indicate the web service call did not complete successfully. The HTTP Request Status Code column shows the numeric HTTP code. Common codes and their meaning: 200 = success, 401 = authentication failure (expired OAuth2 token or incorrect credentials), 404 = the web service endpoint was not found (incorrect URL or web service not published), 500 = an application error occurred on the remote server.

Step 6 — Read the response text.
The Response (text) column shows a plain-text summary of the error message extracted from the SOAP fault response. This is often sufficient to identify the root cause — for example, "IC Partner Code X not found" or a field validation error on the remote company.

Step 7 — Download and inspect the response XML.
If the response text is truncated or does not contain enough detail, select the log entry and choose the Response XML action in the action bar. Business Central will download the full SOAP response as an XML file. Open it in a text editor or browser to read the complete fault string returned by the Supply Company.

Step 8 — Download the request XML to verify what was sent.
If you suspect the document content was incorrect, use the Request XML action to download the full SOAP request payload. This shows exactly what data was transmitted — including all order lines — and can be compared against the expected document content.

Step 9 — Use Document Relations to confirm receipt.
If the Interaction Log shows a successful call (HTTP status 200, status OK) but the Supply Company reports they did not receive the order, open the IC Document Relation records for the outbox transaction. A missing relation record means the Supply Company did not post a shipment for that transaction. If a relation record exists but the Supply Company cannot find the document, use the Document No. field in the relation to search for the posted shipment directly in the Supply Company.

Step 10 — Reopen a locked order if needed.
If a sales or purchase order is locked at a status above Open due to an IC processing failure, use the Reopen page (accessible from the IC outbox or purchase order actions) to reset the status and allow further editing. The page lists all purchase orders with a status above Open. On the sales side, reopening the sales order in the Sales Company will also trigger the app to reopen the corresponding sales order in the Supply Company via a web service call.

Related Features

The IC Interaction Log and Document Relations work alongside the standard Business Central IC Outbox and IC Inbox pages, which show the current pipeline of pending transactions. For deep investigation of what was in a specific transaction, the Export IC XML action on the Handled IC Outbox Transactions and Handled IC Inbox Transactions pages lets you download the full IC transaction XML that was transmitted — this is the same document that appears in the Request XML of the corresponding Interaction Log entry. The IC Partner setup contains the web service connection details (URL, credentials, timeout) that determine how calls are made, and checking these settings is a prerequisite when investigating 401 or 404 errors. For large documents, the Intercompany app automatically routes IC inbox transactions to the Job Queue for asynchronous processing; in this case the transaction status on the IC Inbox Transactions page will show "Scheduled for Handling" and the outcome can be monitored through the Job Queue Entries page using the SCBIC category. The Change Log, configured through the standard BC Change Log Setup, records every field-level modification to IC-related master data and transaction records, providing a full audit trail for compliance and support purposes.

User Stories

1. As a system administrator, I want to open the IC Interaction Log from the Tell Me search and see a list of all web service calls made between companies, so that I have a complete communication history in one place.

2. As a support agent, I want to filter the IC Interaction Log by Target IC Partner Code and a date range, so that I can focus on the calls made to a specific partner during a specific time window without scrolling through unrelated entries.

3. As a support agent, I want to filter the IC Interaction Log by Method, so that I can see only calls of a specific type — for example, all ImportOutboxTransaction calls — and assess whether a pattern of failures exists for a particular operation.

4. As a support agent, I want to select a log entry and download the Request XML, so that I can see the exact SOAP payload that was transmitted to the Supply Company and verify that the order lines and quantities were correct.

5. As a support agent, I want to select a log entry and download the Response XML, so that I can read the full SOAP fault message returned by the Supply Company and identify the precise error that caused a call to fail.

6. As an operations user, I want to see the HTTP Request Status Code on a log entry, so that I can quickly distinguish between an authentication error (401), a missing endpoint (404), and a server-side application error (500) and route the issue to the right person.

7. As an operations user, I want to identify a log entry with HTTP Request Status = Error and trace it back to the source outbox transaction using the Outbox Transaction ID field, so that I can find the original sales order that triggered the failed call.

8. As a salesperson, I want to see the IC Status, Purchase Order Status, and Vendor Order No. in the IC Sales Order Fact Box on my sales order, so that I can confirm the order has been transmitted and acknowledged by the Supply Company without leaving the sales order page.

9. As a supply chain coordinator, I want to use the IC Document Relations to find which posted shipment on the Supply Company side corresponds to a specific IC outbox transaction from the Sales Company, so that I can confirm delivery and reconcile documents across companies.

10. As a supply chain coordinator, I want to open a purchase order that has been locked at a status above Open due to an IC processing issue, using the Reopen page, so that I can correct the order and resume the IC workflow.

11. As a compliance officer, I want to review the IC Change Log Part on IC-related pages to see who changed which fields and when, so that I can audit modifications to IC transactions and master data.

12. As a support agent investigating a case where the Supply Company never received a document, I want to check the Interaction Log for the relevant outbox transaction and confirm whether the call was made and what HTTP status was returned, so that I can determine whether the failure was a network/authentication issue or whether the transaction was never sent (still sitting in the outbox).

13. As a support agent investigating a case where the Supply Company processed a document but the Sales Company's status was not updated, I want to check the Interaction Log for any calls made after the transaction was sent — particularly calls with methods such as RemotePurchOrderUpdate or RemoteHandledInboxTrans — so that I can determine whether the confirmation callback from the Supply Company failed and where in the sync process the status update was lost.

14. As a developer or system administrator, I want to understand that deferred web service calls occur when a sales document is posted inside a transaction context where commits are suppressed, so that I know to look for transactions marked as deferred in the IC Outbox and monitor the Job Queue under the SCBIC category rather than expecting an immediate synchronous call.

15. As a support agent, I want to use the Export IC XML action on the Handled IC Outbox Transactions or Handled IC Inbox Transactions page to download the full IC transaction XML for a specific transaction, so that I can compare the document payload with the corresponding Request XML in the Interaction Log and verify that the content was transmitted correctly.

Field Reference

Interaction Log Entries

IC Document Relations

Feature Overview

Every time the Intercompany app makes a web service call between companies — sending an order, syncing a confirmation, or transferring a posted document — it writes a record to the IC Interaction Log. Each entry captures the exact timestamp, the user who triggered the action, the web service method that was called, the full SOAP request and response payloads as downloadable XML files, a plain-text summary of the response, the source and target IC partner codes, the outbox transaction the call relates to, and the HTTP status code returned by the remote server. A status flag of OK or Error makes failed calls immediately visible. The log is read-only and accessible from the Tell Me search or directly from the IC setup area, so support staff and administrators can review the full communication history between companies without leaving Business Central.

Document Relations provide a cross-company audit trail that links each IC outbox transaction to the resulting posted document on the Supply Company side. When the Sales Company releases a sales order, the Intercompany app places an outbox transaction in the IC outbox. Once the Supply Company processes that transaction and posts a shipment, the resulting document number is stored in the IC Document Relation table against the original transaction number, IC partner code, and sales line reference. This means you can start from a sales order line in the Sales Company and trace exactly which posted shipment on the Supply Company side was generated by that order — even across different Business Central environments. The chain is: sales order line → IC outbox transaction → IC inbox transaction at the Supply Company → posted shipment (or invoice), with the Document Relation record holding the final posted document number.

Two additional surfaces complete the monitoring picture. The IC Sales Order Fact Box, visible directly on the sales order, shows at a glance the IC partner code, vendor order number, purchase order status, IC status, and intercompany flag for each sales line — so a user can assess whether an order has been successfully transmitted without leaving the sales order page. The standard Business Central Change Log, surfaced through the IC Change Log Part, records field-level changes to IC-related records and answers the question of who changed what and when. Together these four surfaces — the Interaction Log, Document Relations, the IC Sales Order Fact Box, and the Change Log — give a complete picture of the state of any IC transaction.

Key Facts

Getting Started

The steps below describe a typical investigation, starting from the first symptom (an order that does not appear to have reached the Supply Company) and working through to resolution.

Step 1 — Check the IC Sales Order Fact Box on the sales order.
Open the sales order in the Sales Company and locate the IC Sales Order Fact Box on the right-hand side of the page. Verify that the IC Partner Code is populated, the Intercompany flag is set, and that the IC Status and Purchase Order Status reflect the expected state. If IC Status is blank or the Vendor Order No. is missing, the transaction may not have been sent at all.

Step 2 — Establish the outbox transaction number.
Open the IC Outbox or Handled IC Outbox Transactions list and filter by the sales order number using the External Document No. field. Note the transaction number — you will use this to cross-reference in the Interaction Log. If the transaction is still in the outbox and has not been moved to Handled, the web service call may not have been attempted yet.

Step 3 — Open the IC Interaction Log.
Search for "IC Interaction Log" using the Tell Me function or navigate directly from the IC setup. The log is sorted by Entry No. descending by default, so the most recent calls appear at the top.

Step 4 — Filter by IC partner and date.
Use the filter pane to narrow the log to the relevant Target IC Partner Code and an Interaction DateTime range covering the time the order was released. You can also filter by Outbox Transaction ID using the transaction number found in Step 2 to find the specific call.

Step 5 — Identify failed calls.
Look at the HTTP Request Status column. Entries marked Error indicate the web service call did not complete successfully. The HTTP Request Status Code column shows the numeric HTTP code. Common codes and their meaning: 200 = success, 401 = authentication failure (expired OAuth2 token or incorrect credentials), 404 = the web service endpoint was not found (incorrect URL or web service not published), 500 = an application error occurred on the remote server.

Step 6 — Read the response text.
The Response (text) column shows a plain-text summary of the error message extracted from the SOAP fault response. This is often sufficient to identify the root cause — for example, "IC Partner Code X not found" or a field validation error on the remote company.

Step 7 — Download and inspect the response XML.
If the response text is truncated or does not contain enough detail, select the log entry and choose the Response XML action in the action bar. Business Central will download the full SOAP response as an XML file. Open it in a text editor or browser to read the complete fault string returned by the Supply Company.

Step 8 — Download the request XML to verify what was sent.
If you suspect the document content was incorrect, use the Request XML action to download the full SOAP request payload. This shows exactly what data was transmitted — including all order lines — and can be compared against the expected document content.

Step 9 — Use Document Relations to confirm receipt.
If the Interaction Log shows a successful call (HTTP status 200, status OK) but the Supply Company reports they did not receive the order, open the IC Document Relation records for the outbox transaction. A missing relation record means the Supply Company did not post a shipment for that transaction. If a relation record exists but the Supply Company cannot find the document, use the Document No. field in the relation to search for the posted shipment directly in the Supply Company.

Step 10 — Reopen a locked order if needed.
If a sales or purchase order is locked at a status above Open due to an IC processing failure, use the Reopen page (accessible from the IC outbox or purchase order actions) to reset the status and allow further editing. The page lists all purchase orders with a status above Open. On the sales side, reopening the sales order in the Sales Company will also trigger the app to reopen the corresponding sales order in the Supply Company via a web service call.

Related Features

The IC Interaction Log and Document Relations work alongside the standard Business Central IC Outbox and IC Inbox pages, which show the current pipeline of pending transactions. For deep investigation of what was in a specific transaction, the Export IC XML action on the Handled IC Outbox Transactions and Handled IC Inbox Transactions pages lets you download the full IC transaction XML that was transmitted — this is the same document that appears in the Request XML of the corresponding Interaction Log entry. The IC Partner setup contains the web service connection details (URL, credentials, timeout) that determine how calls are made, and checking these settings is a prerequisite when investigating 401 or 404 errors. For large documents, the Intercompany app automatically routes IC inbox transactions to the Job Queue for asynchronous processing; in this case the transaction status on the IC Inbox Transactions page will show "Scheduled for Handling" and the outcome can be monitored through the Job Queue Entries page using the SCBIC category. The Change Log, configured through the standard BC Change Log Setup, records every field-level modification to IC-related master data and transaction records, providing a full audit trail for compliance and support purposes.

User Stories

1. As a system administrator, I want to open the IC Interaction Log from the Tell Me search and see a list of all web service calls made between companies, so that I have a complete communication history in one place.

2. As a support agent, I want to filter the IC Interaction Log by Target IC Partner Code and a date range, so that I can focus on the calls made to a specific partner during a specific time window without scrolling through unrelated entries.

3. As a support agent, I want to filter the IC Interaction Log by Method, so that I can see only calls of a specific type — for example, all ImportOutboxTransaction calls — and assess whether a pattern of failures exists for a particular operation.

4. As a support agent, I want to select a log entry and download the Request XML, so that I can see the exact SOAP payload that was transmitted to the Supply Company and verify that the order lines and quantities were correct.

5. As a support agent, I want to select a log entry and download the Response XML, so that I can read the full SOAP fault message returned by the Supply Company and identify the precise error that caused a call to fail.

6. As an operations user, I want to see the HTTP Request Status Code on a log entry, so that I can quickly distinguish between an authentication error (401), a missing endpoint (404), and a server-side application error (500) and route the issue to the right person.

7. As an operations user, I want to identify a log entry with HTTP Request Status = Error and trace it back to the source outbox transaction using the Outbox Transaction ID field, so that I can find the original sales order that triggered the failed call.

8. As a salesperson, I want to see the IC Status, Purchase Order Status, and Vendor Order No. in the IC Sales Order Fact Box on my sales order, so that I can confirm the order has been transmitted and acknowledged by the Supply Company without leaving the sales order page.

9. As a supply chain coordinator, I want to use the IC Document Relations to find which posted shipment on the Supply Company side corresponds to a specific IC outbox transaction from the Sales Company, so that I can confirm delivery and reconcile documents across companies.

10. As a supply chain coordinator, I want to open a purchase order that has been locked at a status above Open due to an IC processing issue, using the Reopen page, so that I can correct the order and resume the IC workflow.

11. As a compliance officer, I want to review the IC Change Log Part on IC-related pages to see who changed which fields and when, so that I can audit modifications to IC transactions and master data.

12. As a support agent investigating a case where the Supply Company never received a document, I want to check the Interaction Log for the relevant outbox transaction and confirm whether the call was made and what HTTP status was returned, so that I can determine whether the failure was a network/authentication issue or whether the transaction was never sent (still sitting in the outbox).

13. As a support agent investigating a case where the Supply Company processed a document but the Sales Company's status was not updated, I want to check the Interaction Log for any calls made after the transaction was sent — particularly calls with methods such as RemotePurchOrderUpdate or RemoteHandledInboxTrans — so that I can determine whether the confirmation callback from the Supply Company failed and where in the sync process the status update was lost.

14. As a developer or system administrator, I want to understand that deferred web service calls occur when a sales document is posted inside a transaction context where commits are suppressed, so that I know to look for transactions marked as deferred in the IC Outbox and monitor the Job Queue under the SCBIC category rather than expecting an immediate synchronous call.

15. As a support agent, I want to use the Export IC XML action on the Handled IC Outbox Transactions or Handled IC Inbox Transactions page to download the full IC transaction XML for a specific transaction, so that I can compare the document payload with the corresponding Request XML in the Interaction Log and verify that the content was transmitted correctly.

Field Reference

Interaction Log Entries

IC Document Relations