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 (Release version: Yokohama), installs multiple tables that store data imported from SAP systems. These tables enable ServiceNow customers to manage SAP license compliance and optimize SAP usage by capturing detailed information on users, roles, connections, license metrics, and activities.
Show less
For a comprehensive list of all components installed with the SAP publisher pack, customers should refer to the Application Files table within the system.
Key Tables and Their Purpose
- Named User Type Role [sampnamedusertypehasrole]: Maps roles assigned to each named user type.
- SAP Client [sampsapclient]: Stores RFC destinations that connect ABAP systems to external systems; accessible via SAP Compliance and Optimization administration.
- SAP Connection [sampsapconnection]: Contains details of SAP system connections.
- SAP Engine Usage [sampsapswclientaccess]: Records the latest engine usage metrics for SAP clients based on license metrics.
- SAP License Metric [sampsaplicensemetric]: Maintained by the ServiceNow Content Service, this table lists all SAP license metrics used by engines. It updates periodically to reflect changes in SAP licensing.
- SAP License Metric Measurement [sampsaplicensemetricmeasurement]: Stores monthly engine usage measurements per SAP client.
- SAP Roles [sampsaprole]: Contains SAP roles pulled directly from SAP systems.
- SAP System User [sampsapsystemuser]: Holds discovered SAP users; mapped to system user records for identity correlation.
- SAP User Activity [sampsapuseractivity]: Captures user activity metrics such as time spent and database records created or updated.
- SAP User Roles [sampsapuserhasrole]: Links SAP users to their assigned roles.
- SAP Web Activity [sampsapwebactivity]: Tracks web or RFC connection activities, including call counts and data volumes.
- SAP User Active Transactions [sampnamedusertypehastransactions]: Records named user transaction activities based on SAP transaction codes (e.g., ME21N for purchase order creation).
- SAP USMM Rules [sampsapusmmrule]: Contains USMM rules data from connected SAP applications.
Additional tables outside the core SAP publisher pack include:
- Price List [samppricelist]: Stores SAP price list data.
- Named User Type [sampnamedusertype]: Stores named user types pulled from SAP.
- SAP Digital Access [sampsapdigitalaccess]: Captures digital access details such as client, user name, document types, and measurement data.
Practical Use for ServiceNow Customers
These tables collectively enable customers to:
- Track and analyze SAP user roles, activities, and license consumption accurately.
- Maintain up-to-date SAP license metric data aligned with SAP’s licensing changes.
- Manage SAP system connections and client configurations efficiently.
- Optimize SAP license usage through detailed transaction and user activity data.
- Integrate SAP data with ServiceNow’s Software Asset Management tools for licensing compliance and cost control.
Related Actions and Resources
- Deploy the ABAP program for SAP integration.
- Establish SAP system connections within ServiceNow.
- Create and map entitlements, software models, named user types, and price lists specific to SAP.
- Import custom SAP named user types and price lists as needed.
- Leverage Software Publisher Analytics dashboards and SAP publisher overview resources for enhanced reporting and insights.
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 .