Skynome ABAP Azure SDK
Microsoft's ABAP SDK for Azure moves bytes. Skynome adds ADLS2, Fabric, audit logging, PII classification, and CDC watermarks — under the registered /SKYN/ namespace.
Roadmap announcement · v0.1 Community target December 2026 · transport files not yet available
After June 9, 2026, non-SAP tools that used ODP via RFC are blocked. The temporary fallback expires in December 2026. The replacement architecture is ABAP Push: code inside SAP initiates outbound HTTPS to Azure.
Microsoft's open-source SDK covers Event Hubs, Service Bus, Blob, Key Vault, Entra ID, and Azure OpenAI. That is the foundation. Production analytics estates still need the governance layer Microsoft did not ship.
Skynome installs alongside the Microsoft SDK — it does not replace it.
Community Edition covers the push and audit core. Professional Edition adds PII classification, Meter telemetry, and ECC extraction templates.
| 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 CDHDR/CDPOS deltas | Community |
| /SKYN/CL_PII | Field classification + mask / tokenise / exclude | Professional |
| /SKYN/CL_METER | Azure Monitor custom metrics emitter | Professional |
Professional also includes pre-built ECC templates for BKPF/BSEG, VBAK/VBAP, MKPF/MSEG, and common master-data tables.
Community · MIT · Free
Auth, HTTP, ADLS2, Event Hubs, logger, and CDC watermark core. Enough to land governed payloads in ADLS2 from a development system and validate ABAP Push before production cutover.
Professional · Licensed
Community core plus PII classification, Skynome Meter telemetry, ECC extraction templates, and licence validation. Priced per SAP system for estates that need audit-ready instrumentation.
Scheduled jobs and exits inside ECC or S/4 push over ICM outbound HTTPS. No ODP subscription. No external extraction server. No RFC port exposure to Azure.
SAP (ECC / S/4)
└─ ABAP job / exit
├─ /SKYN/CL_AUTH → Entra ID token
├─ /SKYN/CL_PII → classify / mask (Professional)
├─ /SKYN/CL_* → ADLS2 | Event Hubs | Logger | CDC
└─ ICM outbound HTTPS :443
└─ Azure (ADLS2 · Fabric · Event Hubs · Monitor)EhP5+, BASIS 702+ — explicit v0.1 test target
1909+ — same /SKYN/ objects
ADLS2, Event Hubs, Entra ID, Monitor; Fabric via OneLake path
v0.1 Community is timed to the ODP fallback expiry — so teams that start ABAP Push design now have a tested path when the temporary mechanism ends.
July 2026
Public technical direction published.
Q3 2026
ABAP partner engaged; /SKYN/ namespace registration in flight.
December 2026
Auth, HTTP, ADLS2, Event Hubs, Logger, CDC core + GitHub transports.
Q1 2027
PII, Meter, ECC templates, licence validation.
Q1–Q2 2027
Packaged architecture: SDK + job templates + Azure ARM + compliance runbook.
Not available for download today. Do not plan a production cutover on vapour. Use the interim to score ODP exposure, design the ADLS2 landing zone, and configure ICM / Entra ID — then import transports when v0.1 ships.
ODP Compliance Reviews and ABAP Push architecture workshops are open now. Tell us about your ECC or S/4 estate — we'll map which modules you need and what can be ready on the Azure side before code lands.
Related: ABAP-Native Data Bridge · GRS Domain 7