Setting up Oracle, diffentiating between divisions and contracts

andynewey · 3 weeks ago

Hi all, I am looking to start setting up Oracle within SAMP. We have entitlement belonging to different divisions and each division has their own contract.

Does anyone have any pointers on how to set this up correctly so each division can see their own deployments, entitlement and ELP?

NOTE: All the data gathering is setup as per steps 1 and 2 in this reply Oracle setup help - ServiceNow Community

so it should just be configuring SAMP correctly.

dreinhardt · 3 weeks ago

Hi @andynewey ,

I would recommend to take a closer look into consumption rules, this feature allows you to define and set rules based on foundation data to separate the license consumption. In the workspace you’ll be up in a single result per consumption rule, but having still one software model.

second option: running the recon with grouping, but the grouping is used for all products and could be a bit messy in the workspace.

third: with Zurich a new ELP grouping based in reconcile data was introduced and could be a low setup alternative for quick results.

keep in mind: all entitlements, servers, user, … must be assigned to the correct company, department, ….

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

MikeW0609686430 · 3 weeks ago

To answer this question, please can you outline how Oracle requires your organization to report license compliance - do they require reports by division or one report for your entire organization? If it is the latter, then Dennis' solution will work and you can assign license consumption rules to each entitlement for internal compliance (one software model). For the former, you will need to create 'duplicate' software models that represents the contract of the individual business entity/division and set software install conditions so that the model only consumes Oracle installs that are related to the specific contract.

dreinhardt · 3 weeks ago

Hi @MikeW0609686430 , why does the consumption rules does not fulfill his requirement? Contracts are linked per entitlement and no influence to other objects like sw model, entitlements etc.

best, Dennis

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

MikeW0609686430 · 3 weeks ago

I've had this use case for a large bank that have different contracts for specific regions. For example, their Singapore contract covered about 20 different countries, so consumption rules worked fine in this situation. One software model linked to multiple country entitlements, which each had a consumption rule based on the country of the install and the license position report shows consumption at the contract level with country breakdowns of license allocations. However, they had other specific contracts in other countries (e.g. India, Philippines, Fiji, NZ, China) which requires license reporting for each of these countries. It's even more complicated because they have 3 different contracts in India alone based on legal entity. Therefore, this required for country/legal entity specific software models with linked entitlements so that license position reports are linked to a specific country/legal entity contract. For example, if I used one software model for all contracts, how would I be able to report consumption for a specific legal entity (usually a business unit) using consumption rules?

In my view, one of the missing pieces in ELP grouping is the inability to group by business unit, since internally, this is how most customers charge back license usage. In general, ELP grouping helps with outbound reporting to software vendors but more and more customers want to see internal reporting that groups by attributes such as business unit and user personas.