ERPClimb logoERPClimb
SAP transaction codeObjectKSPIModuleFI_FICO

KSPI — Plan Price Calculation

KSPI calculates plan prices for activity types from planned costs and planned activity quantities. It runs iteratively, so when cost centers supply activities to each other the resulting prices include those internal charges. The calculated prices are stored for the plan version and used by product costing and activity allocations.

Calculates plan activity prices from planned costs and planned activity, including iteration across cost centers that supply each other.

Published 31 Oct 2026· 485 words

What KSPI is for

Entering activity prices by hand is error-prone when many cost centers and activities are involved. Plan price calculation divides planned costs by planned activity for each activity type and repeats the calculation until internal activity flows between cost centers are fully reflected. The result is a consistent set of plan prices that matches the cost plan.

When it is used

It runs at the end of annual planning, after cost planning and activity planning are complete and before standard cost estimates are created. It is rerun whenever the plan changes significantly. Controllers also run it in test mode to check whether a planned change in costs or volumes produces acceptable prices.

How it is used in practice

Select the cost centers or a cost center group, version and fiscal year, and run in test mode first. Review the price list for unusually high or low prices, which usually indicate missing activity quantities or misassigned costs. Then run in update mode. Only activity types whose price indicator allows calculation receive a calculated price.

Fields and objects that matter

  • Cost center group, version and fiscal year range
  • Test run and detailed list options
  • Price indicator of each activity type, which controls whether it is calculated
  • Fixed and variable price results per period

How to prove it in the data

For one activity type, add up planned costs on its cost center, including costs received from other cost centers, and divide by planned activity from KP26. The result should match the calculated price. Then check that a standard cost estimate created afterwards uses that price for the same activity.

ECC vs S/4HANA

Available in S/4HANA. With the Universal Journal, actual costs and allocations are posted in ACDOCA, while plan prices continue to drive standard costing and activity confirmations. Actual price calculation is a separate period-end step with its own transaction.

Common pitfalls and how they show up

Most strange prices come from the inputs, not from the calculation.

  • Cost centers with costs but no planned activity, producing extreme prices
  • Running before all internal activity plans are entered
  • Forgetting to rerun after plan changes, so cost estimates use outdated prices
  • Activity types set to manual prices, which KSPI does not change
  • Unexpected price jumps caused by one cost center receiving a large allocation late in planning

Whose problem this is

Controlling owns the run and the review of resulting prices before standard costing starts. Cost center managers are asked to explain prices that move sharply against the previous year, because those changes flow straight into product costs and margins.

Related SAP objects

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

Lessons and topics

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