Can you explain further the need/importance of using an Asset Tag on software entitlements?

[ritahester]

The client has made a request that we discontinue using asset tags when loading software entitlements. I was unable to provide a solid reason for continuing to use them. 

I have read the Community posts: Best practice documents on creating a unique Display name on the Software Entitlement record & What's the criteria to have multiple entitlements with same software model in SAM ? In the latter article, you stated, "However, it will be a concern when looking up Software Entitlements from other tables or when assigning allocations during execution of the Request Workflow." Can you go more in depth on this? 

There have been some entitlements that have been loaded without the asset tag; what issues will we experience because of this?

[Alex Panzarella · Accepted solution]

Asset Tags are an optional means of maturity. Asset tags don't have an impact on the license compliance logic, but could make it easier to track and maintain entitlements.

The asset tag makes an individual entitlement unique and easily referenceable.

[Daniel Slocum]

@Alex Panzarella gave you a strong foundational answer. I'd like to add a little more color with a couple of specific use cases where having an Asset Tag value is helpful.

1. When allocating entitlements through the Sourcing Task in the procurement workflow having asset tags populated will allow you to easily identify the Entitlement record you wish to allocate from. Without the asset tag, all entitlements for the same software will look the same.

2. When upgrading entitlements, having an asset tag value will allow you to easily choose the original purchase you are upgrading from. Again, having an asset tag value precludes entitlements for the same software from looking the same in lists.

[Scott Halverso1]

To build on what Alex said, we frequently use them when you need a way to distinguish entitlements from each other when companies are managing entitlements at a lower level than the enterprise.  E.G. The enterprise purchases 25,000 Office 365 subscriptions, but needs to track/allocate at a more granular level (business unit, cost center, agency, department, etc....) When looking at a list view it's helpful to be able to have a column to give additional meaning.

Other times we see it used as a way to correlate a reference back to a statement from the reseller the license/entitlement was purchased from.

Bottom line the field is frequently treated as an out-of-box field to use however.