Why Payroll Was Blocking My WBS — and How I Fixed It in SAP PS

If you manage capital projects in SAP Project System, you have probably encountered the dreaded budget availability control error at month-end. The system throws a warning — or worse, a hard stop — because a posting has exceeded the approved WBS budget. Most of the time this is expected behavior. But when the culprit turns out to be a payroll posting, things get confusing fast.

This is exactly what happened at our site during the June close. A routine payroll run posted labor costs to a capital WBS element, immediately triggering an availability control block. The project was well within budget on actual capital spend — but the system didn't care. Payroll had consumed the headroom.

What Is Budget Availability Control?

Budget availability control in SAP PS is a real-time check that runs every time a cost posting hits a WBS element. It compares the cumulative actual and commitment spend against the approved budget and takes action based on configured tolerance keys.

The tolerance keys define what happens when spend approaches or exceeds the budget. A typical configuration looks like this:

Tolerance Key	Usage %	Action
++	85%	Warning message only
++	100%	Warning + email to project manager
++	110%	Hard error — posting blocked

Why Payroll Posts to WBS Elements

In a mining company, it is common for employees to time-write their hours against capital project WBS elements. This is correct — labor costs that directly relate to constructing or commissioning an asset should be capitalized under AASB 116.

The problem occurs when the payroll run timing conflicts with the budget availability control check. Specifically:

The Fix — Two Approaches

Option A — Exclude Payroll Cost Elements from Availability Control

The cleanest long-term fix is to configure SAP to exclude payroll cost elements from the availability control check entirely. This is done in customizing.

Option B — Supplement the WBS Budget

If you need an immediate fix during close, you can supplement the WBS budget using transaction CJ30 to cover the payroll posting temporarily, then reverse it after the payroll costs are settled or transferred.

Which Option Should You Use?

Budget availability control issues like this are rarely glamorous but getting them right saves significant time at every month-end close. If your payroll team is time-writing to capital WBS elements regularly, Option A is worth the config effort — it removes the problem permanently rather than patching it each period.

If you have questions about your specific SAP PS configuration or want to share how your team handles this, feel free to reach out via the contact page or connect on LinkedIn.