Table

How used

dataEntitlements

This is the primary table used to track entitlement definitions.

dataEntitlementsOwned

This is the primary table for tracking the owned position of a given entitlement.  A link is maintained back to the dataEntitlements table.  The owned position is derived by taking the ASNCount and subtracting UnitsToReturn.  LicensesMigrated keeps a top level count of any licenses that have been migrated, either through the portal or due to automated license migration.  UnitsAllocated is a count of authorizations that have been upgraded due to optional entitlements.  UnitsAllocatedEnterprise is a count of authorizations that have been upgraded due to enterprise entitlements.  ASNCount-UnitsToReturn-LicensesMigrated must be greater than 0 for any licenses to be migrated due to this owned record.  ASNCount-UnitsToReturn-UnitsAllocated-UnitsAllocatedEnterprise must be greater than 0 for any authorizations to be eligible for upgrade due to this owned record.

For return records (where owned position is being returned), if a matching owned record can be found, then the owned record that matches will be updated as follows:

UnitsToReturn will be set to the absolute value of the ASNcount in the return record.

EntOwnNoReturn will be set to the return records EntOwnNo value (to show the match back to the return record)

The return record will be updated as follows:

UnitsReturned will be set to the value that UnitsToReturn was set to in the owned record.  Basically, the return record's UnitsReturned will equal the owned record's UnitsToReturn value upon successful processing of the return record.

dataEntitlementsExercised

This is the main tracking table for entitlements that have been exercised.  There are three actions that may be taken when exercising an entitlement (ExActNo): 1-migrate the license, 2-unmigrate the license, 3-upgrade an authorization with possible migration of sufficient licenses.  Every exercise event is recorded in this table.  For license migrations, there will be one record for every license record (one-for-one with the ATdataHarvestedSW table).  This table maintains the primary audit source for determining how entitlements have been used.

dataEntitlementsXHarvSW

This is the primary table that tracks how an owned entitlement has been allocated to a license.  There may be more than one owned entitlement assigned to the same license (especially as new owned position comes in to renew expiring owned position).  This table will maintain a pointer to every owned entitlement position that was ever assigned to the license (with some exceptions – those exceptions being if the entitlement was formally de-allocated at any point.)  This table also maintains the date of last successful migration for this license.  The entitlement allocation logic in Consolidate is the primary maintainer of this table.

ATdataHarvestedSW

When a license is migrated, this table will have the mslNoHarvested set to the upgraded mslNo, the mslNoHarvestedOld set to the previous mslNoHarvested, the EntOwnNo set to the owned position record, and Description set to the description of the new license version.  When a license is un-migrated, this table will have the mslNoHarvested set to mslNoHarvestedOld, mslNoHarvestedOld set to mslNoHarvested, and EntOwnNo set to the negative value of the owned position pointer.  A negative EntOwnNo is an indicator of license records that have been un-migrated.  When an authorization is upgraded, all records in the harvested software table that point to the authorization record being upgraded will have their mslNo column updated to the new mslNo (to which the authorization is being upgraded).

ATdataAssetsXManagedSW

When an authorization is upgraded, this table will have the mslNo set to the upgraded mslNo, the Description set to the description of the new title, and the EntOwnNo set to the owned position record.  If the entitlement is exercised from the Gen II SRP (or anywhere the "push" flag is set), the DateApproved column will be updated to the current server date/time, and the DateDownload column will be nulled (which will make the authorization record visible to the PackagesToPush view).

ATdataMSLEntitlementLog

This table closely follows the dataEntitlementsExercised table in that a record is created whenever an entitlement is exercised.  One difference between the tables, however, is that this table will have only one record created in the event several records in the ATdataHarvestedSW table are impacted, whereas the dataEntitlementsExercised table will have one record for each record affected in the ATdataHarvestedSW table.  A link is maintained between this table and the dataEntitlementsExercised table.