---
title: "Monitoring & Resolving Exceptions"
slug: "monitoring-and-troubleshooting-2"
description: "Explore the IC Interaction Log and Document Relations for seamless tracking of intercompany transactions, ensuring efficient order processing and error resolution."
status: "update"
updated: 2026-09-03T09:31:09Z
published: 2026-09-03T09:42:52Z
canonical: "docs.abakion.com/monitoring-and-troubleshooting-2"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abakion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring & Resolving Exceptions

## 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, 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, so you can trace a sales order line all the way to the posted shipment or invoice it produced — even across different Business Central environments. Two further surfaces complete the picture: the IC Sales Order Fact Box, visible directly on the sales order, shows at a glance whether a line has been transmitted and acknowledged; and the standard Business Central Change Log, surfaced through the IC Change Log Part, records field-level changes to IC-related records.

Beyond transaction-level troubleshooting, the app also raises proactive, app-level notifications so administrators catch configuration problems before they cause failures: an activation reminder when the app is installed but not yet set up, a warning when one or more IC Partners are not yet using Web Service communication (which is being made mandatory), and a blocking notification when a required data upgrade has not yet been applied — the app will not process any transactions until that upgrade is executed.

### Key Facts

| Page | What it covers |
| --- | --- |
| IC Interaction Log | Full history of all outbound web service calls: method, HTTP status, request XML, response XML, partner codes, linked document |
| IC Document Relations | Links IC outbox transactions to posted documents (shipments, invoices) on the Supply Company side |
| IC Sales Order Fact Box | Per-line IC status panel on the sales order: partner code, vendor order, purchase order status, IC status |
| IC Change Log Part | Field-level change history for IC-related records (who changed what and when) |
| Handled IC Outbox Transactions | Transactions that have been sent; includes Export IC XML action to download the transaction payload |
| Handled IC Inbox Transactions | Transactions received by the Supply Company; includes Export IC XML action and Created DateTime |
| Reopen | List of purchase orders with a status above Open, used to reopen orders locked due to IC processing |
| Role Center / Setup / Partner notifications | Proactive alerts for activation, mandatory Web Service enablement, and required data upgrades |

---

## Getting Started

**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. Verify the IC Partner Code is populated, the Intercompany flag is set, and the IC Status and Purchase Order Status reflect the expected state.

**Step 2 — Establish the outbox transaction number.** Open Handled IC Outbox Transactions and filter by the sales order number using the External Document No. field. If the transaction is still in the outbox and not yet Handled, the call may not have been attempted yet.

**Step 3 — Open the IC Interaction Log.** Search "IC Interaction Log" via Tell Me. Entries are sorted by Entry No. descending, so the most recent calls appear first.

**Step 4 — Filter by IC partner and date.** Narrow the log to the relevant Target IC Partner Code and the time window of interest, or filter directly by Outbox Transaction ID.

**Step 5 — Identify failed calls.** Check HTTP Request Status: Error entries did not complete. Common HTTP Request Status Code values: 200 = success, 401 = authentication failure, 404 = endpoint not found, 500 = remote application error.

**Step 6 — Read the response text, then the response XML if needed.** The Response (text) column often names the root cause directly. If it's truncated, use the Response XML action to download the full SOAP fault.

**Step 7 — Use Document Relations to confirm receipt.** If the log shows a successful call but the Supply Company reports nothing arrived, check IC Document Relations for that outbox transaction — a missing relation means no shipment was posted.

**Step 8 — Reopen a locked order if needed.** Use the Reopen page to reset a purchase order stuck above Open status due to an IC processing failure.

**Step 9 — Act on any standing app notifications.** Resolve any Role Center / Setup notifications about activation, mandatory Web Service enablement, or pending data upgrades — until the data-upgrade notification is cleared, no IC web service calls will run at all.

---

## Related Features

Monitoring surfaces the outcome of the automation performed by **Sending and Receiving Documents Automatically** and **Automatic Order Creation Between Companies** — every call those features make is logged here. Fixing a failure often means revisiting **Setting Up a Partner Company** or **Partner Configuration**, since 401/404 errors typically trace back to connection or Web Service settings on the IC Partner Card. **Cross-Company Invoicing** documents that fail to post correctly can also be traced back to a specific outbox transaction and Interaction Log entry.

---

## User Stories

****Reviewing the full communication history between companies****

**As a** system administrator **I want to** open the IC Interaction Log from the Tell Me search **So that** I have a complete history of every web service call made between companies in one place

**Setup:**

1. Search "IC Interaction Log" using Tell Me.
2. Review entries sorted by Entry No. descending (most recent first).

****Narrowing the log to a specific partner and time window****

**As a** support agent **I want to** filter the IC Interaction Log by Target IC Partner Code and an Interaction DateTime range **So that** I can focus on calls to a specific partner during a specific window

**Setup:**

1. Open IC Interaction Log.
2. Use the filter pane to set Target IC Partner Code and Interaction DateTime.

****Isolating failures for a specific operation type****

**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 and spot a pattern of failures for one operation

**Setup:**

1. Open IC Interaction Log.
2. Filter the Method field (e.g. a specific import/update method name).

****Verifying exactly what was sent to the partner****

**As a** support agent **I want to** download the Request XML from a log entry **So that** I can see the exact SOAP payload transmitted and verify order lines and quantities were correct

**Setup:**

1. Select the relevant log entry in IC Interaction Log.
2. Choose the Request XML action.

****Reading the full error returned by the partner****

**As a** support agent **I want to** download the Response XML from a log entry **So that** I can read the complete SOAP fault and identify the precise cause of a failed call

**Setup:**

1. Select the relevant log entry in IC Interaction Log.
2. Choose the Response XML action.

> **Note:** The Response (text) field already shows a 250-character summary — download the full XML only if that summary isn't specific enough.

****Routing an error by its HTTP status code****

**As an** operations user **I want to** see the HTTP Request Status Code on a log entry **So that** I can distinguish an authentication error (401), a missing endpoint (404), and a server error (500), and route it correctly

**Setup:**

1. Open IC Interaction Log.
2. Review the HTTP Request Status Code column for the failed entry.

****Tracing a failed call back to its source order****

**As an** operations user **I want to** trace a log entry with HTTP Request Status = Error back to the source outbox transaction via Outbox Transaction ID **So that** I can find the original sales order that triggered the failed call

**Setup:**

1. Note the Outbox Transaction ID on the failed log entry.
2. Look up that transaction in Handled IC Outbox Transactions.

****Confirming a sales line's IC status without leaving the order****

**As a** salesperson **I want to** see IC Status, Purchase Order Status, and Vendor Order No. in the IC Sales Order Fact Box **So that** I can confirm the order was transmitted and acknowledged without leaving the sales order page

**Setup:**

1. Open a sales order in the Sales Company.
2. Review the IC Sales Order Fact Box.

****Reconciling documents across companies****

**As a** supply chain coordinator **I want to** use IC Document Relations to find the posted shipment matching a specific outbox transaction **So that** I can confirm delivery and reconcile documents across companies

**Setup:**

1. Open IC Document Relations for the outbox transaction in question.
2. Use the Document No. to locate the posted shipment in the Supply Company.

****Reopening an order locked by an IC processing failure****

**As a** supply chain coordinator **I want to** use the Reopen page to reset a purchase order locked at a status above Open **So that** I can correct the order and resume the IC workflow

**Setup:**

1. Open the Reopen page from the IC outbox or purchase order actions.
2. Select the affected order and reopen it.

> **Note:** Reopening a sales order in the Sales Company also triggers a web service call to reopen the corresponding order in the Supply Company.

****Auditing who changed intercompany data****

**As a** compliance officer **I want to** review the IC Change Log Part on IC-related pages **So that** I can see who changed which fields and when

**Setup:**

1. Open an IC-related record (e.g. IC Partner Card).
2. Review the Change Log Part/FactBox.

****Diagnosing a document that never arrived at the Supply Company****

**As a** support agent **I want to** check the Interaction Log for the relevant outbox transaction and confirm whether the call was made and what status it returned **So that** I can determine whether the failure was a connection/authentication issue or the transaction was never sent

**Setup:**

1. Identify the outbox transaction from the sales order.
2. Filter the Interaction Log by Outbox Transaction ID.

****Diagnosing a stuck status update after successful processing****

**As a** support agent **I want to** check the Interaction Log for confirmation calls made after a transaction was sent **So that** I can determine whether the callback from the Supply Company failed and where the status update was lost

**Setup:**

1. Filter the Interaction Log by the relevant Outbox Transaction ID and a later time window.
2. Review any confirmation/update calls and their status.

****Downloading the full transaction payload for comparison****

**As a** support agent **I want to** use the Export IC XML action on Handled IC Outbox/Inbox Transactions **So that** I can compare the transaction payload with the Request XML in the Interaction Log and verify content was transmitted correctly

**Setup:**

1. Open Handled IC Outbox Transactions or Handled IC Inbox Transactions.
2. Select the transaction and choose Export IC XML.

****Getting reminded to activate the app after installation****

**As an** administrator **I want to** see a notification on the Role Center when Intercompany is installed but not yet activated **So that** I don't forget to complete setup

**Setup:**

1. Open the Role Center after installing the app.
2. Follow the Activate action, or postpone/dismiss the reminder.

****Being warned when a partner isn't using Web Service communication****

**As an** administrator **I want to** see a notification listing IC Partners not yet enabled for Web Service communication **So that** I can enable it before it becomes mandatory and calls start failing

**Setup:**

1. Open the Role Center, Intercompany Setup, or an IC Partner page.
2. Follow the notification's action to read the setup guide or activate Web Service communication for all partners at once.

****Clearing a required data upgrade that blocks all processing****

**As an** administrator with SUPER or D365 IC PARTNER EDIT permissions **I want to** see and act on the Data Exchange Type upgrade notification **So that** the app can resume processing — no web service calls run until this upgrade is applied

**Setup:**

1. Open the Role Center, Intercompany Setup, IC Partner, or a related sales/purchase document.
2. Follow the notification's action to run the upgrade.

> **Note:** This is a hard block, not a warning — transactions will not be sent or received until the upgrade completes.

---

## Field Reference

### Interaction Log Entries

| Field | Where to find it | What it does | Default value |
| --- | --- | --- | --- |
| Entry No. | IC Interaction Log | Unique identifier for the log entry | Auto-incremented |
| Interaction DateTime | IC Interaction Log | Date/time the web service call was made | — |
| User ID | IC Interaction Log | User who triggered the call | — |
| Method | IC Interaction Log | Name of the remote web service method called | — |
| Request XML | IC Interaction Log | Full SOAP request payload (downloadable) | — |
| Response (xml) | IC Interaction Log | Full SOAP response payload (downloadable) | — |
| Response (text) | IC Interaction Log | Plain-text summary of the response/error | — |
| Outbox Transaction ID | IC Interaction Log | Related IC outbox transaction number | — |
| Source IC Partner Code | IC Interaction Log | Partner code of the calling company | — |
| Target IC Partner Code | IC Interaction Log | Partner code of the receiving company | — |
| HTTP Request Status Code | IC Interaction Log | Numeric HTTP status returned by the remote server | — |
| HTTP Request Status | IC Interaction Log | Status flag: blank, OK, or Error | — |
| Record URL | IC Interaction Log | Deep link to the source document | — |

### IC Document Relations

| Field | Where to find it | What it does | Default value |
| --- | --- | --- | --- |
| Transaction No. | IC Document Relations | IC outbox transaction this relation links to | — |
| IC Partner Code | IC Document Relations | Partner involved in the transaction | — |
| Document No. | IC Document Relations | Resulting posted document on the Supply Company side | — |