Transaction Tax Data Model

Two tax factsOn BSET & WITH_ITEMConformed dimensions

One owned model for Transaction Tax. The VAT and withholding facts are built from the tax line tables — BSET and WITH_ITEM — and join one shared set of conformed dimensions. The same set the rest of finance uses.

One source (BSET and WITH_ITEM) · two tax facts · one shared set of conformed dimensions — the same set your finance model uses.

Why it matters: when the Transaction Tax facts share the same tax code, account, and date, a number means the same thing in every Transaction Tax report — and it reconciles with the rest of finance, because the dimensions are the same ones the enterprise model uses.

Tap a section to drill in.

◆ The Transaction Tax facts— each is a thin view over the source, sharing the same keys.

Fact	Grain (one row per)	Built from
fct_tax_line	tax line per document × code	BSET
fct_withholding	withholding line per vendor × type	WITH_ITEM

Tax lives in its own line tables, not in ACDOCA — BSET holds every tax-relevant line (including the zero-rated ones a G/L report would miss), and each ties back to its document header (BKPF).

◆ The conformed dimensions— one tax code, one account, one calendar — used by every fact.

Dimension	What it is	Master
dim_tax_code	Tax code (MWSKZ)	T007A
dim_gl_account	Tax G/L account (HKONT)	SKA1
dim_vendor	Vendor (withholding)	Business Partner
dim_company_code	Company code (BUKRS)	T001
dim_date	Posting period	calendar

Conformed means the same dimension table, the same keys, joined by every fact that needs it — so a value means the same thing in every report.

◆ Why it is one model, not two— the dimensions are shared, and it plugs straight into your finance model.

Shared dimensions — all two facts join the same tax code, account, and date dimensions, so a number reconciles across the reports instead of arguing.
One source — BSET and WITH_ITEM feeds every fact; the reports differ only in grain.
It is the same conformed set the rest of finance uses — dim_company_code, dim_gl_account, and dim_date are shared with the enterprise model, so Transaction Tax is not a silo.
Add later without rebuilding — new measures join the dimensions that already exist.

◆ How it is built & owned— over the source + released CDS views, on your cloud, extracted the compliant way.

Source — BSET for tax lines and WITH_ITEM for withholding, joined to the document header (BKPF).
Build — dbt models: the facts and conformed dimensions, reconciled to the source ERP before go-live.
Land — your own cloud warehouse: GCP, AWS, or Azure.
Extract — released CDS + ODP-OData, SLT, or Table/Table-CDC; never ODP-RFC. See the extraction pattern →
Fits the whole — these facts and dimensions slot into the enterprise data model via the conformed keys.

Terms on this page

Tax code (MWSKZ): Sets the rate and treatment of a tax line — output, input, or zero-rated.
BSET: The tax data document segment — one summarized tax line per document per code.
Withholding: Tax withheld from a vendor payment — held in WITH_ITEM.
Fact: A table of measures and keys — the numbers you aggregate.
Conformed dimension: One dimension shared by every fact, so a value means the same thing everywhere.
ACDOCA: The Universal Journal — the single S/4HANA table behind the finance facts.
Star schema: One fact surrounded by its dimensions — the report-friendly shape.
Grain: What one row of a fact represents — the level of detail.

Want your Transaction Tax model built & owned?

We build the VAT and withholding facts on BSET and WITH_ITEM — the return reconciled to the G/L tax accounts before go-live — and your team owns every line of code.

Talk to us