Over-licensed amount inconsistency

Thomas E_
Tera Expert

Hello, we have a simple example for license reconciliation. A software model has an entitlement assigned with 2500 active rights each with a cost of 40,00 Euro. License metric is Named User. We have three User allocations. Reconciliation results table shows an over-licensed amount of 99.880 Euros which is correct. However, in license workbench I see different values for over-licensed amount.

 

On the publisher level it is â‚¬130.38K

On the product level it is â‚¬114,117.6153.

On the version / model level it is â‚¬106,761.732.

 

Not only that the over-licensed amount displayed is too high, it is different on each level I am looking at.

1 ACCEPTED SOLUTION
4 REPLIES 4

Lionel Falk
Tera Contributor

Hi Thomas,
I have noticed in SAM Pro some inconsistencies in the currency management, including currency symbol displayed. Maybe this could explain yours.

  • Our general currency setting in ServiceNow is USD, symbol $
  • Our entitlements are created in the currency mentioned in the contracts, here in EURO
  • The Asset Workbench display financial figures in the user local setting. I'm in Switzerland, therefore CHF. (converted with the Exchange Rate in [fx_rate] table).
  • In some sections of the Asset Workbench, like the Summary section, it displays the financial figures in CHF, but... with the default currency symbol. In this case $.
  • Reports extraction are in the default currency (USD) and with the right currency symbol ($)

The ServiceNow internal team is working on an harmonization of the default currency and symbol settings. 
I don't know if it could help you.

@Lionel Falk, thanks for these insights, as I wan't aware of all of these inconsistencies.

Are you able to share any PRB I can use to link other customers to it.

 

Thanks, Dennis

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

Dear Dennis,

This issue has not yet been reported to ServiceNow Support as such. It was identified after this request and suggestion you kindly made.

Thomas E_
Tera Expert

We were able to solve the problem by following the steps described here:

Product result shows different amount than the software model result for the same over-license amoun...