SAP S/4HANA End-to-End Lab

If you run a standard cost estimate every month, sooner or later someone asks a question no single SAP screen answers well: which materials were only marked, which were actually released, and when? Opening CK11N or CK24 material by material is not an answer when there are hundreds of them. Three tables carry the whole story — KEKO , MBEW and MBEWH . Below are the queries I use to read status, monthly trend and missed releases straight out of them, in ABAP SQL and in native HANA SQL for the DB02 SQL editor. The three states of a cost estimate Estimating, marking and releasing are three separate acts, and each leaves its trace in a different field. Getting that mapping right is most of the job: Status How it is recognised What it means ESTIMATED_ONLY FREIG ≠ 'X', VORMDAT = 00000000 The estimate was run (CK11N/CK40N) and nothing else happened. The material master still carries the old price. MARKED_NOT_RELEASED FREIG ≠ 'X', VORMDAT > 00000000 Marked (CK24 marking...

Both of these mean “someone outside does part of the work.” They are configured differently, they post differently, and picking the wrong one gives you a cost structure you cannot analyse later. The fastest way to keep them straight is not the definition — it is the accounting entry each one produces. What follows are the actual postings from two products made side by side in the same S/4HANA client: kimchi dumplings made by a subcontractor , and shrimp dumplings made in-house with one outsourced operation . Subcontracting: the vendor makes the product We buy the semi-finished product as work . We supply the raw materials, the subcontractor shapes them, and a single goods receipt settles the entire arrangement. That one document fires several OBYC account-determination keys at once: Posting at the subcontract goods receipt Amount OBYC key Dr 5080 raw material consumed — supplied to subcontractor 4,200 GBB · VBO Cr 1050...

Buying 6,700 KRW of pork and wrappers produced four documents, two accounting entries, and zero effect on the profit and loss statement. That surprises people the first time they trace it, and the reason it works that way is the single most useful thing to understand about procurement in SAP. Below is the actual relay, with the real document numbers from a dumpling factory I built from an empty S/4HANA client. Four documents, but only two of them are accounting # Document What it claims Accounting entry 1 Requisition · ME51N EBAN 0199000553 “we want this” — internal only none 2 Purchase order · ME21N EKKO 4500006934 a promise to the vendor none 3 Goods receipt · MIGO 101 MSEG 5000006252 “it physically arrived” Dr 1050 raw material Cr 9010 GR/IR 4 Invoice receipt · MIRO RBKP 5100004739 “the vendor billed us” Dr 9010 GR/IR + input tax Cr 2...

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...

50% OFF Both books and the bundle are half price : the story $18 $9 , the build record $35 $18 , the bundle $47 $24 . No code needed. Everything on this blog comes from one project: a small Korean dumpling company, built from a completely empty SAP S/4HANA client and driven through a full business month — plan, standard cost, purchase, produce, sell, close. I have now turned that project into two books . Same company, same real numbers, two very different altitudes. BOOK 1 · THE STORY · $18 $9 How Sarah Joined a K-Dumpling Company and Became an SAP Genius A business novel about SAP S/4HANA. Sarah is a junior accountant at a dumpling factory; when 6,700 won of ingredients vanish from the balance sheet overnight, a consultant named J starts teaching her how a company actually works — one posting at a time. By the last chapter she has watched a 36% margin quietly become 6%, with every posting correct and nobody doing anything wrong. Webtoon-styl...

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...

This post covers the last stretch of cost center month-end: variance calculation. The four steps are KSS2 (actual cost splitting) → KSS3 (target cost basis display) → KSII (actual price calculation) → KSS1 (variance calculation) — and for each step I compared the database before and after execution to see exactly which tables it touches. Environment: controlling area JNC2, cost center JNC29010, period 2026/007, KRW, S/4HANA 2021. ※ Screens, menus, and settings may differ depending on your SAP release and system configuration. One of the four steps is different in kind KSS3 has no Test Run checkbox and saves nothing. It computes target costs on the fly from the splitting result and actual activity quantities every time you view it. The other three steps each update different tables: T-code Step Test Run Updates KSS2 Actual cost splitting yes COSS KSS3 Target cost display n/a nothing (computed on view) KSII Actual price calculation yes COKL, COSL + CO documents (the on...