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

Similar Messages

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

Agent Determination error in workflow

Hi all ,
We are working on Travel Management workflow ( 4.6 C ) . We have transported the workflow to our quality server where the workflow is giving error .
The workflow is not able to determine the agent for a task giving an error "no valid agent found" . We then executed the FM which was attached to the role which gave us the desired output .
Any inputs from your side ?
Thanks ,
Sonu M.

Sonu,
Task attributes are HR data and have to be moved using a standard HR data transfer program.
Use program RHMOVE30 - enter object type TS, and your task number. Use eval path TASKHIER.
Use the dropdown on the request parameter to create a transport request.
When you get the result list, make sure your task is selected for transport then use the option to include it in the Transport.
You should then be able to go to txn SE09 and see your task has been assigned to the transport.
You can then transport your task.
Regards,
Jocelyn

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

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.

Agent determination problem

I have a workflow that has been in production for almost a year. We are in the middle of integration testing for another rollout and I'm getting agent determination errors in this workflow. There are three steps involved. The first two use the exact same rule. The first of these two works fine. When it tries to run the rule again for the second step, it gets no agent found. If I test the rule it works. If I restart the workflow, it works. When it moves on to the third work item using a different rule, it errors out no agent found. When I test this rule, it works. When I restart at this step, it also works.
This is a new integration client that was copied from production. I've performed the standard workflow customization like I always do. I've run several other workflows and only notice the agent determination problems in this one. The workflow hasn't changed in months although there have been some user security changes...I'm not sure how that could really affect the agent determination during the creation of work items.
One thing that might be important...userA created the first workitem and the agent determination resolves to userB. When userB executes the first work item and completes, the second work item should also resolve to userB using the exact same rule. This fails. I restarted it using my account and it resolves to userB. UserB executes work item #2 and work item #3 should resolve to userC but the agent determation fails again. I don't know whether the work item agent is "used" to perform the creation of the next workitem or not but this is the only difference between the first two work items and one works while the other does not.
It's almost like userA can perform the agent determination but userB cannot. I can't manually execute the agent determination as userB so I ran se37 as myself in debug and changed SYST-UNAME to userB and it worked fine and returned userB as the agent. That would seem to eliminate security as an issue with the agent determination.

Hi,
Are you absolutely sure that it is not an authorisation issue? Can you give SAP_ALL (and the possible structural authorisations) to all the users that are involved in the process? (I don't think that changing sy-uname in debug mode to another user really is a correct way to try to prove whether this is an authorisation issue.)
The agent determination of the following step is executed by the previous WF agent, if there is no background steps between. So if the previous agent doesn't have enought authorisations, the agent determination will fail.
Regards,
Karri

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 issue with no error, cant use SWPR?

Hello gurus.
We currently have 81 invoices that have workflow status "in process". However, the last line of this status is "agent determination issue". I've assigned the appropriate user in PFOM and i want to restart the workflow item, but i cannot use SWPR.
Normally it should be in error and you can use SWPR, and that fixes everything- however why is the workflow still "in process" and not in error? and how can i complete the workflow item now that the agent has been assigned? do i just create a new workflow using SWUE and delete the old one? Many thanks.

Hi,
OK then try like this , as you said you do not have authorizations to SWI1_RULE right so do teh below steps,
1. Execute SE37 and execute the fucntion module ALINK_CALL_TRANSACTION.
2. Now mention the txn name as SWI1_RULE.
3. Now you should be able to see teh initial screen of the txn.
4. Now enter teh workitem ID which is in ready state not the top workitem ID, the workitem for which the agent is not assigned. Click F8.
5. Now choose that workitem ID and click CTRL + SHIFT + F11.
it should re evalutae the agents, if this is also not determing then make a note of the RULE ID from activity step and open the txn by using the above function module and try to simulate the rule or please let us know what is the rule type.
Regards
Pavan

Purchase Requistion - Agent Determination using responsibilities - Issue

Hi Everyone,
I am new to workflow. I am having an issue wrt Purchase Requistion - Agent Determination using responsibilities.
Created some 30 to 40 resposibilities with combination of inputs - R1, P1 & Cost Center
Checked rule with responsibilities in Simulation mode and for the given inputs shows correct output.
Same config is present both in DEV and ACP. Simulation works fine in both systems.
But when I created Purchase Req. in DEV and save it. Workitem is generated for the correct agent. But when I do the same test in Quality, it fails and created Workitems for several agents.
Checked container info. in both systems,no.of agents is the ONLY difference (i.e. 1 in DEV and 30+ agents in Quality).
Put shred some light on this issue.
Workflow Used: BUS2009
Task : TS00007986
Thanks a ton in advance.
Regards,
Krishna

Hi,
Open the workflow (WS*******) with SWDD and see the bindings for the rule in the approval step (using TS00007986). Do they look the same in both environments? Are you passing the same parameters for the rule?
Another thing that you should check is a possible authorisation error. Maybe the users are not authorised to execute the needed functions for finding the agent inside the rule (common problem).
Also try to read the technical workflow log (Start a workflow, open SWI1 and drill-down to the workflow log). Can you see some error messages there? You will probably find a message saying that "cannot execute agent rule" or something like that. It is WF behaviour that if it cannot find an agent it will send the work item to all possible agents (unless otherwise configured).
Regards,
Karri

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 Organizational Data

Hi Experts,
Good Day!
I would like to ask some help regarding a workflow the problem is the "user received the workitem however user claimed that he is not supposed to receive" that is why i would like to know who are the agents dedicated for these tasks. we are able to find the step it is a user decision where the agent is the Rule "0090010" for purchasing group. In transaction PFAC we entered the rule "0090010" the information regarding the rule below:
Transaction: PFAC
Rule Display:
      Basic data:
               Abbr: Purch. group
               Name: Purchasing Group
Rule Definition:
      Category: Agent Determination: Organizational Data
      OrgObj type: T024
We would like to know:
1. How does it determine the Agent who is supposed to receive mail using the "Category: Agent Determination: Organizational Data"? Where can we find the agent that is configured on the workflow using the rule?
2.Is there a standard rule for agent determination: Organizational Data for this workflow?
Answer's will be a great help.
~Thank You,
Junne Ray

got it now! sorry, i am a bit dumb today.
o.k. here is what you have to check:
transaction PFOM - relationship between the purchasing group (which will be the one of the PO and therefore and object of table T024) and your organizational structure. check the relationship.
documentation:
Data basis for role resolution
For role resolution, the link between the objects of type
T024 (individual purchasing groups) and the organization
objects (position, organizational unit, ...) is evaluated.
Required settings and Customizing
The linkages between the various purchasing groups and the relevant
organizational objects must first be maintained using
transaction PFOM.
Procedure for errors
If the role resolution delivers no result, the work item for which the
role resolution was carried out is not faulty but addressed to all
possible processors (flag "abend in role resolution without result"
is not set).

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 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.

Agent determination for workflow

Hi everyone,
I have a classic issue: I'm trying to assign a workflow task to an agent. The agent should be determined from the container element "APPROVER". In the task I've entered the expression &APPROVER&; however, I'm receiving error "Agent determintaion for step 4 failed..." "Result of agent determination does not agree with agents of task". And, yes, I've made sure the APPROVER element is of type Import and has a proper value.
I don't get this; I thought setting the agent to the value of the container element should do the job? After all, the container element "APPROVER" comes up in the F4 search help under the Decision tab of the task... what's wrong here?
The WF works fine if I set the "WF_Initiator" as the agent, however. But, this is a bit limiting in the long run...
Regards,
Trond

Hi Ravi,
this is what I actually did... but I found another post, with a reply from Ramki Maley, advising me to make the APPROVER of type SWHACTOR. That helped!
Thanks anyway,
Trond

N Step BADI Approval Workflow Error in SRM 7.0

Hi,
I have implemented SC Workflow Approval based on line item(sequential approval). I implemented process controlled workflow for this using N step Badi. Necessasy configuration done for each level at schema. All steps are executed per line item and agents determined using N step Badi /SAPSRM/BD_WF_RESP_RESOLVER.
Even in SC after the document is ordered, in approval overview tab i see the all level sequence with approvers name for that line item.
But when approved by first approver, it doesnot move to the next level for approval and the SC is approved bypassing all approvers in the following levels.
For example, if there four levels of approvals for one line item. as soon as the first approver approves the SC is approved and in SC Approval Overiew tab that contained four level of approval in it is now reset to one level with SC marked as appproved.
Have anybody come across this error.
Not able to figure out why it is happening so... need some expert advice.
Thanks in Advance.

Hi Masa .. thanks for your reply.
Was on vacation so could not reply.
I have below settings in SRM for SC
Process Level definition should be like this.
Level Eva.ID ; Resolver Task ID Decision Type
100 L100 R100 40007953 Item-Based decision for Partial Doc.
200 L200 R100 40007953 Item-Based decision for Partial Doc.
300 L300 R100 40007953 Item-Based decision for Partial Doc.
I have implemented /SAPSRM/BD_WF_RESP_RESOLVER for R100.
for grouping we are using line item number ... so each line item is a group.
Below are issues that i am facing now.
For say 2 line item in a SC... with 3 level of approvals for each line item. I am not able to approve one line item in a sequence. For example: If for first line item, when I approve level one .. then the workitem doesnot move to 2nd approver's inbox for that line item. Now if second items (asssuming there are only 2 line items in SC) first approver has approved then i see all second level of approvers available for all line item.
In short system waits for all one level approvers to approver for all line item and when all the line items are approved at one level then the workitems are available for seconds level of approval.
Is this the standard behaviour?
As per our requirement we wanted one line item shoudl follow the approveral sequence without being dependent on other items approval.

2 step confirmation agent determination error

Similar Messages

Maybe you are looking for