Data Product Data Governance in SAP Business Data Cloud (SAP Community blog)
Tag: S-2026-09-09-sap-bdc-data-product-governance Type: article (vendor blog — SAP Community “Technology Blog Posts by SAP”) Author(s): not captured (page did not render); SAP employee post Date of source: 2026-09-09 (stated deployment date of wave 2026.19; blog publication date not captured) Date ingested: 2026-09-10 Authority weight: low — vendor blog, and captured only through search-engine excerpts because the page is JavaScript-rendered and returned empty on fetch; the excerpts are specific and internally consistent but partial Raw file: S-2026-09-09-sap-bdc-data-product-governance.md
What it claims
SAP Business Data Cloud (SAP BDC) gains a “data product data governance” capability in wave 2026.19, with live deployments “planned for Wednesday, September 9, 2026”. It replaces direct permissions and manual sharing with a request-based access model for data products: requests are tracked, reviewed and recorded as access agreements. A Data Steward, acting on behalf of the Domain Owner, reviews each request against the domain’s governance policies and approves or rejects it, with the decision documented either way. The post says the previous mechanisms captured neither why access was requested, who reviewed it, nor how long it should last; the new capability adds a formal request lifecycle and a centralised Governance area in the SAP BDC cockpit. Additional approver roles — the examples given are Legal, Works Council and Budget Responsible — can be inserted into the workflow where regulatory or organisational policy requires it, which SAP frames as a compliance requirement rather than an edge case in regulated industries and the public sector.
Notable quotes
“Rather than relying on direct permissions and manual sharing, governance shifts access management to a request-based model — one where requests are tracked, reviewed, and recorded as access agreements.” (search excerpt)
“Neither mechanism captured why access was requested, who reviewed it, or how long it should last.” (search excerpt)
“in regulated industries and public sector organizations, multi-party approval is a compliance requirement, not an option.” (search excerpt)
What’s speculative vs. asserted
- Asserted (vendor): the capability, its wave number, the request/steward/domain-owner model, access agreements, the cockpit Governance area, configurable additional approvers.
- Forward-looking: “live deployments planned for” 9 September — completion of the rollout is not confirmed by any source read.
- Unverified / framing: that multi-party approval is a “compliance requirement” — no regulation is named.
- Not captured: the full post (author, date, screenshots, permission model details, regional availability, licensing tier). All claims above are limited to the excerpted passages.
Topics this feeds
- SAP — company page (created from this source).
- Agentic Data Access Governance — topic: adds an ERP-platform instance of request-based, documented data-product access alongside the catalogue/access vendors already tracked; this instance is human-workflow governance, not agent-facing.
Open questions raised
- Does the access-agreement record (requester, reason, reviewer, decision, duration) persist and export as an audit artefact, and for how long?
- Does the request model apply to programmatic/agent consumers of data products, or only to named users?
- Which SAP BDC editions/regions received wave 2026.19 on 9 September, and is EU data residency affected? [not addressed]