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
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| PA0001HR Master Record: Infotype 0001 (Organizational Assignment) | Cost centre and employee group (driving table) | Read | ECC + S/4 |
| PA0000HR Master Record: Infotype 0000 (Actions) | Active employment status | Read | ECC + S/4 |
| PA0008HR Master Record: Infotype 0008 (Basic Pay) | Basic pay and pay scale group | Read | ECC + S/4 |
| PA0014HR Master Record: Infotype 0014 (Recurring Payments/Deductions) | Recurring payments | Read | ECC + S/4 |
| HRP1000Infotype 1000 (Object) Database Table | Vacant positions | Read | ECC + S/4 |
| CSKSCost Center Master Record | Cost centre master and controlling area | Read | ECC + S/4 |
| COSPCO Object: Cost Totals for External Postings | CO plan values in ECC (primary costs) | Write | ECC + S/4 |
| ACDOCPPlan Data Line Items | Plan data in S/4HANA | Write | ECC + 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
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_KOKRS | Controlling area | Single value | CSKS-KOKRS | Yes | 1000 |
| P_GJAHR | Plan year | Single value | — | Yes | 2027 |
| P_VERSN | Plan version | Single value | COSP-VERSN | Yes | 000 |
| S_KOSTL | Cost centre | Range / multiple | CSKS-KOSTL | No | 4100-4999 |
| P_SCEN | Increase scenario | Single value | — | No | BUTCE-2027 |
| P_VACANT | Include vacant positions | Checkbox | — | No | X |
| P_TEST | Test run (no posting to CO) | Checkbox | — | No | X |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Cost centre | CSKS-KOSTL |
| 2 | Cost element | Calculated Wage type → cost element mapping |
| 3 | Headcount | Calculated Active employees + planned positions on the cost centre |
| 4 | Current annual cost | Calculated 12 months at today's pay |
| 5 | Increase effect | Calculated Scenario rate × months after the effective month |
| 6 | New positions | Calculated Vacant positions × average pay × remaining months |
| 7 | Plan total | Calculated Current + increase effect + new positions |
| 8 | Transfer status | Calculated Test, transferred or error |
Sample result list
| Cost centre | Cost element | Headcount | Current annual cost | Increase effect | New positions | Plan total | Transfer status |
|---|---|---|---|---|---|---|---|
| 4100 | 620000 | 24 | 9,840,000 | 885,600 | 0 | 10,725,600 | Test |
| 4100 | 620100 | 24 | 2,066,400 | 185,976 | 0 | 2,252,376 | Test |
| 4200 | 620000 | 11 | 4,290,000 | 386,100 | 360,000 | 5,036,100 | Transferred |
| 5100 | 620000 | 58 | 17,980,000 | 1,618,200 | 0 | 19,598,200 | Error: cost centre locked |
How does the program work?
- Active headcount at the start of the plan year is read from PA0000 and PA0001 (cost centre, employee group, position).
- 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).
- 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.
- Planned hires and vacant positions (HRP1000, HRP1001 and the position’s cost centre) can be added to the scenario with an average salary.
- 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.
- 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
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 …
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 …
Personnel Cost Distribution by Organizational Unit and Expense Group
A report that distributes payroll costs to the directorate, department and company levels of the org structure and to management's own expense groups …
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.