KE27 Ran Without Errors — So Why Are the COGS Detail Value Fields Still Zero?

This time I ran KE27 periodic valuation and hit a puzzling result: the COGS total was filled, but every COGS detail value field stayed zero. The run finished without a single error, which made the cause harder to find.

※ Screens, menus, and settings may differ depending on your SAP release and system configuration.

Environment and symptom

Operating concern JNC2 (line item table CE1JNC2), period 2026/007, record type F. After running KE27, document 2 was created with Cost of Goods Sold (VV020) = 6,000 — but COGS-Raw Materials, COGS-Labor, COGS-Depreciation, and COGS-Subcontracting were all empty.

The original billing line item (document 1) already carried the detail split (6,800 / 3,000 / 3,000), and the execution log showed zero errors. So at first I assumed a valuation setting was missing.

Checking the valuation customizing — all fine

I walked the CO-PA valuation chain in order: KE4U has valuation strategy JNC assigned to PV 01·02 with record type F; strategy JNC is defined as material-cost-estimate-based with quantity field ABSMG. KE40 costing keys JN1 (costing variant PPC1 / version 01) and JN2 exist.

The decisive line was the last one: the KE4R detail-split assignments were registered for periodic valuation (PV 02) exactly as for realtime valuation (PV 01). So this was not a missing setting.

The answer was in the execution history

Looking at the execution history (table TKEVAA): run number 000001, variant SV2, user HUB2150 — 2 selected / 2 processed / 0 errors.

The problem was the value fields chosen at execution time. Only VV020 was ticked; VV021 through VV024 were blank. The customizing was fine — the run had simply been told to revalue only the total field. The four detail fields were never part of the run at all.

The fix

Simple: cancel the previously created KE27 delta line item (document 2) with KE27S, then rerun KE27 with VV020 and VV021~VV024 all ticked.

Result: documents 2 and 3 (the cancellation) offset each other, and the rerun (document 4) posts COGS-Depreciation 6,000. The COGS total 18,800 now matches the detail sum 6,800 + 3,000 + 9,000. Our line-item report ZCO0030 shows the four lines adding up to Sales 20,000 / COGS 18,800 / margin 1,200.

Takeaways

  • A clean KE27 run does not mean every value field you care about was filled. Even with correct KE4R assignments, only the value fields ticked at execution time are processed.
  • When values come in partially, check the TKEVAA execution history first — before digging through customizing again.
  • Wrongly created delta line items are cancelled with KE27S, then just rerun.
  • Reminder: CO-PA line item tables are per operating concern (JNC2 → CE1JNC2), and both PALEDGER 01 and 02 ledgers are stored.

Korean original (with screenshots): KE27 주기적 재평가 후 COGS 세부 가치필드가 0으로 남는 경우

Where these documents come from
Everything on this blog comes from one small dumpling factory built end-to-end in an S/4HANA sandbox — one plant, one product, one month, every document number real. The whole build is written up in two books.
· Free 16-page sample — the opening chapters, no email required
· How Sarah Joined a K-Dumpling Company and Became an SAP Genius — the business novel, 53 pages, $25
· The Dumpling Factory: Building a Complete SAP S/4HANA Company from Scratch — the build manual, 85 pages, $50

Comments

Post a Comment

Popular posts from this blog

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

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

A 36% margin became 6% at month-end, and every posting was correct

On the day we shipped, the billing document said the margin was 36% . Three weeks later, after the close, the same sale carried a margin of 6% . Nobody made a mistake. No posting was reversed. Every document in between was correct. This is the part of SAP that spreadsheets never prepare you for, so it is worth walking through with real numbers. Everything below comes from a small dumpling factory I built from an empty S/4HANA client and drove through one complete business month. 1. The sale looked great A sales order for 20,000 KRW of dumplings, delivered and billed: Step Transaction Effect Sales order VA01 Revenue 20,000 · standard cost of goods 12,800 → expected margin 7,200 (36%) Goods issue VL01N → PGI Cost of goods sold hits the P&L for the first time — at standard Billing VF01 Revenue 20,000, receivable 22,000 (incl. tax) If you stop reading the system here — and a lot of people do, because t...
Read more