Modules > Asset Management > Software License Management > Licenses > Additional Entitlements > Owned Entitlements > Establishing Owned Entitlements through the ASN Processor

The Advance Shipping Notice (ASN) Processor may be used to add to your owned entitlements. When an MSL title has been added to an Entitlement Definition, then that MSL title will be visible in the Master Catalog of the ASN Processor. Individual ASN items can then be matched to that Entitlement and pushed up via the ASN Processor. Additionally, for ASN line items that are both a license and an additional entitlement, such as "Office 2010 w/SA", a single ASN item can be matched to both the license and the optional entitlement entries in the ASN Processor's master catalog.

When owned entitlements are created, or updated, via the ASN Processor, the start date, end date, and term of the owned entitlement will be established using the associated Entitlements Definition record's settings. (See exception below) If those settings are changed and the ASN is pushed up again, the existing owned entitlement record will be updated with new start date, end date, and term, if the underlying definition record's settings cause a change.

Exception: The ASN Processor does allow you to specify a start and end date for any given ASN line item that you match to an entitlement. If you specify the entitlement start and end dates in the ASN Processor, that information is transmitted to the MIE on an ASN line item by line item basis. When those line items are processed by Consolidate, and loaded into the Entitlements Owned form, the establishing of the actual start and end dates of the owned entitlement will be performed as follows:

1.If the Entitlement Definition controlling the incoming owned entitlement position has been set to cause the start date of the entitlement to start the same as the linked contract, and the contract exists and there is a defined start date for that contract, that start date will be used as the start date of the entitlement owned record.

2.Otherwise, if the Entitlement Definition has a hard start date set, then that will be the start date of the owned entitlement record.

3.Otherwise, if the Entitlement Definition has been set to start on an anniversary date and a term has been specified, then the start date will be set to the closest anniversary date.

4.Otherwise, if the incoming ASN record has an entitlement start date specified, then that will be used as the start date.

The end date will be determined as follows:

1.If the start date ended up being used from the incoming ASN record, then the end date will also be used from the incoming ASN record.

2.Otherwise, the end date will go through the same hierarchy as the start date (first level will be the contract end date, then a hard date, then a calculated end date based on anniversary)

Once those dates have been determined. If they differ from the dates currently set, the current dates will be updated to the new dates. This means if an entitlement definition is changed and an ASN is re-processed, it may cause the start and end dates of existing owned entitlement records to be changed.

If, in all cases for a given entitlement definition, the ASN records will be used to specify the start and end dates of the individual owned position records, then the overarching Entitlement Definition must be set in such a way as to not cause the MIE to calculate the start and end dates based on it (turn off start same as contract, do not specify a hard date, and do not specify an anniversary date and term).