Versions Compared

Version Old Version 1 New Version Current
Changes made by

Akash Kumar Jaiswal

Akash Kumar Jaiswal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

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 Image Removed on the home page to open the Dashboard page.

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

  • aDashboard (Image Removed): 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.
  • aDashboard (Image Removed): This section displays the details of the Transactions that have triggered successfully but may or may not have been executed successfully. 

  • aDashboard (Image Removed): 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.

  • aDashboard(Image Removed): This section displays the details of SAP logs.

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.

Image Removed

You can also view the EDI and Non-EDI Transactions detail from the Overview section displayed below the graphical chart. Click the appropriate tab to view the details.

Transactions Tab Details

Image Removed

...

EDI Transactions Tab Details

Image Removed

...

 

 

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.

...

Transactions

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

Info

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 Image Removedto view only aborted Transactions.

Image Removed

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 Image Removed. 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.

Image Removed

The following table lists the description of the fields.

...

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. 

Image Removed: Successful execution of the Transaction.

Image Removed: An error in the execution of the Transaction.

Action

...

Image Removed: View details of the execution. Execution status is displayed graphically.

Image Removed indicates all the stages of the Transaction execution have been processed successfully.

Image RemovedImage Removed

Click Image Removedto view the execution details.

In case of an error, the status is displayed with the cause and fix of an error.

Image Removed

Click Image Removedto view the error details.

...

Image Removed: 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.

Image Removed

You can only Re-run the parent Transaction in case of Post Process Transactions.

...

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.

Image Removed

The below table lists the description of the fields.

Field NameDescription
TransactionName of the Transaction.
TemplateName of the Template used for creating Transaction.
PartnerName of the Partner for which Transaction is executed.
TypeType of Transaction whether App Inbound or Outbound or File Inbound or Outbound.
Previous RunDate and time when the Transaction was last executed.
Next RunDate and time when the Transaction will execute next.
StatusStatus of the Transaction - Running, Queued, Fetching, No Data, and Stopped.
Last Execution StatusStatus of the Transaction when executed last.
ActionHistory 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. You can also filter the data to view logs of either last 30 days or last 7 days.

Info
You need to configure the value of the abpm.EDI.logRetainTime property in the log-cleanup.properties file (.../<AdeptiaInstallFolder>/ServerKernel/etc) to view execution details of either 30 days or 7 days. By default, the value is set to 5, therefore, you can only view logs of last 5 days only irrespective of the option selected as Last 30 days or Last 7 days.  

Image Removed

...

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.

...

Status of IDoc file - SENTANDCONFIRMED and FAILTOSEND.

SENTANDCONFIRMED: IDoc file received at the server.

FAILTOSEND: IDoc file not received at the server.

...

Icons/Buttons on Dashboard

...

The information about the process flow and the activities are stored in the logs. There are three levels of logging:

  • ERROR: This is the minimal setting. This is the default log level selected during the process flow creation. This indicates that in the Process flow log, messages of ERROR level are logged by default. The following message types are logged:
    • SEVERE errors are the ones that cause premature termination.
    • ERROR and FATAL type messages deal with other runtime errors or unexpected conditions.
  • NOTICE: The NOTICE log level captures all the notable events in the application including the error messages. For example, the Cluster and Queue Processor component log messages at the NOTICE log level. 
  • INFO: This is the typical setting. By default, logs of INFO level are logged in the log database. The following message types are logged:
    • All messages as defined in the ERROR category.
    • Warning (WARN) messages such as runtime situations that are undesirable or unexpected, but not necessarily "wrong", are logged.
    • All Process flow Start and End messages.
    • Detailed information about each process flow and activity details (INFO) are logged such as start and end time for each activity/module/node, number of records processed, etc.
  • DEBUG: This is the most detailed setting. It is expected that you want this level of detail for tracing errors and troubleshooting. The following message types are logged:
    • All messages as defined in the ERROR category.
    • All messages as defined in the INFO category.
    • Detailed messages for each module, activity or node as it is executed including trace messages and flow information.
    • Display of Process flow global variables after end of every activity.
    • Any other information that may be helpful in debugging.

Access Control to Logs

Log information that is displayed in the logs is not filtered as per the user's permissions. Every user with the minimal read permissions can view the logs. Only the logs specific to the user's group are displayed to the user. A user cannot view log information for other groups.

The logs are classified into four categories:

  • Viewing Audit Trail Log
  • Viewing Event Log
  • Viewing System Log

  • Viewing Process Flow Log


Panel
borderStylesolid
titleYou may be interested in...
What's new
Best practices
Training guides
Frequently asked questions
Adeptia Connect APIs
Adeptia security report