202
CAPABILITY TOPICExplore the building blocks that make EAM work
EAM 202 · DETECT
How is maintenance demand captured and qualified?
Connect requests or notifications to technical objects, symptoms, damage, cause, priority, malfunction, safety, and history.
CORE MODEL
Three questions to resolve
A sound design makes ownership, control, and evidence explicit before configuration.
01
Request and notification
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →02Failure and condition evidence
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns →03Screening and prioritization
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.