cancel
Showing results for 
Search instead for 
Did you mean: 

Agent assignment 's icon become not active

Former Member
0 Kudos

Hi guys,

i am currently facing this problem , in PFTC, step 657 object BUS2105, method RELEASEUPDATEPROFILE , in Dev the agent's icon is green (active) , somehow in production, it becomes not active (gray) color, can you please help and advice, how the icon can become not active?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

This setting of agent assigment is client specific and also system specific.

You might have a customizing request got created when you did this agent assignment in DEV system. Just transport that customizing request in PRD.

If you do not hae the request, then still you can do the setting manually similar to DEV system , in PRD system eventhough Workflow builder is in display mode.

Hoep this helps you.

Regards,

Akshay

Former Member
0 Kudos

Hi Akshay,

Can you please tell me the path in spro, the setting of where the agent assignment took place

Former Member
0 Kudos

Hi,

when you are inside Wf builder and select the particular step by double clicking, click on the Button near Agent assignment inactive icon.

After that you will be able to see the screen where you can choose the task <i>Attribute</i> ( Button) as General task or which ever is required .

Regards,

Akshay

Former Member
0 Kudos

Hi Akshay,

I have done the steps and the agent icon became active already, now i have another problem.

I check SWI5, and can find the work item parks under the user, but if i use the user's id to login and check it is not inside SBWP.

i use SWIA to check, it says that the agent is not available even in SWI5, the work item is already in there.

Can you please help on how we can trigger this to SBWP , do we have to do one by one using SWIA ?

Former Member
0 Kudos

Hi,

Pls check if user has sufficient / proper authorizations so that he can see work items in his inbox. You can take help of basis guy for this.

Regards,

Akshay

KKilhavn
Active Contributor
0 Kudos

This is probably just a buffer update problem. After changing the assignment of possible agents, you need to regenerate the indices/update the buffers. There is a button to regenerate the index in the agent assignment screen, but in SBWP you need to go into the menu (same menu you go to to change personal workflow settings). Once you have done that (I mean to recall the menu item is called "Refresh organisational environment") you just refresh the inbox and the work item will be visible.

However, you probably won't read this until after midnight, so the problem will automagically have solved itself

Answers (1)

Answers (1)

Former Member
0 Kudos

Before transporting please check Tcode OOCR and check the entry for General task be unchecked. This is absolutely necessary. This setting is set as checked in default. You need to uncheck it. It is the duty of Wflow Expert to recognize this and change it before transport.

Thanks

Arghadip

martin_nooteboom
Active Contributor
0 Kudos

Hi Arghadip,

Could you explain what you mean or elaborate on it? I checked transaction OOCR out of curiosity but couldn't find and entry for general task. Also I am not sure what you mean by the entry should be unchecked, what will this accomplish?

Regards,

Martin

Former Member
0 Kudos

Hi Guys,

I have activated the Agent assignment yesterday, re-generate the index, but today PR created still encounter agent is not available and user didn't receive notificaiton in their SBWP, please help and advice how i can trace this ?

martin_nooteboom
Active Contributor
0 Kudos

Hi Ester.

Did you check the workflow log to see where the task went to? Maybe the task went to the wrong user.

Regards,

Martin

Former Member
0 Kudos

Hi Martin,

THe WF log does not indicate error, step 596 , the FM to get the agent generates username SSOBAH, but when i click on the Agent icon in wf log, it states 'No selected Agents'. I even borrowed the user id and check her SBWP, the PR was not sent to her .. how can i prevent this from happening today as we have many PRs already issued and not sent out to the users

KKilhavn
Active Contributor
0 Kudos

Seems you have no overlap between possible agents and selected agents. The only question remaining is why. If the task is a general task the problem <u>must</u> be in the rule.

When you say "the FM to get the agent generates username SSOBAH", are you then referring to a user name field internally in the function module, or to the contents of the returned structure (SWHACTOR table)?

Remember the user name is only the object ID part of the agent specification. It must be prefixed by the object type US.

<i>Message was edited by Kjetil Kilhavn:</i>

Hmmmm... I see the question is marked as answered. So forget this post

martin_nooteboom
Active Contributor
0 Kudos

Hi Ester,

In the log what does it read when you click on Possible agents?

Regards,

Martin

Former Member
0 Kudos

Hi Martin,

It says that 'All users can process this task'.

martin_nooteboom
Active Contributor
0 Kudos

Hi Ester,

You should check Kjetil's answer. I think your answer is in there.

Regards,

Martin

Former Member
0 Kudos

Hi Kjetil,

THis problem is solved only for activation of the agent assignment in the WF template but not for the SBWP case in where now the users do not receive any.

SSOBAH is already set in the org chart with object type US , i tested the scnenario in qas , it is working but not in production environment..pls help

KKilhavn
Active Contributor
0 Kudos

You are aware that agent settings are client dependent? So, basically you need to do the same job in each system - unfortunately.

Former Member
0 Kudos

Hi Kjetil,

Yes the agent setting for org chart is client dependent . can u pls advice on how i can work on these? i just executed SWU_OBUF to refresh the buffer, shall i wait until tomorrow ? because the i read in the book, the update starts at 00:00:00

KKilhavn
Active Contributor
0 Kudos

I don't understand what you are asking when you ask "how I can work on these", but with respect to the buffer there is usually no need to wait until the next day. Using SWU_OBUF is all it takes as far as I have experienced.

Former Member
0 Kudos

Hi Kjetil,

I am not facing the case in where users do not received SBWP.

I have done SWU_OBUF but still it happened until today.

This is the error i got from SWI6.

1. Agent determination for step '0000000657' failed

Message no. SWF_RUN519

Diagnosis

An error occurred when determining users for step 0000000657. This error can be caused by a problem in the resolution of a rule for agent determination. See the additional messages within the workflow log.

2. Result of agent resolution does not agree with agents of task

Message no. SWF_RUN544

Diagnosis

When determining the recipient, the system established that none of the responsible agents determined belong to the possible agents of the task used in this step.

In the WF builder, step 657 uses rule 20000026, i have checked the binding exists and no error happened.

Field 'Terminate if Rule Resolution has no Result ' is already ticked.

is there anything i shud check to ensure the agent is working?

KKilhavn
Active Contributor
0 Kudos

> is there anything i shud check to ensure the agent is working?

>

Not that I know of. It seems to work perfectly. You have defined possible agents, and you are using a rule that finds selected agents. The rule is defined so that it will fail when there are no agents. And it does, i.e. it works perfectly.

This could be a master data problem, incorrect definition of possible agents, or something wrong in your rule. Impossible to say. You have to figure that out yourself.