Navigate to License Manager > Manage > Manage Licenses > Import and Qualify.

The user should review their entitlements after they have added them to ensure that they were added correctly and that they are fully qualified with a percentage of 100. Only fully qualified entitlement records will be processed.

Be sure to pay attention to the qualification percentage next to each license record. Only 100% qualified entitlements are included license position calculations.

To qualify licenses:

1. Select the entitlements that you want to qualify.
2. Click the Qualify Licenses button.
3. Select Manually.

If the user Selects the Manual option then the Entitled Details Qualification interface will then appear. The user can select entitlement record(s) in the top half and enter Product Data and License Data for that record(s). Clicking Update with this information filled out will update that record(s) with the information entered by the user. A user can locate under-qualified records and update them to make them fully qualified for the License Position Calculation.

The user also has the option to not include the entitlement in the calculation regardless of the information entered by un-checking the Include in calculation check box.

LED records must be 100% fully qualified in order to be included in the License Position calculation. 100% qualification means that values for the following fields have been specified:

1. Licensed Software Product Version (LPV): The Manufacturer, Product, and Version fields are required for a fully qualified entitlement. Although it is not shown, the Release Date for the Licensed Software Product Version is crucial for processing of LED records into License Position. Release Dates coupled with Coverage Start/End Dates determine Entitled License Version for a product which determines what version upgrades can be applied.
2. License Metric: License Metric qualification requires License Rules with a matching metric for Licensed Product (SPV). In the case where a License Rule does not exist, a new License Rule can be specified for an SPV via the UI.
3. Normalized Product Type: The Product Type is necessary for determining how the entitlement is processed during the license position calculation.
4. Usage Country: Licensing rules can be different for each country, so it is important to specify the usage country for an entitlement.
5. Entitlement Quantity: The number of license units is is necessary for the license position calculation.
6. Coverage Start and End Date: Coverage Start/End Dates are required even if no coverage exists. If there is no coverage, then dates should be set to same value such as purchase date or import date.

Optional Fields:

• Link to Agreement allows for entitlement transaction linking to an enrollment agreement which serves as the record of proof for the source of the license entitlements.
• Organizational Designator can be customized in your instance to allow for additions sub-catigorization of entitlements to specific Regions, Departments, etc. This impacts how transactions are grouped for the License Position Summary calculation.
• Notes can be added for specify any relevant free form data about the entitlement transaction. These notes are preserved on the Current License Position as well.

• License: A perpetual license for a software product with no maintenance coverage.
• License with Coverage: A license that includes a specified coverage period for the active enrollment period. Start/End Coverage Dates are required.
• Subscription: A term license. The right to use the software expires on the Coverage End Date and any past subscriptions are excluded from the License Position Summary calculation. Start/End Coverage Dates are required.
• Coverage Renewal: Software maintenance coverage extension. This type of entitlement transaction extends the maintenance coverage for a License with Coverage transaction that is within the coverage renewal tolerance period. This period can be specified when submitting the License Position Summary calculation and is defaulted to 60 days.
• Version Upgrade: An upgrade of a base license to a more recent version. The exact version may be dependent on the Coverage End Date.
• Edition Upgrade: An upgrade to a base license that changes the edition of the software product covered by the license. The version may also change depending on the Coverage End Date.
• No Entitlement: An entitlement record that carries no actual entitlements. For example, software delivery such as disk kit or electronic.