BusinessGPS Intelligence
The Capability Brief — SAP Compass
Strategic navigation for SAP customers in the agentic era. What vendor announcements actually mean for your roadmap, your stack, and the decisions you can't defer.
Two SAP pages, two dates: October 2026 and December 31, 2026. Ask SAP which applies to the runtime you use.
On 6 October 2026 SAP put availability dates on its assistants, and the German-speaking user group DSAG said the same day that robust customer experience of Joule Work is so far missing. An SAP News piece of 28 September 2026 says Joule Studio runtime is free through October 2026; SAP Help says free access to runtime execution is valid until December 31, 2026. This edition prints both, gives a filled-in plan with SAP's page and date beside every line, and gives one question for your next steering meeting.
Three Cheques, One Supply Chain — SAP Is Buying the Ground the Agents Will Stand On
SAP’s three now-closed acquisitions — Reltio, Dremio and Prior Labs — assemble a single capability: the trusted data foundation agents run on. The move is more defensible than its headline, and one clock is already running: the Joule and agent free tier ends 31 December with no 2027 price.
Forced Open, Metered Shut
Two gates moved in opposite directions in one fortnight. Forced open: the EU settlement kept prising the support market open, with Rimini on record and launching a governance product, though its rivals stayed silent a fourth fortnight and no customer has yet cited the settlement as a switch trigger. Metered shut: SAP's interface policy is now enforced in code, routing third-party AI agents through Joule and its Agent Gateway, with the free Joule window closing 31 December 2026 and 2027 pricing undisclosed — Forrester calls it a metered access layer. The quarter's numbers show the meter being built: cloud up 24% and backlog up 26%, with cloud margin dipping as the gateway is paid for. The settlement opened your support options; the same fortnight SAP metered the AI gate — price both at the renewal, not after.
The Wave Arrived: the First Vendor Spoke, and the First Customer Had Already Left
Rimini Street's Q2 results made its CEO the first third-party maintenance vendor on record about the EU settlement — revenue beat, earnings missed, and the verdict came hedged: more customer choice, 'not everything we all would want' — while rivals stayed silent a third fortnight. The proof sits earlier in time: Kingfisher rejected S/4HANA, moved ECC support to Rimini and built AI directly on ECC data before the settlement existed — precedent, not consequence — which is exactly why the remedy matters: it makes a route one retailer took the hard way cheaper and partly reversible for everyone else, while SAP's agent-access gate stays shut by choice and the December decision clocks run on.
The Number Came In, and It Proved the Paradox
SAP's Q2 print resolved the number the previous edition set as the tell: current cloud backlog grew 26% at constant currency to €22.93bn, clearing the bar it missed in January, while on-premise software licences fell 32% and the EU maintenance settlement sits restated inside the same release — the cloud-steering paradox now visible in the vendor's own accounts. The honest asterisk is the profit line: full-year operating-profit guidance cut to €11.8–12.2bn partly on elevated AI token costs, EPS of €1.59 missing the €1.76 consensus, and UBS cutting its target to €164 — the engine works, and the price of running it is the new question.
The Support Gate Opened, and the Counter-Move Has a Price
Two weeks after Brussels made SAP's maintenance commitments binding for ten years, the first verdicts landed: Gartner says the ruling shatters the historical barriers to third-party support and tells customers to re-price the vendor's deadline on their own terms; a DSAG board voice says ECC customers who leave will not come back; UKISUG carries the counter-weight that extended maintenance remains the lower-risk bridge. The analytical lead is the paradox in the remedy's own scope — it protects the on-premise estate only, which strengthens the commercial pull toward RISE subscriptions where none of the protections reach, a pull the standing migration credits already price. Q2 results on 23 July are the next tell: watch cloud backlog growth against the bar the January print missed.
Forced Open, Bolted Shut: Brussels Opens the Maintenance Layer, the API Policy Holds the Agent Door
On 9 July the European Commission closed case AT.40823 with SAP commitments accepted as legally binding worldwide for ten years — reinstatement fees abolished, back-maintenance reduced, an alternative licence-fee calculation, and partial third-party maintenance permitted, on-premise only — while in the same fortnight API Policy Section 2.2.2's gating of third-party AI agents was corroborated across the trade press and the 2017 AB InBev lawsuit was publicly re-read as agentic-era precedent. A regulator can lower the cost of leaving; only the customer can build the capability to exercise the freedom — the maintenance line, the sanctioned-API perimeter, and the December decision clock now belong in the same Q3 planning document.
The Decision Clock: Enforcement Is Live, the December Window Is Running
Four weeks into the 9 June ODP-RFC enforcement, the opt-out mechanism (SAP Note 3731818) is confirmed active post-enforcement — its precise meaning is a commitment to the December 2026 hard-cutover window, not a deferral, because customers who applied it are on the Note 3439624 clock whether they understood it as a commitment or not. The eighth consecutive analyst drought cycle holds; the IBM + SAP A2A interoperability announcement (2 July) brings the own-vs-rent question to the delivery layer — IBM owns the engine, clients rent the outcome — while the Microsoft Fabric ABAP Add-on path remains the documented migration target for ODP-RFC-dependent pipelines whose December planning window is now a timed obligation.
The Migration Runway and the December Clock: What Three Weeks of Enforcement Mean for 2026 Decisions
Three weeks after the 9 June ODP-RFC enforcement trigger, the analyst quiet holds into a seventh consecutive cycle — still no post-enforcement retrospective from Gartner, Forrester, Constellation, Diginomica, or SAPinsider, stated as the confirmed absence of noise — while the migration runway has sharpened: Microsoft's 'Copy Job in Fabric for SAP with ABAP Add-on' is now generally available as a documented migration path to a new architecture, not a connector fix. The governing date remains December 2026 — when the customer-applied fallback (SAP Note 3439624) expires — and the durable, date-independent point is unchanged: the customer's defensible territory is its own contract language, whatever the migration timeline.
The Second Quiet: What Twelve Days of Silence Do and Do Not Tell Us, and the Date That Actually Matters Next
Twelve days after the 9 June ODP-RFC enforcement trigger the analyst quiet holds into a sixth consecutive cycle — read honestly as the confirmed absence of noise, not of disruption — but concrete breakage is now on the record, with Security Note 3748819 the live blocking instrument and the Microsoft Azure Data Factory SAP CDC connector confirmed affected. The date that actually governs what comes next is not 9 June but the December 2026 rollback expiry; the durable, date-independent point remains the Contract Boundary.
The Patch Landed: What Enforcement Looks Like in Its First Week, and the Boundary That Did Not Depend on the Date
SAP's ODP-RFC enforcement patch went live on 9 June, and five days on the public record shows no mass customer disruption — a silence that is itself material, consistent with either pre-remediation or phased enforcement. The durable customer-side point is unchanged and date-independent: the Contract Boundary, where enforceability turns on the customer's own agreement rather than the vendor's posted policy or its softened words.
The Words and the Policy: What Moved in the SAP Ecosystem This Week, and the Boundary That Holds Regardless
SAP has softened its words on the third-party API policy without softening the enforceable policy text; the 9 June enforcement is a development in motion, not a cliff. The durable customer-side point is the Contract Boundary — enforceability turns on the customer's own agreement — with Ericsson's 85,000 live Joule users underlining that data foundation and ownership are the prerequisite the customer keeps.
After Madrid: The 77 Percent Voted on the Discipline.
Fourteen days after Madrid, the customer-side evidence has arrived. Seventy-seven percent of DSAG members using AI productively in 2026 will use non-SAP solutions; three percent will rely on SAP's AI tools. That is the Capability Sovereignty discipline already in operation across the largest organised SAP customer cohort. Eight days from publication, SAP's API policy enforcement window closes on 9 June 2026. The Forrester analyst register has escalated from concentration-risk to gatekeeper.
After Madrid: Sovereignty Became a Product. The Discipline Did Not.
Madrid was the European answer to Orlando. SAP launched EU AI Cloud as a discrete Sovereignty Product with four dimensions — data, operational, technical, legal. Two substrate vendors have converged on a four-dimension framing in 90 days. Substrate Sovereignty is a product; Capability Sovereignty is the customer-side discipline upstream of it, and no substrate vendor will name it on your behalf.
After Sapphire: The Substrate Opened. The Engagement Layer Closed.
Klein gave you open substrate at the tier SAP does not control and constrained engagement at the tier SAP does. The capability discipline that turns Sapphire's partner density into sustainable competitive advantage is the work that is now yours — and no vendor will name it on your behalf.
Agentic SAP. Now What?
First edition of SAP Compass — strategic navigation for SAP customers in the agentic era. Five questions every SAP customer is now asking, with directional scenarios for the Sapphire Orlando keynote.