Dashboard displays detailed information related to the execution of your Transactions. You can verify the status of the Transaction execution, execution details, errors occurred during execution, errors detail, and much more. Click on the home page to open the Dashboard page.

Dashboard contains the following sections displayed in the left pane of the screen.

Icon	Name	Description
	Overview	This section displays the execution details of your recent Transactions, Partners, and Data Usage in the graphical form. This section also displays the execution details of EDI and Non-EDI Transactions in the donut and bar chart.
	Transactions	This section displays the details of the Transactions that have triggered successfully but may or may not have been executed successfully.
	Trigger	This section displays the details of the Transactions that are either fetching data, are queued, have not found any data, or have stopped due to an error while triggering.
	Channel	This section displays the details of SAP logs.
	Audit Trail	This section maintains a log of all changes made to all the services.
	AIMap	This section displays the AIMap logs.
	Custom Dashboard	This section displays the logs of dashboard design. You can also execute the dashboard design from this section.
	System Logs	This section displays messages related to the system.
	EDI Reports	This section displays EDI reports.

Overview

This section displays the execution details of your recent Transactions, Partners, and Data Usage of last 30 days. You can also filter the graph on the basis of the Transactions, Partners, and Data Usage to view the execution details of last 30 days or last 7 days. Move the mouse pointer over the graphical area to view the details of the data processed (sent or received) and the number of times an execution has occurred for each of the categories.

You can view the EDI and Non-EDI Transaction details under the Transactions tab on the Overview screen. You can also view process flows and triggers under the Process Flows & Triggers tab. Click the appropriate tab to view the details.

Non EDI tab details

Name	Description
Internal Transactions	Displays the total number of Transactions (failed or successful) run by the Company. The successful and failed Transactions are displayed in the green and pink color.
Inbound Transactions	Displays the total number of Inbound Transactions (failed or successful) run by the Partner. The successful and failed Transactions are displayed in the green and pink color.
Outbound Transactions	Displays the total number of Outbound Transactions (failed or successful) run by the Partner. The successful and failed Transactions are displayed in the green and pink color.
Partner to Partner Exchange Transaction	Displays the total number of Partner to Partner Exchange Transactions (failed or successful). The successful and failed Transactions are displayed in the green and pink color.
Top 5 Partners By Transaction Run	Displays the list of top five Partners of a Company who had run the Transactions maximum number of times. The number in the chart corresponding to a Partner displays the number of times the Partner has run the Transaction.
Top 5 Partner to Partner Exchange Transaction Run	Displays the list of top five Partner to Partner Exchange Transactions of a Company who had run the Transactions maximum number of times. The number in the chart corresponding to a Partner displays the number of times the Partner has run the Transaction. Click here to enable this setting.

EDI tab details

Field name	Description
Acknowledgments	Displays the number of acknowledgments segregated with the following status: Sent: Number of acknowledgments sent for the successful Inbound Transactions. Reconciled: Number of acknowledgments received from the Partner for the successful outbound Transactions. Overdue: Number of acknowledgments not received from the Partner after the expiry time for the successful outbound Transactions. Pending: Number of acknowledgments to be received from the Partner for the successful outbound Transactions. Queued: Number of acknowledgments to be sent and are in the queued state for the successful Inbound Transactions.
Inbound Transactions	Displays the total number of Inbound Transactions (failed or successful). The successful and failed Transactions are displayed in the green and pink color respectively.
Outbound Transactions	Displays the total number of Outbound Transactions (failed or successful). The successful and failed Transactions are displayed in the green and pink color respectively.
Top 5 Partners By Volume	Displays the top five Partners with the maximum number of Transactions (inbound and outbound).
Top 5 Message Types By Volume	Displays the EDI and Non-EDI Message types with the number of volumes. The volume in each of the Transaction is calculated by the number of transaction sets in each type. All non-EDI Message types are shown as the Other option on the graph.
Inbound Acknowledgments	Displays acknowledgment summary of Partner's Inbound Transactions. Acknowledgment summary of a particular Partner can also be viewed by selecting the Partner from the drop-down list.
Outbound Acknowledgments	Displays acknowledgment summary of Partner's Outbound Transactions. Acknowledgment summary of a particular Partner can also be viewed by selecting the Partner from the drop-down list.

Transactions

This section displays the details of the Transactions that are executed successfully or aborted.

You can also filter the data based on Current Logs and Archived Logs. You can also choose to view only the process flows by selecting the 'Process Flows' option from the drop-down box lying just next to the Search box.

Click to view only aborted Transactions.

Post Process Transactions

You can also view the execution details of all the Transactions and Process Flows called in the Post Process Transaction by clicking . However, to view the process flows logs on Dashboard, you have to select View Logs on Connect Dashboard option while creating a process flow in the Developer's Studio.

The following table lists the description of the fields.

Field name	Description
Transaction	Name of the Transaction.
Template	Name of the Template used for creating Transaction.
Partner	Name of the Partner for which Transaction is executed.
User ID	Name of the user who last activated the transaction. Name of the user who triggered the transaction by uploading the file in file upload transaction.
Type	Type of Transaction whether App Inbound or Outbound or File Inbound or Outbound.
Started	Date and time when the Transaction was executed.
Reference	Displays the name of the source file used in the Transaction. In case, track variable function is used in the mapping, this field will display the tracked value. If multiple values are tracked, View link is displayed listing all the tracked values. You can also view the values of the track variables created in the Developer's Studio Data Mapper. For this, you need to use PF_ReferenceID as a second parameter in the Track Variable function in the Developer's Studio Data Mapper. For example, trackVariable($_class ,'PF_ReferenceID' ,'BUNAME' ,$Input_Text_edi/Root/Record/Seatno) This field will display the tracked value if both source file and tracked variable function are used in the Transaction.
Status	Displays the status of the Transaction. The status can be Fetching, No Data, Queued, Running, Success, and Abort. Fetching: Transaction is fetching data from the specified location. No Data: Transaction couldn't find any data at the specified location so far. Queued: Transaction is in a queue and is waiting to fetch data. Running: Transaction execution is in progress. : Successful execution of the Transaction. : An error in the execution of the Transaction.
Action	: View details of the execution. Execution status is displayed graphically. indicates all the stages of the Transaction execution have been processed successfully. Click to view the execution details. In case of an error, the status is displayed with the cause and fix of an error. Click to view the error details.
	: Re-runs the aborted Transaction after rectifying an error. You can only Re-run the Transaction till the time its reprocessing file is available and not deleted by the cleanup job. You can either Re-run the Transaction from the last failure stage or upload a new file to Re-run the Transaction. You can only Re-run the parent Transaction in case of Post Process Transactions.
	: Displays the detailed logs of the process flow (running in the background of Adeptia Connect, that is, in the Developer's Studio). It also displays the activities used in the process flow that is executed to process the Transaction.
	: Displays the list of repository files created during execution of the Transaction or process flow.
	: Displays the log details of the activities used in the process flow to execute the Transaction.
	: Displays the value of the context variables used in the Transaction or process flow.

When a transaction is in running state, you get two options to terminate it. At any time, you can Kill or Abort a transaction.

Abort: This action aborts the transaction instantly whenever the execution of currently running service is complete.
Kill: This action hard kills and terminates the transaction on the currently running service.

Trigger

This section displays the details of the Transactions that are either fetching data, are queued, have not found any data, or have stopped due to an error while triggering.

The below table lists the description of the fields.

Field name	Description
Transaction	Name of the Transaction.
Template	Name of the Template used for creating Transaction.
Partner	Name of the Partner for which Transaction is executed.
Type	Type of Transaction whether App Inbound or Outbound or File Inbound or Outbound.
Previous Run	Date and time when the Transaction was last executed.
Next Run	Date and time when the Transaction will execute next.
Status	Status of the Transaction - Running, Queued, Fetching, No Data, and Stopped.
Last Execution Status	Status of the Transaction when executed last.
Action	History of the Transaction when triggered last.

Channel

This section displays the details of SAP logs that are generated while sending files from SAP Client to the server.

Field name	Description
Created Date	Date and time when the log is generated.
TID	SAP Transaction ID.
TID Status	Status of TID - EXECUTED or CONFIRMED. EXECUTED: SAP Client sent an IDoc file but server fails to receive. CONFIRMED: SAP Client sent an IDoc file and is received at the server.
IDoc Number	IDoc number.
IDoc type	Type of IDoc.
Sender Name	Name of the sender.
Receiver Name	Name of the receiver.
Status	Status of IDoc file - SENTANDCONFIRMED and FAILTOSEND. SENTANDCONFIRMED: IDoc file received at the server. FAILTOSEND: IDoc file not received at the server.
Error	Displays error details for FAILTOSEND status only.
Download	IDoc file sent or received.

Control buttons on Dashboard

Control buttons	Description
	Refresh the Dashboard screen.
	View all executed Transactions.
	View only aborted (error) executed Transactions.
	Displays all transactions and EDI and EDIFACT Interchanges and Messages.
	Search a specific Transaction.

Default view log

You can change the default view of the dashboard as per your requirements. This means that you can change the default All Messages view to any other view, for example, Transactions view.

Click here to understand how to change the view.

AIMap logs

This section displays the logs related to AIMap where the details like low confidence, medium confidence, and high confidence suggestions are listed for source and target layouts.

EDI Reports

Adeptia Connect generates the following types of EDI reports for you to refer. You can access these reports from the dashboard tab.

Duplicate Check
This report contains information about Duplicate Inbound EDI files received.
Missing SAP IDOCs in EDI
This report contains information about Adeptia processed inbound EDI files and SAP that did not create IDOC.
Missing EDI Documents in SAP
This report contains information about SAP IDOCS that did not get processed in EDI.
EDI Stuck Documents
This report contains information about EDI documents that are stuck in the queue.

Some of the action that you can perform on the EDI Reports page are as follows:

You can download these reports in an excel format by clicking . It downloads only the logs showing on the current page.
For rest of the logs, you need to navigate and download the report page by page.
To refresh the EDI Reports page, click .

You can also perform a search for a specific report by using the Quick Search option. The Quick Search feature looks for the keyword in the columns for respective reports as listed below in the table:

Report Page	Column
Duplicate Check	Partner Name, ISA CONTROL, ORDER #, MEMBER ORDER, EDI FILE, and IDOC.
Missing SAP IDOCs in EDI	Partner Name, EDI TYPE, ISA CONTROL, ORDER #, INVOICE #, DOC REFERENCE, B2B STATUS, EDI FILE NAME, and IDOC.
Missing EDI Documents in SAP	IDOC TYPE, IDOC #, RECEIVER, and IDOC STATUS.
EDI Stuck Documents	EDI TYPE, ISA CONTROL, DIRECTION, PARTNER NAME, EDI FILE PATH, IDOC FILE, EDI FILE, IDOC, and STATUS.

You may be interested in...

Browser not supported