Is it okay to create a Software Entitlement before a Software Model?

[nagaryu]

We are currently testing SAM Pro and M365 integration, and I am also learning about SAM myself.

However, because testing takes time, the customer has requested that we postpone the introduction of SAM and first create a system for license usage applications in Catalog Item.

Because there are a large number of "product records" to select on the application screen, we are considering creating records in a custom table and allowing the product to be selected in the Reference type field of Catalog Item.

However, if we decide to introduce SAM Pro in the future, we think that the product record will probably be equivalent to a Software Entitlement (alm_license), so we are considering changing our approach and "just installing SAM Pro, and setting the reference destination of the Reference type field of Catalog Item to alm_license."

So, first we tried to manually create a record in the alm_license table.

Then, when we pressed the "New" button and entered the PPN number, the record was automatically set in the Software Model.

When I checked the Software Model table (cmdb_software_product_model), I found that dozens of records had been automatically created with the same date and time that I entered the PPN number, and with my name in the Created by field.

I think the Software Model record corresponding to the PPN number was probably created by referencing the Content Library. (Please let me know if I'm wrong.)

So here are my questions.

<1>
Is it okay to physically delete unrelated records from the automatically created Software Model records?

<2>
I think the correct order is to create the Software Model first, and then create the Software Entitlement, but in this case, I'm thinking of "first creating the Software Entitlement with Easy Import and deleting the automatically created unnecessary Software Model records," and then "normalizing the data so that it is correctly mapped to the existing Software Model when SAM Pro is fully operational and information is retrieved through M365 integration." I would like to know if this method is possible, or if it is not recommended because there is some fatal flaw.

*I haven't learned much about normalization yet, so I plan to learn about it in the next phase.

＜3＞
When I manually created an alm_license record, the following message was displayed in a yellow band.

You are creating an entitlement for a subscription product that has no integration profile defined. You will not be able to track usage activity or reclaim stale subscriptions.

The following Community article applies to this message.

https://www.servicenow.com/community/sam-forum/i-am-current-getting-this-banner-when-i-create-entitlement-has/td-p/1302015 

So I checked the samp_sw_subscription table and found that there are currently no records.

I imagine that in the future, when the M365 integration is implemented, records will be automatically created, but if they are automatically created, will this yellow message disappear and the table will be able to be used correctly?

I apologize for asking so many questions, but I would appreciate your help.

[andynewey]

I am still a noob but here are my comments.  SN advised us not to have automatically create software model switched on as it is meant for mature Sam Pro instances.  We have a lot of models without products, discovery maps etc.

Also the 365 integration only show allocated licences so if you want to see your whole entitlement. You need to devise a workaround.

[nagaryu]

Wow, I see you gave me that kind of advice.

I thought that if I could set up M365 integration, the data would be automatically created neatly, but that's not necessarily the case...

Thank you for the information.

[dreinhardt · Accepted solution]

Hi @nagaryu,

<1> 

It's not recommended. The additional created models are based on the content library details for suite components and downgrade rights related to M365 products and suites. It's by design, created entitlements based on PPN or software models created based on DMAP will trigger actions to create additional objects based on the content library.

<2>

For SaaS integrations the recommended way is to enable the SaaS integration, thus will auto create all required software models and last step is the entitlement onboarding.

For standard publisher onboarding, it's recommended to start with the entitlements & PPN's, as this process will also auto create all required software models, suite components & down grade rights

<3>

Correct, as soon the SaaS integration is up and running, all the user subscriptions details will be available in the mentioned table and linked with the software models to be included into the reconcile as part of the license balance calculation

Best, Dennis

[nagaryu]

Hi @dreinhardt ,

Thank you for your answer!

<1>
I see, so the records created are correct. I was surprised that the number of records suddenly increased, but if they are correct, I will not delete them and will leave them as they are.

<2>
I am not yet integrating with SaaS, so for now I will start by creating a Software Entitlement (alm_license) record using the PPN number.
I downloaded the template in Software Asset Workspace, entered the PPN number and tried to import, and the information was generated correctly from the PPN number and an alm_license record was created.

<3>
Thank you. I'm relieved.