Skynome ABAP Azure SDK: Announcing Our Open-Core Roadmap
Microsoft's ABAP SDK for Azure gives you transport. It does not give you ADLS2, Fabric, governance logging, PII classification, or CDC watermarks. We are building the open-core governance layer on top — Community Edition on GitHub, Professional Edition licensed — targeting ECC 6.0 and S/4HANA with a December 2026 v0.1 release.
This is a roadmap announcement, not a shipping release. Transport files are not available yet. v0.1 Community Edition is targeted for December 2026. If you need architecture help before then, the ABAP Push pattern is already documented — and our ODP Compliance Review engagements are open now.
In our review of the Microsoft ABAP SDK for Azure, we said the quiet part out loud: Microsoft built a solid transport library. It did not build a production governance layer.
That gap is why Skynome exists in this space. Today we are publishing the open-core roadmap for the Skynome ABAP Azure SDK — the modules we will ship on top of Microsoft's foundation, under the registered /SKYN/ namespace, for SAP ECC 6.0 and S/4HANA systems that need compliant Azure extraction after the ODP-RFC ban.
The Problem We Are Solving
After June 9, 2026, non-SAP tools that used ODP via RFC are blocked. The temporary fallback expires in December 2026. The architectural replacement is not another pull connector. It is ABAP Push: code inside SAP initiates outbound HTTPS to Azure.
Microsoft's SDK covers Event Hubs, Service Bus, Blob Storage, Key Vault, Entra ID auth, and Azure OpenAI. That is necessary infrastructure. It is not sufficient for a governed analytics landing zone.
What most ECC and S/4 teams still need:
- ADLS2 hierarchical namespace writes — required for Fabric OneLake and Synapse Delta Lake landing zones
- Microsoft Fabric push — first-class path into Lakehouse, not a Blob workaround
- Structured audit logging — every push recorded with source, watermark, byte count, and HTTP status
- Field-level PII classification — mask, tokenise, or exclude before serialisation
- CDC watermark management —
CDHDR/CDPOSdeltas without ODP - Telemetry to Azure Monitor — latency, volume, and failure signals outside SAP
Those are the modules we are building. Microsoft's SDK remains the transport foundation. Skynome does not replace it.
What We Are Building
| Module | Purpose | Edition |
|---|---|---|
| /SKYN/CL_AUTH | Entra ID client-credentials token manager | Community |
| /SKYN/CL_HTTP | ICM outbound HTTPS wrapper | Community |
| /SKYN/CL_ADLS2 | Azure Data Lake Gen2 hierarchical write | Community |
| /SKYN/CL_EVENTHUB | Event Hubs push for streaming / CDC | Community |
| /SKYN/CL_LOGGER | Structured audit log to /SKYN/SDK_LOG | Community |
| /SKYN/CL_CDC | Watermark manager for change-document deltas | Community |
| /SKYN/CL_PII | Field classification + mask / tokenise / exclude | Professional |
| /SKYN/CL_METER | Azure Monitor custom metrics emitter | Professional |
| ECC extraction templates | BKPF/BSEG, VBAK/VBAP, MKPF/MSEG, master data | Professional |
The Microsoft SDK stays installed alongside. Where Skynome modules need HTTP or auth primitives that Microsoft already solved well, we delegate — we do not fork a parallel transport stack.
Open-Core Model
Community Edition (MIT, free)
Transport files on GitHub. Auth, HTTP, ADLS2, Event Hubs, logger, and CDC watermark core. Enough to prove the ABAP Push pattern on a development system and land governed payloads in ADLS2.
Professional Edition (commercial licence)
Same Community core, plus PII classification, Skynome Meter telemetry, pre-built ECC extraction templates, and licence validation against api.skynome.com. Priced per SAP system — designed for production estates that need audit-ready instrumentation, not just a successful POST.
This is the same open-core shape Google proved with cloud ABAP SDKs: a free foundation that earns trust, and a commercial layer that pays for governance depth.
Target Platforms
| Platform | Minimum | Notes |
|---|---|---|
| SAP ECC 6.0 | EhP5+, BASIS 702+ | Explicit v0.1 test target — not an afterthought |
| SAP S/4HANA | 1909+ | Same /SKYN/ objects; Clean Core packaging later |
| Azure | ADLS2, Event Hubs, Entra ID, Monitor | Fabric Lakehouse via ADLS2/OneLake path in v0.1 |
Distribution is standard SAP CTS: .cofile + .datafile pairs imported via STMS. No agent on an external server. No ODP subscription. Outbound HTTPS through ICM only — the pattern SAP still allows.
Roadmap
| Milestone | Target | What ships |
|---|---|---|
| Spec locked | July 2026 | ✅ Public technical direction (this post + prior reviews) |
| Partner build start | Q3 2026 | ABAP partner engaged; /SKYN/ namespace registration in flight |
| v0.1 Community | December 2026 | Auth, HTTP, ADLS2, Event Hubs, Logger, CDC core + GitHub transports |
| v0.2 Professional | Q1 2027 | PII, Meter, ECC templates, licence validation |
| ECC Data Bridge | Q1–Q2 2027 | Packaged architecture: SDK + job templates + Azure ARM + compliance runbook |
| SAP AppCenter | Later | Certification path after namespace + production references |
December 2026 is not an arbitrary marketing date. It lines up with the ODP fallback expiry. Teams that start ABAP Push design now will have a tested path when the temporary mechanism ends. Teams that wait for a polished marketplace listing will be late.
What This Is Not
- Not a replacement for the Microsoft ABAP SDK for Azure. Install both.
- Not available for download today. Do not plan a production cutover on vapour.
- Not an ODP wrapper. No
RODPS_REPL_*. No RFC pull from Azure into SAP extraction APIs that SAP has banned. - Not a Datasphere substitute. If you want SAP's licensed stack, buy SAP's licensed stack. This is for Azure-native estates that need compliant push from ECC/S/4.
What You Can Do Now
- Read the architecture posts — ABAP Push Architecture and the Microsoft SDK review.
- Score your exposure — GRS Domain 7 turns ODP risk into a number your steering committee can act on.
- Run Note 3439624 in non-production first — know which pipelines still depend on the fallback.
- Design your landing zone — ADLS2 container layout, Entra ID app registration, ICM outbound, STRUST certs. The Azure side can be ready before ABAP code lands.
- Contact us if you want an ODP Compliance Review or an ABAP Push architecture workshop while the SDK is still in build.
Why We Are Saying This Early
Roadmaps that stay private create two failure modes: customers invent incompatible custom Z-code that they will later regret, and partners cannot plan capacity against a real module list.
Publishing the open-core shape now lets BASIS, data, and security teams align on /SKYN/ as the intended governance layer — and lets us take design feedback before transport files freeze.
If you are an ABAP shop that has already built ADLS2 or CDC helpers on top of Microsoft's SDK, we want to hear what broke in production. That feedback shapes v0.1 acceptance criteria more than any slide deck.
Skynome is independent of Microsoft and has no affiliation with the Microsoft ABAP SDK for Azure project. The Skynome ABAP Azure SDK is a separate product that builds on publicly available Microsoft transport patterns. SAP namespace /SKYN/ registration is in process. Module names and edition boundaries may adjust as partner testing proceeds; breaking changes before v0.1 will be noted in subsequent posts.
How governed is your SAP estate?
The Governance Readiness Score measures your SAP on Azure environment across 9 domains — from AI sovereignty to data extraction compliance. Get your score.
Get Your Governance Score