bdc-troubleshooter

name

bdc-troubleshooter

description

Use ONLY for SAP-Note symptom→fix lookup — i.e. when the user pastes a specific BDC/Databricks error message, cites an SAP Note number in the 34xxxxx–37xxxxx range, or describes a concrete failure (provisioning stuck, CSN publish errorCode 500, OIDC code exchange failure, duplicate hostname, orphan data product, SCIM "only one replace" error, Azure storage 403/AuthorizationFailure, metastore owner share error, negative dates from SAP, Business Name missing in Unity Catalog, HANA Cloud missing from Customer Landscape, CIS integration not configured). For "how do I..." / setup / configuration / conceptual questions, DEFER to the right skill instead — bdc-onboarding, bdc-core-admin, bdc-governance-catalog, bdc-connect-sharing, bdc-intelligent-apps, or sap-databricks. Trigger phrases include "BDC error", "errorCode 500", "AuthorizationFailure", "oidc_code_exchange_failure", "only one replace operation", "tenantHostName invalid", "orphan data product", "Business Name missing", "metastore owner", "HAR file Databricks".

SAP BDC Troubleshooter (symptom-lookup only)

Narrow skill: given an error message or a described failure, return the matching SAP Note, the one-line cause, and concrete steps — nothing else. Curated against 22 SAP Notes (18 from the 2026-04-13 batch + 4 new from the 2026-04-15 batch) plus 4 procedural rules from the 2026-05-02 SAP help.sap.com batch.

Scope rule

In scope (use this skill):

• User pastes an error message or stack trace
• User cites an SAP Note number
• User describes a failure whose symptom matches the tables below

Out of scope (route elsewhere):

• "How do I set up BDC?" → bdc-onboarding
• "How do I manage users / configure SCIM / monitor capacity?" → bdc-core-admin
• "How do I publish / enrich a catalog asset?" → bdc-governance-catalog
• "How does BDC Connect / Delta Sharing work?" → bdc-connect-sharing