Defining and Monitoring Entitlement Events

In the previous unit, we used the Define Background Jobs app to set up and manage multiple tasks to run in the background. Now that we have set up and reviewed entitlements, let’s explore the creation of entitlement events.

The Define Entitlement Events feature within the EMS allows organizations to track key actions related to their entitlements. Organizations can specify any number of events that they want to monitor.

For example, when a user's entitlement to a particular software is about to reach an activation date, an event is triggered to send a notification to the provisioning team. Conversely, when a particular software is about to reach an expiration date, an event is triggered to notify sales or the customer to start a renewal. Or an event can be set for cloud storage where a remaining balance of less than 10 percent also prompts a notification. Entitlements for licensing and hosting services that have been activated or canceled can have events that automatically change the relevant associated entitlement needs.

Let’s go inside the Define Entitlement Events app.

In SAP Event Management System (EMS), the Monitor Event Logs app is used for tracking and monitoring the event logs in your system. This tool provides a comprehensive overview of all events that have occurred within the system.

Once an event is created and event detection is turned on, the system captures the triggered event. To see the list of triggered events, choose the Monitor Event Logs tile in the Operations section of the Entitlement Management launchpad. By default, the list page contains all events which send out notifications. Select the arrow beside Send Notification to switch to the list of events which triggers the entitlement update.

Events are triggered differently depending on their defined Raised When setting. For Raised When status of Entitlement Saved and Consumption Saved, the corresponding event is triggered once the record is saved and the saved data matches the Relevance event condition. For Raised When status of Entitlement Becomes Valid and Entitlement Becomes Invalid, the corresponding assigned background job compares the entitlement Valid From/Valid To dates with the Job Execution date and then triggers the corresponding event that matches the Relevance condition.

For each event, the following fields are displayed:

• <Trace ID> - the ID of the triggered event instance.
• <Event Name> - name of the event.
• <Event Type> - the corresponding event type.
• <Event Time> - the time the event was triggered.
• <Document Number> - entitlement number or entitlement number combined with consumption serial number, which triggers this event.
• <Update Status> - indicates whether the update is successful; possible statuses are Successful, Failed, In process, or Partial Success.
• <Update Detail> - the list of entitlement to be updated and their update statuses with messages.

To view full details of an event, select the Event Name. From the event details page, choose Edit to make any desired changes.

Let’s look at an actual event log page.