The bill you cannot read line by line

One question measures any pricing model: what did this query cost? On the vendor’s managed warehouse, by the vendor’s own note, that question has no answer.

RuleBuy warehousing you can attribute: storage plus compute, priced per query, on ground you own.

Neversign a capacity commitment you cannot decode. If consumption cannot be attributed, neither can savings.

◆ How the meter workscapacity units in, three kinds of fees out.

Datasphere is sold in capacity units, a composite meter that converts storage, compute, and features into one number. On top of the base meter, premium outbound integration is billed in blocks per 20 GB transferred, and replication carries per-gigabyte fees. Moving data in costs; moving it out costs more.

Fee	How it is metered
Base platform	Capacity units, a composite of storage, compute, and features.
Premium outbound integration	Billed in blocks per 20 GB transferred out.
Replication	Per-gigabyte fees on data copied in.
Attribution	Not available per space or per statement, per SAP note 3507826.

SAP note 3507826 confirms the part that matters for cost control: consumption cannot be attributed per space or per statement. The meter totals, but it does not itemize.

◆ The telling factcustomers asking how to read their own bill.

The community threads on this billing are not arguing about the price. They are asking how to decode their own capacity-unit consumption: which workload burned last month’s units, and why the number moved. When customers need forum help to read their own bill, the bill is the product problem.

Licensing analysts who work these contracts report that initial deployments are commonly over-contracted, sized on guesswork because consumption could not be modeled in advance. Those figures are practitioner-reported, not vendor-published. The unreadable meter and the oversized contract are the same fact seen from two sides.

◆ The owned answerstorage plus compute, attributable to the query.

A commodity warehouse prices two things: storage by the gigabyte, and compute metered while queries run. Every query is attributable: this job, this model, this team, this cost. Chargeback is a query over the billing table, not a support ticket.

The platform this page prices is also the history store the source system lacks, documented on the no-history page. And the arithmetic is not SAP-specific: the Workday storage pricing page is the sibling cost story on another platform. Owned ground, readable meter, on either.

Use case

Problem

The managed warehouse bills in capacity units that cannot be attributed per space or statement, so nobody can say what a workload costs.

What we build

An owned warehouse on commodity pricing, fed by the extraction pattern, with cost attribution modeled from the platform billing tables.

What you get

A bill you can read: cost per pipeline, per model, and per team, on ground where the meter and the data are both yours.

Can you say what last month’s units bought?

We build the owned warehouse where every cost has an owner.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
ERP: Enterprise resource planning, the system of record for operations and finance.
CU: Capacity unit, the composite meter SAP’s managed warehouse bills by.
GB: Gigabyte. Outbound integration is billed in blocks per 20 GB moved.
space: The workspace unit the managed warehouse divides work into.
premium outbound: The metered fee class for moving data out to non-SAP targets.
chargeback: Attributing platform cost back to the team or workload that caused it.