Resources State of SAP data pipelines

How do SAP estates really move their data? Help us find out.

There is no public dataset on how SAP estates extract data, how exposed they are to the ODP restriction, how they load planning systems, or how predictable their integration bills are. This survey builds one. It takes twelve minutes, it is anonymous, every respondent receives the report first, and the aggregate results are published for anyone to use. Fielding runs this quarter; the report follows in the first quarter of 2027.

1FieldQ4 2026: SAP data owners, Basisleads, planning COEs, dataengineers; target 300+ responses.2CleanDuplicates and incompleteresponses removed; company sizeand region recorded, names never.3AnalyseAggregates by ERP version,industry and estate size; noresult shown below a cell size often.4PublishQ1 2027: web report, data tables,PDF; respondents first.
Four stages. Respondents see the report two weeks before it is public.
300+
target responses
method
12 min
to complete
method
10
minimum cell size before a result is shown
method
Q1 2027
report published
plan
0
names collected
method
What the survey asks

Five sections, thirty questions.

SectionQuestionsWhy it matters
Your estateERP versions (ECC, S/4HANA, both), other ERPs, planning applications, warehouse or lakehouse, industry, size.Results are cut by these.
How you extractMethods in use: table reads, BAPIs, CDS views, extractors, ODP over RFC, ODP over OData, HANA log, SAP's own services; add-ons installed in SAP.The first public picture of extraction methods.
The ODP restrictionAwareness of Note 3255746; opt-out status; jobs affected; vendor statements received; plan and date.How exposed the market is, six months before the opt-out ends.
Planning loadsPlanning applications fed; cadence; hours to a first load; run-window misses; how bad records are handled; whether plans return to the ERP.The planning-integration picture nobody has measured.
Bills and predictabilityPricing units in use (rows, credits, processing units, capacity); surprise invoices in the last year; tool count.Whether bill shock is as common as reviews suggest.
What you receive

The report, first.

The report, two weeks early

Aggregates by ERP version, industry and estate size, with the method and the cell sizes stated.

Your own answers against the aggregate

A one-page comparison of your responses with the population, for your own planning.

The data tables

Aggregate tables for your own analysis, under a licence that lets you cite them.

How the results are protected

Anonymous by design.

No names, no company names and no email addresses are stored with the answers; the report delivery list is kept separately from the responses. No result is shown for a group smaller than ten. Free-text answers are quoted only with permission asked at the end of the survey.

Terms on this page

Plain meanings.

Cell sizeThe number of responses behind a published figure; below ten, the figure is withheld.
AggregateA figure computed across many responses so that no single one can be identified.
FieldingThe period during which the survey collects responses.
Questions

Asked about this guide.

Who should answer?

The person who knows how the estate extracts and loads data: an SAP data owner, a Basis lead, a data engineering lead or a planning COE lead. One response per company is enough; several are welcome.

Will Lima contact me?

Only to send the report, if you ask for it. The delivery list is separate from the answers.

Can we cite the results?

Yes. The aggregate tables are published under a licence that allows citation with attribution.

Twelve minutes for the first public picture.

Take the survey; receive the report two weeks before anyone else.