SAM - Regarding entitlement import process

[Priya Bonam]

I got the entitlement data to import into the software entitlements. I have verified that a few publishers and products are not there in my current respective tables. Should we need to create them before importing the entitlements? please confirm.

Also, for given data, if no existing software model (based on 4 or 6 important fields) is available to populate automatically, what needs to be done?  

Also, if the import is a success then normalization and reconciliation will be done through jobs per my understanding. If discovery models are not normalized, in what cases can I manually normalize them? and what will be the best approach for this?

Please share any useful information if I am stuck with import entitlements, normalization, and reconciliation of non-compliant issues to resolve.

Please let me know if any Business rules, Scheduled jobs, etc I should refer to for this entire process.

who manages the content library? if our product with a publisher is not listed in that library to normalize against discovery values then what needs to be done?

Please clear my doubts and thanks in advance.

[Srinivas Ramanu]

Hi

Usually when you import entitlement, one of the most important attribute that is required is PPN (Published part number), ensure that it is there on the entitlement import template. This should automatically create software models. 

Once imported, do check if the entitlements are in published state. Only entitlements that are published are considered for reconciliation.

Discovery models are automatically created from software installations. Hence ensure that software installs are created that means Discovery has run for the same. Software Normalization, also works automatically, if some Discovery models are not normalized you can normalize them manually / or opt-in to send those discovery models to ServiceNow.

There are many questions , tried to answer few of them. Thanks