SAP Concur Travel & Expense – Best Approach for Per Transaction License Compliance in SAM Pro

Maniteja_2003
Tera Guru

yesterday

Hello Community,

 

We are working on SAP Concur Travel & Expense licensing in ServiceNow SAM Pro.

From our understanding, the product licensing is based on a Per Transaction license metric rather than traditional named user licensing. Currently, we are only retrieving user data through SSO integration for this product.

We would like to understand the best approach to achieve accurate compliance reporting for SAP Concur Travel & Expense.

Our questions are:

  1. Does the SAP Publisher Pack integration support SAP Concur Travel & Expense transaction-based licensing?
  2. Will the publisher pack help calculate compliance for Per Transaction metrics, or is it mainly focused on SAP ECC/S4HANA engines, named users, Digital Access, and FUE models?
  3. For SAP Concur products, what is the recommended approach to track transaction-based consumption and generate proper compliance reports in SAM Pro?
  4. If entitlement is created for it what will be the license metric and the Metric Group that is required to choose?

Thanks,
Maniteja

Labels:
0 Helpfuls
  • 159 Views
1 REPLY 1

pr8172510
Tera Guru

yesterday

Hi @Maniteja_2003,

SAP Concur Travel and  Expense licensing is generally transaction-based, and this is different from the traditional named-user or device-based metrics commonly handled by SAM Pro.

  • The SAP Publisher Pack is primarily designed for SAP products such as ECC, S/4HANA, Named Users, Digital Access, and FUE licensing.
  • There is no OOTB SAM Pro compliance engine specifically for SAP Concur Per Transaction licensing.
  • Simply importing users through SSO integration will not provide accurate transaction-based compliance.

For SAP Concur

 

  1. Import transaction consumption data from SAP Concur (via integration or custom import).
  2. Create entitlements that reflect the contractual transaction limits.

  3. Use custom reporting/Performance Analytics to compare:

    Purchased Transactions
vs
Consumed Transactions
  4. Track compliance through custom dashboards or reports rather than standard user-based reconciliation.

 

If creating an entitlement, the appropriate metric depends on the contract terms. In most cases, Per Transaction is not an OOTB SAM metric group supported by the SAP Publisher Pack, so a custom metric/reporting approach is typically required.

0 Helpfuls