Software Asset Management publisher pack for SAP

concept australia Updated Sep 10, 2026 13 min read sap-publisher-pack.md
Raw file servicenow.com

Use the Software Asset Management publisher pack for SAP to manage and optimize your SAP licenses. Get comprehensive visibility into your SAP license compliance and uncover potential savings.

Note: You can use the SAP publisher pack to manage and optimize licensing for SAP NetWeaver 7.4, SAP_BASIS 740, and later versions.

Note: To use the publisher pack, install the Software Asset Management Professional for SAP plugin (com.sn_samp_sap).

Supported license types

The SAP publisher pack supports licensing for named users, engine measurement, third-party access, user subscription, and full usage equivalent.

  • Named Users

    SAP named users are the members in your organization who use SAP applications. You can purchase different types of named user licenses and then assign each license to a named user.

    The SAP publisher pack supports named user licenses for both SAP ERP Central Component (ECC) applications and SAP S/4HANA applications. Different named user license types are supported based on the application type. SAP ECC applications support various named user license types, including Professional, Limited Professional, and Employee Self Service. SAP S/4HANA applications support only the Developer Access, Enterprise Management for Professional Use, Enterprise Management for Functional Use, Enterprise Management for Productivity Use, Technical SAP Engine User, and Technical Use named user license types. The ServiceNow AI Platform supports all named user types for both SAP ECC applications and SAP S/4HANA applications.

  • Engines (automated, calculated, and self-declared)

    SAP engines, also known as packages, are optional applications that require additional licenses. Every engine has a unique license metric that is used to calculate the license usage for the engine. Examples of license metrics include the number of employees or number of contracts.

    License usage is calculated through either an automated SAP engine measurement, calculation based on multiple engine measurements plus an indicator, or a manual self-declaration process.

    • If an engine is supported by the SAP engine measurement process, Software Asset Management automatically calculates the license usage for that engine.
    • If an engine is identified to be composed of multiple engine measurements, Software Asset Management calculates this value if the indicator license metric is also available.
    • If an engine isn’t supported by the SAP engine measurement process, you must manually enter the license usage information for that engine using the self-declaration process. For information on how to self-declare your SAP engine license usage, see Self-declaring SAP engine license usage. To view the complete list of engines that are supported by each process, see Engine & Self-Declaration Product Measurement in the SAP Support Portal.

    Important: You must have an SAP Support Portal account to access the SAP Support Portal.

    The SAP publisher pack supports engine licenses for both SAP ERP Central Component (ECC) applications and SAP S/4 HANA applications.

    Note: Starting with the Brazil release, revenue-based licensing support is enabled for SAP Engine products. You can use higher value revenue-based products for purchased rights and unit cost. For details on enabling the support for revenue-based licensing, see the knowledge base article KB1641524.

  • Digital Access

    The Digital Access license applies to indirect usage of SAP systems by people or third-party applications without logging in to the system directly. A few examples for indirect usage of SAP systems are as follows:

    • Using a third-party application to perform actions in the SAP system
    • Entering data into the SAP system from a third-party application
    • Viewing data in the SAP system from a third-party application When you have many third-party product integrations with SAP systems, you can avoid unnecessary consumption of your named user license by purchasing Digital Access licenses. In this licensing model, the usage of SAP applications is licensed by the count of the predefined documents created by the third-party application. The details of the predefined document types are stored in the SAP Document Type [samp_sap_document] table that's installed with the Software Asset Management Professional for SAP (com.sn_samp_sap) plugin.
    Document name Document multiplier
    Sales document 1
    Purchase document 1
    Invoice document 1
    Manufacturing document 1
    Material document 0.2
    Quality Management document 1
    Service and Maintenance document 1
    Financial document 0.2
    Time Management document 1

    The SAP system stores the digital access data of the supported document types for different users and client systems. Make sure you have any of the following tools to pull the digital access data from the SAP system to your ServiceNow instance:

    • SAP Passport tool
    • SAP Estimation tool Note: When you purchase an SAP Digital Access license, these tools are available for installation without any additional cost. For details on the SAP tools, see SAP Help Portal.

    When any of the predefined document types are created in the SAP system through a third-party application, the Digital Access licensing cost is applicable. However, there are no additional charges associated with reading, updating, or deleting these documents.

    For the SAP Digital Access software model, digital access usage is calculated as follows:

    1. The total count of documents of a particular document type created on each SAP system by all your users is calculated.

      Consider a scenario where User A created 5 Material documents, and User B created 5 Material and 10 Sales documents on an SAP system. The total count of Material documents is 10 and Sales documents is 10.

    2. The license consumption is calculated by multiplying the total count of a particular document type by the Document multiplier.

      Based on the scenario mentioned in the preceding step, licenses consumed by Material documents is 2 (10*0.2) and by Sales documents is 10 (10*1). So, the total Digital Access license consumed is 12.

    Note: The SAP Digital Access software model is installed with the Software Asset Management Professional for SAP (com.sn_samp_sap) plugin.

    Reconciliation for the SAP Digital Access software model is done by comparing the Purchased rights with the licenses that you consumed.

  • User Subscription and Full Usage Equivalent (FUE)

    Full Usage Equivalent (FUE) is a licensing framework for SAP S/4HANA Cloud applications. FUE grants access to the number of users that are authorized to access specified solution capabilities. A single FUE can be allocated across four cloud use types and each use type has a specific weighting factor:

    • Self-Service

    • Core

    • Advanced

    • Development The FUE framework applies to both SAP S/4HANA Cloud, Public Edition and SAP S/4HANA Cloud, Private Edition. The license metric name differs by deployment:

    • For SAP S/4HANA Cloud, Public Edition, the metric is named User Subscription. In releases earlier than Brazil, this metric was named Full Usage Equivalent.

    • For SAP S/4HANA Cloud, Private Edition, the metric is named Full Usage Equivalent. The predefined cloud use types for SAP S/4HANA Cloud, Public Edition are stored in the SAP Cloud Use Types [samp_sap_cloud_use_type] table that’s installed with the SAP S/4HANA Spoke plugin (sn_s4_hana_cld_spk).

    For SAP S/4HANA Cloud, Private Edition, the use type for each user is determined on the SAP system during use collection. Based on this classification during data collection. For details on uploading the license ruleset for Private Edition, see Upload the license ruleset for SAP S/4HANA Private Cloud. For details on SAP S/4HANA Cloud, Public Edition, see Integrating with SAP S/4HANA Cloud Public Edition.

    For descriptions of each cloud use type, the weighting factors, and how FUE licenses are calculated, see License calculation for SAP cloud use types.

    Note: The FUE feature requires the following minimum system requirements:

    • Environment: ECS
    • Deployment Type: SAP S/4HANA Cloud Private Edition
    • SAP S/4HANA Version: 2025
    • FPS Level: FPS01 (02/2026)
    • SAP_BASIS: 816

SAP connection with the ServiceNow AI Platform

To start connecting your SAP systems and your ServiceNow instance, see Set up SAP integration to establish a connection with SAP. After completing the configuration, establish an SAP connection using one of the following authentication methods:

The Software Asset Management publisher pack for SAP uses a centralized design. When you import transport files into an SAP client that is considered a central system, the client uses the custom program-selected Remote Function Call (RFC) connection list to connect all other clients through RFC from the central system. It then fetches data to store in central system custom tables. To import the transport files, use either the SAP Solution Manager or another SAP client that has RFC connections activated to fetch data into a central system.

After the connection is established, data is pulled into your ServiceNow instance from your SAP system. For a list of all data that is pulled, see Tables installed with the SAP publisher pack.

SAP data is scheduled to be pulled weekly. User activity data, web activity data, and engine usage data are pulled monthly. All user and web activity is deleted after 90 days. Engine usage measurement records in the SAP License Metric Measurement table [samp_sap_license_metric_measurement] are deleted after one year.

When SAP data enters the ServiceNow AI Platform, it’s initially stored in staging tables before it’s transferred to the final SAP tables. To edit the tables where data transfer takes place or to view the transfer logic, see transform maps.

Note: The user activity and web activity transform maps aren't enabled by default because they may cause performance issues due to the large amount of data. However, you can manually enable these transform maps. To enable the activity transform maps, navigate to All > Software Asset > SAP Compliance and Optimization > SAP Connections and select the connection. In the Configuration section, set the Fetch activity field to True and then select Update.

View SAP license usage and compliance

View your SAP license costs, usage, and compliance using the Software Publisher Analytics dashboard (Software Asset Management classic application) or publisher overview (Software Asset Workspace). The dashboard and overview also show how you can optimize license consumption by reassigning user roles in your SAP system. You can view the license optimization details in the Software asset analytics view. For more details, see Publisher optimizations for SAP.

Reconciliation runs weekly or on demand to determine your license compliance position for all of your SAP products. Reconciliation compares your purchased rights recorded in software entitlements with actual usage data pulled from your SAP systems. You can view reconciliation results for SAP in the License usage view of the Software Asset Workspace. The License usage view shows unlicensed users and engines, digital access licenses available and required, and remediation options to make your license position compliant, potential savings, and more. For more information on the License usage view, see License usage view.

To view Software license compliance position reports for SAP, navigate to License usage > Reports > Software license compliance position in the Software Asset Workspace.

Parent Topic:Supported software publisher licenses

Search documentation
Search document titles and file paths on the australia branch