I have been raised this question in at least last three interviews, but i sense that i am not able to convince them on it, here is the question.
Q: what exactly do you do when you get an error message.
A: I try to recognized by my previous experience, or understand the dialog box, or try to analyze, or i do research in my books, i have a lot of sd books, but guess they don't seem to convince for that, what exactly could be a good convincing answer that should be given.
Given an error, this is the general approach I would take:
1) Understand the underlying process-- what behavior is expected of the system as part of the business? What is happening now? --Root cause analysis.
2) Then drill down to the sub process/area where the error is occuring?
categorize it if it was not recognized till now? or, one off errors? drilling down to the problem area.
3) In case, the error has been there from long, would try to fix it from a long term perspective--it might require configuration change/ abap development/ basis help/ database related/ archiving/ missing information/ no authorization etc...
4) Else, if its an one time error, will drill down further to analyse it and find the cause--this might again mean that this particular sub process is one off case and requires a solution or at that particular time when the process ( program) was being executed, there was some other resource accessing this and hence the error, or a temporary problem.
I guess, this is what was expected from you from a Consultant perspective--my opinion.