How does B2R control project plans and budgets?

Connect WBS plans, budget authority, project release where used, commitments, actuals, and forecast evidence.

B2R ROLE

Keep project budget control object-specific

Rail 2 uses project objects when scope, funding, execution, and settlement need their own lifecycle. B2R governs the approved authority and availability view; PS supplies the project structure and execution evidence.

WORKING FLOW

Keep the B2R question in front

Use the specialist object only where the rail needs it; the B2R page keeps authority, consumption, close evidence, and reporting connected.

01PLAN

Plan project demand

Record scope, package, timing, amount, funding source, owner, and project assumptions.

02AUTHORIZE

Approve budget and release where used

Separate approved project budget from the portion currently released or otherwise available for consumption.

03MONITOR

Compare commitments and actuals

Read purchase commitments, service entry, internal activity, postings, and forecast signals against the selected WBS control basis.

DIAGNOSTIC EVIDENCE

What proves the rail is under control?

Preserve the B2R evidence trail even when the specialist module owns detailed execution.

AUTHORITY

Approved WBS budget, release where applicable, approver, date, version, funding source, and change route.

CONSUMPTION

Commitments, actual postings, reversals, open items, and status by WBS or assigned execution object.

ACTION

Availability result, variance reason, transfer, supplement, return, release change where used, and owner decision.

RAIL MOMENT

A project has budget but only part is usable now

The total project is approved, but procurement should only consume the released phase. B2R keeps total authority, current availability, commitments, and actuals visible as separate records.

Authority and consumption remain separate
The owning object stays visible
Close and reporting evidence reconcile

SAP REFERENCE BOUNDARY

Validate the selected solution

Budget availability control, planning functions, workflows, and planning products vary by SAP edition, release, and licensed scope.