KAZY table — Periodic Cost and Quantity Distribution Table

One row in KAZY represents a slice of an order's or cost object's costs and quantities for a single fiscal year, period, value type (plan, actual, target or variance) and version, broken down by cost element. It is a periodic totals-style record, similar in spirit to the other CO cost totals tables, but generated specifically to support work in process calculation, results analysis and related settlement processing for cost object controlling. Consultants rarely build custom reports directly on KAZY; it functions as an internal data carrier that the standard WIP and results analysis programs read and rewrite each time those runs execute for a given order or period. Because it is regenerated rather than posted to directly, its content reflects the last calculation run, not a running ledger of individual transactions.

Always restrict on client first, then narrow by object number derived from the order rather than scanning by cost element or period alone, since the table can carry a large number of rows across every order that has ever run through WIP or results analysis. Fix the fiscal year and period before running any selection, and never mix value types in a single sum without separating plan from actual from variance, since combining them silently produces meaningless totals. This is not a table with natural selectivity on its own; selectivity comes entirely from first identifying the order or cost object through the production order tables and only then reading the periodic rows for it.

Symptom: the work in process or variance value shown for an order in a given period looks wrong or unexpectedly zero. Confirm by taking the order number, finding its object number through the order header, then selecting the periodic cost table for that object number, the fiscal year and period in question, separated by value type. Compare the raw distributed value against what the WIP or results analysis report is displaying for the same period; a mismatch usually means the calculation run has not been re-executed since the last confirmation or settlement posting.

In ECC this sits in the family of CO-PC and cost object controlling totals tables that get read and rewritten by WIP calculation and results analysis programs. In S/4HANA, actual cost postings are consolidated into the universal journal, and standard reporting for order costs, WIP and variances is expected to run through that layer or through the standard order cost analysis transactions rather than direct table access. Whether this specific table has a public CDS compatibility view or has been functionally superseded for reporting purposes is not confirmed here and should be checked against the installed release before relying on it for any S/4HANA build.

A discrepancy traced to this table belongs to the CO-PC or cost object controlling consultant, since the content is generated by WIP calculation, results analysis and settlement configuration rather than by PP order execution itself. PP involvement is limited to confirming that the underlying order structure, operations and confirmations are correct. Basis gets involved only if the table's size is causing a performance problem in a background job.

The production order header and item tables supply the object number this table keys on, the operation table carries the activity types whose consumption drives the cost distribution, and the confirmation table is the source of the actual quantities that a WIP or results analysis run later distributes into periodic cost rows. The standard transactions that actually generate or refresh this content are the WIP calculation and settlement runs, not any manual entry transaction.