B2A 202 · CONTROL BOUNDARY
How does B2A apply controlling within a project boundary?
Compare enterprise-wide B2R controlling with B2A's finite investment corridor, from authorized budget through capitalization.
READ THE CAPABILITY
Keep the finite investment corridor distinct from enterprise controlling
B2A uses controlling evidence inside a finite investment corridor: approved authority, project structure, commitments, actual cost, AuC, final asset, and handover. B2R may provide the broader budget and cost-control framework, but B2A must still make the investment boundary explicit.
The boundary prevents two common errors: treating a project plan as enterprise-wide authority, or treating a project cost collector as proof that the delivered asset is financially and operationally complete. Each hand-off needs its own owner and reconciliation.
WORKING FLOW
From business decision to controlled evidence
Follow the capability through the records and decisions that make the result explainable.
Set the corridor
Define the investment scope, accountable WBS, budget authority, release, status, and completion criteria.
Control consumption
Trace commitments and actual costs to the project object while preserving the relationship to the wider budget policy.
Recognize asset value
Separate eligible capitalized cost from expense, settle to AuC, and transfer to the final asset when ready.
Close the boundary
Reconcile authority, cost, value, asset ownership, operational acceptance, and remaining obligations before closure.
DIAGNOSTIC EVIDENCE
What should be traceable?
When the result looks wrong, start with the last trusted record and follow the owning boundary.
Approved scope, budget, release, status, availability result, owner, and relationship to B2R control.
Commitment, actual cost, AuC, settlement, capitalization, receiver, and remaining balance.
Final asset, technical identity, acceptance, operational owner, open obligations, and closure decision.
SCENARIO
A project is financially under budget but operationally incomplete
The cost report shows a favorable balance, but open commitments and missing handover evidence remain. The project-bound control view keeps those facts visible and prevents a favorable variance from being mistaken for a completed, operable investment.
- Business rule and accountable owner are explicit
- SAP object and source evidence remain connected
- Exception or outcome is reconciled before closure
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
Enterprise versus project control boundary
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns02Budget, commitment, actual cost, and capitalized cost
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns03Completion and capitalization as the B2A endpoint
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patternsSee how this capability changes across valid integration models.