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

Similar Messages

Agent determination in PO release

HI all,
In my work flow 2 agents are there. I usng the standard rule ( 20000027)to identifying the agents. This is identifying the 1 st agent , not working for 2nd agent . to find out the agents I find the below code from SDN and wrote it .. Still it is not finding the 2nd agent.
DATA:
      releasecode type t16fs-frgc1,
      frggr type ekko-frggr,
      frgsx type ekko-frgsx,
      frgzu type ekko-frgzu.
select single FRGGR FRGSX FRGZU from ekko into (FRGGR,FRGSX,FRGZU) where
ebeln = object-key-PurchaseOrder.
CALL FUNCTION 'ZPO_REL_CODE'
EXPORTING
    PURCHASEORDER = object-key-PurchaseOrder
    RELEASEGROUP = FRGGR
    RELEASESTATUS = FRGZU
    RELEASESTRATEGY = FRGSX
IMPORTING
    RELEASECODE = releasecode
EXCEPTIONS
    OTHERS = 01.
CASE SY-SUBRC.
WHEN 0.            " OK
WHEN OTHERS.       " to be implemented
ENDCASE.
swc_set_element container 'releasecode' releasecode.
END_METHOD.
Code inside ZPO_REL_CODE is as below :
FUNCTION ZPO_REL_CODE.
""Local Interface:
*" IMPORTING
*"     REFERENCE(PURCHASEORDER) TYPE EKKO-EBELN
*"     REFERENCE(RELEASEGROUP) TYPE EKKO-FRGGR
*"     REFERENCE(RELEASESTATUS) TYPE EKKO-FRGZU
*"     REFERENCE(RELEASESTRATEGY) TYPE EKKO-FRGSX
*" EXPORTING
*"     REFERENCE(RELEASECODE) TYPE FRGCO
data: itab type STANDARD TABLE OF T16FS,
      wa_itab LIKE LINE OF itab.
select single * from t16fs into wa_itab where
frggr = RELEASEGROUP and
frgsx = RELEASESTRATEGY.
if RELEASESTATUS is INITIAL.
    RELEASECODE = wa_itab-frgc1.
    ELSEIF RELEASESTATUS = 'X'.
    RELEASECODE = wa_itab-frgc2.
    ELSEIF RELEASESTATUS = 'XX'.
    RELEASECODE = wa_itab-frgc3.
    ELSEIF RELEASESTATUS = 'XXX'.
    RELEASECODE = wa_itab-frgc4.
    ELSEIF RELEASESTATUS = 'XXXX'.
    RELEASECODE = wa_itab-frgc5.
    ELSEIF RELEASESTATUS = 'XXXXX'.
    RELEASECODE = wa_itab-frgc6.
    ELSEIF RELEASESTATUS = 'XXXXXX'.
    RELEASECODE = wa_itab-frgc7.
    ELSEIF RELEASESTATUS = 'XXXXXXX'.
    RELEASECODE = wa_itab-frgc8.
    ENDIF.
ENDFUNCTION.
Please help me to solve the issue.
regards,
Ajay reddy

Hi,
You can acheive your requirement using deadline. substitution is nto required.
1)Specify the 2days time in the latest end tab
2) select the modelled deadline in the options below.
3) in outcomes tab, activate the processing obsolete line
4) now u can c 3 lines from the task for release
     1) normal flow whn executed
     2) Will check the deadline. Once it is reached it will progress with the steps in processing obsolete branch.
     3) Processing obsolete branch. In this branch,
           a) place the 'PRocess Control' step to remove the workitem from the preovious user
           b) Include the workitem step to send it to the next person who shld release the PO.
Hope this helps you.
Regards,
Sivagami R

PC WF - Agent Determination for Items with Multiple Account Assignment

Hello Gurus!
The quoted text below is from [SAP Help Documentation|http://help.sap.com/saphelp_srm70/helpdata/en/ad/d8fd25beb64bbe9d671f3199eb7edf/content.htm]. I haven't been able to find any further documentation on how to implement this feature. Is this something the system can do without any BAdI implementations? Has anybody implemented this? How can this be accomplished? We are on SRM 7.0.
"You can distribute costs across accounts by percentage, by quantity, or by value. If the responsibility for approving items according to given accounting data is divided between several approvers, the system can create one work item for each approver. The item can only receive the status Approved after each approver has approved it. As soon as one approver rejects an item, the item receives the status Rejected."
Regards,
Ramki.

Hi,
SAP does not provide the standard Badi implementation to achieve your business requirement.. but you can refer enhancement implementation /SAPSRM/BD_WF_AGENTS_SC where you can find badi implementation /SAPSRM/BD_WF_SC_RR_PGRP is similar..
Saravanan

Need help with agent determination for release workflow

Hi,
I am trying to perform a release in the contract(FS-contract management) by using the framework for principle of dual control. When i create a contract, i get a message that says contract created, not yet released. But i am not able to get the work item in my inbox to release the contract. The SWI1 transaction shows 'no agent' for the triggered workflow. I am using the template WS50100021 as there is only one release step. By default there is a rule '50100017' given for the template. But in the customizing settings i have the section called 'assign rule to release steps'. Do i need to assign a rule here for agent determination. If so, what about the rule in the WS50100021 template? Which one should i use? I am able to execute the method 'release' of object BUSISB001 from SWO1 and release or reject the contract creation. But i am not able to get the workitem in my inbox in SBWP transaction

Hi Suhas,
The rule used in workflow template WS50100021 is a standard one. So try to find out that on what basis it is fetching the agents. It could be the case that the logic specified in the rule does not fulfill your requirement.
The other reason could be that you have not specified the task as general. Please check if the agents tab is activated(green) in the task or not. If it is not you need to set the task as general.
SOLUTION : if you want to get the workitem in your own SAP Inbox for testing purpose, you can set the WFINITIATOR as agent instead of that standard rule. This setting will send the workitem in your own SAP Inbox.
Regards,
Guddan

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

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 issue

Hello Experts,
We have developed one custom workflow a year back and last two months we are seeing the issue with Agent Determination randomly. We created a position with 3 users and assigned the Position to the Agent Assignment. Some times the work item sent to other users other than 3 users assigned to the position. We are not able to trace it, why it's behaving like this. Any help would be appreciated.
with best regards
K. Mohan Reddy

If this happens randomely then we can only assume
Please check the wflow log from SWIA whether someone has forwarded the workitem?
There can be also change in Position assignment, Substitute getting maintained.
Also check whether the users are maintained in the Task level if it is General forwarding Not allowed task from the task attribute.
Thanks
Arghadip

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

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

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 best practices

Hi, workflow dev team!
Another question about workflow best practices.
I build a workflow, the first step of each workflow, at least as I see it, is to determine agents for all steps in the workflow and store it in multiline WF-container. After that, to use this WF-container data to execute a step inside of workflow.
The questions are:
1. Suppose, I filled a WF-container with a list of all possible agents and their position (in order to supply more user-friendly approve/decline notifications) for the different steps inside of this workflow (username & position). As I understand, I can access to specific line of multiline container with &AGENTS[&INDEX&]& inside of EXPRESSION field (not via ABAP-code in method of class), but how can I access specific column of the WF-container? E.g. &AGENTS[1]& will return «USJOHN — Junior Manager», is it possible to retrieve username and position from multi line and pass it to the task as two separate container elements?
2. Is it possible to query specific line of multiline container element according to some logical condition inside of EXPRESSION field (not via ABAP-code in method of class) or in order to do this I have to implement that logic inside of ABAP class method?
And the last question, probably, less connected to the questions asked above.
3. If I need to define agents for the task, what is the best approach to do that:
— define the task as General Task and insert the relevant agents as multiline container element via EXPRESSION field;
— to play with Agent Assignment (try to implement agent determination logic there) and not to define the task as general one.
Thanks.

Ronen already had great input, but here are some additional points:
-In general I would try to avoid some kind of "Let's get all the agents at the beginning of the workflow into a multiline container, and try to pick up the correct ones for the individual steps" approach. Of course if your aim is just to display the list of agents somewhere (task description etc.,), then this might be OK approach.
-Rules are better than expressions in agent determination (at least in most cases). If the approvers change during the process, you can (as an WF admin) just click the "Execute agent rule again" functionality, and the system will find the correct new approver for the work item. Otherwise you need to go to manipulate the container element(s) (and first figure out that who is the approver).
Answer for 3: You don't need to use only expressions/container elements. Try to check if you can use rules. In some rare cases you might consider of using the tasks' agent assignment (the same place where you set the task as general task). Let's say that you want to send the work item to all users that have certain authorization role. Now you can set the role as a "restricting entity" at the task level (=same place where you set the general task). This will mean that only the users who have the role are the possible agents for the task. And now if you leave the agent determination part at the workflow template empty (no expressions, no rules etc), you are done!
Regards,
Karri

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 for SRM WF

Hi All,
I have developed a custom WF i.e. copy of 2 step Invoice approval WF.
For agent determination, I have put in logic for Adhoc agent, which is working fine.
My query is that I can have multiple agents for a particular step, which I am able to see when referring to approval preview.
However when i try to change one of the entries for agent , system replaces <i>all entries</i> with changed entry for an agent.It does not change the one particular agent out of these multiple agents.
Wanted to know is it the std behaviour that at the time of changing the agent, evenif we have multiple agents , it will be chaged to only one agent - which is being replaced ?
Awaiting your inputs.
Regds,
Akshay

Hello Abraham,
To understand what's happened, you will need to debug /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP and /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID methods from /SAPSRM/CL_IM_WF_RR_PGRP_SC implementing class (interface for BAdI definition /SAPSRM/BD_WF_RESP_RESOLVER from enhancement spot /SAPSRM/BD_WF_AGENTS )
If mapping between area and item is correct, see why purchasers from purchasing group(s) are not correctly found by debbuging /SAPSRM/IF_WF_AREA~GET_RESPONSIBLE_APPROVERS method from implementation /SAPSRM/CL_WF_AREA_PURCH_GRP.
Regards.
Laurent.

Agent Determination - PR Item Release

Similar Messages

Maybe you are looking for