<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Software License Management > Licenses > Additional Entitlements > Owned Entitlements > Allocating Entitlements to Licenses > De-allocation Due to Date Changes

Entitlements that were previously allocated to licenses may be de-allocated if the start and end dates of the entitlement owned position are changed or updated.  If the start date of an entitlement owned position is changed such that it now falls outside a range of plus or minus the number of grace days allowed between license purchase and entitlement purchase (start), it will be de-allocated.  The grace days allowed is defined in the Entitlement Definition, but defaults to 30 days.  As an example, if at one time an entitlement owned record had a start date of 8/1/2015, and that caused it to get allocated to a license that was purchased on 7/30/2015, if later the start date of that same owned position got changed to 6/28/2016, or to 9/1/2016, the entitlement will be de-allocated from the license (assuming the grace days setting was set to 30).  This is because the time between the license purchase and the entitlement start is outside the allowed number of days. 

 

In addition to start date change, if the end date of an entitlement owned position is changed such that it now occurs before the purchase date of any license to which it has been assigned, it will be de-allocated.  This seems obvious, but in this case the entitlement was no longer in force when the license was purchased, so it could not have been eligible to have been allocated.

 

In any case, if an entitlement is de-allocated from a license, and if, during the time it was allocated it caused one or more license migrations, then the next Consolidate run to occur (after the entitlement de-allocation) will cause the reverse migration of those licenses.

 

Licenses that have entitlements de-allocated still remain eligible to have different owned positions allocated to them.