<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Software License Management > Licenses > Upgrades > How Upgrades are handled by Consolidate > Managing Licenses

Consolidate handles new upgrade licenses that are being presented, either through the Manage Licenses screen or via the ASN processor.

The following rules are followed:

1.  The staged record will be processed only if there are sufficient number of existing qualifying licenses.  Otherwise, Consolidate will mark the staged record as an exception.  Qualifying licenses are the licenses necessary to qualify for the upgrade, and each upgrade license must consume a qualifying license.

2.  The market price for the upgrade title, not the MSL title, will be used in the license cost threshold test (as defined by system setting SLMASNPriceToMarketPriceTest. If the ratio of the purchase price being reported to the market price as defined in the upgrade record falls below this setting, the staged record will be marked as an exception.  Note, however, that the qualifying license count will have already been decremented, leaving an "owned" position of fewer qualifying licenses but no new upgraded licenses (until the exception record is cleared).

3.  Qualifying licenses from the highest family member (usually this translates to the oldest version) are consumed first, followed by the next oldest, and so on.

4.  License "swapping" for upgrades (consumption of the qualifying license and incrementing of the linked MSL license) is performed prior to any license allocation.

5.  If any constraints were specified when establishing the upgrade definition in the MIE (such as requiring that the upgrade license be purchased off the same contract as the qualifying license), those constraints will be imposed as the MIE chooses qualifying licenses to consume.  If one or more constraints are specified, and a license that would otherwise be used as a qualifying license does not match the defined constraints, then the qualifying license will not be used.  

NOTE:  When assigning constraints, it becomes very important to ensure the value(s) on which the constraint depends are present on both the license record and the upgrade record (usually both being sourced by the ASN Processor).  Spelling must match precisely or the qualifying license will be ignored.  Failure to carefully attend to sourcing the correct information, spelled correctly, will cause upgrade licenses to be cast as exceptions and not honored.