Agent determination

[Khanna, Manish]

Gavin,

That is not the case. 
1. The decision task is general task
2. The agent determination step correctly fills next agent in
NEXTAPPROVER.
3. However the work item appeared in 2 different inbox who are not
related. 4. Also there is no substitution setup.

Regards,
Manish

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Gavin Mooney
Sent: Wednesday, December 20, 2006 4:17 PM
To: SAP Workflow Users' Group
Subject: Re: Agent determination

Manish,

The technical log should show you the output from the agent
determination step, i.e. with which user ID the element NEXTAPPROVER
is filled. Is it possible that no agent is being returned and the
decision step is being routed to the possible agents defined on the
task?

Regards,
Gavin

2006/12/20, Khanna, Manish <manish.khanna at amd.com>:
>
>
>
>
> Apologies for incomplete information,
>
>
>
> NEXTAPPROVER is a single line of type WFSYST-AGENT. It contains the
user id
> (of the form US<xyz>).
>
>
>
> Also the agent determination step is one step prior to the decision
step,
> with no modifications to the container element between the steps.
Moreover
> since it is a single line element - can't contain 2 values.
>
>
>
>
>
>  ________________________________
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf Of
> Dart, Jocelyn
>  Sent: Wednesday, December 20, 2006 10:48 AM
>  To: SAP Workflow Users' Group
>  Subject: RE: Agent determination
>
>
>
>
> Also check what you are filling NEXTAPPROVER with... e.g. if it's a
position
> id then it's perfectly reasonable to have multiple people linked to
the one
> position.
>
>
>
>
> Regards,
>  Jocelyn Dart
>  Senior Consultant
>  SAP Australia Pty Ltd.
>  Level 1/168 Walker St.
>  North Sydney
>  NSW, 2060
>  Australia
>  T   +61 412 390 267
>  M   + 61 412 390 267
>  E   jocelyn.dart at sap.com
>  http://www.sap.com
>
> The information contained in or attached to this electronic
transmission is
> confidential and may be legally privileged. It is intended only for
the
> person or entity to which it is addressed. If you are not the intended
> recipient, you are hereby notified that any distribution, copying,
review,
> retransmission, dissemination or other use of this electronic
transmission
> or the information contained in it is strictly prohibited. If you have
> received this electronic transmission in error, please immediately
contact
> the sender to arrange for the return of the original documents.
>
> Electronic transmission cannot be guaranteed to be secure and
accordingly,
> the sender does not accept liability for any such data corruption,
> interception, unauthorized amendment, viruses, delays or the
consequences
> thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
sender
> is authorized to state them to be the views of SAP AG or any of its
> subsidiaries. SAP AG, its subsidiaries, and their directors, officers
and
> employees make no representation nor accept any liability for the
accuracy
> or completeness of the views or information contained herein. Please
be
> aware that the furnishing of any pricing information/ business
proposal
> herein is indicative only, is subject to change and shall not be
construed
> as an offer or as constituting a binding agreement on the part of SAP
AG or
> any of its subsidiaries to enter into any relationship, unless
otherwise
> expressly stated.
>
>
>
>
>
>  ________________________________
>
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf Of
> Sharath Chandra Kotla
>  Sent: Wednesday, 20 December 2006 3:48 PM
>  To: SAP Workflow Users' Group
>  Subject: Re: Agent determination
>
>
> Manish,
>
>
> I assume 'NEXTAPPROVER' is your workflow container element.
>
>
> check what all other steps are using in their binding.It looks by the
time
> workflow control is reaching the decision step, it is filled with two
> agents.
>
>
>
>
>
> good luck
>
>
>
>
>  "Khanna, Manish" <manish.khanna at amd.com> wrote:
>
>
>
> Hi,
>
>
>
>
>
> The scenario is as follows -
>
>
>
>
>
> For a particular decision step in our capital project workflow the
agent is
> determined by an expression NEXTAPPROVER. This expression is single
line and
> is filled one step prior to the decision step.
>
>
>
>
>
> Now in our production system we are getting 2 agents. I've checked
there is
> no delegation setup or forwarding.
>
>
>
>
>
> Not sure how to proceed in this case. Can anybody suggest something?
Any
> idea what function module SAP uses to determine agent for a step; I
can try
> simulating the agent determination process for this step.
>
>
>
>
>
> Regards,
>
>
> Manish
>
> _______________________________________________
>  SAP-WUG mailing list
>  SAP-WUG at mit.edu
>  http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> __________________________________________________
>  Do You Yahoo!?
>  Tired of spam? Yahoo! Mail has the best spam protection around
>  http://mail.yahoo.com
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug