JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

July 18, 2026 · 11 min read

SAP Service Cloud Knowledge Base Provider

Knowledge Base Provider is SAP Service Cloud’s configuration record that connects the native Agent Desktop widget to an external knowledge base — powering recommended articles tied to the open Case or Registered Product, in-widget article search, a top-trending-articles list, copy-URL, and send-as-email. Unlike Email Channel (SC-A03-01) or Email Template (SC-A03-02), it is not a single flat master record: it is a Communication Configuration copied from one of three provider-type templates (NICE CXone Expert/Mindtouch, SAP Build Work Zone, or Generic), plus — only when the provider is Mindtouch — a separate credentials sub-record entered under Provider Settings. This article maps both layers, the widget-consumption behavior that depends on them, and the objects Knowledge Base Provider deliberately does not connect to.

Part 1: Knowledge Base Provider — Core Concepts (All Modules)#

1.1 What Is the Knowledge Base Provider?#

Knowledge Base Provider represents the connectivity that lets the Agent Desktop’s native Knowledge Base widget pull content from an external knowledge base system — it is a configuration record, not the article content itself. It exists so that recommended-article suggestions, in-widget search, and a trending-articles list can run against a live third-party knowledge base without custom development: the administrator points a Communication Configuration at the provider’s API endpoints and, for one specific provider type, supplies that provider’s credentials in a second, conditional record.

1.2 Provider Types#

Knowledge Base Provider is not authored as a blank record. Administrators copy one of three pre-built templates at System Settings > Integration > Communication Configuration, and which template is copied determines both the API shape expected on the two HTTP Data paths and whether a second configuration layer (Provider Settings) is required at all.

Design principle: Provider Type template selection is the single decision that determines whether a second configuration layer exists at all. Mindtouch is the only one of the three that requires completing Provider Settings; the other two stop at the Communication Configuration.

1.3 Organizational Levels and Data Hierarchy#

Data hierarchy with a concrete example (Zone E · Communication & Knowledge — tenant-level; SAP Service Cloud has no Company Code / Plant scoping above this)

Client (SAP Service Cloud Tenant)
   │
   ├── Communication System "COMSYS-KB-EXPERT" — outbound protocol HTTPS (Integration prerequisite, created first)
   │
   └── Communication Configuration "KB-PROVIDER-01" — copied from template "NICE CXone Expert (Mindtouch)"
           HTTP Data: "Retrieve articles based on..." API path · "Get Top Trending Articles from..." API path · Active: Yes
           │
           └── (Mindtouch template only) Provider Settings — "Knowledgebase Providers > NICE CXone Expert (Mindtouch)"
                   User: kb-integration-account · Key: •••••••• · Secret: ••••••••

Communication Configuration "KB-PROVIDER-01" ── read at runtime by ──> Agent Desktop native Knowledge Base widget (Customer Hub)
                                                                            └── recommended articles keyed off the linked Case or Registered Product

Design principle: Communication System sits above Communication Configuration as a true prerequisite — it must exist first. Provider Settings is a conditional child scoped only to the Mindtouch template; do not draw it as a step that applies uniformly to all three provider types, since SAP Build Work Zone and Generic providers never populate it.

1.4 Integration with Other Master Data Objects#

Knowledge Base Provider’s only true dependency runs upstream, to the generic Integration objects it is built on — its relationship to Case and Registered Product runs the other way, as a live read at widget display/search time, never as a stored field-level reference. It is worth being explicit about the objects it does not connect to, since Zone E’s other two members (Email Channel, Email Template) invite the same “is this object secretly wired to Case Type or routing?” question.

Scope note: SAP’s current Set Up Guide documents the Communication Configuration + Provider Settings path above as the native-widget mechanism. An older HTML Mashup / OpenSearch-based integration path — referenced in SAP Support knowledge base content and in the Mindtouch/NICE vendor’s own documentation — is described as usable for third-party OpenSearch-compliant providers outside the three built-in templates. This research did not find an SAP-official reconciliation of the two mechanisms; treat the mashup path as a documented alternate/legacy pattern, not one resolved into or superseded by the native widget with full certainty. Separately, whether this same admin-configured record also drives an external customer self-service portal (as opposed to only the internal Agent Desktop widget) is documented only in the knowledge-base vendor’s own materials, not confirmed by SAP-official Service Cloud V2 documentation — treat as an open item, not a confirmed capability.

Part 2: SC-Specific Field Details#

2.0 Scope of SC Ownership#

Legend: ◎ = Owner / Critical, ○ = Direct involvement

2.1 Communication Configuration (Base Connectivity)#

This is the layer every Knowledge Base Provider configuration goes through, regardless of which vendor sits behind it — get these fields right and the widget can at least call out to the provider.

Prerequisite: A Communication System (outbound protocol HTTPS) must already exist before this Communication Configuration can be created — configure it first at System Settings > Integration > Communication System if one does not yet exist for this provider’s host.

2.2 Provider Settings (Mindtouch/NICE CXone Expert Credentials)#

This second layer only exists for one of the three provider types — it carries the account credentials the widget authenticates with when calling out to a Mindtouch-based knowledge base.

Prerequisite: This section only applies when the Communication Configuration in Section 2.1 was copied from the NICE CXone Expert (Mindtouch) template — SAP Build Work Zone and Generic providers skip this step entirely.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction