SAP S/4HANA — Sources — Binom Governance

Copy formulas into the KPI Definition Card, then adapt grain and filters.

Example

Billing revenue

How much revenue was billed in the period?

SUM(dmbtr) FROM fi_document WHERE account_type = revenue AND budat IN period

Grain: FI document line
Fields: FI Document.dmbtr, FI Document.budat, FI Document.bukrs
Dimensions: company_code, cost_center, profit_center, country

Map revenue accounts via SKA1/SKB1 — check SD billing (VBRK/VBRP) as alternative.

Adapt: Clarify net vs gross, currency conversion and reversal documents.

Example

Open order backlog

How much open order value is still outstanding?

SUM(netwr) FROM sales_order_item WHERE open_qty > 0

Grain: Order line item
Fields: Sales Order Item.netwr, Sales Order Item.kwmeng, Sales Order.gbstk
Dimensions: company_code, material_group, country

Derive open qty from VBAP/VBEP — delivered vs ordered quantity.

Adapt: Lock snapshot vs flow and currency handling.

Order intake

How much order value was newly captured in the period?

SUM(netwr) FROM sales_order WHERE audat IN period

Grain: Order
Fields: Sales Order.netwr, Sales Order.audat
Dimensions: company_code, country, material_group

audat as period filter — exclude cancelled orders.

Adapt: Filter intercompany orders and test clients.

Cost center spend

How much cost was posted per cost center?

SUM(dmbtr) FROM fi_document WHERE kostl IS NOT NULL AND budat IN period

Grain: FI document line
Fields: FI Document.dmbtr, FI Document.kostl, FI Document.budat
Dimensions: cost_center, company_code, profit_center

Map expense accounts via chart of accounts.

Adapt: Define plan vs actual and allocation rules separately.

Units ordered

How many units were ordered?

SUM(kwmeng) FROM sales_order_item JOIN sales_order WHERE audat IN period

Grain: Order line item
Fields: Sales Order Item.kwmeng, Sales Order.audat
Dimensions: material_group, company_code, country

Harmonize unit of measure (meins) before aggregation.

Adapt: Exclude returns and cancelled line items.

Formula overview

Same formulas as a table — copy into KPI cards or SQL drafts.

Label	Formula	Grain	Fields
Billing revenue	`SUM(dmbtr) FROM fi_document WHERE account_type = revenue AND budat IN period`	FI document line	FI Document.dmbtr, FI Document.budat, FI Document.bukrs
Open order backlog	`SUM(netwr) FROM sales_order_item WHERE open_qty > 0`	Order line item	Sales Order Item.netwr, Sales Order Item.kwmeng, Sales Order.gbstk
Order intake	`SUM(netwr) FROM sales_order WHERE audat IN period`	Order	Sales Order.netwr, Sales Order.audat
Cost center spend	`SUM(dmbtr) FROM fi_document WHERE kostl IS NOT NULL AND budat IN period`	FI document line	FI Document.dmbtr, FI Document.kostl, FI Document.budat
Units ordered	`SUM(kwmeng) FROM sales_order_item JOIN sales_order WHERE audat IN period`	Order line item	Sales Order Item.kwmeng, Sales Order.audat

Id	Label	Grain	Notes
`company_code`	Company code	Company code	Link legal entity and local currency via bukrs.
`cost_center`	Cost center	Cost center	Harmonize controlling area (kokrs) before the mart.
`profit_center`	Profit center	Profit center	Load only when segment P&L is needed.
`material_group`	Material group	matkl / material group	Derive material group hierarchy from T023/T023T.
`country`	Country	land1 / region	Consciously choose customer vs ship-to country.

PII hotspots

Inventory direct and quasi identifiers for this source — tag, restrict RAW, hash or drop before marts.

Entity	Fields	Classification	Stage treatment	Treatment
KNA1 (Customer)	`kunnr, name1, stras, pstlz, ort01, smtp_addr, telf1, telf2`	Direct	RAW: restrict access; Curated: hash/tokenize; Mart: no cleartext	Customer master — tag email/phone/address; keep kunnr as business key.
LFA1 (Vendor)	`lifnr, name1, stras, pstlz, smtp_addr, telf1`	Direct	RAW: restrict access; Curated: hash/tokenize; Mart: no cleartext	Vendor contact PII — separate policy from customer PII.
ADR6 / Communication	`smtp_addr, tel_number, consnumber, addrnumber`	Direct	RAW: restrict access; Curated: hash/tokenize; Mart: no cleartext	Central communication data — often a second PII surface beside KNA1/LFA1.
USR21 / SAP User	`bname, persnumber, addrnumber, smtp_addr`	Workforce	RAW: workforce policy; Curated: separate from customer PII; Mart: aggregates only	SAP users and technical accounts — separate workforce vs integration users.
VBAK / VBAP (Order texts)	`bstnk, ihrez, text lines (STXH/STXL)`	Sensitive	RAW: rarely load; Curated: drop/redact; Mart: never	Order texts and customer references can identify persons.
Custom Z-fields	`Z* email/phone fields, Z* external id / national id`	Direct	RAW: restrict access; Curated: hash/tokenize; Mart: no cleartext	Inventory all Z-fields with email/external id via Data Dictionary.

DSDR discovery

Where personal data can hide beyond obvious contact fields — warehouse copies included.

Focus	Notes
Match keys	kunnr, lifnr, matnr, smtp_addr, telf1, external id (Z-fields), bukrs.
Primary objects	KNA1, LFA1, ADR6 — plus any object with contact/address fields.
Warehouse copies	CDS/BW extracts, SLT/replication, Datasphere, reverse-ETL and BI shared stages.
Change documents (CDHDR/CDPOS)	Historical field values remain PII — clarify retention before load.

Source-specific guidance: what goes wrong, how to prevent it, what staff must know — plus where metadata lives and how to access it.

Data quality guides 6

Prevent issues in the source first. Warehouse checks are a safety net — not a substitute for staff habits.

High Open order without kunnr

Problem: VBAK without kunnr cannot slice backlog and order intake by customer/region.
Prevent: Order entry: sold-to party required; review customizing.
Staff must know: SD: Every sales order needs a valid customer (kunnr).
Checks: VBAK.kunnr IS NULL AND gbstk NOT IN (closed/cancelled codes)
Fix in source: Mandatory sold-to in order type; block save without kunnr.
Warehouse safety net: Unknown-customer dim; exclude from customer KPIs.

High Line item without matnr

Problem: VBAP without matnr breaks product mix, units and material group reports.
Prevent: Material number required for relevant item categories; tag text items separately.
Staff must know: SD: Product lines need matnr — use text items deliberately only.
Checks: VBAP.matnr IS NULL AND pstyv NOT IN (text item types)
Fix in source: Item category rules; material required on product lines.
Warehouse safety net: Flag non-material lines; separate KPI.

High Open order without netwr

Problem: Open VBAK/VBAP without netwr makes backlog and pipeline unusable.
Prevent: Pricing before release; derive netwr from conditions.
Staff must know: SD: Do not release order when line values are missing.
Checks: netwr IS NULL OR netwr = 0 on open order lines
Fix in source: Pricing procedure; block release without values.
Warehouse safety net: Exclude from backlog or document impute policy.

Medium FI document without bukrs

Problem: BKPF/BSEG without bukrs prevents legal entity and currency slices.
Prevent: Company code always from context; integration always writes bukrs.
Staff must know: FI: No document without company code — check client/company code.
Checks: bukrs IS NULL on BKPF or BSEG
Fix in source: Mandatory bukrs in posting interface.
Warehouse safety net: Quarantine rows; exclude from P&L.

Medium audat before erdat

Problem: Order date before created date distorts order intake and cycle metrics.
Prevent: Validation on manual date changes; document migrations.
Staff must know: SD: audat = real order receipt — no backdating without process.
Checks: audat < erdat on VBAK
Fix in source: User exit / validation on date fields.
Warehouse safety net: Flag invalid dates; use erdat fallback.

Medium Duplicate kunnr with same email

Problem: Multiple KNA1 with same smtp_addr distort customer counts and DSDR.
Prevent: Duplicate check on customer create; MDM golden record.
Staff must know: Master data: Search existing customer before create.
Checks: COUNT(DISTINCT kunnr) GROUP BY smtp_addr HAVING COUNT > 1
Fix in source: Duplicate check program; MDM merge workflow.
Warehouse safety net: Golden customer id; merge map table.

MDM / duplicates 2

KNA1 Duplicate customers

Match keys: kunnr, smtp_addr, name1 + land1 + pstlz, External Id (Z-field)
Prevent in source: Duplicate check on create; Business Partner Central if available.
Resolve in warehouse: Golden kunnr; merge map for duplicates.
Survivorship: External id wins; then highest revenue / latest activity.

MARA Material duplicates / legacy numbers

Match keys: matnr, ean11/gtin, External Id, Legacy material number
Prevent in source: Control material number ranges; maintain cross-reference tables.
Resolve in warehouse: Canonical matnr via cross-ref; legacy map table.
Survivorship: Active material with GTIN wins.

Product settings to improve 3

SE11 Data Dictionary Document tables/fields for load allowlist

Why: Stable field inventories for PII and DQ.
How: SE11 → table/field display; export for data catalog.

Customizing → sales document types Sold-to / material required for relevant order types

Why: Prevents open orders without kunnr/matnr.
How: Review VOV8/VOFA; mandatory partner/material per order type.

CDS views / Fiori analytical apps Use CDS expose list as extract source

Why: Avoids raw table sync without semantics.
How: View Browser / IWFND — allowlist permitted views.

Metadata: what exists & how to get it 4

Source-native catalogs for schema, picklists/properties and access paths — not a full dump.

Data Dictionary (SE11)

Where in product: SE11 → table/structure/domain; DDIC in ADT
How to access: UI or ADT data preview; DD03L/DD04T for batch export.
Use for: Field inventory, PII tags, load allowlist, DQ checks.
Watchouts: Z-fields and customizing tables differ per client.

CDS views

Where in product: Eclipse ADT → CDS views; Fiori View Browser
How to access: View Browser, read @Analytics.dataCategory annotations.
Use for: Semantic extracts, fact/dim candidates.
Watchouts: Released vs local CDS — check transport status.

IDoc segments / WE60

Where in product: WE60 → IDoc types / segments; BD64 partner profiles
How to access: Segment documentation for integration mapping.
Use for: Integration field mapping — do not misuse as mart load.
Watchouts: Partner segments can contain PII — skip by default.

Customizing tables (SPRO)

Where in product: SPRO → relevant IMG paths; tables TV*/T*
How to access: Document customizing transports; read-only extract for dims.
Use for: Status/stage maps, currencies, order types.
Watchouts: Cross-client differences — do not merge blindly.

Object overview with short descriptions and load guidance — not a full schema dump.

Table	Description	Grain	Load
`material` Material (MARA)	Material master — product/SKU dimension for sales and inventory.	One material	Load
`customer` Customer (KNA1)	Customer master — dimension and PII for contact/address fields.	One customer	Load
`vendor` Vendor (LFA1)	Vendor master — procurement dimension with contact PII.	One vendor	Load
`sales_order` Sales order (VBAK)	Sales order header — fact for backlog, pipeline and order KPIs.	One order	Load
`sales_order_item` Sales order item (VBAP)	Order line items — finer grain for product mix and quantities.	One line item	Load
`fi_document` FI document (BKPF/BSEG)	Accounting documents — revenue, AR/AP and GL analytics.	One document / line item	Load
`cost_center` Cost center (CSKS)	Cost centers — controlling dimension for cost and allocation.	One cost center	Load
`company_code` Company code (T001)	Company code — legal entity and currency root.	One company code	Load
`profit_center` Profit center (CEPC)	Profit center — optional segment dimension for P&L.	One profit center	Optional

Most important fields to load early — not a full schema dump.

Entity	Field	Role	Why
Material	`Material.matnr`	Key	Material join
Material	`Material.mtart`	Dimension	Material type
Material	`Material.matkl`	Dimension	Material group
Material	`Material.meins`	Dimension	Base unit of measure
Customer	`Customer.kunnr`	Key	Customer join
Customer	`Customer.name1`	Dimension	Customer label
Customer	`Customer.land1`	Dimension	Country
Customer	`Customer.smtp_addr`	PII	Email / PII
Customer	`Customer.telf1`	PII	Phone / PII
Vendor	`Vendor.lifnr`	Key	Vendor join
Vendor	`Vendor.name1`	Dimension	Vendor label
Vendor	`Vendor.smtp_addr`	PII	Contact email / PII
Sales Order	`Sales Order.vbeln`	Key	Order join
Sales Order	`Sales Order.netwr`	Measure	Order value
Sales Order	`Sales Order.audat`	Measure	Order date / period grain
Sales Order	`Sales Order.gbstk`	Dimension	Overall status
Sales Order	`Sales Order.kunnr`	Dimension	Customer join
Sales Order Item	`Sales Order Item.vbeln`	Key	Parent join
Sales Order Item	`Sales Order Item.posnr`	Key	Line key
Sales Order Item	`Sales Order Item.matnr`	Dimension	Material
Sales Order Item	`Sales Order Item.kwmeng`	Measure	Order quantity
Sales Order Item	`Sales Order Item.netwr`	Measure	Line value
FI Document	`FI Document.belnr`	Key	Document join
FI Document	`FI Document.dmbtr`	Measure	Amount in local currency
FI Document	`FI Document.budat`	Measure	Posting date
FI Document	`FI Document.bukrs`	Dimension	Company code
FI Document	`FI Document.kostl`	Dimension	Cost center
Cost Center	`Cost Center.kostl`	Key	Join
Cost Center	`Cost Center.kokrs`	Dimension	Controlling area
Company Code	`Company Code.bukrs`	Key	Legal entity join
Company Code	`Company Code.waers`	Measure	Local currency

System and noise objects/fields you typically should not sync into the warehouse by default.

Skip tables / objects

Table	Category	Why
`Change documents (CDHDR/CDPOS)`	System	Change documents — high volume, rarely KPI-relevant.
`IDoc archives (EDIDC / EDID4 / EDIDS)`	System	Integration payloads — technical noise, not mart core.
`Application logs (SLG1 / BAL)`	System	Runtime and debug logs — not for business KPIs.
`Spool / print queue tables`	System	Print spool — not an analytics load.

Skip fields / content

Change document tables (bulk) — High volume without KPI value.
IDoc payload archives — Technical noise and partner PII in segments.
Application / job logs — Not analytical.
Unused Z-fields (bulk sync all) — Expands DSDR surface and cost.
Long text (STXH/STXL) bodies — Free text with PII — only with a use case.

Warehouse-neutral examples for landing (RAW) and curated models — copy and adapt to your dialect. Not vendor SOQL/API DDL.

Landing (RAW)

RAW sales order (VBAK/VBAP) landing

Source-shaped landing from SD extract — tag kunnr/netwr; no Open SQL in mart.

-- Warehouse-neutral RAW example (adapt dialect)
CREATE TABLE raw_sap_vbak (
  vbeln        VARCHAR,
  kunnr        VARCHAR,
  audat        DATE,
  erdat        DATE,
  netwr        DECIMAL(18,2),
  waerk        VARCHAR,
  gbstk        VARCHAR,
  vkorg        VARCHAR,
  vtweg        VARCHAR,
  spart        VARCHAR,
  _loaded_at   TIMESTAMP
);

CREATE TABLE raw_sap_vbap (
  vbeln        VARCHAR,
  posnr        VARCHAR,
  matnr        VARCHAR,
  kwmeng       DECIMAL(18,3),
  netwr        DECIMAL(18,2),
  pstyv        VARCHAR,
  _loaded_at   TIMESTAMP
);

RAW customer + vendor (KNA1/LFA1) landing

smtp_addr/telf1 are PII — keep RAW restricted; separate grants vs facts.

CREATE TABLE raw_sap_kna1 (
  kunnr        VARCHAR,
  name1        VARCHAR,
  land1        VARCHAR,
  pstlz        VARCHAR, -- quasi/direct PII
  smtp_addr    VARCHAR, -- direct PII
  telf1        VARCHAR, -- direct PII
  _loaded_at   TIMESTAMP
);

CREATE TABLE raw_sap_lfa1 (
  lifnr        VARCHAR,
  name1        VARCHAR,
  land1        VARCHAR,
  smtp_addr    VARCHAR, -- direct PII
  _loaded_at   TIMESTAMP
);

Curated

Curated fact sales order / line

Conformed fact — no cleartext PII; kunnr/matnr as keys + measures.

CREATE TABLE curated_fct_sap_sales_order AS
SELECT
  h.vbeln,
  h.kunnr,
  h.audat,
  h.netwr AS header_netwr,
  h.waerk AS currency_code,
  h.gbstk AS overall_status,
  h.vkorg,
  l.posnr,
  l.matnr,
  l.kwmeng,
  l.netwr AS line_netwr
FROM raw_sap_vbak h
JOIN raw_sap_vbap l ON l.vbeln = h.vbeln;
-- Open backlog: filter gbstk + open qty in mart logic.

Curated dim customer / material

Dims without email/postal cleartext in default marts.

CREATE TABLE curated_dim_sap_customer AS
SELECT
  kunnr,
  name1,
  land1 AS country
  -- omit smtp_addr, pstlz from default analytics dims
FROM raw_sap_kna1;

CREATE TABLE curated_dim_sap_material AS
SELECT
  matnr,
  mtart AS material_type,
  matkl AS material_group,
  meins AS base_uom
FROM raw_sap_mara;

Curated measure SELECTs

Order intake, open backlog, units — adapt period filters.

-- Order intake in period
SELECT SUM(header_netwr) AS order_intake
FROM curated_fct_sap_sales_order
WHERE audat BETWEEN :period_start AND :period_end;

-- Open order backlog (example — adjust status filter)
SELECT SUM(line_netwr) AS open_backlog
FROM curated_fct_sap_sales_order
WHERE overall_status NOT IN ('C', 'X');

-- Units ordered
SELECT SUM(kwmeng) AS units_ordered
FROM curated_fct_sap_sales_order
WHERE audat BETWEEN :period_start AND :period_end;

Tools

Open related Binom-Tools workflows to adapt formulas, PII and measures for this source.

Playbooks

Related governance stories for modelling, PII and measure design around this source.

Vendor help on Resources Official docs, governance and learning paths for this source. Open Resources →