Agent determination using attribute

Hi all,
My scenario is to find agent from a z table which has organisational unit number with prefix O.
I created a attribute in business object and programed accordingly that it finds the correct org number for the key field. I had done a self test and it is able find correctly.
Now i have called the attribute to workflow and event container using the same type it is able to get the value, i have done the bindings also. Using expression in the agent assignment i used this variable directly likes this &org_U& here the value now would be O 5981001 which has a business partner under and user below business partner... my problem is if the business partner is not there my workflow works if the orgunit has a business partner then it is not passing the work item....
Thanks
Annamalai

In the table HRP1001 you retrieve all the agent that is assigned to the Organization unit and append the SAP User ID concatenated with US to a container element. You then use this container elementas an Expression. This will surely work.
<b>Reward points if useful</b>

Similar Messages

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

Agents determination using Organization chart

Hi,
I have a Organization chart.
and I assigned a Job in that Organization chart to the Agents assignment in TASK.
Job Is assigned to a user ( US.....)
I am not knowing how to get that agents So as to start the task.
I am taking about the AGENTS field in the control tab of the ACTIVITY
Regards

Hi,
In my Scenario I have an Org Object.
In my Org Object there are two positions.
1 Manager
2 Admin
Both the positions are assined a Job and User each.
Now I want the person in the Manager position must be Doing the activity,
Your Questions
You tell me who are the possible agents? -
> the person in Position assigned ( Manager in this case )
Whats their Position? -
> The position which is assigned( Manager in this case)
How you identify them?----> This is what I am asking you
To whom you need to send the workitem?-------> Manager in my case
Regards

SRM Contract alert management Workflow - WS10400022 Agents determination

Hi Experts,
I am trying to implement Alert management for SRM Contracts that are expired/ or the threshold is exceeded.
All the necessary configs are done and the event linkage is also done for the workflow Template WS10400022.
The task used in this workflow TS10407926, for agent determination, used the expression &Agents_0001.Agents&
This container value is neither passed from the event linkage binding.
Can anyone explain how this agent determination is done for this workflow?
Your replies are very much appreciated
Cheers,
Prem.

Hello,
OK, i did not see the event linkage between event and workflow...
Currently, &Agents_0001.Agents& is not populated with data coming from the event:
Event is managed by BBP_EV_API_EVENTS_SAVE function modul, and inside this FM by CL_BBP_EVENTS class.
Maybe you should open an OSS message and check all OSS notes dealing with BBP_CONTRACT_CHECK report.
Regards.
Laurent.

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 Rule using Function Module

Hi all,
I am trying to create a custom agent determination rule using function module. But my rule is not getting invoked when the workflow is executed.
I created a custom rule and linked my function module (with proper signature).
FUNCTION 'ZRULEXXX''
""Local Interface:
*" TABLES
*"      AC_CONTAINER STRUCTURE SWCONT
*"      ACTOR_TAB STRUCTURE SWHACTOR
*" EXCEPTIONS
*"      NOBODY_FOUND
And I am hard coding some values into table ACTOR_TAB
REFRESH ACTOR_TAB.
CLEAR ACTOR_TAB.
IF SY-SUBRC NE 0.
    RAISE NOBODY_FOUND.
ELSE.
    ACTOR_TAB-OTYPE = 'US'.
    ACTOR_TAB-OBJID = 'XXXX'.
    APPEND ACTOR_TAB.
    ACTOR_TAB-OTYPE = 'US'.
    ACTOR_TAB-OBJID = 'XXXXXX'.
    APPEND ACTOR_TAB.
ENDIF.
But a worklist item is not being created for the users appended to ACTOR_TAB.
Is there anything am missing. Please let me know.
Thanks in advance
Regards
Raju

Hi,
Change it to following code. It will work.
REFRESH ACTOR_TAB.
CLEAR ACTOR_TAB.
*IF SY-SUBRC NE 0.
*RAISE NOBODY_FOUND.
*ELSE.
ACTOR_TAB-OTYPE = 'US'.
ACTOR_TAB-OBJID = 'XXXX'.
APPEND ACTOR_TAB.
ACTOR_TAB-OTYPE = 'US'.
ACTOR_TAB-OBJID = 'XXXXXX'.
APPEND ACTOR_TAB.
*ENDIF.
Regards,
Vaishali.

Use AGENT through dynamic attribute access

I'm working with some persistent objects, but don't know the actual persistent class until runttime. To get the agent, I've coded this
DATA: l_agntclass TYPE classname,
     lr_det_agent TYPE REF TO cl_os_ca_common.
FIELD-SYMBOLS <lr_det_agent> TYPE any.
l_agntclass = me->derive_agent_classname( ).
ASSIGN (l_agntclass)=>agent to <lr_det_agent>.
lr_det_agent ?= <lr_det_agent>.
Now I can call the methods of lr_det_agent. All well and good, and it works, but is this the right way? I tried defining <lr_det_agent> as TYPE REF TO. But that failed in the assign. And I tried CASTING TYPE on the assign, but that doesn't accept classes.
Am I missing something obvious?
Thanks
matt

Hello Matt
The solution is quite simple (see below):
*& Report ZUS_SDN_PERSISTENT_CLASS
*& Thread: Use AGENT through dynamic attribute access
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1143122"></a>
REPORT zus_sdn_persistent_class.
DATA: gd_clsname    TYPE classname,
      gd_method     TYPE string,
      gd_attribute TYPE string.
DATA: go_obj        TYPE REF TO object, " root object
      go_os_common TYPE REF TO cl_os_ca_common.
DATA: go_persist    TYPE REF TO cb_alert,
      go_agent      TYPE REF TO ca_alert.
FIELD-SYMBOLS <go_det_agent> TYPE ANY.
START-OF-SELECTION.
BREAK-POINT.
gd_attribute = 'CA_ALERT=>AGENT'.
" In your case: CONCATENATE l_agntclass '=>AGENT' ...
ASSIGN (gd_attribute) TO <go_det_agent>.
go_os_common ?= <go_det_agent>.
BREAK-POINT.
END-OF-SELECTION.
Regards
Uwe

SRM 7.0 WF: SC_RR_PURCHASING_GROUP Agent Determination

Does anyone know which set of criteria is used by the SC_RR_PURCHASING_MANAGER Resp. Resolver Name function to determine the agents list? I am getting mixed results, including non-manager users in different org units appearing in the results list. The descrption of the RR_PURCHASING_MANAGER function looks more like what I need however the notes say its not for Shopping carts.
Is it manger of the org unit that is Responsible for both the Org Unit of the originator, and the Product category? (Responsibilty Tab). Or it is the PRCAT attribute? Or some other combination? I am not seeing a pattern.
What I am trying to accomplish is to have the final approver on the shopping cart be the manager of the purchasing group, I am not concerned with the product category selected as the purchasing agents process by department not product category.
Thanks in advance.
J

I have about 8 levels. I haven't fully cofigured all of them yet but the core ones are in place. The RR_MANAGER and RR_MANAGER_OF_MANAGER agent determination based on org assignments work correctly.
First is Department manager must approve, agent determination via RR_MANAGER (works)
Next is Purchasing Manager if > 5K, agent determination via RR_ROLE (role assignment, works)
Next is Director if > 25K, agent determination via RR_MANAGER_OF_MANAGER (works)
Next is Budget Manager if its an Asset, agent determination via RR_ROLE (role assignment, not working yet)
Next is Finance Director if > 100K, agent determination via RR_ROLE (role assignment, works)
Next is IT Asset manager if PRCAT is for computer equipment, agent determination via RR_ROLE (role assignment, not configured yet)
Next is Fleet manager if PRCAT is for Vehicle, agent determination via RR_ROLE (role assignment, not configured yet)
Final Approver is the Purchasing Agent, This should be the agent (Head of Org Unit) of the Purchasing Group that the end user department is assigned under, however using SC_RR_PURCHASING_GROUP, I get the expected purchasing agent, the director of the end user department, the manager of the end user department and an end user in a different org unit as posisble agents.
When I set the Resp. Resolver Name for the final step to RR_PURCHASING_GROUP, I get the message 'An Exception has Occured' and the cart is lost. This is the resovler role that is stated as not working for shopping carts.
Thanks
Jon

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

Agent determination using attribute

Similar Messages

Maybe you are looking for