The standard does not really give much options to fulfill this requirement. Perhaps the biggest problem here is that it is a bit hard to say that who is (or are) the original user(s) and who is not. When the work item gets first created, they are "sent" to the agent (let's call it the original agent). At this point, you can easily find who is the agent (table SWWUSERWI or certain WAPI-function).
Now there can be multiple reasons why the work item gets transferred to different agent. E.g. a work item gets forwarded or a substitute user clicks/reserves it. Basically you can find these "actions" from the step history (and if I remember correctly, there is a function to read this). So, basically you could have a report that goes through all the active work items, and then reads the step history and you could see if the work item was reserved by a user (by reading the step history).
Problem 1: At this point, you don't know who was the original agent. So you cannot compare the possible new agent and the original agent. Basically you should store the original agent to a Z-table or something like that.
Problem 2: Let's say that you know who is the original agent (this info is stored somewhere). Now you could check that the original agent and new agent are different. So, how do you know if there is a new agent, because of substitution? Well, you could read this from HRUS_D2. You could see if the original user had set up a substitution for this "new user" and then come into conclusion that the work item has changed agent because of substitution. Anyhow, this will not work after the user possibly comes back from holiday and deletes the substitution. At this point you don't even know that a substitution existed. There is no entry in HRUS_D2 anymore.
Do you know what really is the problem of your client? They want a report (which could be difficult to build), but normally that means that they want to solve some problem with that report (work items do not get completed on time etc.). There could be much easier and better ways to tackle the problem than building some kind of report.
Regards,
Karri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.