No agent found

Dear all,
I ve created a WF with user decision where as i used rule 168 .Wf starts fine and the problem is when it reaches this step it wont go the agent found by the role determination.
I changed the agent part from into a user fro testing purpose or recieving the WI , but still its not goin to the agent.
Can anyone plz suggest the reason.
Also tell me what bidings to be done if i use the default rule and b/w which containers.

While simulating the rule from PFAC_DIS are you getting any users. If yes please check whether the defined task in Wflow is General or Not. If it is not General make it General. How to make it you can search the forum.
If thru simulation in PFAC_DIS you do not get result then you need to setup Line Manager.
Thanks
Arghadip

Similar Messages

  • No agents found, error message.

    For mass mutations in PPOME we drag and drop Employees from one to the other place.
    When we make a new organizational unit in the future, for example 30.12.2008, this isn't really a problem.
    Then we put an employee on this organizational unit at 30.12.2008.
    This won't work, and the system refers to Infotype 1 of the PA data.
    SAP returns; Structure 01 O: No agent found.
    When we put the employee at an organizational unit in present (on a OU which already exists for a longer time) there is no problem.
    anyone an idea?? This one's wurth max points for the right answer.
    kind regards.

    Hi, thanks for your answer, but we already use PA40 for regular changes.
    When there is a large piece of our concern is changing, PA40 is just too slow.
    In stead of transfer each person with PA40 and fill a procedure for these people. We use PPOME to transfer multiple employees to another Organizational Unit.
    We know there will not be a procedure of that action, that is not really a problem.
    The real problem is the error message "No agent found" when updating Infotype 0001 of the PA Record.
    This has worked for us, but now we are working with workflows, planning on qualifications and more.
    If someone has got a suggestion to find the key to our problem, feel free to reply.
    (points are still available)

  • BPM Error - No Agent found

    Hi All,
    I am getting the dreaded "No Agent" found in my BPM. Scenario is :
    1> Receive interface from SAP
    2> Send it to another system. Correlation is activated here.
    3> Wait for Ack step from other system. There is a deadline in this step and if ack not recvd within the deadline time, cancel the process. This is created as another block (named as "Ack" block) and receive step is used to get the ack. I have used the correlation ID from the send step here.
    I have checked the SXI_cache for my process and return code  is 0.
    Message is successfully delivered to other system but there is an error (Red Flag) in the first step (IDOC to PE) in the "Outbound Status" column in MONI. This is the "Ack" block
    Can any one suggest what is the problem ?
    Thanks

    Your BPM is like this?
    1) receive step
    2) send step async, activate correlation
    3) block - receive step, use correlation, deadline branch (control step:cancel process) - end block
    4) send step ??!?
    With IDOC to PE, you are saying that the error appears when XI is trying to send the IDOC (outbound message) to the Process Engine, that is to the BPM? or does the problem occurs when the ACK returns to the BPM?
    Regards,
    Matias.
    Ps: just in case, check with this blog if everything around the BPM is configured ok /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    Message was edited by:
            Matias Denker

  • Handling decision step when no agents found

    Hi Experts,
    I have copied the standard decision step and also made it as a General Task. As in few scenarios, the users can have multiple managers, I have used multiline container element in the agent assignment under 'Expression'. This all works fine if atleast one agent is found.
    Though not normal, I need to handle scenario where no agent is found.
    Currently my workflow is sending workitem to all users whenever no user is found which is not ideal.
    I expected the workflow would stop saying no agents found, but curently the workflow doesnot stop at decision step.
    Is there any possibility where we can hold the workflow at decision step when no agents is found.
    Please help.
    Note: we have cleanup reports run by administrator to complete all the workflows with no agents.
    Thanks in advance,
    Cay.

    Hello,
    "So I want to know if it is possible in any way to hold the workflow at decision step without skipping the decision step or erroring out the workflow"
    There is nothing wrong with having it go into error status - that would alert the workflow admin that something has to be done, and it's easy to locate the workitem (with SWI2_DIAG). You can also easily set up the system to mail the workflow admin when this happens.
    But anyway, if that's what you really want, you could change the task so that it's not a General Task and define the possible agents more restrictively so that it will just end up under the category "workitems without agents". You'll have to research how to do this, I almost always use General Task.
    regards
    Rick Bakker
    hanabi technology

  • Errors: Structure : No agent found.

    Hi,
    We are using extended classic scenario.
    Currently we are carrying out SUS configuration.
    When i try to register the SUS vendor through the link it gave an error like
    Errors: Structure : No agent found.
    Kindly help me
    Thanks,
    Mounika.K

    Hello,
    Please check the entries in BBP_BACKEND_DEST table. The local system should point only to SRM system/client.
    You cannot have more than one local system.
                                                                                    Change the same and also re-check the customizings done in your system. Then run srmsus_selfreg application afterwards.
    Regards,
    Ricardo

  • How to route the workitem to Agent, when no agent found

    1.when agent is not found, i was able to see the workitem in swi2_freq.
       If this is case, how do i send workitem to an agent?
    2. As this is a general task, but i didn't see this workitem in all user's inbox. is it true that if agent not found for a workitem,will be sent to all agents?
    3. I set my userid as workflow administrator, but still am not able to forward workitems to any user in sap.(lack of authorizations). What kind of authorizations required to forward a workitem.
    Any inputs on this...

    1. Either you can set default agents for the task (or) modify the container elements in transaction SWIA (or) complete it manually without agent.
    2. Its true that, for a task specified as general task, all users become possible agents. Remember that they dont become responsible agents. SAP agent assignment always take the intersection of possible and responsible agents. If you donts specify responsible agents, you cannot see workitem in anyone's inbox.
    3. As told earlier, if you dont have authorization, check for the auth object in SU53 and get that added to your profile. Anyways, you can also check for the SAP provided standard authorizations for the workflow users in sap.com
    regards,
    Sandeep Josyula
    *Mark if helpful

  • Agent Assignment - if no agent found

    Hi,
      I have created a dialog work item. i have done agent assignment with position id.
      My problem is  if  position id is not having users( in some cases)  then the workitem will go to whom? ,  how  can i resolve this .
    Thanks & Regards
    Sankar.

    Hi Sankar,
    The work item is sent to the position, so If the position is empty then it will go to no one (well... that's what happens on 4.6C - unfortunately, no warnings or errors are produced to indicate this work item is without an agent).
    Note: If the "Position" doesn't Exist on the runtime environment - then your Workflow Will go into Error when "establishing the agent".
    However... run tx. SWI2_ADM1 to get a list of "Work Items Without Agents" and... Your Work item is there... And you can reserve the work item and forward it to an agent
    To resolve this:
    Check your "Agent Assignment" on that dialog task...
    You can specify the "Possible Agents", so that the work item will be sent to the "Position" and all "Possible Agents" (not 100% ideal - but will ensure that an Agent is found). Make sure it's Not a General Task to do this.
    Alternatives:
    You might want to reconsider applying a "position" directly to a task in the workflow. Instead, try using "Roles" - it gives you more flexibility in runtime.
    Hope it helps.
    Tom

  • Decision should Not go to all SAP Users if no agent found in rule. How to ?

    I am determining user agents in rule , when agent is find decision is going to only the agent sap inbox which is fine.
    in some cases no agent is found , at that time decision is going to all SAP users in the system.
    I am using Generic Decision task with General task in agent assignment step.
    As per our requirement if no agent is found it should do nothing ( means no decision to all users ).
    Please help me how can i acheive this .
    Regards,
    VeeraBrahmam

    Hi VeeraBrahmam,
    Does you rule call a function or is it a rule with responsibilities?
    If it is a responsibility rule then you could create a catch all responsibility so if no user is found in the other responsibilities you could send the work item to a backup user or admin user who could take action.
    If you set the flag as Rick suggested it will set the work item to error so make sure you are aware of this and check work items in error on a regualr basis.
    You could copy the Generic User task TS00008267 and maybe set more restrictive users rather than have it set as general. However this means more maintainence.
    Regards,
    Eddie

  • Agent Not Found for rule 168 in Travel Management WF WS20000040

    Hi,
    I got a strange error occurring that I can not quite figure out. I am using a copy of a standard delivered SAP Work flow for Trip Approval (WS20000040) that is identical to the SAP delivered workflow except without the expense department tasks (we only need manager approval). I also updated the agent assignment for tasks TS20000131, TS20000139, and TS20000189 to be General Tasks. When an employee creates a trip, the workflow is started properly and goes to the first workflow step which is user decision step 416. It uses rule 168 to determine the manager of the workflow initiator. This works properly. The manager goes to their inbox and executes this workflow step. The trip changed and trip approved buttons work fine, but if the manager chooses the reject button, the form is closed and the workflow stops with an error. The next step down the reject path is an activity step 476 - enter and send message. This runs task TS20000139. The agent assignment also uses rule 168 to determine the manager of the workflow initiator. The same agent should be choosen for both this step and the previous step since the workflow initiator is the same for both and the same rule is being used. The advance with dialog check box is checked in both steps. Both step refer to tasks that are both marked as synchronus object methods and object method with dialog.
    For testing purposes, I changed the agent determination in both workflow steps to be the workflow initiator and ran it. The workflow stopped at the approve trip facts step as expected and when I choose reject trip, I was taken immediately to the create mail task that task TS20000139 runs as it should. I tried creating a trip as the employee and the manager and it work properly in both occasions regardless of which user the trip was created under when just workflow initiator is used for agent determination.
    I ran SWI2_DIAG to look at the errors that occurred when it stopped in error when I used rule 168. According to the error message, the approve trip fact step completed successfully, but the enter and send message step failed with no agent found. Following is the error message:
    Workflow WS90000048 no. 000000277688 activity 0000000476 role 'AC00000168': No agent found
    What I don't understand is that the agent determination for the approve trip facts step which works perfectly uses the same agent determination as the enter and send message step which is terminating with an error. Also when I change both steps to use workflow initiator as the agent, then they both work perfectly.
    Help, Please
    Gregg
    Edited by: Gregg Hinkle on Feb 12, 2008 4:48 PM

    Thanks Martin,
    I used your suggestion and passed the actual agent from the prior task to the container and then used this value as an expression to determine the agent for the step that was causing me pain. Now the workflow step is continuing properly and automatically bringing up the create message step as expected.
    Arghadip,
    I tried your idea about creating a copy of the standard delivered workflow and even set it as a general task and I got the same result as with the standard SAP (error with no agent found).
    Thanks again for everyone's assistance

  • Workflow for PO release strategy agent not found

    Hi all,
    I m beginner in the workflow. i  want to create a workflow for the PO. release strategy I have done all the settings in the SPRO for the release strategy. I have copied the standard workflow definition  WS20000075 also done the binding with object type BUS2012. in the steps 'Release of purchase order' i have mentioned the task TS20000166 i.e. 'Release of purchase order' and also maintain the AC Rule 20000027 i.e. 'Person responsible for PO release' for agents. But still its not getting the agents. the workflow is getting triggered but its not getting the agent. What else setting I need to do to get this done.
    Thanks a lot.
    Regards.

    Very well put Rick. In my case if i simulate this workflow from swdd transaction then it works fine but the same workflow when initiated from ME21N doesn't work and throws same error.
    1. I have copied standard workflow and task 166 is throwing error.
    "Resolution of rule AC20000027 for task TS20000166: no agent found"
    2. I have recreated the step but still the workflow is throwing error.
    3. If I execute the rule individually (PFAC_DIS) with a specific PO then the rule works fine. The rule executes the below mentioned exit successfully.
    4. I am using exit to determine the agent, the workflow works fine if I don't use the exit. The exit is EXIT_SAPLEBNF_005. I am just pulling the agent from a ztable.
    Please advise if you can help as I have not seen anyone answering.
    by the way irrespective of the explicit rule update in the workflow the step executes AC20000027 by default.
    Any help on above is appreciated.

  • Workflow error " Work item could not be found"

    Hi Experts,
    I used transaction SWI2_DIAG to diagnose the error and tried to restart the workitem manually .The changes were made to Org chart  and now everything is fine but I am still getting error message:
    Work item could not be found                                                             
    Workflow 'Post with Clearing Workflow' step number 4: work item could not be created     
    Agent determination for step '0000000004' failed                                         
    Workflow WS93000005 no. 000004806372 activity 0000000004 role 'AC00000168': No agent found
    Resolution of rule AC00000168 for task TS93000019: no agent found   
    Can someone explain what this error message mean and why i cant restart the workitem manually?
    Thanks.

    This is my message from Production:
    Resolution of rule AC00000168 for task TS93000019: no agent found                         
    Workflow WS93000005 no. 000004806372 activity 0000000004 role 'AC00000168': No agent found
    Agent determination for step '0000000004' failed                                          
    Workflow 'Post with Clearing Workflow' step number 4: _work item could not be created_      
    This is my message from development.. I recreted the scenario and getting different message.
    Workflow 'Journal Entry Approval- Approval WF' step number 36: work item could not be created 
    Agent determination for step '0000000036' failed                                              
    Workflow WS93000001 no. 000000986124 activity 0000000036 role 'AC93000003': No agent found    
    Resolution of rule AC93000003 for task TS00007914: _no agent found_
    Edited by: Sergey on Nov 2, 2010 5:05 PM

  • Agent Assignment in Process Controlled workflows

    1. For testing one-level approval, I activated the one-step apparoval shopping cart BC set. while creating the shopping cart it is showing the manager id. But when manager logs in, there is no workitems, Also if I check from workflow log I cannot see any id, but from swii5, I can see the workitem in manager id...Is there any config I am missing. I have checked the Determine agnets from spro, but I have not done anything there.
    2. If I activate one step approval today, can I activate N-step approval tomarrow
    3. Is there any specifi guide which can help me in doing the process controlled worklows configuration step by step.

    Hi Masa!
    I can see in the system configuration of system administration from portal that the webflow is configured and the status is registered.
    Let me explain you the scenario once again.
    User A is requestor and created SC. User B is manager. From the workflow log it is showing in READY status but "No agents found". But when I goto manager inbox from swi5, I can see the workitem available in his inbox but manager cannot see either from portal nor swbp inbox.
    I also checked the approval workflow 40000016 and step is 293..Here it is rule with function module checking for agents.
    Am I missing any configuration from SPRO ?
    Do I need to do anything in "Determine agents" in SPRO ?
    Regarsd,
    pavan

  • 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 using a Rule

    Hi All,
    I tried finding related threads, but was not able to find anything that exactly matches this issue.
    I have an Activity type task to which I have assigne a rule for agent determination. I am assigning the SAP userid to the actor_tab in the function module. This is the code I am using:
      ACTOR_TAB-OTYPE = 'US'.
      ACTOR_TAB-OBJID = 'AJOHN'.
      APPEND ACTOR_TAB.
    But, when I try to simulate the rule in PFAC, it says "no agent found". What am I doing wrong?

    I created a function module called ztest_rule in se37 and put your exact code.  I then created a rule called ztest_rule in PFAC and chose Agent Determination: Function to be executed and entered ztest_rule as my function module.  When I hit the little abacus and then the wrench in PFAC to test, it returns  US  AJOHN.

  • Not clearable : 1 distinct types of ORA- errors have been found in the alert log.

    ( Correct me if I'm wrong.)
    What could be the reason for the fact that the event "1 distinct types of ORA- errors have been found in the alert log." is not clearable?
    Even if the problem is solved, the ORA- error will still be in the alert.log.
    Therefore the event would eventually only disappear after 7 days.
    Doesn't sound very logical to me.

    - The event page showing a warning event for "Generic Alert Log Error Status" metric,
    - "Generic Alert Log Error Status" event is a statefull metric,
    - On each evaluation of the metric defined as 'Statefull', the Cloud Control Agent recalculates the severity,
    - This means, EM Agent scans the alert log for ORA errors, "Generic Alert Log Error Status" will return the number of ORA error found,
    - Whenever the returned number is grater than the assigned thresholds of "Generic Alert Log Error Status", an alert is raised on EM console,
    - On the next scan of alert log file, this alert will be cleared ONLY if the collected value is less than the assigned threshold,
    - By checking your system, the warning threshold of "Generic Alert Log Error Status" is 0, so whenever a single ORA error is found in alert log, a warning event will be raised and you will not be able to clear it manually as this is a stateful metric.
    There are three cases where this alert can be cleared:
    1. The agent found 0 ORA errors in Alert log, then the alert will be cleared automatically
    2. Manual clear: By disabling/enabling the metric
    3. Manual clear and further not receiving similar alerts frequently: By assigning higher thresholds values
    So, I suggest to disable the metric, then, enable it after some time as follows as follows:
    - Go to the problematic database home page >> open the 'Oracle Database' drop-down menu >> 'Monitoring' >> 'Metric and Collection Settings',
    - Choose 'All metrics' from the 'View' drop-down list >> search for the 'Generic Alert Log Error Status' metric,
    - Click the pencil icon under 'Edit' column opposite to the above metric >> remove the Warning Threshold (make it empty) >> 'Continue' >> 'OK'.
    - Wait for the next collection schedule in order for the warning events to be cleared, then, enable the metric again with the same steps (setting Warning Threshold=0).
    References:
    Note 604385.1 Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric
    Note 733784.1 What are Statefull and Stateless Metrics in Enterprise Manager - Explanation and Example
    HTH
    Mani

Maybe you are looking for