ERPClimb logoERPClimb
SAP transaction codeObjectKP26ModuleFI_FICO

KP26 — Activity Type and Price Planning

KP26 plans activity output for cost center and activity type combinations: planned activity quantity, capacity and, where needed, a manually set plan price. Together with cost planning in KP06 it provides the basis for activity prices, which are used to value internal activity confirmations in production, maintenance and other cost allocations.

Plans activity quantities, capacities and prices per cost center and activity type for a fiscal year and version.

Published 31 Oct 2026· 510 words

What KP26 is for

Activity types such as machine hours or labour hours are how cost centers charge their costs to orders and other receivers. To charge them, the system needs a price. KP26 is where the planned activity quantity and capacity are entered per cost center, and where a price can be maintained directly or left to be calculated. Without realistic activity plans, activity prices are either missing or meaningless.

When it is used

It is used during annual budgeting and whenever plans are revised, typically by cost center managers and controllers. Product costing depends on it, because standard cost estimates value routings and recipes with these activity prices. It is also checked when a confirmation or cost estimate fails because no price exists for an activity type.

How it is used in practice

Choose version, fiscal year range, cost center and activity type, then enter planned activity, capacity and optionally a fixed and variable price. The price indicator decides whether the price is entered manually or calculated from planned costs by price calculation (KSPI). Use the overview layout for many cost centers, save, and check the results in planning reports before running cost estimates.

Fields and objects that matter

  • Version and fiscal year, usually version 0 for the operational plan
  • Planned activity quantity and capacity per period
  • Fixed and variable plan price and the price unit
  • Price indicator that decides between manual and calculated prices
  • Allocation cost element of the activity type, used when the activity is charged

How to prove it in the data

For a cost center and activity type, compare planned costs from KP06 with planned activity in KP26. If prices are calculated, the price after KSPI should equal planned costs divided by planned activity, split into fixed and variable parts. A cost estimate in CK11N for a product using that activity should show the same rate in its itemization.

ECC vs S/4HANA

KP26 remains available in S/4HANA. Many companies also plan in SAP Analytics Cloud or other planning tools and load results, but activity prices for costing still need to exist in the system.

Common pitfalls and how they show up

Activity plans are often entered once and forgotten until a costing run fails.

  • Missing price for an activity type, causing errors in cost estimates or confirmations
  • Unrealistic planned quantities, which produce distorted calculated prices
  • Price indicator set to calculated but KSPI never run
  • Planning in the wrong version or fiscal year, so costing does not find the price

Whose problem this is

Controlling owns activity planning and prices. Cost center managers provide realistic quantities and capacities, and product costing depends on the result, so planning deadlines are usually tied to the start of the costing run.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Lessons and topics

Source: ERPClimb — https://erpclimb.com/sap-tcodes/kp26ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.