When was a CO-PA value field (VVxxx) created? HANA SQL in DB02 on DD03L/DD04L

Who created the CO-PA value fields (VV010, VV020, ...) and when. HANA SQL for DB02 → Diagnostics → SQL Editor.

Verified on an S/4HANA sandbox (client 100, operating concerns OC10 and JNC2) on 2026-08-27.

0. Before you start — find the table that stores the value fields (CE1xxxx)

CaseCompany code → controlling area → operating concern (TKA02 / TKA01)
What it doesValue fields (VVxxx) are created as columns of the operating concern line item table CE1<ERKRS>. Starting from the company code, TKA02 gives the controlling area (KOKRS) and TKA01 gives the operating concern (ERKRS), which names the table.
Watch outOn this system: CC10 → CA10 → OC10 (CE1OC10) and JNC2 → JNC2 → JNC2 (CE1JNC2). Each company code ends up in a different table.
Result2 rows (CC10 → OC10, JNC2 → JNC2)
SELECT k.BUKRS, k.KOKRS, a.ERKRS
  FROM TKA02 k
  INNER JOIN TKA01 a
     ON a.MANDT = k.MANDT
    AND a.KOKRS = k.KOKRS
 WHERE k.MANDT = '100'
   AND k.BUKRS IN ('CC10', 'JNC2')
 ORDER BY k.BUKRS;
Result — 2 rows
BUKRS | KOKRS | ERKRS
------+-------+------
CC10  | CA10  | OC10
JNC2  | JNC2  | JNC2

1. The query — value field creation date (data element change date)

CaseVV columns of the CE1 tables + data element dates (DD03L / DD04L)
What it doesThe value field itself stores no creation date (the field catalog TKEF has no date field either). When KEA0 creates a value field it also creates the data element RKE2_VVxxx, so the VV columns of the CE1 table (DD03L) are joined to the data element (DD04L) to read AS4USER / AS4DATE.
Watch outDD03L / DD04L are client-independent — no MANDT condition.
Watch outAS4DATE is the last change date. It is updated when a value field is changed or regenerated later, so it is not strictly the first creation date.
Watch outData elements are shared across operating concerns, so OC10 and JNC2 show the same dates.
Result18 rows — VV024 = 20260726 (added on 2026-07-26); the other 8 value fields (VV010–VV090) = 20260620, created in one batch. Same dates in CE1OC10 and CE1JNC2.
SELECT d3.TABNAME, d3.FIELDNAME, d3.ROLLNAME,
       d4.AS4USER, d4.AS4DATE
  FROM DD03L d3
  INNER JOIN DD04L d4
     ON d4.ROLLNAME = d3.ROLLNAME
    AND d4.AS4LOCAL = 'A'
 WHERE d3.TABNAME IN ('CE1OC10', 'CE1JNC2')
   AND d3.FIELDNAME LIKE 'VV%'
   AND d3.AS4LOCAL = 'A'
 ORDER BY d3.TABNAME, d3.FIELDNAME;

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