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

Similar Messages

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

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 assgnment in PO release

Hi all,
I am using the default rule (Default rule 20000027)for agent assignment . In SPRO 2 release codes are there.
when I am using the default , it is identifed the only 1 user, it is nor identifying the 2 nd person, When I hard coded user, then it is identify. please for this agent assigement.
regards,
Ajay

when I am using the default , it is identifed the only 1 user,
it is nor identifying the 2 nd person, When I hard coded user,
then it is identify. please for this agent assigement
In SPRO settings for the second relaese code maintain Role resolution for workflow as 9 , I think in the rule it is determninig the agents based on the release code , may be you have set the release code as 1 and when realease code is one it always determines only one agent, so maintain the release code as 9 and define the logic to determine all the responsible agents in the user exit
EXIT_SAPLEBNF_005
Please check in the rule for user exit at line number125.

Problem in agent determination for custom wf of contracts

Hi
I've copied standard wf for contracts i.e. 20000079. In my custom wf the step for release contract I've maintained the standard rule 20000029. bcos this rule is assigned for standard one with task 20000172. Am I correct in agent assignment??bcos my agent determination fails and wf goes into error. But if I simulate the rule separately it works fine. So there is no prob in rule,also i've properly binded it with task passing purchasingContract and releasecode.
Could u pls help me.
Thanks

Check that the binding between the workflow and rule are OK. Maybe your workflow is not delivering all the needed parameters for the rule (the same parameters that you are using while simulating the rule).
Another thing that you should check is that make sure that this is not an authorisation problem. It is possible that the rule is executed by the dialog user (not WF-BATCH) that doesn't have enough authorisations to do all the necessary rule logic. Just give remporarily SAP_ALL to the user who is executing the test.
Regards,
Karri

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

Agent Determination for Service Entry (BO-BUS2091)

HI,
I am new to workflow and facing below issue.
I have created a workflow for Service entry sheet approval (BO- BUS2901) and I am having an issue with the agent determination. I am using my own Ztable to determine the possible agents.
I am using the following code in the FM of the rule I created for determining the agent:
FUNCTION ZME_SRV_REL_GET_RESPONSIBLE.
*"*"Local Interface:
*" TABLES
*"      ACTOR_TAB STRUCTURE SWHACTOR
*"      AC_CONTAINER STRUCTURE SWCONT
*" EXCEPTIONS
*"      NOBODY_FOUND
INCLUDE <cntain>.
TABLES: essr_rel, essr,zmm_service_mail.
DATA: object TYPE swc_object.
DATA: BEGIN OF essrkey,
lblni LIKE essr-lblni,
END OF essrkey.
DATA: verak_user TYPE csks-verak_user.
REFRESH actor_tab.
CLEAR actor_tab.
swc_get_element ac_container 'service' object.
if sy-subrc eq space.
essrkey-lblni = object-objkey(10).
select single * from essr where lblni = essrkey-lblni.
select single * from zmm_service_mail
where frggr = essr-frggr
and frgsx = essr-frgsx.
if essr-frgzu eq ' '.
verak_user = zmm_service_mail-pernr1.
elseif essr-frgzu eq 'x'.
verak_user = zmm_service_mail-pernr2.
endif.
actor_tab-otype = 'us'.
actor_tab-objid = verak_user.
append actor_tab.
endif.
ENDFUNCTION.
When I debug, sy-subrc = 8 at swc_get_element ac_container 'service' object.
What could be the problem?
Note- I have gone thru below thread but still I am unable to find the error.
http://scn.sap.com/thread/2017416

Hi,
You should re-read the thread that you quoted above. The mighty Sue Keohan suggested a solution.
Instead of trying to pass a service *object*, and then extracting the key, you can just pass the key itself. It has type EESSR-LBLN1.
swc_get_element ac_container 'service_key' lv_service_key.
if sy-subrc eq 0.
essrkey-lblni = lv_service_key.
(etc)
cheers
Paul

Agent Determination for Service Entry

Hi Guys,
I created a workflow based on BO BUS2901 to send approval notification to an approver and I am having an issue with the agent determination. I am using the cost centre owner from the PR associated with the PO for the service entry as the approver.
I am using the following code in the FM of the rule I created for determining the agent:
FUNCTION ZME_REL_GET_RESPONSIBLE.
*"*"Local Interface:
*" TABLES
*"      ACTOR_TAB STRUCTURE SWHACTOR
*"      AC_CONTAINER STRUCTURE SWCONT
*" EXCEPTIONS
*"      NOBODY_FOUND
INCLUDE <cntain>.
TABLES: eban, essr_rel, essr, ekpo, ebkn, csks.
DATA: object TYPE swc_object.
DATA: BEGIN OF essrkey,
           lblni LIKE essr-lblni,
           ebeln LIKE essr-ebeln,
        END OF essrkey.
DATA: verak_user TYPE csks-verak_user, kostl TYPE ebkn-kostl.
REFRESH actor_tab.
CLEAR actor_tab.
swc_get_element ac_container 'ServiceEntry' object.
IF sy-subrc EQ space.
    essrkey-lblni = object-objkey(10).
    essrkey-ebeln = object-objkey+10(10).
      select * from ekpo where ebeln = essrkey-ebeln.
        select single * from ebkn where banfn = ekpo-banfn.
          kostl = ebkn-kostl.
      endselect.
    select * from csks where kostl = kostl.
      verak_user = csks-verak_user.
    endselect.
    actor_tab-otype = 'US'.
    actor_tab-objid = verak_user.
    APPEND actor_tab.
endif.
ENDFUNCTION.
When I debug, sy-subrc = 8 at swc_get_element ac_container 'ServiceEntry' object.
What could be the problem?
Thanks
Regards

Hi Sarvesh, T
This thread was already answered some time ago. Please open a new Discussion marked as a question. If the thread you originally posted to has material related to your question, include a link. Your content is attached below to make it easy for you to simply paste it into the new Discussion. It is recommended to read the Rules of Engagement and other documents in the Getting Started link at the top right.   If you have any questions, feel free to respond to this DM (Direct Message) and I will be happy to try to assist.
Rgds,
Jocelyn (SCN moderator)

Responsibility rules : Agent determination only works after restarting the WF

Hi Experts,
We are facing a very strange issue related to agent determination in one of our custom workflow:
For agent determination we are using a responsibility rule with two parameters "Company code" and "Plant".
The responsibility rule works well and returns the agents for all the company code.
Recently I have added few company codes to this responsibility rule in the same way we used to maintain and simulate it . It returns the correct agent for newly added company codes but at run time the agent determination is getting failed and the WF goes into an error because of it. However when i restart the WF via SWPR it works well and the agent determination works well either.
This is only happening for newly added company codes the old ones agent determination work well at the run-time.
Pls suggest what could cause this problem. If there is a problem in responsibility rule then why it works after restarting from SWPR.
Thanks in advance. The helpful/correct answers will be rewarded.
Regards,
Him

Hi Rick,
Thanks for replying.
1. Can you replicate this problem in the test system?
Yes I could replicate this issue in test system and it works fine there.
2. Is this a true responsibility rule or does e.g. a function module get called?
We have a responsibility where several responsibilities have been added with two parameters "company codes" and "plant". Every responsibility has a POSITION assigned into it and this position contains the related users.
This responsibility rule is getting called in one other rule with FM. Here in this another rule we are calling the responsibility rule by using the standard FM RH_GET_ACTORS to fill the ACTOR_TAB.
I have tried to simulate both the rules and it returned correct agents but failing at run time.
Regards,
Him

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 in PO release

Similar Messages

Maybe you are looking for