Read this first
Risk monitoring is not an SLP capability, and modular-questionnaire answers never reach your ERP. Those two sentences decide most of the architecture.
SLP, SIPM, Supplier Risk and SPM are four solutions with a shared surface — modular questionnaires, certificates, findings and D&B enrichment — and sharply different edges. Risk monitoring and control-based risk assessment require separately-licensed SAP Ariba Supplier Risk. SPM Reviews, conversely, are not a Supplier Risk capability. And the industry shorthand that “SIPM is classic, SLP is new” is unreliable: SAP's own material treats new-versus-classic as an attribute of both. Confirm entitlement, not positioning.
That matters immediately, because modular questionnaires do not exist in SIPM classic architecture. Promise them before confirming the architecture and you have promised a capability the site cannot deliver. Supplier Management applications run on SAP BTP and are reached from the Ariba site — which means at least four admin surfaces, two of them near-identically named, before you configure anything at all.
The lifecycle, and where each stage fails
Six lifecycle phases, each with its own project type. Qualification is keyed by matrix point, not by supplier — design the commodity/region/department matrix before you mass-create anything.
| Stage | What is created | Where it fails |
|---|---|---|
| Supplier Request | Supplier Request project | Duplicate check catches the request; approval never resolves an approver; request approved but no supplier created |
| Supplier 360 profile | SM Vendor ID (VDR…) | Profile created without an ERP Vendor ID |
| Supplier Registration | Registration project, external + internal questionnaires | Invitation never sent; supplier cannot see the questionnaire; approval starts too early or not at all |
| ERP sync | SAP Business Partner / vendor master record | Minimum-status trigger misfires; ERP rejects on uniqueness or field length; status stuck In Progress |
| Qualification | Qualification project per matrix point | “A qualification already exists for one or more of these matrix points” |
| Modular questionnaires | MQ projects, certificates | Answers cannot reach the ERP; mass invite capped near 100 suppliers |
| Preferred Supplier Management | Preferred designation per category | Blocked by a disqualification at a lower matrix level |
| SPM | Scorecards, surveys, KPIs | Template does not allow KPI documents; survey score never reaches the scorecard |
The request → registration handoff is the most fragile seam in the product. A dozen independent support articles describe failures there, spanning 2022 to 2025: stuck in Submitted, approved with no supplier created, field values not carrying across. The third variant usually turns out to be an answer-type mismatch — Address on the request against Extended Address on registration.
The supplier experiences all of this through Ariba Proposals and Questionnaires on SAP Business Network. Buyer-side configuration being correct proves nothing about supplier visibility, which puts Business Network account administration squarely on the go-live critical path — not on the integration backlog.
The decisions you cannot take back
- Unified Vendor Model migration
- Required for SLP. A one-time data migration, not a configuration change — it fails on duplicate records, empty mandatory fields and format incompatibility. Clean the data first.
- Where ERP-bound fields live
- Modular-questionnaire answers are explicitly unsupported for ERP sync. Getting this wrong means rebuilding questionnaires and re-collecting data from live suppliers.
- ERP vendor ID convention and casing
- Write-once on an integrated supplier. Standardise casing and enforce uniqueness before loading the legacy base.
- Internally registered legacy suppliers
- Internally registered suppliers cannot establish a trading relationship — that constrains the transactional path for however much of the base you onboard that way.
- Process rollout (SM-16798)
- Once enabled, new legacy qualifications are blocked. The source does not document whether it is reversible. Decide before production.
- Template base language
- SAP documents how to modify it. Nothing says it is reversible.
A migrated site can still admit records through the old door — legacy supplier self-registration has been observed surviving a UVM migration. Budget a separate test cycle for the migrated base: it behaves differently from natively-registered suppliers in duplicate checking, API retrieval, arriving status and qualification expiry.
Which question goes where
An SLP implementation lives or dies on this one decision, and the product documentation offers no guidance on it.
| Put it in… | When | Hard constraint |
|---|---|---|
| Supplier Request | Needed for the create/duplicate-check decision, or ERP-bound and known at request time | Duplicate check operates here, per question |
| Registration questionnaire | It must reach the ERP / SAP Business Partner record | The only documented ERP-bound path alongside the request |
| Supplier Profile Questionnaire | Durable profile information, not tied to one lifecycle event | Mapping SPQ → registration questionnaire is a manual admin step |
| Modular questionnaire | Recurring, periodic, certificate- or compliance-driven | Answers cannot be synchronized to an integrated ERP |
The trap. “Lean registration plus rich modular questionnaires” is an otherwise sensible architecture — modular questionnaires can be re-issued on a cycle. Teams that adopt it find their ERP-relevant fields stranded, and the fix is rebuilding questionnaires and re-collecting data from live suppliers.
Answer types are richer than documented
The narrative names five families — free text, multiple choice, upload, numeric, date. The support corpus evidences Bank Account, Address, Extended Address, Tax, Money, Certificate, List of Choices, Yes/No, Attachment and the Commodity / Region / Department matrix selectors, each with its own behaviour. Attachment answers carry a stated 10 MB ceiling — size that against certificates, insurance documents and bank letters.
Bank and tax questions deserve disproportionate design time. IBAN fields ship with no default syntax validation and no mandatory flag; duplicate bank details are accepted during registration; character limits bite on bank name, account-holder name and region. Country behaviour is real and under-documented — test against the customer's actual supplier country list.
Conditions, and the defect cluster
Four condition kinds exist: visibility, editability, user/group-based, and project-level. The constraint that reshapes designs: you cannot condition a whole questionnaire inside a registration template — only questions. There is no branching a registration into different questionnaires.
- Conditions inside repeatable sections — a Known Error and the densest defect cluster in SLP
- Conditions + repeatable sections + GenericCustomField mappings is known-bad
- Initial/default values interfere with visibility conditions
- Commodity conditions do not cascade to child commodities
- Conditionally hidden is not deleted
The User Matrix
The User Matrix appears nowhere in the narrative documentation, yet it drives approver resolution across three project types. It exists only in support-article titles — but it appears repeatedly and carries its own SAP component code, BNS-ARI-SLP-REG-UMX. That combination is strong evidence of a first-class, central administration object.
It is imported through SM Administration, carries commodity, region and buyer-category assignments per user, and drives automatic assignment of approvers, project owners and Team-tab membership in Supplier Request, Supplier Registration and Engagement Request projects. Its file format, column names and matching algorithm are undocumented.
Approvals in SLP fail by not resolving an approver far more often than by rejecting. Build and validate the matrix before you test any approval flow, or you will debug the wrong layer for days.
Related warning worth stating plainly: Team Access control on Supplier Management projects does not restrict visibility or editing for other users. Do not rely on project team membership for field-level confidentiality.
| Symptom | KBA |
|---|---|
| “No task approvers were found based on the provided information” | 3181051 |
| Approval groups assigned, system still asks to add missing approvers | 3187869 |
| Approvers not auto-assigned by category despite buyer-category assignments | 3643900 |
| Matrix not populating approvers to the Team tab on Supplier Requests | 3613932 |
| Matrix does not add the group as project owner in registration projects | 3748470 |
| User Matrix import error captured as “Verify Group” | 3188861 |
The vendor-key model
No documentation lays this out; it is inferable only from support content. Four identifiers exist, and the relationship between the first two is a mapping, not an identity.
| Identifier | What it is |
|---|---|
| SM Vendor ID (smVendorId) | SLP's internal vendor key, rendered as a VDR… number |
| ERP Vendor ID (erpVendorId) | The vendor / Business Partner number in the backend ERP. Treat as write-once |
| ANID | The SAP Business Network identity, stored on the SM vendor record |
| ACM ID | An Ariba core-platform organization ID. Never expanded or defined in the source — don't print an expansion you can't cite |
The one-line diagnostic: if Supplier 360 shows a VDR… value where you expect the ERP vendor number, the supplier has an SM Vendor ID and no ERP Vendor ID. It was never successfully integrated, or the key mapping never came back. That is a reconciliation finding, not a display bug — build the report “SLP suppliers with no ERP Vendor ID” on day one.
Two Ariba suppliers can end up on the same ERPVendorID and require manual conflict resolution. ANID unlink is blocked while the record exists in SM. ANID and ACM ID are not in the outbound payload by default. And a supplier with no valid vendor ID blocks a Sourcing award — not just supplier administration. Sync status is not sync success: reconcile against the ERP rather than trusting the field.
Symptom → layer
| Symptom | Look at |
|---|---|
| Supplier can't see the registration questionnaire | Supplier-side visibility on Ariba Proposals and Questionnaires, then the invitation chain |
| Supplier request stuck in Submitted | Missing contact, NullPointerException, or auto-approval configuration |
| Request approved but no supplier / no 360 profile | The request → registration handoff — the most fragile seam in SLP |
| “Add missing approvers” / empty Team tab | The User Matrix, before anything else |
| Visibility or editability conditions not firing | Repeatable sections, GenericCustomField mappings, initial values, translations |
| Data lost after a template change | Template Upgrade eligibility and destructive change types (KBA 3232993) |
| Supplier not syncing / status stuck In Progress | Minimum-status trigger, then payload generation; sync status is not sync success |
| ERP Vendor ID shows a VDR… number | Never integrated, or the key mapping never came back — a reconciliation finding |
| maxLength / MinOccurs / “not defined for country” errors | Field mapping catalogue and character limits — a design concern, not a UAT one |
| Mass operation reported success but did nothing | Reconcile counts and download the import summary from SM Administration |
Two habits pay for themselves. Silent success is the dominant failure mode of bulk operations — mass invites that send nothing, imports that report success and create no records — so reconcile record counts every time. And scope regression testing outside SLP whenever supplier status or the supplier data model changes: deactivating a supplier in SLP also deactivates it in Buyer, and registration status can gate sourcing-event access.
Build order, and what you see if you invert it
| # | Do this first | What you see if you invert it |
|---|---|---|
| 1 | Confirm entitlement and raise every SM-/ARI- enablement request | Supplier Management simply missing from the site; some features need a support case, which is calendar time |
| 2 | Establish the SAP Business Network account strategy | Buyer-side configuration complete and correct while no supplier can see anything |
| 3 | Load organizations and groups before users | FatalAssertionException: User with UniqueName … and PasswordAdapter … not found |
| 4 | Load commodity codes, regions and departments before templates | A matrix-driven qualification template references master data that isn't there |
| 5 | Decide the Request / Registration / SPQ / modular split before mapping a field | ERP-bound fields stranded in modular questionnaires. Not reversible by parameter |
| 6 | Build and validate the User Matrix before testing any approval flow | Days debugging the approval layer for a fault in the matrix |
| 7 | Publish the template before expecting users to see it | Nothing — and it's a three-layer failure: publish state × template access × group membership |
| 8 | Enable the modular questionnaire framework before planning certificate expiry | Certificates ship with modular questionnaires; there is no certificate-only path |
| 9 | KPI library → SPM template allows KPI documents → SPM projects | “Can't add selected items because of template rules” |
And one ordering that is a cutover, not a sequence. Enabling process rollout (SM-16798) blocks new legacy-style qualifications outright. The source does not document whether it can be reversed. Decide before production, not during hypercare.
Configuration checklist
Foundations and data
- Supplier Management entitlement confirmed before any configuration diagnosis.
- Unified Vendor Model migration scoped, with supplier data cleaned before it runs.
- Site architecture (new / classic) confirmed — it determines modular-questionnaire availability.
- Enablement requests raised early for every SM-/ARI- feature in scope.
- SAP Business Network account strategy agreed and on the go-live plan.
- Commodity codes, regions and departments loaded before template design.
- Organizations and groups loaded before the users that reference them.
- Export before every import; verify record counts and never trust an import success message.
Design, approvals and integration
- Request / Registration / SPQ / modular split decided before a single field is mapped.
- Answer types kept consistent across request → registration (Address ≠ Extended Address).
- Conditions inside repeatable sections minimised.
- Bank, tax and address fields designed against the actual supplier country list.
- User Matrix built and validated before any approval flow is tested.
- Group licensing checked before assigning SM Ops / SM ERP Administrator.
- Two integration tiers planned, not three — the managed gateway supports Test and Production only.
- ERPVendorID uniqueness and casing enforced at the integration layer.
- Reconciliation report built: SLP suppliers with no ERP Vendor ID.
- No live questionnaire template edited without rehearsing the upgrade in a test realm.
Glossary
- SLP
- SAP Ariba Supplier Lifecycle and Performance — request through registration, qualification, preferred status, disqualification and discontinuation
- UVM
- Unified Vendor Model — the centralized supplier data model required for SLP; adopting it from supplier organizations is a one-time migration
- ANID
- Ariba Network ID — the SAP Business Network identity held on the SM vendor record
- SPQ
- Supplier Profile Questionnaire — durable profile, capability and certification data
- Modular questionnaire
- Re-issuable, cycle-driven questionnaire. Not available in SIPM classic architecture; answers never reach an integrated ERP
- User Matrix
- Undocumented but first-class SLP object driving approver, owner and Team-tab resolution from commodity, region and buyer category
- Template Upgrade
- The mechanism that carries template changes to existing projects. Eligibility is state-dependent and some changes destroy answer data
- Matrix point
- The commodity / region / department combination that qualification uniqueness is enforced against
- Managed gateway
- SAP Integration Suite, managed gateway for spend management (formerly CIG). Test and Production only — there is no DEV integration tier
- Process rollout (SM-16798)
- The modular process framework. Once enabled, new legacy-style qualifications are blocked; reversibility is undocumented
Grounded in SAP Help Portal documentation at release 2605 and 1,066 indexed supplier management and supplier risk articles within a corpus of 13,050 SAP KBAs and Notes (2013–2026). Where the source material is silent, this guide says so rather than filling the gap.