Articles in this section

Track an order's EDI documents with the dashboard's lifecycle view

The EDI activity dashboard gives EDI administrators one place to monitor EDI flows and the X12 and EDIFACT documents processed through integrator.io. The dashboard is only available at the account level (Home → Dashboards → EDI activity). Use the EDI activity dashboard to view EDI flow performance, track EDI documents, and resolve processing errors in real time.

 

Note

 If you click the Dashboard tab within an EDI integration, it doesn't show the EDI activity. That is, it is not available at the integration level.

Prerequisites

Before you can monitor EDI activities, ensure you meet the following requirements:

  • Subscription: You must have a valid B2B Manager subscription.
  • Permissions: You must have Admin or Manage All permissions to view account-level dashboard data.
  • Configuration: Only completed flows with an assigned EDI profile appear in the dashboard.

Tracking EDI documents overview 

To understand how EDI documents are tracked, let's consider an order-to-cash process. 

In this EDI process, an order between you and a trading partner usually produces several EDI documents. A buyer sends a purchase order, the supplier acknowledges it, ships the goods with an advance ship notice, and then sends an invoice. In the past, the EDI dashboard listed these documents separately by type and date, and you had to match them by hand to see how an order was progressing.

Now, the lifecycle view connects the documents for you. From an order, integrator.io reads the order reference (usually the PO number) from each document as it's processed, then groups documents that share that reference and the same trading partner pair. The EDIFACT equivalents for documents in this business process are ORDERS, ORDRSP, DESADV, and INVOIC, and REMADV.

You can similarly view other lifecycle processes, such as shipping or supply chain management and so on. This article uses the order-to-cash process as an example. 

EDI dashboard tabs & views for tracking

The tab strip at the top of the EDI activity dashboard has three default tabs, followed by any custom views you save. Select X12 docs or EDIFACT docs based on your requirements. Within tabs for documents, you can use the lifecycle and list views for tracking.

Dashboard tabs

Tab What it shows
Flows EDI flow runs. You can use filters to view specific details or for any analysis. This tab is not covered in this article.  For more information on flows, see View flow run logs.
X12 docs X12 transactions. Opens in the lifecycle (grouped) view. This is the default tab for most accounts. 
EDIFACT docs EDIFACT transactions in list view. This is the default tab for accounts on the EU domain (eu.integrator.io).
Any custom view

Custom views you create based on any details you'd like to quickly open for review or action.

Save a combination of filters, columns, and view mode as a named tab, such as "Acme 850s".

  • Create view + starts a new view with no filters.
  • Save as view copies the current tab's filters, columns, and view mode into a new view.
  • When you change filters or columns on a custom view, choose Save changes, Save as view, or discard the changes.
  • Rename or delete a view from More. You're asked to confirm before a view is deleted.

After you save, rename, or delete a view, an Undo option appears for 10 seconds. Switching between list and lifecycle view isn't saved as a change and can't be undone.

Lifecycle & list views for documents

Use the view toggle in the panel header to switch between the lifecycle & list views in the doc-related tabs. Switching is instant because both views load together. You can now view all the documents in the database, and the views are not restricted to a 24-hour window as they earlier were.

The doc tabs offers two views: 

  1. Lifecycle view groups all the related documents for a transaction, so you can follow the whole exchange in one place and see where it stopped in a business process.
  2. List view shows each processed document as its own row, so you can check its status or look into a specific document. That is, each row is a single document, with no grouping. Use a list view when you want to sort or scan individual transactions. 

X12 docs and EDIFACT docs each remember their own filters and search keyword while you stay on the page, so you can switch tabs and come back without losing your place. Refreshing the page returns to the default tab with no filters.

Lifecycle (grouped) view of EDI documents

Each row is an order group. The group row shows the most recent document in the group, its lifecycle status, and how many documents the group contains. Groups are sorted newest first, based on the most recent activity in each group.

  • Select the arrow on a group row to expand it and see every document in the group, newest first. Collapsing the group doesn't reload anything.
  • The arrow appears only when a group contains more than one document. A document with no related documents shows as a regular standalone row. For more information, see Special scenarios
  • Rows that are associated or linked with the main reference document leave Reference doc and Lifecycle status blank as shown in the table below.
  • The table loads 30 groups at a time and loads more as you scroll.
Reference doc Doc no. Lifecycle status Doc type Direction Ack status Partner
▾PO 6P31195 · 4 INV-20931 Invoice sent IN 810 Outbound Accepted Acme Retail
  ASN-7741   SH 856 Outbound Accepted Acme Retail
  6P31195   PR 855 Outbound Accepted Acme Retail
  6P31195   PO 850 Inbound Not applicable Acme Retail
▸PO 6P31188 · 2 6P31188 PO acknowledged PR 855 Outbound Rejected Acme Retail
— 8820144 Inventory sent IB 846 Outbound Not received Northwind

Use the lifecycle view to:

  • Find every document for an order by searching its PO number.
  • See the latest stage an order has reached without opening each document.
  • Spot where an order stalled, such as a PO that was never acknowledged or an ASN that was rejected.

Documents processed before this feature was enabled don't carry an order reference, so they appear as standalone rows instead of in a group. Lifecycle history builds up from the date the feature is turned on for your account. How far back you can see is also limited by your account's data retention period.

How documents are grouped in the lifecycle view

Documents are linked and grouped for an EDI business process. For example, in the case of the order-to-cash  – when integrator.io processes an EDI document, it saves three values used for grouping:

  • Reference document number: the order reference extracted from a specific segment of the document. It's stored in uppercase with a prefix, for example PO 6P31195 for X12 or ORDERS PO-123 for EDIFACT.
  • Partner pair: the sender and receiver IDs from the ISA (X12) or UNB (EDIFACT) envelope. The pair is direction-neutral, so a PO you receive and the invoice you send for it land in the same group.
  • Trading partner name: taken from the EDI profile.

Documents are grouped when they share both the same reference document number and the same partner pair, within the same environment (production or sandbox) and the same standard (X12 or EDIFACT).

 Example: Order-to-cash X12 reference fields

Example transaction set Document Reference taken from
850 Purchase order BEG03
855 PO acknowledgment BAK03
860 PO change (buyer) BCH03
865 PO change acknowledgment BCA03
856 Advance ship notice PRF01 (in the order loop)
810, 811, 812, 880 Invoice and related BIG04, or REF02 when REF01 = PO
875 Grocery PO BEG03
876 Grocery PO change BCH03
870 Order status report REF02

Example: Order-to-cash EDIFACT reference fields

Example message Reference taken from
ORDERS Document number (BGM), because the order number is the reference
ORDRSP, DESADV, ORDCHG, INVOIC, HANMOV, RECADV RFF reference number, only when the qualifier is ON (order number)


Grouping depends on the field names in your file definition rules. If you rename the fields that hold these values, the reference may not be extracted and the document shows as standalone.

Lifecycle status

Lifecycle status shows the latest stage in an EDI process. For example, in the case of the order-to-cash process, it tells you which stage of the order a document represents. It's set once, when the document is processed, based on two things: the document type and its direction. For example, an inbound 850 means you received a purchase order, and an outbound 810 means you sent an invoice.

On a group row, lifecycle status shows the status of the most recent document in the group. That makes it a quick answer to "how far has this order gotten?"

Example
Stage X12 EDIFACT Status 
Order 850, 875 ORDERS PO received (inbound) · PO sent (outbound)
Change 860, 876 ORDCHG PO change received · PO change sent
Acknowledgment 855, 865 ORDRSP PO acknowledged
Status 870 — Order status reported
Shipment 856 DESADV Shipped
Receipt — RECADV, HANMOV Goods received
Billing 810, 811, 812, 880 INVOIC Invoice received · Invoice sent

Reading lifecycle status

  • The group stops at an early stage. If a group's latest status is still the order stage days after the PO arrived, the acknowledgment or shipment hasn't been sent.
  • Lifecycle status doesn't mean success. It shows which stage was reached, not whether the partner accepted it. Check Ack status on each document to see whether it was accepted or rejected.
  • The cell is empty. The document type isn't part of a lifecycle (for example, an 846 inventory document), or the document was processed before the feature was enabled.

Ack status, different from lifecycle status

Ack status is separate from lifecycle status. It shows whether the trading partner's functional acknowledgment accepted the document.

Status Meaning
Accepted The partner accepted the document.
Accepted with error The partner accepted the document but reported errors.
Rejected The partner rejected the document. Hover to see View Ack error details, then select the chip to open the acknowledgment details.
Failed The acknowledgment couldn't be processed.
In-progress The acknowledgment is being processed.
Not received An acknowledgment was expected but hasn't arrived.
Not applicable No acknowledgment is expected for this document.

Special lifecycle scenarios 

One order, several shipments or invoices

When one PO is fulfilled in several shipments or billed on several invoices, every ASN and invoice appears in the same group as its own row.

One document for several orders

A consolidated invoice can reference more than one PO. The document appears in every group it references, so you'll see it under each PO. It's the same document, not a duplicate. 

Standalone documents

A document appears as its own row, with no warning, when:

  • It's the first document of an order, and nothing related has arrived yet.
  • No reference could be extracted from it.
  • Its reference matches a PO from a different partner pair.
  • It was processed before the lifecycle feature was enabled.

Missing PO or mismatched identifiers 

If an ASN or invoice references a PO that wasn't received in this account, the documents are still grouped by that reference. If documents share a PO number but their envelope identifiers don't match closely enough, they aren't merged into the group, and a warning badge appears beside the doc number.

Missing documents outside the data retention period

Sometimes, you might not find documents because they cannot be retained beyond the data retention period you're entitled to. Retain your log and error data for more than 30 days

Default columns in lifecycle & list views

Column Description
Reference doc The order reference that links documents, such as PO 6P31195. On a group row it's followed by the number of documents in the group. Shows a dash if no reference was found.
Doc no. The document's own number (for example, the invoice number on an 810).
Lifecycle status *The order stage the document represents. This column is available by default only in the lifecycle view. See Lifecycle status
Doc type The functional group code and transaction set, such as PO 850 or IN 810.
Direction Inbound (received from the partner) or Outbound (sent to the partner).
Ack status The functional acknowledgment (997, 999, or CONTRL) status. 
Partner The trading partner, taken from the EDI profile name. Shows a dash on older documents.
Date and time When the document was last processed.
Actions

For EDI flows & EDI acknowledgment flows, select an option below to view transaction details.

  • Download EDI file for completed EDI flows.
  • MDN activity log for only AS2 flows when the MDN status shows either as Sent or Received. The option shows for successful processed exports/imports. For imports, it also shows for unsuccessfully processed MDNs, that is, received but with errors, warnings, or failure. Check the title of the MDN activity log and read through the status message to get visbility into the issue and resolve it.
  • Download ack for completed acknowledgment flows. The option is not shown when Ack status is Failed, In progress, Not Applicable, or Not Received.

Additional specific view columns

 Additional columns, such as ISA, GS, and ST control numbers (for EDI X12), UNB no., UNH no., UNB sender, UNB receiver (for EDIFACT), MDN status, and Processed are available from the column picker. To change columns, open the column picker, select the columns you want, and select Apply. You can also drag columns to reorder them. Column choices are saved separately for list view and lifecycle view.

For EDI X12

Column Description
MDN status

The Message Disposition Notification (MDN) status or the electronic return receipt sent in an AS2 (Applicability Statement 2) transaction. The column shows Sent or Received only for AS2 Trading Partner or VAN export or import steps.

  • Exports (inbound): Shows Sent for only successful transactions
  • Imports (outbound): Shows Received for successful and unsuccessful transactions. You can click Actions → MDN activity log  and view the details.
Processed The date and time the EDI transaction was processed.
ISA no. The interchange control number for the transmission.
GS no. The group control number for related transaction sets.
ST no. The transaction set control number for each document in a group.
ISA sender The identifier for the entity sending the EDI interchange.
ISA receiver The identifier for the entity receiving the EDI interchange.
GS sender The identifier for the party receiving a specific group of messages.
GS receiver The identifier for the party originating a specific group of messages.

For EDIFACT 

Field Description
MDN status

The Message Disposition Notification (MDN) status or the electronic return receipt sent in an AS2 (Applicability Statement 2) transaction. The column shows Sent or Received only for AS2 Trading Partner or VAN export or import steps.

  • Exports (inbound): Shows Sent for only successful transactions
  • Imports (outbound): Shows Received for successful and unsuccessful transactions. You can click Actions → MDN activity log and view the details.
Processed The timestamp indicating when the transaction was processed.
UNB no. The Interchange control reference used to correlate messages between partners.
UNH no. The Message reference number for tracking independent messages in an interchange.
UNB sender The unique code identifying the sender of the EDIFACT interchange.
UNB receiver The unique code identifying the recipient of the EDIFACT interchange.


Customize column view

You can customize the Documents view to show only the data you need. Your selections persist across sign-in sessions. 

  1. Click the customize button (customize-edi-dashboard.png).
  2. Check the boxes next to the columns to include in your view.
  3. Drag and drop any column to reorder it. You can reorder all columns except the first and last columns, that is, the Reference doc and the Actions columns.

Search for EDI documents

On the X12 docs or EDIFACT docs tab, type at least 3 characters and up to 100 characters in the search box. You can search by a full or partial document or reference number, such as 6P311.Results appear as you type. In the lifecycle view, matching groups are already expanded, and the matching text is highlighted. If the match is in a hidden column, that column is shown for this search, and the footer names it.

To return to the full table, clear the search. Groups collapse again.

Lifecycle status filter isn't applied while you're searching. The filter chip stays on the bar and takes effect again when you clear the search.

Filter or sort columns to find EDI documents

Filter from the column headers. Available filters:

  • Doc type, Direction, Ack status, Partner, Lifecycle status, and MDN status (delivery receipt)
  • Date and time: pick a from and to date on the calendar, then select Apply. You can pick dates within your account's data retention period.

Filters are applied on the server, so they search all of your documents, not just the rows on screen. Select Clear on a filter to remove it.

Sorting is available in list view only, on Date and time and Partner. Lifecycle view is always sorted by most recent activity.

Download EDI records or rows 

Select Download to export all the documents in the database as a  CSV file. When you're viewing the dashboard, it uses your current view, filters, and search. Download is unavailable while the table is loading.

The footer shows how many records are loaded and the connection state:

Footer Meaning
60 of 133 records 60 records are loaded out of 133. Scroll to load more.
133 records · · · The table is loading.
133 records ✓ Up to date The data just refreshed. The label clears after 3 seconds.
12 cached Server connection failed. The rows shown are from the last successful load. Select Retry.

FAQ

Why isn't my invoice grouped with its PO?

Check that both documents carry the same PO number in the reference fields listed in How documents are linked, and that both use the same ISA or UNB sender and receiver IDs. Also check whether the PO was processed before the feature was enabled, or has aged out of your retention period.

Why does the same invoice appear under two orders?

The invoice references both POs. It's one document shown in each order it belongs to.

 Does a CONTRL, 997, or 999 appear as a lifecycle stage?

No. Functional acknowledgments are shown in the Ack status column of the document they acknowledge, not as separate stages.