Components installed with Supplier Lifecycle Operations

Several types of components are installed with activation of Supplier Lifecycle Operations, including tables and user roles.

The user roles and tables, even though installed along with Supplier Lifecycle Operations, reside in the Supplier Common Architecture application. For more information, see Supplier Common Architecture.

Note:

The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see Find components installed with an application.

Demo data is available for this feature.

Roles installed

Note:

Users with the Supplier Manager [sn_slm.manager], Supplier Fulfiller [sn_slm.fulfiller], and Supplier Owner [sn_slm.owner] roles cannot access the Supplier Collaboration Portal.

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.	decision_table_admin sn_shop.shopper awa_admin sn_vdr_risk_asmt.vendor_assessor sn_fin.supplier_payment_info_write sn_slm.manager sn_kpi.admin
Supplier Fulfiller [sn_slm.fulfiller]	Users with this role can do the following: Create tasks View suppliers related to assigned cases or tasks View assigned cases and tasks, or tasks that are created by them Update assigned cases and tasks, or tasks that are created by them	task_editor template_read_global sn_shop.shopper workspace_user vendor_reader canvas_user sn_fin.finance_user awa_agent survey_reader sn_fin.procurement_user email_composer
Supplier Owner [sn_slm.owner]	The supplier owner can do everything the supplier fulfiller can do, plus users with this role can: Create suppliers using the playbook Create cases and tasks for suppliers they own View the suppliers they own View cases and tasks for the suppliers they own Update the suppliers they own Update the cases and tasks that are created by them or assigned to them Note: The Supplier Owner [sn_slm.owner] role can create, manage, and edit records for only the suppliers that they own.	personalize_responses workspace_user canvas_user sn_slm.fulfiller sn_fin.finance_user sn_fin.procurement_user sn_vdr_risk_asmt.vendor_assessment_reviewer
Supplier Manager [sn_slm.manager]	The supplier manager can do everything the supplier owner can do, plus users with this role can: Create suppliers using the playbook Create cases and tasks View all the suppliers, cases, and tasks Update the suppliers they manage and also other suppliers Update the cases and tasks that they create or that are assigned to them	sn_slm.owner dm_user_criteria_read
Supplier Agent sn_slm.agent	The supplier agent can do everything the supplier fulfiller can do, plus users with this role can: Create cases and tasks View all the suppliers, cases, and tasks Update all the tasks and assigned cases	sn_slm.fulfiller
Supplier Contact [sn_slm.contact]	A user with this role can do the following: Submit requests using the supplier catalog from the Supplier Collaboration Portal Complete assigned tasks using the Supplier Collaboration Portal 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.	sn_fin.supplier_payment_info_read snc_external
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

Note:

The Supplier Payment Information [sn_fin_supplier_payment] table, which stores the bank account records of the suppliers, is installed with the Finance Common Architecture (com.sn_fin) application.

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.