HCM Program Custom development Background program

Personnel Cost Planning Report and Transfer to CO Planning

Short answer: A program that forecasts next year's personnel cost per employee and cost centre by month from the current headcount, basic pay, recurring payments and planned increase rates, and transfers the result to controlling planning by cost element. Planned hires and vacant positions can be added to the scenario, and a test run checks everything before transfer.

Estimated effort
L · 10–14 working days
System
ECC and S/4HANA
Tables
8
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

Standard personnel cost planning (PCP) is powerful but its data collection, scenario and approval setup is heavy, so many companies never implement it. With KP06 the plan is entered manually or uploaded from Excel, leaving the per-employee calculation in Excel. The program does the calculation from SAP's own data and delivers the result as a simple report and CO plan values.

Who uses it? Budgeting and controlling teams, HR compensation, finance managers.

Closest standard alternatives

  • KP06 Change Cost Element/Activity Input Planning. Cost centre primary cost plan is entered manually; no per-employee calculation.
  • KP26 Change Plan Data for Activity Types. Plans activity types; does not calculate personnel cost.

Tables used

The tables the program reads and updates. ECC and S/4HANA differences are marked separately.

TableRoleAccessSystem
PA0001HR Master Record: Infotype 0001 (Organizational Assignment)Cost centre and employee group (driving table)ReadECC + S/4
PA0000HR Master Record: Infotype 0000 (Actions)Active employment statusReadECC + S/4
PA0008HR Master Record: Infotype 0008 (Basic Pay)Basic pay and pay scale groupReadECC + S/4
PA0014HR Master Record: Infotype 0014 (Recurring Payments/Deductions)Recurring paymentsReadECC + S/4
HRP1000Infotype 1000 (Object) Database TableVacant positionsReadECC + S/4
CSKSCost Center Master RecordCost centre master and controlling areaReadECC + S/4
COSPCO Object: Cost Totals for External PostingsCO plan values in ECC (primary costs)WriteECC + S/4
ACDOCPPlan Data Line ItemsPlan data in S/4HANAWriteECC + S/4

S/4HANA notes

  • COSP → ACDOCA: In S/4HANA COSP is a view, not a table; actual totals are calculated from ACDOCA.

BAPIs and functions used

  • PYXX_READ_PAYROLL_RESULTRead Payroll Result. Reads payroll results for overtime and additional payment averages
  • BAPI_COSTACTPLN_CHECKPRIMCOSTPrimary Cost Planning: Check. Checks plan values before transfer
  • BAPI_COSTACTPLN_POSTPRIMCOSTPost Primary Cost Planning. Posts the primary cost plan to the cost centre
  • K_KOKRS_READRead Controlling Area. Reads controlling area settings

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
P_KOKRSControlling areaSingle valueCSKS-KOKRSYes1000
P_GJAHRPlan yearSingle value—Yes2027
P_VERSNPlan versionSingle valueCOSP-VERSNYes000
S_KOSTLCost centreRange / multipleCSKS-KOSTLNo4100-4999
P_SCENIncrease scenarioSingle value—NoBUTCE-2027
P_VACANTInclude vacant positionsCheckbox—NoX
P_TESTTest run (no posting to CO)Checkbox—NoX

Result list columns

#ColumnSource
1Cost centreCSKS-KOSTL
2Cost elementCalculated Wage type → cost element mapping
3HeadcountCalculated Active employees + planned positions on the cost centre
4Current annual costCalculated 12 months at today's pay
5Increase effectCalculated Scenario rate × months after the effective month
6New positionsCalculated Vacant positions × average pay × remaining months
7Plan totalCalculated Current + increase effect + new positions
8Transfer statusCalculated Test, transferred or error

Sample result list

Cost centreCost elementHeadcountCurrent annual costIncrease effectNew positionsPlan totalTransfer status
4100620000249,840,000885,600010,725,600Test
4100620100242,066,400185,97602,252,376Test
4200620000114,290,000386,100360,0005,036,100Transferred
51006200005817,980,0001,618,200019,598,200Error: cost centre locked
A view built with fictional sample data; not real system data.

How does the program work?

  1. Active headcount at the start of the plan year is read from PA0000 and PA0001 (cost centre, employee group, position).
  2. Basic pay comes from PA0008, recurring payments and deductions from PA0014. Optionally, the 12-month average of overtime and additional payments is calculated from payroll results (PYXX_READ_PAYROLL_RESULT).
  3. The increase scenario is read from a settings table (effective month, rate, by employee group or pay scale group). Employer contributions and benefits are added per wage type with factors that are entered in the scenario, not hard-coded.
  4. Planned hires and vacant positions (HRP1000, HRP1001 and the position’s cost centre) can be added to the scenario with an average salary.
  5. Wage types are assigned to cost elements with a mapping table similar to the payroll posting mapping (T52EL / symbolic accounts); the result is summed as cost centre × cost element × month.
  6. The transfer is checked with BAPI_COSTACTPLN_CHECKPRIMCOST and written to the selected plan version with BAPI_COSTACTPLN_POSTPRIMCOST. In ECC the values land in COSP (plan value type), in S/4HANA in ACDOCP.

Performance notes

Read the headcount in a single selection and calculate payroll averages only when selected. Call the BAPI once per cost centre with the values for all months.

Features

  • Test mode (check without posting) Plan result and check messages without posting to CO
  • ALV list (sort, filter, subtotals) ALV at employee and cost centre level
  • Export to Excel Scenario results can be exported to Excel
  • Line-by-line result and error log Each transfer is logged with plan version and scenario

Authorization objects

  • P_ORGINAuthorization to read employee data by personnel area, employee group and infotype
  • K_CSKS_PLAAuthorization to post cost centre plan data

Frequently asked questions

Does it replace standard personnel cost planning?

For simple needs, yes: annual budget from headcount, increases and new positions. If multi-step approval, several data collection methods and HR budget management are needed, standard PCP is the better fit.

Can several scenarios be compared?

Yes. Scenarios are kept under separate keys in the settings table and can be transferred to different plan versions; the report can show two scenarios side by side.

Does it work on S/4HANA?

Yes. The plan BAPI is also used on S/4HANA and values are written to ACDOCP. If planning is done in SAP Analytics Cloud, the result can also be provided there as a data source.

Related reports

CO Report Custom ALV report

Cost Center Plan vs Actual with Commitments Report

A custom ALV report that shows plan, actual and open purchasing commitments per cost center and cost element on one row, and calculates the remaining …

COSP · COSS · CSKS · CSKT

CO Program Custom Mass upload

Cost Center Cost Plan Upload from Excel

A custom program that loads periodic plan amounts per cost center and cost element from a budget file into the CO plan in bulk. It checks every row in …

COSP · CSKS · CSKB

Let us build this program for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Personnel Cost Planning Report and Transfer to CO Planning