Tables installed with the SAP publisher pack
Summarize
Summary of Tables installed with the SAP publisher pack
The SAP publisher pack, part of the Software Asset Management Professional for SAP plugin, installs various tables that store data imported directly from SAP systems. These tables enable comprehensive tracking and management of SAP licensing, user activity, roles, connections, and other critical SAP system information within ServiceNow. Demo data is also available to facilitate testing and configuration.
Show less
Customers can use the Application Files table to view all components installed by the SAP publisher pack, supporting effective administration and troubleshooting.
Key Tables and Their Purpose
- Named User Type Role [sampnamedusertypehasrole]: Maps roles assigned to each named user type.
- SAP Client [sampsapclient]: Stores Remote Function Call (RFC) destinations connecting ABAP systems to external systems. Accessible under SAP Compliance and Optimization > Administration > SAP Clients.
- SAP Connection [sampsapconnection]: Contains SAP system connection details. Accessible under SAP Compliance and Optimization > Administration > SAP Connections.
- SAP Engine Usage [sampsapswclientaccess]: Tracks recent engine usage measurements for SAP clients based on license metrics.
- SAP License Metric [sampsaplicensemetric]: Lists all SAP license metrics used by engines, updated periodically from the ServiceNow Content Service. Viewable under SAP Compliance and Optimization > Administration > Engines.
- SAP License Metric Measurement [sampsaplicensemetricmeasurement]: Records monthly engine usage measurements per license metric, accessible via SAP Compliance and Optimization > Licensing > All SAP Engines.
- SAP Roles [sampsaprole]: Contains roles pulled from SAP systems.
- SAP System User [sampsapsystemuser]: Lists discovered SAP users, mapped to system users in ServiceNow. Viewable under SAP Compliance and Optimization > Licensing > All SAP Users.
- SAP User Activity [sampsapuseractivity]: Captures user activity details on SAP clients, such as time spent and records created or updated.
- SAP User Roles [sampsapuserhasrole]: Shows SAP users and their assigned roles.
- SAP Web Activity [sampsapwebactivity]: Tracks web or RFC connection activity, including call counts and data volume.
- SAP User Active Transactions [sampnamedusertypehastransactions]: Contains transaction activity for named users based on SAP transaction codes, such as ME21N for creating purchase orders.
- SAP USMM Rules [sampsapusmmrule]: Stores USMM rules information from connected SAP applications.
- Additional data tables:
- Price List [samppricelist]: Stores price list data from SAP.
- Named User Type [sampnamedusertype]: Contains named user types pulled from SAP.
- SAP Digital Access [sampsapdigitalaccess]: Holds digital access details such as client, user name, document types, and measurement data.
Practical Use for ServiceNow Customers
These tables provide a structured and comprehensive data foundation to:
- Manage SAP licensing more effectively by tracking engine usage, license metrics, and user activity.
- Map SAP roles and users accurately to understand entitlements and compliance needs.
- Monitor SAP system connections and client data for optimized integration and troubleshooting.
- Leverage transaction and user activity insights to support license optimization and cost control.
- Utilize SAP USMM rules and digital access data to align with SAP licensing requirements and audit readiness.
Customers can access and manage these tables through the SAP Compliance and Optimization modules within ServiceNow, facilitating streamlined SAP software asset management workflows.
Tables are installed with the Software Asset Management Professional for SAP plugin. The tables store data pulled from the SAP systems.
Demo data is available for the SAP publisher pack.
Tables
| Table | Description |
|---|---|
| Named User Type Role [samp_named_user_type_has_role] | Roles assigned to each named user type. |
| SAP Client [samp_sap_client] | Remote Function Call (RFC) destination connecting Advanced Business Application
Programming (ABAP) systems to external systems. To view the table, navigate to . |
| SAP Connection [samp_sap_connection] | SAP system connections. To view the table, navigate to . |
| SAP Engine Usage [samp_sap_sw_client_access] | Most recent engine usage measurements for SAP clients based on the license metric for each engine. |
| SAP License Metric [samp_sap_license_metric] | This table is populated by the ServiceNow Content Service. It’s a list of all license metrics that are used by SAP engines. To view the table, navigate to . Note: The table is periodically updated with new data from the Content Service. New license metrics may be added, and existing license metrics may be deactivated to reflect current SAP licensing. To view your software models that have deactivated license metrics, navigate to . |
| SAP License Metric Measurement [samp_sap_license_metric_measurement] | Monthly engine usage measurements for SAP clients based on the
license metric for each engine. To view the table, navigate to . |
| SAP Roles [samp_sap_role] | SAP roles pulled from the SAP systems. |
| SAP System User [samp_sap_system_user] | Discovered users pulled from the SAP systems. To view the table, navigate to . Note: The Discovered Users table [samp_discovered_user] maps
the discovered SAP users to system user records in the Users table
[sys_user]. |
| SAP User Activity [samp_sap_user_activity] | Data related to a user’s activity on an SAP client, such as the amount of time spent on an SAP system or the number of database records created or updated. |
| SAP User Roles [samp_sap_user_has_role] | SAP users and their assigned roles. |
| SAP Web Activity [samp_sap_web_activity] | Data related to web activity or RFC connections performed in the SAP client, such as the number of calls or amount of data received or sent by each connection. |
| SAP User Active Transactions [samp_named_user_type_has_transactions] | Data related to a named user's transaction activity on an SAP client. User transaction activity is based on SAP transaction codes, which are shortcuts for performing transactions or tasks on an SAP client. For example, the ME21N transaction code enables you to create a purchase order in SAP. |
| SAP USMM Rules [samp_sap_usmm_rule] | USMM rules information from all connected SAP applications. |
- Price list data is pulled and stored in the Price List table [samp_price_list].
To view the table, navigate to .
- Named user types are pulled and stored in the Named User Type table [samp_named_user_type].
To view the table, navigate to .
- The Digital Access details such as Client, User name, Document
type, Document type count, and Measured by are pulled from the SAP systems and stored in the SAP Digital Access [samp_sap_digital_access] table.
To view the data in the table, navigate to .