202
CAPABILITY TOPICExplore the building blocks that make PS work
PS 202 · CONTROL
How do planning, budgeting, and status differ?
Keep cost and revenue planning, approved budget, availability control, forecast, versions, and lifecycle status conceptually separate.
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
01
Plan versus budget
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →02Availability control and releases
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →03System and user status
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →DESIGN DISCIPLINE
Do not confuse a capability with one process
The same capability can participate in several streams. Configure it only for approved scenarios.
Business rule→SAP object→Evidence→Financial result
CONTINUE THE PATHContinue to PS 303
Open patterns →See how this capability changes across valid integration models.