What to check
A useful error report explains what was expected, what happened, and how to repeat it. Screenshots help with context, but selectable error text and timestamps make log correlation easier. Keep customer information out of shared examples.
Troubleshooting steps
- Record the SAP build, company, client machine, operation, exact time, and complete error text, including any nested message.
- Reduce the sequence to the fewest repeatable steps. Note whether another authorized user or workstation sees the same result.
- Collect the relevant logs for that attempt and state recent changes, the business impact, and any tested workaround.
Confirm the result
A colleague should be able to repeat the issue from the report. Distinguish observations from suspected causes so support can test the hypothesis independently.