Source-to-Pay on ServiceNow, Part 1: What actually makes up Supplier Lifecycle Operations

[sachinbhasin11]

Source-to-Pay on ServiceNow: The SLO Application Landscape

Part 1 of a 4-part series on Supplier Lifecycle Operations. Tested on the Australia release.

I'm currently implementing Supplier Lifecycle Operations (SLO) for a large logistics company. This series shares what I've learned on that engagement: the application scopes, the table structure, the roles, and the behaviours that only show up once you're building. This first post sets the scene: which applications make up Source-to-Pay, which ones SLO depends on, and what changes when you add Procurement Case Management.

The three Source-to-Pay modules

ServiceNow Source-to-Pay (S2P) is built around three core modules that automate the procurement lifecycle:

Module	What it covers
Sourcing and Procurement Operations (SPO)	Sourcing, requisitioning, and purchasing goods and services for employees
Supplier Lifecycle Operations (SLO)	Supplier onboarding, risk assessment, compliance, documents and ongoing supplier management
Accounts Payable Operations (APO)	Invoice receipt and digitisation, matching, payment and supplier invoice inquiries

This series focuses on SLO. It sits in the middle of the chain: SPO buys from suppliers and APO pays them, but SLO is where the supplier relationship itself is managed.

 

The applications SLO depends on

SLO is not one application. On an instance it is a handful of scoped apps, each owning a different part of the data model. Knowing which scope owns what saves a lot of time when you're debugging an ACL or looking for a table.

Application	Scope / plugin	What it gives SLO
Finance Common Architecture	sn_fin (com.sn_fin)	The supplier record itself (sn_fin_supplier) plus supplier metadata: tax info, payment info, legal entity mapping
ERP Integration Framework	com.sn_fcms_intg	Staging tables, transform maps, scripts and the framework for bringing supplier data in from your ERP
Common Service Delivery	com.sn_spend_sdc	The base Finance Case and task tables (sn_spend_sdc_service_request) that the Supplier Case extends
Supplier Common Architecture	sn_slm	The supplier-related tables: contacts, locations, product codes, segmentation, documents, supplier cases and tasks
Supplier Lifecycle Operations	com.snc.sn_supplier_mgmt	The onboarding and lifecycle processes, playbooks and configuration. Renamed Supplier Case Management from v5.2.0 (Yokohama December 2025), so you may see either name in the Store
Supplier Collaboration Portal	com.snc.sn_supplier_sp	The portal suppliers log into to raise requests, complete tasks and upload documents
Source-to-Pay Workspace	—	The main interface for fulfillers working with suppliers

Install order matters. ServiceNow documents an installation sequence for the S2P plugins. It starts with Finance Common Architecture, then ERP Integration Framework, then Common Service Delivery, and each plugin lists the dependencies it needs first.

Follow the official installation sequence rather than installing whatever the Store suggests first. Installing out of order is a common cause of missing demo data and half-configured workspaces.

In the Australia release, add Supplier Operations. The Australia release notes say the Supplier Operations plugin (com.snc.sn_so) must be installed after upgrading SLO to Australia. Several of the newer document expiry notifications live in that scope (sn_so), so missing it shows up as missing reminders. See the Australia release notes.

Tip: When you look for an SLO table and can't find it under Supplier Lifecycle Operations, check Supplier Common Architecture. That's where every sn_slm table lives. The supplier record itself is one level further down, in Finance Common Architecture.

Adding Procurement Case Management

SLO gives you supplier cases. If your procurement team also needs cases for its own request types, such as PO changes or master data management (MDM) etc. , activate Procurement Case Management (sn_spend_psd).

The easiest way to see the difference is the Create new case dialog in the Source-to-Pay Workspace. Here is what the Case type list offers before and after activation:

Without Procurement Case Management	With Procurement Case Management (first entries)
Banking information change request	Contract review
Conduct sanction screening	Delivery address review
General supplier inquiry	Due Diligence Case
Supplier due diligence	General procurement case
Supplier information change request	General supplier inquiry
Supplier issue	GL coding review
Supplier location change request	Invoice case
Supplier support request	…and more

Here is what it looks like without Procurement Case Management activated 

Here is how it looks with Procurement Case Management activated (you can see Procurement-related case types being introduced)

Note: when we say case type, these aren't different tables like CSM; it's just a choice field on the case form

Procurement Case Management brings its own roles, separate from the SLO roles:

Role	What it allows
sn_spend_psd.psd_admin	Configure system properties, request types and categories
sn_spend_psd.manager	View, create and update procurement cases and tasks
sn_spend_psd.agent	Manage fulfilment workflows and knowledge articles
sn_spend_psd.procurement_task_owner	Access and complete assigned tasks
sn_spend_psd.requestor	Create procurement cases

Roles from Procurement Case Management in the ServiceNow docs. Plan your fulfiller groups with both role sets in mind: an SLO fulfiller won't automatically work procurement cases, and the reverse is also true.

 

Key takeaways

• SLO spans several scoped apps. The supplier lives in Finance Common Architecture (sn_fin), and everything around it lives in Supplier Common Architecture (sn_slm).
• Follow the documented install sequence. Order matters for dependencies and demo data.
• Procurement Case Management is optional. Add it when procurement needs its own case types, and plan its roles separately from the SLO roles.

Next in the series: Part 2 walks through the 15 core sn_slm tables and how they all hang off one supplier record.