Some typical examples :-
Missing basic information
Users forget to enter critical data into the error reports, for example which system is affected, which SAP transaction was running, which Sales Order has the incorrect data etc. You simply can’t start investigating the problem without information like this.
Incorrect information entered
Users mistype information, for example enter a wrong material number etc. This can make your developers debug for hours just to come back to the user that everything works fine. “Ooops, sorry it was Purchase Order 112000898 and not 112000989.”
No technical information
Users can’t add technical data, for example they don’t know how to get the program and screen number of the current transaction. This is fine, why would they be trained to know this?
Missing attachments
Users forget to add a screenshot, short dump or an authorization report that will be required by the support staff anyway. If you had one dollar each time your IT support asked for a screenshot or a SU53 authorization report, you’d probably read this post on your yacht in Monaco.
Also, there are so many different ITSM tools out there. In order to report an error in SAP, users have to open new browser windows to launch the ITSM tool to report the error. There of course they have to enter all data manually that may take some time. Some organizations have more than five ITSM tools implemented. Test system connected to HP Quality Center, production system connected to ServiceNow, a development project using Bugzilla. Different UIs, different processes. No wonder end-users may become confused.