SAP Note 3439624: Run This Self-Assessment Before Your December Deadline

When SAP activated the June 9, 2026 security enforcement behind Note 3255746, it simultaneously published a companion note that most teams have not noticed. SAP Note 3439624 is not a fix. It is not a workaround. It is a diagnostic — a self-assessment ABAP report that scans your SAP system and produces a complete picture of every active ODP-RFC consumer, every extraction tool using it, and every data volume flowing through it.

The note is called Self-Assessment for ODP RFC Usage. SAP published it precisely because they knew the enforcement would be a shock and that most organisations would not know where to start.

Start here.

---

What Note 3439624 Actually Does

The report queries your SAP system's ODP framework metadata — the same infrastructure that the ODP replication API sits on top of. It surfaces three categories of information:

Active subscribers. Every RFC destination that has registered as an ODP subscriber. If ADF, Fivetran, Qlik, Talend, or any other tool has ever extracted from this system via ODP, it appears here with its last active timestamp.

Extraction volumes. For each subscriber, the report shows the cumulative volume of data extracted: row counts, byte volumes, delta watermarks. This is the data you need to prioritise which pipelines matter most.

Data objects accessed. The specific ODP extractors being consumed — which tables, which BW DataSources, which CDS views. This tells you what the downstream system is actually receiving and what you need to replicate via a compliant method.

None of this information requires consulting your data engineering team or your cloud provider. It is all in the SAP system, because ODP was always an SAP-side framework. The question was never whether SAP knew about it — it was whether you did.

---

Step-by-Step: Running Note 3439624

Step 0 — Apply the Note

Go to SAP Support Portal → Notes & Knowledge Base → search 3439624. Download the attached correction file and apply it via transaction SNOTE (Note Assistant).

This requires BASIS-level access. If you do not have it, send the note number to your BASIS administrator with the message: "SAP Note 3439624 — ODP RFC self-assessment. Required for compliance. Apply and run ABAP report."

Application time: under 30 minutes for a BASIS admin who knows their system.

Step 1 — Run the ABAP Report

After applying the note, the report is available via transaction SE38 (ABAP Editor) or SA38 (Programme Execution). The programme name is documented in the note itself.

Execute the report with the following parameters:

• System scope: Select all clients if you are running a single-client production system. In multi-client landscapes, run in your production client.
• Date range: Set to the past 12 months to capture all active subscribers. Some tools may not have run recently but are still configured.
• Output format: ALV grid, exported to spreadsheet. You will need this for your migration planning.

Runtime: 5–20 minutes depending on system size and ODP history volume.

Step 2 — Read the Output

The output is structured as a table with the following columns you need to focus on:

| Column | What It Means | |---|---| | RFC Destination | The SAP RFC connection name — often matches your tool's connector config name | | Last Extraction | Timestamp of most recent successful ODP-RFC pull | | Total Rows Extracted | Cumulative row count — use this to understand migration scope | | Extractor / DataSource | The specific ODP object being consumed | | Subscriber Status | Active, Inactive, or Unknown |

Any row with Active status and a last extraction timestamp after June 9, 2026 means you are on the temporary fallback mechanism. That pipeline is running on borrowed time.

Step 3 — Classify Your Exposure

Group your results into three tiers:

Tier 1 — Active, high volume, production-critical. These are pipelines where the last extraction was recent, the row volume is large, and the downstream system (data lake, data warehouse, BI tool) depends on them for operational reporting. These are your migration emergency.

Tier 2 — Active, lower volume or non-critical. These pipelines are technically affected but can tolerate a short interruption. Plan migration within 60 days.

Tier 3 — Inactive or historical. Subscribers with no extractions in the past 90 days. Decommission the configuration rather than migrate it — if nobody noticed the extraction stopped, it may already be obsolete.

---

What the Results Tell You About Your Options

Once you have the Note 3439624 output, the migration path depends on what the extractor type is:

The extractor type is the fastest way to scope the migration effort. BW DataSources can typically switch to DeltaQ within days. Table-based extractions need RFC Table Read or an ABAP Push pattern — that is a larger change, but it is architecturally clean and SAP-compliant.

---

The December 2026 Deadline Is Not Theoretical

SAP has confirmed that the temporary fallback mechanism — the mechanism keeping ODP-RFC pipelines alive for systems that have not yet applied the June 2026 security patch — expires in December 2026. The exact date has not been published, but "December 2026" is the commitment from SAP.

After that date, there is no documented path to restore ODP-RFC functionality. There is no extension. There is no waiver process. The function modules that implement ODP replication (RODPS_REPL_*) will be permanently inaccessible to third-party consumers.

The five-step plan for the next 30 days:

1. Run SAP Note 3439624 — get your complete exposure list. (Week 1)
2. Classify by tier — identify your production-critical pipelines. (Week 1)
3. Architect your replacement — RFC Table Read, OData, or ABAP Push. (Weeks 2–3)
4. Test in a non-production client — validate the new pipeline returns identical data. (Week 3–4)
5. Cut over and decommission — remove the ODP-RFC subscriber registration. (Week 4)

---

What the Note Does Not Tell You

Note 3439624 tells you what is using ODP-RFC. It does not tell you what to build next, and it does not validate that your replacement architecture is compliant.

This is where the risk sits for most teams. The easy trap is to see "RFC Table Read" as a replacement, implement it, and assume the problem is solved. For many scenarios, it is. But RFC Table Read gives you table-level granularity with no native delta — you are effectively full-loading the table every run. For large tables (VBAK, BSEG, ACDOCA), that is not a production-viable architecture.

The architecturally correct replacement for high-volume delta scenarios is the ABAP Push pattern: ABAP code running inside SAP that detects data changes and pushes them outbound via HTTPS to Azure Data Lake, Event Hubs, or Microsoft Fabric — no RFC extraction, no external tool polling the SAP system, no reliance on ODP at all. It is what Google's ABAP SDK does for Google Cloud, and it is the pattern Skynome's ABAP Azure SDK is being built to implement for the Microsoft stack.

---

Where Skynome Fits

Immediate: Run a Governance Readiness Score assessment — Domain 7 of the GRS framework covers data extraction compliance, including ODP-RFC exposure, migration completeness, and the December 2026 deadline. The assessment gives you a scored, documented view of your compliance posture — something auditors and CIOs can review.

Short-term: If your Note 3439624 output shows significant ODP-RFC exposure and you need help designing the migration architecture, contact us. We can scope the replacement in a structured engagement — typically a 2-4 week ODP Compliance Review.

Long-term: If your landscape is heavily ECC-based and RFC Table Read is not sufficient for your delta requirements, the Skynome ABAP Azure SDK will provide a governance-native push architecture that replaces ODP-RFC permanently.

The December deadline is not a problem you solve in December. It is a problem you scope in August.

---

SAP Note 3439624 is available on the SAP Support Portal with a valid S-User ID. SAP Note 3255746 Version 11 is the primary enforcement note. This post reflects Skynome's analysis of publicly available SAP documentation and enforcement behaviour observed in the field as of July 2026.