SAM Pro and Creating asset for Perpetual+Maintenance record after first year renewal

FR-Canada
Giga Contributor

There are 65 different asset records.  Do I have to create 65 Maintenance record after first year renewal?  And every year after that?

 

Thank you

3 REPLIES 3

dreinhardt
Tera Sage

Hello @FR-Canada ,

it depends on your maintenance renewal entitlements. For both options, you've to do these steps for each renewal.

 

Option 1: Per current software entitlement you've received a single maintenance record, the answer is yes - you've to create and link each of the 65 maintenance entitlements  to a base license

 

Option 2: You've received a single maintenance record covering the amount of the existing entitlements, the answer is no - you've create a single maintenance entitlement and link all base licenses to this.

 

Software license maintenance (servicenow.com)

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

FR-Canada
Giga Contributor

Thank you Dennis for looking into this.  This is about Oracle and one Service Contract has 65 different assets and I understand to create on Maintenance record but not sure how to link all 65 assets to this one Maintenance record.  Related Entitlement tab won't let me to link all these 65 to this one record since they are all different products.  I am sure the right way is to create 65 different Maintenance record and link every one Perpetual + Maintenance to this one record but it takes lots of time doing with each renewal every year.  This SAM Pro approach works perfectly with other simple desktop installation software but not with Oracle server licenses and its components.  Thanks again.

dreinhardt
Tera Sage

Good to know about the "one Service Contract" case. Starting Oracle onboarding for a customer within the next weeks. You have already formulated the solution yourself, the creation of maintenance entitlements per product is necessary. Depending on the customer's requirements for mapping entitlements and maintenance, you might also consider the following approach:

 

Link all Oracle entitlements to the latest service contract and update the end date based on the contract end date  for all linked "Perpetual + Maintenance" entitlements. This way would be pragmatic, but you lose the transparency of the individual extensions + additional effort if certain products are not renewed.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.