Intoduction
Many actions create events in DOKA
e.g. completion, rejection or error. These are stored in the system and can be checked and displayed for the following types:
Bolero
Download
Incoming Messages
Messages
Local Print Request
Pending Item
Service
System
Transaction
A time range, text, user ID and/or status can be selected or entered. Depending on the nature of the selection all relevant events are displayed. In particular, this feature enables the user to analyze error codes and more detailed information regarding the event requested.
Transaction DBMEVT
If a problem or an error occurs while working in the application or with a background manager, these will be logged as events. One error, one error event. The error events cause the Watchdog to report the entire system as faulty, even if the problem has already been rectified.
The transaction DBMEVT can be used to mark these events as having been handled. The Watchdog will then ignore those events marked as handled and will no longer report the system as faulty.
Event Information-Transaction INFEVT
A search panel will be displayed allows you to filter on Type, Time Range, Text, User ID, and Return Code. All events fitting the selection criteria are displayed in a selection list. Select one to view more details on the contract. This detailed information consists of all data stored on the event selected.
Follow the below GIF to view the events created
A good example of this would be to check the incoming daily exchange rates if they are being handled by IMPTSK.
Filter on the Text "IMPXRT" and it shows those events with that in the text.
Clicking on one , will display the details, including the log , which can itself be viewed from here
Comments
0 comments
Please sign in to leave a comment.