# Personnel Cost Planning Report and Transfer to CO Planning

> 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.

- Type: Program, Custom development, Background program
- Module: HCM
- Estimated effort: L (10–14 working days)
- Last updated: 2026-11-18
- URL: https://nekuhub.com/en/programs/personnel-cost-planning-report-and-transfer-to-co-planning/


## 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.

### Closest standard alternatives

- KP06: Cost centre primary cost plan is entered manually; no per-employee calculation.
- KP26: Plans activity types; does not calculate personnel cost.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| PA0001 | Cost centre and employee group (driving table) | Read | - | ECC + S/4 |
| PA0000 | Active employment status | Read | PA0000-PERNR = PA0001-PERNR | ECC + S/4 |
| PA0008 | Basic pay and pay scale group | Read | PA0008-PERNR = PA0001-PERNR | ECC + S/4 |
| PA0014 | Recurring payments | Read | PA0014-PERNR = PA0001-PERNR | ECC + S/4 |
| HRP1000 | Vacant positions | Read | - | ECC + S/4 |
| CSKS | Cost centre master and controlling area | Read | CSKS-KOSTL = PA0001-KOSTL | ECC + S/4 |
| COSP | CO plan values in ECC (primary costs) | Write | - | ECC + S/4 |
| ACDOCP | Plan data in S/4HANA | Write | - | ECC + S/4 |

## BAPIs and functions used

- PYXX_READ_PAYROLL_RESULT: Reads payroll results for overtime and additional payment averages
- BAPI_COSTACTPLN_CHECKPRIMCOST: Checks plan values before transfer
- BAPI_COSTACTPLN_POSTPRIMCOST: Posts the primary cost plan to the cost centre
- K_KOKRS_READ: Reads controlling area settings

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| P_KOKRS | Controlling area | Single value | CSKS-KOKRS | Yes |
| P_GJAHR | Plan year | Single value | - | Yes |
| P_VERSN | Plan version | Single value | COSP-VERSN | Yes |
| S_KOSTL | Cost centre | Range / multiple | CSKS-KOSTL | No |
| P_SCEN | Increase scenario | Single value | - | No |
| P_VACANT | Include vacant positions | Checkbox | - | No |
| P_TEST | Test run (no posting to CO) | Checkbox | - | No |

## Result list columns

| Column | Source |
|---|---|
| Cost centre | CSKS-KOSTL |
| Cost element | Calculated: Wage type → cost element mapping |
| Headcount | Calculated: Active employees + planned positions on the cost centre |
| Current annual cost | Calculated: 12 months at today's pay |
| Increase effect | Calculated: Scenario rate × months after the effective month |
| New positions | Calculated: Vacant positions × average pay × remaining months |
| Plan total | Calculated: Current + increase effect + new positions |
| Transfer status | Calculated: Test, transferred or error |

## 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.

## Authorization objects

- P_ORGIN: Authorization to read employee data by personnel area, employee group and infotype
- K_CSKS_PLA: Authorization 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.

---
Let us build this program for your system: https://nekuhub.com/en/request-a-quote/?report=hcm-personnel-cost-planning-to-co
