The account-level dashboard provides an overview of your EDI-specific integration activities, allowing you to view and manage data centrally. The EDI activity tab on the Dashboard offers access to detailed information on all EDI flows and documents across various tiles.
Using flow branching, you can establish different connections to execute EDI flows with one or multiple trading partners. Additionally, you can manage multiple tiles with different trading partners or the same trading partners grouped by different EDI document types.
Note
-
You can view the EDI activity tab on the Dashboard, only if you have a valid EDI subscription.
-
The EDI dashboard displays 100 records per page (default setting).
The Dashboard's EDI activity tab offers several benefits:
-
Centralized data viewing in one location.
-
Real-time or near real-time data display, keeping users informed on critical information without manual data gathering and analysis.
-
Filter records with functional acknowledgement status.
-
Tracking of key performance success versus failure metrics.
-
Reduced time and effort for data collection and analysis, increasing productivity by minimizing the need to gather data from multiple tiles and flows.
As an EDI admin, you have access to a consolidated view of all EDI data processing activities across all integration tiles within your integrator.io account. The EDI Dashboard allows you to see all inbound and outbound flows and the status of functional acknowledgments. The EDI activity tab is divided into two segments: Flows and Documents.
The Flows view displays all activities related to EDI flows at the account level. By default, the Document view is selected; you need to choose Flows view from the drop-down menu as shown in the image below. In the EDI activity tab's Flows view, only completed flows are visible, and "In-progress" flows are not displayed. Only the completed flows that have an EDI profile assigned are fetched and presented in the EDI flows view.
In the Flows view, you can filter data using the multiple options shown in the image above. By default, you will view the activity of the Last 24 hours. You can apply a manual filter and view the data as per your needs.
|
Field name |
Description |
|---|---|
|
Total flow runs |
The number of times the flow has been completed for the selected date range. |
|
Avg run time |
The average amount of time it takes for a flow to run from execution to completion. This calculation also includes the average amount of time a flow must wait in a queue before the actual run. |
|
Auto-resolved |
The number of errors automatically resolved because they matched another error’s trace key (unique field identifier). |
Additionally, you can monitor and resolve errors. You can find the open error count for each flow in the Open errors column. When you click on the error count, the errors are segregated between the sender and receiver. You can further click on the error count, to see individual error details.
The Documents view is the default view of the EDI activity tab. In this view, you can find data related to EDI-specific attributes collated during the runtime while processing the EDI data. This view sources data based on the information received processing the document, or from the functional acknowledgement generation or functional acknowledgement reconciliation flows. Each record in the dashboard is a transaction on the EDI file.
In the Documents view, you can filter the functional acknowledgement by various statutes such as Accepted, Accepted with errors, Rejected, Failed, Not Applicable, In Progress, and Not Received. You can select one or many statuses to filter the EDI documents.
|
FA status |
Description |
|---|---|
|
Accepted |
A document is successfully parsed and a functional acknowledgment is generated. This status is applicable for functional acknowledgement generation and reconciliation. |
|
Accepted with errors |
A document is successfully parsed and has errors. This status is applicable for functional acknowledgement reconciliation. |
|
Rejected |
A document has failed to parse and a functional acknowledgment is generated with the rejection reason. This status is applicable for functional acknowledgement generation and reconciliation. |
|
Failed |
If the flow fails and fails to generate a functional acknowledgement. This status is applicable for functional acknowledgement generation and reconciliation. |
|
Not Applicable |
While configuring the listener from export, if you uncheck the Send functional acknowledgement box, this status is shown. This status is applicable for functional acknowledgement generation. |
|
In Progress |
When a functional acknowledgement flow is running (in progress), this status is shown. This status is applicable for functional acknowledgement generation. |
|
Not Received |
If you're expecting a functional acknowledgement and haven't received it, this status is shown. This status is applicable for functional acknowledgement reconciliation. |
If the FA status is Rejected, you can click on the status to view a detailed description for rejection.
|
Field name |
Description |
|---|---|
|
Doc no. |
Document number: A unique identifier assigned to a transaction or a processed document. Example: PO123456789 |
|
Doc type |
Document type: The type of business document processed or exchanged through the EDI system. Example: Invoices (INV), Purchase orders (PO), shipping notices (ASN), etc. |
|
FA status |
Functional acknowledgement status: The Functional Acknowledgment (FA) status (a specific type of EDI transaction). The FA status signifies whether the received EDI document was processed successfully or partially, with or without any errors. |
|
File type |
File type: A standardized format that’s used for exchanging data between businesses in a structured manner. Each file type serves a distinct purpose and is chosen based on the requirements of the specific EDI transaction or workflow. |
|
Direction |
Direction: The direction of a data transaction between an ERP and a trading partner. Transactions received by the ERP are “Inbound”, and transactions sent from the ERP to a trading partner are “Outbound”. |
|
Processed |
Data processed on: The date and time an EDI transaction was processed. This timestamp helps to track document or transaction lifecycles and efficiently manage timelines within business processes. |
|
ISA no. |
Interchange control number: A unique identifier assigned to an EDI Interchange. An interchange refers to one or more EDI documents or transactions sent to a receiver via a single transmission. It helps to track, manage, and ensure the integrity of data exchanged between trading partners. |
|
GS no. |
Group control number: A unique identifier used within a specific group of related transaction sets or documents within an EDI transmission. It helps to manage and organize batches of similar transactions sent between trading partners. |
|
ST no. |
Transaction set control number: A unique identifier assigned to each transaction set within a group in an EDI transmission. It ensures that each transaction set, such as an invoice or purchase order, can be uniquely identified and managed throughout the data exchange process. |
|
Int sender |
Interchange sender number: A unique identifier for an entity that sends the EDI Interchange to a trading partner. It helps to identify and manage the communications between businesses involved in the exchange of electronic data. |
|
Int receiver |
Interchange receiver number: A unique identifier for an entity that receives the EDI interchange from the sending partner. This is a key component in the setup of EDI communications, as it ensures that the data being sent is accurately and securely delivered to the intended recipient. |
|
GS sender |
Group sender number: A unique identifier for an entity or party that receives a specific group of related EDI messages within an interchange. These groups are composed of transaction sets or messages that share a functional similarity and are transmitted together from the Group Sender. |
|
GS receiver |
Group receiver number: A unique identifier for an entity or party that originates a specific group of related EDI messages within an interchange. The group, in EDI terms, is a collection of transaction sets or messages that are related by function and sent together as a unit to the Group Receiver. |
|
FA details |
Functional acknowledgment details: The Functional Acknowledgment (FA) details ensure that the EDI messages were successfully received. FA details confirm whether the document batch received was accepted or rejected based on syntax and formatting validation. |
You can find specific transactions on the EDI activity dashboard under the Documents view. The search box features a drop-down menu that allows you to search by Document number (default), Interchange sender ID, or Interchange receiver ID. The search box accepts only string data and has a character limit of 30.
To search for transactions, you can either enter the ID of the document, interchange sender or receiver, or search using a wildcard. For example, entering PO123* will retrieve the results of all the purchase orders starting with PO123. However, only one wildcard can be used at a time; an example of an invalid input would be 123*890*xyz. The search results will be sorted in descending order.
You can filter transactions within the data sets on the EDI activity dashboard under the Documents view. This advanced filtering option helps you focus on relevant information by allowing you to filter transactions based on specific criteria. The filtering is dynamic and real-time. The "Filter By" option lets you select multiple criteria. Click Apply to filter the transactions using the following options:
-
FA status: Accepted, Accepted with Errors, Rejected, Failed, Not Applicable, In Progress, Not Received
-
Doc type: IN, PO, PC, SH, PR
-
File type: X12, EDIFACT (will be supported in the future releases)
-
Direction: Inbound, Outbound
The FA status filter retrieves records from the database based on the selected options. The Doc type, File type, and Direction filters apply to the results already displayed on the Dashboard.
Comments
Article is closed for comments.