CO-PA characteristics and value fields by operating concern: HANA SQL in DB02/ST04 (TKEFE/TKEF/TKEB)

Which characteristics and value fields are assigned to an operating concern — read from TKEFE and TKEF instead of clicking through KEA0. HANA SQL for DB02/ST04 → SQL Editor.

Verified on the EWM system (client 700, operating concerns OC10–OC40) on 2026-08-28.

0. Before you start — the operating concerns on the system (TKEB)

CaseList of operating concerns (TKEB)
What it doesTKEB is the client-dependent operating concern table. Currency (WAERS), fiscal year variant (PERIV) and creation date (CREDA) come with it.
Watch outTKEB has MANDT — a client condition is required in the WHERE clause.
Result10 rows — OC10 / OC20 / OC30 / OC40 (KRW, created in 2026) plus the standard samples 1010 (empty entry), E_B1, S001, S_AL, S_CP, S_GO
SELECT ERKRS, WAERS, PERIV, CREDA
  FROM TKEB
 WHERE MANDT = '700'
 ORDER BY ERKRS;

1. Characteristics and value fields (TKEFE × TKEF)

CaseCharacteristics and value fields per operating concern (TKEFE × TKEF)
What it doesTKEFE lists the fields assigned to an operating concern; TKEF is the field catalog (usage, data element, check table). USGFL filters the usage: F = fixed characteristic, D = derived characteristic, B = value field.
Watch outTKEFE / TKEF have no MANDT (cross-client tables) — a MANDT condition is an error.
Watch outCHTAB is where the characteristic master lives (check table, e.g. KNDNR → KNA1). CQMRK: C = amount, Q = quantity.
Watch outThe other USGFL values are excluded on purpose: T = technical fields (MANDT, PAOBJNR, GJAHR, ...), S = account-based amount fields (WTGBTR, ...), U/V = unit fields. They do not appear in the screen definition.
Watch outCharacteristic and value field names come from DD04T (data element texts). Korean ('3') is not installed on this system, so DDLANGUAGE = 'E' is used; switch to '3' on a system with Korean installed.
Result42 rows, identical for OC10–OC40 — 29 fixed characteristics (F) + 4 derived characteristics (D; OC40 has one more, KMVTNR) + 9 value fields (B: ABSMG, VV010–VV090). No customer characteristics (WW*) — the standard template as delivered.
SELECT e.ERKRS, f.USGFL, e.FIENM, f.ROLNM,
       t.DDTEXT, f.CHTAB, f.CQMRK
  FROM TKEFE e
  INNER JOIN TKEF f
     ON f.FIENM = e.FIENM
  LEFT JOIN DD04T t
     ON t.ROLLNAME   = f.ROLNM
    AND t.DDLANGUAGE = 'E'
    AND t.AS4LOCAL   = 'A'
 WHERE e.ERKRS = 'OC10'
   AND f.USGFL IN ('F', 'D', 'B')
 ORDER BY f.USGFL, e.FIENM;

Comments

Post a Comment

Popular posts from this blog

SAP S/4HANA Table Reference — Tables I Actually Query, by Topic

SAP tables I actually queried while building custom reports and running end-to-end tests on an S/4HANA sandbox, grouped by topic. Updated continuously as development goes on. Each table: Table / Description / Key fields / T-codes / Used in our custom reports. Last updated: 2026-08-13 1. CO — Allocation Cycles (Assessment / Distribution) Table Description Key fields T-codes Used in our reports T811C Allocation cycle header ※ Distribution = ALART 'V', assessment = ALART 'U'. Classic CO-OM uses TAB='CCSS' TAB / CYCLE / SDATE KSU3, KSV3 ZCO0040 (allocation cycle report), ZCO0041 (distribution cycle detail) T811S Cycle segments ※ SRULE (sender rule) / RRULE (receiver rule) / SPERCENT / RCDATA (variable portion type) / NEGTEST (negative tracing factors — stored value differs from the screen code) TAB / CYCLE / SDATE / SEQNR KSU3, KSV3 ZCO0040, ZCO0041 T811K Selection criteria per segment ※ SETKIND: 0=cycle, 1=sender control, 2=sender, 3=rece...
Read more

Production Order Variance Calculation KKS1 — Fixing KV031 and KV011, and What Lands in COSB

In the last post on cost center variance calculation (KSS1) I noted that the similarly-named KKS1 is a different animal. This is that post: production order variance calculation. I hit two errors on the way in, so we start with their causes and fixes, then verify — by comparing the database before and after — exactly what gets stored where. Environment: controlling area JNC2, plant JNC2, period 2026/008, KRW, three production orders. ※ Screens, menus, and settings may differ depending on your SAP release and system configuration. Two errors before it would even run KV031 ("no target cost version") — version 0 itself existed. What was empty was the variance variant for orders (AWVAO) in OKV6: only the cost-center one (AWVAS) was maintained, which is why KSS1 worked fine while KKS1 refused. Same OKV6 screen, different column. KV011 is an order status problem. Order 1004916 got its goods receipt and final delivery on August 2 — run KKS1 for period 007 and, as of that pe...
Read more

Modern ABAP Syntax Notes — Patterns and Pitfalls from Real Development

ABAP syntax actually used while developing our custom Z reports, organized by topic. Examples come from working sources, together with the pitfalls we actually hit. Structure: syntax item → explanation → example code. Last updated: 2026-08-13 1. Data Declarations and Types ▷ Inline declarations DATA(...) / @DATA(...) — Declare and assign in one statement. SELECT result tables land directly in @DATA(lt_...) — the structure is derived from the SELECT list SELECT matnr, maktx FROM makt INTO TABLE @DATA(lt_makt) WHERE spras = @sy-langu. DATA(lv_qty) = ls_stpo-menge * iv_losgr / lv_bmeng. LOOP AT lt_mat INTO DATA(ls_mat). " loop variable inline too ENDLOOP. ▷ FIELD-SYMBOLS / ASSIGNING — Modify internal table rows in place without copying. ASSIGN COMPONENT lets you pick the column name at runtime (used for dynamic logic such as auto-hiding empty columns) LOOP AT gt_list ASSIGNING FIELD-SYMBOL(<ls_list>) WHERE typps = 'M'. <ls_list...
Read more