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.
Request and notification
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns02Failure and condition evidence
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patterns03Screening and prioritization
Define the rule, responsible object, required master data, resulting document or posting, and proof.
Compare patternsDESIGN DISCIPLINE
Do not confuse a capability with one process
The same capability can participate in several streams. Configure it only for approved scenarios.
- 01
Business rule
State the approved condition, decision, and accountable owner before deciding how SAP should behave.
- 02
SAP object
Assign that rule to the object that carries the responsibility, master data, status, and control.
- 03
Evidence
Identify the document, confirmation, posting, or status that proves the intended result occurred.
- 04
Financial result
Reconcile the controlled outcome, cost or revenue effect, and receiving responsibility.
See how this capability changes across valid integration models.