An incident is an unplanned interruption or reduction in business service, managed to restore safe operation. A problem investigates a recurring or underlying cause of one or more incidents. A change request proposes a controlled modification to an application, configuration or operational service. A single SAP issue can lead to all three records, but each has a different objective, owner and evidence requirement.
Incident: restore the affected business service
A warehouse suddenly cannot post goods receipts. The support team logs symptoms, system and process scope, business impact, urgency, users affected and evidence. It identifies an owner, communicates to stakeholders and tries an approved workaround or restoration. Success requires business confirmation that processing works safely, not merely that an error pop-up has disappeared.
Problem: understand why disruption keeps returning
If the same goods-receipt failure returns every Monday, problem management can analyze multiple related incidents. The investigation compares data, interfaces, recent changes and configuration patterns, distinguishing hypotheses from validated root causes. An incident can close after restoring service even while a problem record remains open to prevent recurrence.
Change request: authorize a proposed correction
When a durable change to mapping, authorization or configuration is proposed, it needs risk assessment, approval, testing, release planning and rollback under the organization's change governance. An incident ticket does not automatically authorize production modification. Emergency changes may have specific processes, but business urgency is not proof that normal controls may be skipped.
One case can create a chain of evidence
A payment interface stops, so the desk raises an incident and restores an approved temporary workaround. Repeated failures reveal an underlying input issue, captured as a problem investigation. A validated mapping change is then proposed and assessed. After deployment, Finance confirms that the actual business postings are correct before concluding the chain.
Make ownership and metrics explicit
Incident managers track restoration and communications. Problem owners investigate root cause and prevention. Change authorities control scope, approval and deployment evidence. Ask who declares business recovery, when repeated incidents become a problem, how urgent modifications are approved, and whether documents maintain links across the lifecycle. Exact ticket names and SAP tool coverage vary by customer landscape.