202
CAPABILITY TOPICExplore the building blocks that make EAM work
EAM 202 · PREVENT
How does preventive maintenance become due?
Use strategies, plans, items, cycles, counters, task lists, and scheduling parameters to generate controlled work.
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
01
Time- and performance-based plans
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →02Packages, cycles, and task lists
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →03Call horizon and scheduling
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 EAM 303
Open patterns →See how this capability changes across valid integration models.