Agent determination of 'general' task fails....

I have a task in the workflow which i have kept as general task
I have attached a rule to it.
when the rule doesnt return any agents, the workitem is sent to all the SAP users
this is a very big problem, could you please suggest how to prevent that ?
if the rule doesnt give any agents then the workflow should hang, it should go to all the SAP users.
thanks and regards,
Dipti

Hi Imthiaz,
I have already checked the workflow log and I know very well why my workflow is in error.
My requirement is that even if the workflow goes into error, this message entry should not be created.
As per my knowledge, this is created in workflow administrators inbox due to setting in SWU3 -- Schedule Background Job for Work Items with Errors
But it doesnt look like the above settings effects this message creation. There should be some setting somwhere right ?
Also, it is only in quality system not dev
Dev -- workflow goes in error -- no message seen
QA -- workflow goes in error -- message seen in workflow initiators inbox
please help.....
thank you
regards
Dipti
Edited by: dipti on May 6, 2008 6:30 PM

Similar Messages

Agent determination for step 0000000081 failed error in workflow

Hello All,
I am doing employment verification from ESS portal. In the workflow step I have selected RULE to determine the agent. To configure rule, I double click on rule, on next screen selected "Agent determination - responsibilties" to determine the agent. I configured responsibilties with the valid value ranges and everything but the workflow is going into error! I did research and not sure what I am doing wrong. I checked the workflow container in workflow log and all the values that are supposed to pass to rule container are showing up fine.I keep getting the error:
Agent determination for step 0000000081 failed
Result og agent resolution does not agree with agents of task.
Any feedback you could provide would be greatly appreciated.
Thanks.
Mithun

1. In Transaction PFTC, select Task Type = Standard Task and Task = 01000076
2. display the task details.
3. Now go to Additional data ->Agents Assignment->Maintain
4. Select the task here and click Attributes in the application tool bar.
5. Select the General Task radio button and hit transfer.
-- You have made your task general.
To Synchronise the runtime buffer ,simply excute T-Code SWU_OBUF and hit the Start Synchronization button.

Agent determination for another task

Hi Experts,
I have assigned agent as US for a task. One custom FM is called for an approval screen and that FM is called from the method . That method is assigned to that task. The approval screen should have the approver name.
How to pass the agent assigned for the task to the FM assigned in the method.
Reagrds
Sathish

hi,
plese find my sugestion.
1. In any of the previous steps, find the approver name.Pass that approver name from the 'METHOD' to TASK container.from TASK Container to the WORKFLOW Container
2. Then in the current step, Bind the 'APPROVER_NAME' to the TASK, and then to the 'METHOD'.
3. now u can use the APPROVER_NAME inside the method.
hope u r clear, if not pls lets know.
Regards
Anversha

Error in resolution of rule ... for step - Agent determination failed

Dear All,
In SRM 7.0 CS, i am having a problem in the area of work flow. In general, the workflow is working fine, but at times the work item does not get delivered to the approver.
As per the analysis from SWI2_DIAG, the error is the following for the concerned shopping carts:
Error handling for work item 000000056146
No links corresponding to the specified data could be determined
Error in resolution of rule 'AC40000138' for step '0000000293'
Agent determination for step '0000000293' failed
Error during result processing of work item 000000056156
Error when processing node '0000000293' (ParForEach index 000000)
Error when creating a component of type 'Step'
Error when creating a work item
Error when processing node '0000000293' (ParForEach index 000000)
Work item 000000056155: Object FLOWITEM method EXECUTE cannot be executed
Error handling for work item 000000056154
Error when processing node '0000000293' (ParForEach index 000000)
Does anyone have an idea on the root cause of this error?
Thank you very much.

Hi Masa,
thank you very much for the reply.
Yes, rolewise the approver is having the manager role in SRM and also on the portal. But what do you mean by "manager position in PPOSA_BBP"?
The user is hanging in his node together with the other users. Is there any specific "manager position", where the approvers have to be put in PPOMA? I mean, the other approvers, for whom the workflow is working normal, are hangig in their nodes just like the approver who is not getting the work item.
Moreover, if i drag the users (the requestor and the approver) into an other node (for another plant of another company code for example), than the work flow is working fine.
Can there be any other reason for such an error?
Thank you very much.

Error in resolution of rule ... for step - Agent determination for failed

Dear Experts,
in SRM 7.0 CS, i have come accross the following workflow error:
I have extended my existing organizational plan for a new site (new CoCo, Plant, Purch Org and Purch Gr). But when i use my test users with this site, i receive a workflow error, that has the following wording in SWI2_DIAG:
Error handling for work item 000000055347
No links corresponding to the specified data could be determined
Error in resolution of rule 'AC40000138' for step '0000000293'
Agent determination for step '0000000293' failed
Error during result processing of work item 000000055357
Error when processing node '0000000293' (ParForEach index 000000)
Error when creating a component of type 'Step'
Error when creating a work item
Error when processing node '0000000293' (ParForEach index 000000)
Work item 000000055356: Object FLOWITEM method EXECUTE cannot be executed
Error handling for work item 000000055355
Can you maybe help me understand, what this error means and how to resolve it?
Thank you very much!
P.S. my test users work fine if i drag them to another location in my organizational plan. And also if i take other test user from locations where everything works fine and drag them to this "problem" location, than the same workflow error occures.

Remove the user from the PPOMA node and add him again.. Sometimes this will solve the issue..
Thanks!!
Bharath

Agent determination issue in a workflow

Greetings everyone!
I'm configuring some business scenario with the help of a business workflow in SAP CRM 7.0 I'm using activity step and want to determine agents using standard SAP rule 10000162 ("Employees for responsible org. unit"). I've tested the rule outside of the workflow and it's working fine, but in workflow it fails to determine an agent.
In a log I see following errors:
Agent determination for step '0000000023' failed;
Result of agent resolution does not agree with agents of task;
I've made some tests depending on what assignment task has:
1. When it is a general task, work item was created for a workflow initiator even though rule failed to determine an agent.
2. When it is a task with general forwarding with assigned position(s), which rule will never determine, work item was created for holder(s) of that position(s).
3. When it is a task with general forwarding with no assignments, workflow could not determine an agent as expected.
I've also debugged functional module for that rule and it determines appropriate agent but then do some check with the help of RH_TASK_AGENT_CHECK function and returns an error.
Can someone help me with this problem? Is it some standard expected behavior or not?
Maybe something wrong with the org. plan?
All answers are appreciated.
Thanks in advance,
Alex.

Hello Rick and Eddie.
I've tried to assign user directly instead of position to a task with no help. I get the same result.
I've tried to set a task as a general task and made the rule to fail if there is no resolution and it fails.
I've tried to assign position or user directly to activity in a workflow and it does work but that's not what I need in my scenario.
As I said earlier I've tried to debug that rule invoked from a workflow. I will post some screenshots for you.
I set a task as a general task and assigned rule 10000162 (ABBR="PARTNER_1", Name="Employees for responsible org. unit") to activity step in a workflow and here is what I get:
1. Function CRM_ORGMAN_ORGOBJECTS_FIND_2 gets called by the rule and resp. sales org. unit is passed there ([screenshot1|http://www.picdrop.net/?v=debug1.png])
2. Next function CRM_ORGUNIT_GETEMPLOYEES gets called passing id of a resp. sales org.unit without a type.
3. Next RH_STRUC_GET gets called and returns result table with position and central person for that position ([screenshot2|http://www.picdrop.net/?v=debug2.png])
4. In the end of CRM_ORGMAN_ORGOBJECTS_FIND_2 function only central person in inserted to the actor_tab ([screenshot3|http://www.picdrop.net/?v=debug3.png])
5. After CRM_ORGMAN_ORGOBJECTS_FIND_2 ends we appear in a RH_GET_ACTORS function where we can see that agent check is performed if act_task is not initial. I assume that check is not performed if we do a simulation of a rule ([screenshot4|http://www.picdrop.net/?v=debug4.png])
6. Then RH_TASK_AGENT_CHECK function gets called for every record in a actor_tab. In out particular case it's one record. ([screenshot5|http://www.picdrop.net/?v=debug5.png])
7. Inside that function checks act_wi_id (activity work item id?) if it's initial and get exluded agents. It is initial in my case ([screenshot6|http://www.picdrop.net/?v=debug6.png])
8. Then function tries to read table with keys equal to type and id of found agent and errors there, perhaps because there is no record in that table ([screenshot7|http://www.picdrop.net/?v=debug7.png])
That error results in overall agent determination failure.
Hope this screenshots will help to identify a problem.
Why read table results in an error and because of that all rule fails?
Regards,
Alex.

Agent Determination - PR Item Release

Hi All,
I'm trying to set up standard workflow WS00000038 for purchase requisition release notifications. I'm having a problem with determining the correct agents. I receive the following error in the log when the workflow runs:
Agent determination for step '0000000003' failed
Error in resolution of rule 'AC00000148' for step '0000000003'
I am using standard task TS00007986, and rule 00000148. The configuration for the release procedure is complete and working. I have maintained values for users in T16FW, and set the release codes to '1' for workflow. When I try simulating rule 148 in PFAC, I see that it is pulling from table T161E - and the only release code maintained there is a default 01 in german. I tried creating a custom rule that referenced T16FW, but the simulation failed for it as well.
I am very new to workflow. What do I need to do in order to have this event notify the correct user defined in customizing?
Thanks,
J

Hi,
The entries in table T16FW are made via customizing for the PR release. View V_T16FW is empty... I tried entering manually through SE16 and saving, but it would be blank if I looked at it again.
However, I don't know if that is the problem. I cannot get the rule to determine an agent in PFAC. Currently I have modified rule 00000148 to have the container ReleaseCode look at table T16FW, field FRGCO. It is also still getting requisition from BUS2009. When I simulate in PFAC, I cannot get an agent to be determined.
T16FW contains a link to usernames which are maintained. Why is this rule not determining an agent during simulation?
Thanks

Agent determination failed

HI
I am using a rule with responsibilities created through PFAC in the loans workflow.
We upgrading are from 4.6c to ECC.6
The workflow and rule use to work well in 4.6c.
In ECC 6 ,Simulating the rule works fine,but when running the workflow an error occurs.
The workflow runs well in Delopment box and the error is only on production box
I get the error "Agent determination failed" but when i restart the workflow manually through 'SWIA' the worklow complete succefully.
Thanks
Rendani

HI,
What points I could think of is:
1. Check if task agent assignment atributes ae maintained properly e.g. General Task etc in PRD system.
2. Responsibilities are in place in PRD system same as Development system.
3. Check if any authorization differerence from DEV system , i.e. Responsibility rule might faile due to lack of authorization to certain user ID.
Regards,
Akshay

PR Overall Release Workflow - Agents Determination Failed

Dear All WF Experts,
I have used the standard workflow WS20000077 for PR Overall Release. I have assigned the agents to the task TS20000159 by position maintained in the Workflow Organizational Management Structure. The agents' names are showing correctly in the task's agent settings.
However, when I execute the workflow, the error 'Agent Determination Failed' for that step (TS20000159). I have checked the agent settings in workflow and SPRO, they look fine. Could anyone please kindly give me advices how to solve this error? Thank you so much.

Hi, to all the experts who have helped me all these while,
Thank you very much for spending time helping me to go through this issue.
Yesterday, I ran through the coding for the function module for the rule AC20000026 again. I found out that there is one part of the coding which is causing the failure of determining an agent. The code disregard the company code for overall release of Purchase Requisition while the business requirement involves company codes in every PR created. Thus, by changing that code, the problem is solved.
The snippet of code of function module (ME_REL_GET_RESPONSIBLE):
   CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung ¨¹ber T16fW
      WHEN '1'.
        IF eban-gsfrg EQ space.
*     Einzelpositionsfreigabe Banf
          SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = eban-werks.
        ELSE.
*     Gesamtfreigabe Banf
          SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = space.
There is always a value in werks in my business scenario...
SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                       AND frgco = rm06b-frgab
                                       AND werks = space.
So, by changing it to
AND werks = eban-werks
it will work, however, I think it's better to just remove the If statement
IF eban-gsfrg EQ space.
, since it has no effect anymore.
I hope this would give a hint to all the rest who might be facing the same problem as well.
Thank you very much,
YL

General Task Error although Agent is found

Hi,
I have a little puzzle that I cannot figure out: I have a rule for a general task. The rule finds the agent for the task. However, there seems to be a error when the task is sent to the agents inbox. Due to the fact that it is a general task it is sent to everyones inbox. Since it is not the rule that is failing, I am wondering how I can avoid the task to go to everyones inbox. I have checked the "Terminate if Rule Resolution has no Result" in the rule.
Please help!
/Elvez

Hi,
As u said "Terminate if Rule Resolution has no Result" is there in rule but can u tell me that, is the check box for is clicked or not, If it's clicked and your if your rule will fail then definately it will send workitem to every one's inbox,
But to avoid this there is someting call as secondery priority in responsibilty based rule. where you can maintain one more responsibilty with some default users and some globle condition in it ..
Ex .. If your promary rule is having some parameter
costcenter = 100.
user = A.
costcenter = 200.
user = B.
costcenter = 300.
user = C.
with 99 priorty .
and it's getting fails caz of input provided by wf cointainer (i.e. 301) ..
then you can maintain one default role
costcenter = 0 to 400.
user = D.
with 01 priorty .
So first rule will goto higher priorty and if it ll fail then it wil not go to error and also consider secondery priorty and give default agent maintained in it..
Regards
Dev.

Agent determination failed in Standard Workflow.

Hi Experts,
I am new to workflow and we are trying to implement the standard HCM process of Transfer.
The worflow is giving this error.
Error when processing node "000000032"
which further says Agent determination failed for step "000000032"
Pls help and guide what can be done to resolve it.
We have checked the Org Structure.
Regards,
SV

Hi,
Thank you for your reply,
Which std workflow you are using ?
We are using the WF WS17900427.
Are you using portal to trigger the workflow and webdynpro screen for approval or adobe form for approval ?
Yes
If the agend resolution is getting failed. What role number ?
Rule ID 17900012.
Have your tested individually from PFAC t-code. Is it giving the correct agent from there. check from there.
Testing individually (onclick of Stimulate rule resolution).
Runtime Error MOVE_CAST_ERROR
Exception CX_SY_MOVE_CAST_ERROR
Regards,
Sanjyoti.

I have assigned standard task as General Task in agent assignment but why there is a red flag beside the agent assignment property in task property like the image below?

I have assigned standard task as General Task in agent assignment but why there is a red flag beside the agent assignment property in task property like the image below?

Hi Atiq
Now that's concerning.....!!!
This error usually shows up when the workflow is not able to resolve the outcome of the decision....no branch is there for the selected decision.
Since, the standard workflow is also going in an error....this is something wrong...
Did anyone play around with the standard decision task?
I am not sure if this will help, try generating the task and standard workflow by executing the FM SWD_WFD_REPLICATE_FROM_9999 from SE37 directly. First, generate the task (give full task ID TS00008267 as the input and execute; and then the standard verification workflow in the next exec).
Try and test again...if this works, generate your custom workflow again like this.
The above is a pure guess and I am not sure if this will work.
Regards,
Modak

Determine possible agents of a standard task

Dear Experts,
is there any way to find out the possible agents of a Standard Task. The agents are assigned fix. Without any rule.
Not for the runtime but for the definition time.
I searched for function module but didn't find anything.
Do you have a hint for me in which tables the possible agents of an standard task are saved.
Thanks a lot for your help.
with kind regards
goekselin

Function SWD_GET_TASK_AGENTS should do the job for you, if I remember correctly.
Regards,
Karri

Agent determination error

Hi all
I am trying to configure a workflow for PO release , the Business object am using is BUS2012 in ECC6.0
Whenever a PO is rejected i need to send the work item to the user(Workflow initiator) who created the PO .
I created a standard task and i am using it in the work flow, where the agent is determined using expression (WF initiator) . The standard task is set to general task.
But the worflow fails at this step due to this error "Agent determination for step failed" and details say "Result of agent resolution does not agree with agents of task" which is SWF_RUN 544
I did refresh the worflow buffer using tcode SWU_OBUF and also refreshed organizational settings in SBWP.
Is there something which is still missing.
appreciate your help.. Thanks
Nataraju

Hi Nataraju,
Select the WF initiator from agent dropdown in standard task as shown in screenshot below
Make sure you activate the WF template and Use transaction SWU_OBUF before you trigger the WF.
It is good to execute Transaction SWU_OBUF after you make changes and activate the WF
Regards
Sandy
Message was edited by: Sandy Singh

2 step confirmation agent determination error

Hi everyone!
We have a prod issue where a 2step app confirmation workflow has failed to determine the responsible agent. This has been working correct for years.
Using bbp_pd, the workflow shows no error message. There's a workitem number created but the responsible approver is blank. The item status is 'ready'. The task is a general task and the workitem was not sent to all.
Would you know any idea that might solve this error? Do we have dependencies in any job failure or any basis issue?
Kindly guide me on this matter.
Thanks in advance.

Hello Reymar,
how do you find approvers, via Z* table or organizational hierarchy?
Is that happening to all your 2-step workflows or only one?
Gordan

Agent determination of 'general' task fails....

Similar Messages

Maybe you are looking for