SAP Reference

COSS

transaction S/4HANA status: Active

CO Object: Cost Totals for Internal Postings

Identity
Module: CO · ControllingType: transparent
Notes

Actual internal CO postings flow to ACDOCA on S/4HANA; COSS retains target/plan/statistical totals. Prefer ACDOCA or released CDS views for analytics.

What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Fields

14 fields · 14 key

The join key is all 14 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

14 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 14 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyLEDNRLedger for Controlling objectsCHAR2
Primary keyOBJNRObject NumberCHAR22
Primary keyGJAHRFiscal YearNUMC4
Primary keyWRTTPValue TypeCHAR2
Primary keyVERSNVersionCHAR3
Primary keyKSTARCost ElementCHAR10
Primary keyHRKFTCO key subnumberCHAR14
Primary keyVRGNGCO Business TransactionCHAR4
Primary keyPAROBPartner ObjectCHAR22
Primary keyUSPOBSource Object (Cost Center/Activity Type)CHAR22
Primary keyBEKNZDebit/credit indicatorCHAR1
Primary keyTWAERTransaction CurrencyCUKY5
Primary keyPERBLPeriod blockNUMC3

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading COSS on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <GJAHR>

-- ============================================================
-- Table  : COSS CO Object: Cost Totals for Internal Postings
-- Purpose: Column-selected read of COSS — auto-generated from field metadata
-- Grain  : One row per LEDNR + OBJNR + GJAHR + WRTTP + VERSN + KSTAR + HRKFT + VRGNG + PAROB + USPOB + BEKNZ + TWAER + PERBL
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  c.MANDT AS "Client",
  c.LEDNR AS "Ledger for Controlling objects",
  c.OBJNR AS "Object Number",
  c.GJAHR AS "Fiscal Year",
  c.WRTTP AS "Value Type",
  c.VERSN AS "Version",
  c.KSTAR AS "Cost Element",
  c.HRKFT AS "CO key subnumber",
  c.VRGNG AS "CO Business Transaction",
  c.PAROB AS "Partner Object",
  c.USPOB AS "Source Object (Cost Center/Activity Type)",
  c.BEKNZ AS "Debit/credit indicator",
  c.TWAER AS "Transaction Currency",
  c.PERBL AS "Period block"
FROM <catalog>.<schema>.coss c
WHERE
  c.MANDT = '<MANDT>'
  -- AND c.GJAHR = <GJAHR>
ORDER BY c.LEDNR;

Verified August 2026

Relationships

Diagram of 1-hop neighbors — join details below.

Transaction Codes That Use This Table

No t-code mappings populated for this table yet.

Browse more CO tables

More Controlling tables