| # Events (tlbct5530m000) Use this session to view the events that are in the queue to be published from LN. If the history is kept, you can also view processed events. This session can be started from the Event Subscriptions (tlbct5500m000) overview and details session only if a subscription is selected. If the porting set does not support BLOBs, the session cannot be started. Therefore, it will also be invisible in the Event Subscriptions (tlbct5500m000) session. The session provides an overview of the messages that are in the queue to be published. If event history is switched on, the events that were already processed, either successfully or unsuccessfully, can be viewed. Note the following: If the application transaction that triggered the event is aborted, the event will not be visible because the publishing of the event will also be aborted. Audit-based events not triggered directly from the application using PublishEvent or a ShowAndPublishEvent method– but derived from database actions on the application data– are not monitored. Note If many events exist, the user interface responsiveness will decrease. The reason for this is to optimize the runtime event publishing; the events table has only one index or a few indices. If the event does not have the status ‘To be Published’, an event message might be unavailable; this depends on the event history configuration (refer to the online help of the Event Publishing Settings (tlbct5505m000) session). For Error events, if the error occurred before the actual message was built, an event message might be unavailable. For Irrelevant events, no message will be available. Fields and Commands The session displays the company and business objects from the selected subscription. You cannot change these objects. The existing events for the subscription are listed. For each event, various fields are shown. For details, refer to the Fields section. The session's appropriate menu contains various commands. For details, refer to the Form Commands section. Note You cannot use the standard Find command to search for a specific event. Instead, use the Sort by command in the appropriate menu and then browse through the list of events, or use the standard Filter command to view one or more specific events. Related topics Event Monitoring Event Publishing Settings (tlbct5505m000) Fields Company The number of the LN company from which events are published through the business object. Business Object The business object that provides the event publishing service. Event Timestamp The time when the event was stored. Note The Timestamp is an indication, and is not used for sequencing; it does not have to be equal to the commit time used in the audit trail. Event Key The identifier of the event. Note The Event Key is not a sequence number. For BDE events, the same id is included as the eventRequestID in the event message control area to facilitate traceability. Business ID The Business ID of the object instance for which the event occurred; for example, an order number or an item code. Note The Business ID is an internal identifier, which does not have to be equal to the public identifier used in the event. Values are trimmed. In case of multiple identifiers, the elements are separated using a pipeline (‘|’) character. In case of audit-based events or PublishEvent, it might be empty. The value might be incomplete because of maximum field length. Event Status The current state of the event. For details, refer to Event Statuses. Status Details Additional notes on the status; for example, to indicate that the publisher retried sending the message. Last Update Timestamp The time when the last status change of the event occurred. Form Commands Sort by Use this command to sort the events in the scope of a company and business object. You can order the events with the following: Timestamp, which is the default ordering. Event ID. Business ID, Timestamp. Event Publishing Settings Starts the Event Publishing Settings (tlbct5505m000) session. Show message Use this command to view the event message. The event is displayed in XML format in a separate window. If the event message is large, displaying it might take time and system memory; therefore, the size will be reported beforehand, and the viewing can be canceled. |