Tracking EBICS transactions

EBICS Client generates events that are related to orders. All events are predefined and metadata is populated in the system. A user cannot define the events. The events are logged against an order ID and there are no stand-alone events in EBICS Client.

Users can search for events and view the event details related to orders on EBICS Client dashboard interface based on one of the following or a combination of the following parameters:
  • Search location: Live tables, Archive tables
    Note: Recent orders are stored in live tables and archived orders are stored in archive tables.
  • Event start and end date
  • Event start and end time
  • Event type: All, Info, Warning, Error, Critical
If an EBICS Client admin invokes the search, events related to all the orders in the system are displayed. If an EBICS Client user invokes the search, events related to self submitted orders are displayed. The search result is displayed in a tabular format and can be sorted in an ascending or descending order. The search result can also be refreshed periodically by specifying a time interval to display the updated list of orders. You can click the required event ID link to view complete information about the event. The Event summary details page is divided into two sections: Event details and Order details.
The Event details section provides the following information about the selected event:
  • Event code
  • Event name
  • Description of the event
  • Event type
  • User ID
  • Timestamp
The Order details section provides the following information about the order associated with the event:
  • Order ID
  • Order type
  • Document (Clicking the document icon displays the payload document)
  • Partner name
  • User ID
  • Bank ID (Host ID)

Event Types

Events are classified as follows:
Provides information about events. For example, Encryption successful.
A warning message. For example, order received with warnings.
An event indicating an error condition. For example, delivery to bank failed.
An event indicating a critical condition. For example, the EBICS Client database is not functioning.