SAP ECC Non-Production Instances Showing License Compliance Issues in SAM Pro

[Anshuman Damani]

recently implemented the SAP ECC on-premises connection in ServiceNow. The integration is successfully pulling data for all instances, including Development and Test environments.

However, SAM Pro is currently identifying engine license requirements for the non-production systems as well, resulting in compliance issues being reported for those instances.

Could anyone please advise on how to configure ServiceNow so that non-production instances are either excluded from engine license calculations or do not appear as non-compliant?

[fknell]

Hi @Anshuman Damani,

I assume you're ingesting data from your on-prem SolMan. How does the data look like in SLAW?

Hope this helps!

[dreinhardt]

HI @Anshuman Damani, 

In general, the integration is not able to decide based on the imported data what to include/exclude. All setup RFC connections are triggered and the data is imported/processed. I checked the software model conditions, and it's not possible to setup a "engine measurement" or "general SAP related" condition to include/exclude a set of engines to be processed.

What I can see in several customer instances, the mentioned RFC connections setup in SolMan are covering only the relevant system to be licensed. If a engine/system in non-prod needs to be licensed it's included, if not, no active RFC connection was setup.

Best, Dennis