Agent Determination Problem

[Former Member]

Hi,

I m using a task to determine agents for PO approval using Responsibilities. The responsibilities are based on the purchase group(PG) & release strategy(RS).

The workitem for approval for a particular PG & RS goes to the correct agent as per mapping. But additionally, there are a few users who receive workitems irrespective of their responsibilities.

eg. user A is approver for RS10

user B is approver for ST10

user C is approver for PQ10

user D is approver for xy10.

In my case, the workflow for RS10 picks up A & D as approvers, the workflow for ST10 picks up B & D as approvers, the workflow for PQ10 picks up C & D as approvers.

I ve double checked the mapping, its alright. But in the rule simulation, it shows these additional users.

Where could the problem be?

[Former Member · Accepted solution]

Hi,

you can display and maintain from PFAC.

but i think that you should check the Release Strategy and Hierarchy for that.

Hope magic Works!

Regards,

Purvesh.

[Former Member · Accepted solution]

Hi Purvesh,

What I want to find out is this:

Lets say that in the rule the agent is determined from amongst 10 responsibilities(i can see them from the 'responsibilities' tab in PFAC). When I simulate the rule, I supply the container elements values and I get the agents. But I dont know which responsibility was used. I want to find that out.

Is there a way to do that?

What do you mean by check Release Strategy and Hierarchy? How would that help?

Thanks

[Former Member · Accepted solution]

Hi Adarsh,

You need to go to the workflow log and find the reason. Just go inside the transaciton SWIA and see the agent has determined.

if not determined then you need to rebind all the controls in the workflow and exectue it again. sometimes it happens.

Thanks,

Chidanand

[Former Member · Accepted solution]

Hi Chidanand,

Thanks for your reply.

The problem I am facing is not that agents are not being determined. It is that along with the correct agents mapped(via responsibilities) some additional agents are also picked up. I dont know where they are being picked up from.

Any inputs to help me identify the root cause are greatly appreciated.

Thanks

[Former Member · Accepted solution]

Hi Adarsh,

Did you check the rules for the agent determination.

Also check if you have used any FM to determine the rule then you need to just scan the code and see where is problem is.

Thanks,

Chidanand

[Former Member · Accepted solution]

I think you can check this from transaction PPOSW by giving the User ID only if it is not attached to Personnel Number. If attached to Personnel number you have to search with Person in that transaction code.

You can also check this data from table HRP1001

Thanks

Arghadip

[Former Member]

Issue resolved

[Former Member]

Hi,

I am facing a similar problem that my PO rule always picks an additional user than which is maintained in the rule. I had checked all the responsibilities and made sure that the particular user not maintained anywhere inside the rule. Still it picks up that user by default.

I could see that while simulating the rule as well in PFAC. Could you please explain how did you go about resolving your error.

Thanks,

Kanag.

[Former Member]

Hello,

You're more likely to get an answer if you open a new thread with full details of your problem, including SAP version and what you've tried so far.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi,

Thanks to every one for all the suggestions. I tried them, but still the problem persisted.

Anyways, I did a bit of digging and it turns out that for agent determination using responsibilities, the std. function module 'RH_RESOLVE_RESPONSIBILITIES' is used. I had to debug that.

Turns out that it was picking up all the responsibilites in which neither Release Code/group/strategy were defined. Somehow, to some of those responsibilities, users were assigned and it was these agents that were being picked by default all the time.

[surjith_kumar]

Hi,

The value which you passing to internal Table (ACTOR TAB) may hold additional user id. Check whether the work area are clearing properly, before assigning the user id.

Regards,

Surjith

[Former Member]

hi Adarsh,

you can do one trick that you can restrict the table ACTOR_TAB

By only one entry!

See workflow log via SWIA and see which responsibilities are used may be more than one responsibilties are used!

your problem will be resolved.

Hope magic Works!

Regards,

Purvesh.

[Former Member]

Hi,

I think that there is a faulty responsibility id in this case. Is there any way to find out which responsibility is being used in the rule through the workflow?

Thanks

[former_member184112]

Check their(additional users) Roles and Authorizations.

[Former Member]

Hi,

Thanks for your immediate reply. Where & how can I check the Roles & authorization of the extra workitem recipients?