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

1. Click the Add Licenses button at the bottom of the data view.
2. Select Add Single License to enter an individual license entitlement. This will open a UI panel for entering all required and optional entitlement data.

When the user selects Manual, they are given a pop-up where they can enter the information for that entitlement record.

Now, the user has the option to add the entitlement in two ways:

1. Looking up a Part Number in Chaklun, Asset Vision's information database. If the part number exists then the normalized information from Chaklun will be entered automatically.
2. Optionally if the user does not use the part number look up then they must manually enter the details for the required fields in the top portion of the panel as well as any additional optional data including Notes.
   Start by selecting a Software Manufacturer  or Publisher, a Product, and a Product Version. Use the plus (+) button to add new Product and Versions, but make sure the Product does not already exist potentially with a slightly different name so that you don't add what amounts to a duplicate Product in your local Software Catalog.
3. License (Rule) Metric will be available for selection based on the existence of a Software License Rule (SLR) in the Software Catalog. The plus (+) button can be used to create new SLRs for a Licensable Product, but make sure you understand the product license requirements before specifiying a new rule. If you are not sure speak to your account manager for additional support. A SLR specifies a:
   Capacity Model which should always include Full-Capacity and may also include Sub-Capacity which means that a license can also be assigned directly to a Virtual Machine as opposed to only a Physical Machine.
   Detection Method which determines how the software is discovered in an environment. This is most often Installation, but could be an OS (Operating System), a Service (software is detected based on a running instance), or Consumer (a device or user consumer of a running service such as and Office365 or XenApp hosted application).
   License Metric which include Seat (physical desktop installations), Named User (a license issued to a specific user), Server (Server installation or running service), Microsoft Core (core count based license that takes Microsoft core factor into account), Core (non-Microsoft core count based license, Processor (processor count based license), Oracle Processor (processor count based license that takes Oracle processor factors into accout), Device CAL/User CAL (CAL license for Device or User consumption of a service), and OSE (catch all for any physical or virtual installation in an Operating System Environement).
   Units per SKU which specifies how many units of the license metric come with each license SKU purchased. Most license SKUs grant one unit of the license metric such as a Seat license. But others such as some Processor and Microsoft Core licenses are sold in 2-packs where each SKU grants 2 units of the license metric.
4. Product Type also known as License Type specifies what kind of license entitlement transactions the entry represents. Available options are:
   License: A perpetual license for a software product
   License with Coverage: A base license with software maintenance coverage
   Coverage Renewal: A renewal for software maintenance coverage (this type of transaction extends the coverage on a License with Coverage so it must have such a base license to be successfully processed by the License Position Summary calculation.
   Subscription: a license with a specified subscription coverage period
   Version Upgrade: a specific version upgrade that can be applied to a base License
   Edition Upgrade: a product edition upgrade that can be applied to a base License
   No Entitlement: a transactions that does not actually grant any license such as a disk kit transaction
5. Usage Country represents the country of usage for which the license was issued
6. Quantity is the entitlement quantity count of the Product/License Type
7. Include in Calculation is in part based on the "Include in Summary" field for an MLS but is also used in LM to determine if a 100% qualified transaction should be included in the License Position Calculation or not. More on this in the next lesson.
8. Start/End Coverage Dates represent the active enrollment or coverage dates for a License with Coverage, Coverage Renewal, or Subscription
9. Organizational Designtors can be customized for your instance based on a further subcategorization of licenses by Region, Departement, etc.
10. Enter Optional Data allows for entry of additional license entitlement details such as Notes, Part Numbers, and linking to new/existing Agreements

Click Save when you are done filling in the license entitlement transaction details