Components installed with Supplier Lifecycle Operations
Summarize
Summary of Components installed with Supplier Lifecycle Operations
Activating Supplier Lifecycle Operations installs various components including tables and user roles essential for managing supplier information and processes. These components reside within the Supplier Common Architecture application, providing a structured framework for supplier lifecycle management. Demo data is available for exploring these features.
Show less
User Roles Installed
Several predefined user roles are installed to control access and capabilities within Supplier Lifecycle Operations:
- Supplier Administrator [snslm.admin]: Has full permissions to create, view, update, and delete all suppliers, cases, and tasks, including specialized roles such as decision table admin and vendor assessor.
- Supplier Fulfiller [snslm.fulfiller]: Can create tasks, view and update suppliers related to their assigned cases or tasks, and manage their assigned cases and tasks.
- Supplier Owner [snslm.owner]: Includes all Supplier Fulfiller capabilities plus the ability to create suppliers via playbooks, manage cases and tasks for owned suppliers, and update owned supplier records.
- Supplier Manager [snslm.manager]: Extends Supplier Owner capabilities by allowing management of all suppliers, cases, and tasks, including creation and updates across the board.
- Supplier Agent [snslm.agent]: Can create and update cases and tasks, view all suppliers and related records, with permissions extending beyond Supplier Fulfiller.
- Supplier Contact [snslm.contact]: Enables users to submit requests and complete assigned tasks via the Supplier Collaboration Portal; includes primary and secondary contact designations.
- KPI Roles [snkpi.admin, snkpi.user, snkpi.dataowner]: Added after the December 2024 upgrade, these roles support defining, managing, analyzing, and reading Key Performance Indicators in the Supplier Lifecycle context.
Note: Users assigned to Supplier Manager, Supplier Fulfiller, or Supplier Owner roles cannot access the Supplier Collaboration Portal.
Tables Installed
The application installs multiple tables to store and manage supplier data, relationships, and documents:
- Supplier Case [snslmcase]: Stores supplier case records, extending the Service Case table.
- Supplier Product Code [snslmcodem2msupplier]: Manages many-to-many relationships between suppliers and product codes.
- Supplier Email Domain [snslmemaildomain]: Contains email domain information associated with suppliers.
- Supplier Location [snslmm2mlocation]: Maps suppliers to multiple locations.
- Supplier Contact [snslmsupplierm2mcontact]: Manages relationships between multiple contacts and suppliers.
- Product Code [snslmproductcode]: Stores universal product codes (UPC) for products and services, independent of suppliers.
- Supplier Task [snslmtask]: Stores supplier task records, extending the Service Task table.
- Supplier Document Configuration [snslmdocumentconfig] and Supplier Document Type [snslmdocumenttype]: Store configurations and types for supplier documents, extending the Application File table.
- Supplier Document References [snslmdocumentreferences]: Stores references to supplier documents, extending the Document References table.
- Organization Tax Details [snfinorgtaxdetail]: Contains tax registration details for suppliers, part of the Finance Common Architecture plugin.
- Supplier Payment Information [snfinsupplierpayment]: Although installed with Finance Common Architecture, this table stores supplier bank account information.
Practical Implications for ServiceNow Customers
Understanding these installed components helps customers manage supplier data and workflows effectively by assigning appropriate roles and leveraging structured tables. The defined roles provide granular control over supplier lifecycle activities, ensuring security and operational efficiency. The tables enable comprehensive data management, supporting integration with financial and procurement processes.
Several types of components are installed with activation of Supplier Lifecycle Operations, including tables and user roles.
Demo data is available for this feature.
Roles installed
| Role title [name] | Description | Contains roles |
|---|---|---|
| Supplier Administrator [sn_slm.admin] |
The supplier admin can create, view, update, and delete all the suppliers, cases, and tasks. |
|
| Supplier Fulfiller [sn_slm.fulfiller] |
Users with this role can do the following:
|
|
| Supplier Owner [sn_slm.owner] |
The supplier owner can do everything the supplier fulfiller can do, plus users with this role can:
Note: The Supplier Owner [sn_slm.owner] role can create, manage, and edit records for only the suppliers that they own. |
|
| Supplier Manager [sn_slm.manager] |
The supplier manager can do everything the supplier owner can do, plus users with this role can:
|
|
| Supplier Agent sn_slm.agent |
The supplier agent can do everything the supplier fulfiller can do, plus users with this role can:
|
sn_slm.fulfiller |
| Supplier Contact [sn_slm.contact] |
A user with this role can do the following:
Note: A contact can be a primary contact or secondary contact. A primary contact is a user that has the Primary contact column set to true on the Vendor Contacts page. |
|
| KPI Administrator [sn_kpi.admin] |
The KPI admin can define, manage, and analyze KPIs. | sn_kpi.user Note: Added after the Xanadu December 2024 upgrade. |
| KPI User [sn_kpi.user] |
The KPI user can only read all the records in KPI Framework. |
Note:
Added after the Xanadu December 2024 upgrade. |
| KPI Data Owner [sn_kpi.data_owner] |
The KPI data owner can access only specific tables and fields which are necessary to collect data for KPIs from an internal user. |
Note:
Added after the Xanadu December 2024 upgrade. |
Tables installed
| Table | Description |
|---|---|
| Supplier Case [sn_slm_case] | Stores the supplier case records. Extends the Service Case [sn_spend_sdc_service_request] table. |
| Supplier Product Code [sn_slm_code_m2m_supplier] | Stores the relationships between suppliers in the Supplier [sn_fin_supplier] table and product codes in the Product Code [sn_supplier_product_code] table. |
| Supplier Email Domain [sn_slm_email_domain] | Stores the email domains of the suppliers. |
| Supplier Location [sn_slm_m2m_location] | Stores the relationships between suppliers stored in the Supplier [sn_fin_supplier] table and locations stored in the Location [cmn_location] table. |
| Supplier Contact [sn_slm_supplier_m2m_contact] | Stores the supplier contact and supplier records. It is used for the M2M mapping of one contact with many suppliers. |
| Product Code [sn_slm_product_code] | Stores the product and service records with universal product codes (UPC). These records do not have any relation to the supplier. |
| Supplier Task [sn_slm_task] | Stores the tasks of the suppliers. Extends the Service Task (sn_spend_sdc_service_task) table. |
| Supplier Document Configuration [sn_slm_document_config] | Stores the supplier document configurations. Extends the Application File [sys_metadata] table. |
| Supplier Document Type [sn_slm_document_type] | Stores the supplier document types. Extends the Application File [sys_metadata] table. |
| Supplier Document References [sn_slm_document_references] | Stores the supplier document references. Extends the Document References [ds_document_references] table. |
|
Organization Tax Details [sn_fin_org_tax_detail] |
Stores the tax registration details of the supplier. Note: This table has been added in the Finance Common Architecture (com.sn_fin) plugin. |