Maintaining Status and Entitlement Models

In SAP Entitlement Management, a status model is a framework that defines the various stages or statuses that an entitlement goes through during its lifecycle. It includes the different possible states such as pending, approved, rejected, processed, and more. The status model tracks and manages the progress of entitlements, ensuring that they are processed efficiently and in compliance with business rules and regulations.

Let’s take a closer look at status models. Watch the following video to get started.

Let's create a status model. Watch the following video to get started.

After creating a status model, you can copy, edit, or delete it using the buttons in the footer toolbar. Watch the following video to see how.

Now that we’ve created a status model, let’s move to assigning attributes to an entitlement model.

The Attribute Value Lists and Attributes options define the specific criteria and characteristics of an entitlement in SAP Entitlement Management.

Let's take a closer look. Watch the following video.

The Defined Data Types can be one of five types:

• Boolean
• Date
• Decimal
• Integer
• String

The following value lists are predefined and delivered with the Entitlement Management system. Note that you cannot edit the existing data in these value lists, but you can add more values to the list:

• Business Category
• Distribution Channel
• Provisioning Route
• Right
• Unit

An entitlement model in SAP Entitlement Management is a framework that defines the rules and criteria for determining what entitlements or rights a customer or user has to a specific product or service. It includes the terms and conditions, pricing, usage restrictions, and other parameters that govern the entitlements. The entitlement model is used to manage and enforce entitlements and is configured to meet the specific needs and requirements of a business.

Next, let’s see how an entitlement model is created. Watch the following video.

Note: You can edit the values of an existing entitlement model with the following restrictions:

• If an entitlement model is not used by any configuration, you can change all attributes except the entitlement code and the category of the entitlement model.
• If an entitlement model is used in a configuration or Background Job/Event condition, but no corresponding entitlement records are generated in the repository, you cannot perform the following tasks:
  • Change the entitlement code.
  • Change the entitlement category.
  • Delete an attribute if used in any configuration.
  • Select or deselect the device-dependent checkbox.
  • Change supported licenses.
  • Change the entitlement quantity.

  You can change the status model, but the new status model must contain all transitions and initial status from the earlier status model.

• If the corresponding entitlement records of the entitlement model are generated in the repository, you can only change the expiration date, entitlement quantity, and add an attribute. You can also change the status model, but with the conditions previously specified.

We’ve had a chance to create and maintain the status of an entitlement model and define entitlement attributes. In the next lesson, we set up a consumption form to track usage.