KP06 — Cost Center Planning of Primary Costs

KP06 lets a controller enter planned values for primary cost elements against cost centers, split by period and by planning version, usually for a fiscal year. Primary cost elements are the ones that mirror a GL expense account (rent, salaries, utilities), as opposed to secondary cost elements used for internal allocations, which are planned in a different transaction. The one structural fact that explains most confusion: KP06 never touches FI. It is a pure CO planning transaction writing to cost center planning tables, so a value entered here will never show up on a GL account line item, only in cost center reports comparing plan to actual (cost element report, S_ALR* reports, or the equivalent Fiori app). Consultants who expect a KP06 entry to affect the trial balance are the most frequent source of confusion around this transaction.

KP06 sits in the annual or rolling budgeting cycle, after cost centers and cost elements exist as master data but before the fiscal year opens for actual postings that need variance analysis. Controllers use it to load the operating plan for expense-type costs onto cost centers, either by manual entry, by copying a prior year's actuals as a starting point, or by uploading via a planning layout linked to an interface (BDC, LSMW, or a planning upload program). It is reached for instead of a Fiori planning app when the client is still on classic CO-OM planning rather than SAP Analytics Cloud or Business Planning and Consolidation, which is common in older ECC-derived S/4HANA implementations that never migrated their planning process off the classic layouts.

In SE16N pull the cost center planning totals table, filter on the controlling area, fiscal year, version, cost center, and cost element in question, and check whether a record exists at all before checking whether the amount is nonzero. If no record exists, the plan was never saved for that combination, which usually means the layout used did not include that cost element, or the cost element group referenced by the layout excludes it. If a record exists but reporting shows zero, check the fiscal year variant and period range used by the report against the periods actually planned.

KP06 still exists and functions the same way on S/4HANA for clients running classic CO-OM cost center planning; nothing about the transaction logic or its underlying tables changed structurally in the move to HANA. What changed is the surrounding landscape: many S/4HANA implementations move planning entirely to SAP Analytics Cloud or embedded BPC, in which case KP06 is deliberately left unused or locked down, and its data is uploaded through an integration rather than entered manually. There is no dedicated Fiori replacement app for manual cost element planning at the level of granularity KP06 offers.

This is a functional CO/controlling problem, owned by the controller or FICO consultant managing the planning cycle, not Basis or ABAP unless the issue is an authorization object or a custom upload program failing. A good handover includes the controlling area, fiscal year, version, cost center, cost element, the planner profile or layout used, and whether the entry was manual or via an upload interface.

Start with KS01/KS03 to confirm the cost center master exists, is unlocked, and has the correct validity period before troubleting anything in KP06 itself. Use KSB1 to pull actual cost center line items and compare against the plan figures once loaded, since plan-actual variance is the entire point of planning. FS00 is useful to confirm the GL account behind a primary cost element is configured as a cost-relevant P&L account, since a primary cost element only exists if its GL account allows it.