SRM 4.0 Subtype attribute error in starting event

Chentorycki, Richard Richard.Chentorycki at molex.com
Tue Nov 15 09:14:29 EST 2005


Why am I receiving this email ?

 Rich

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Dart, Jocelyn
Sent: Monday, November 14, 2005 8:19 PM
To: SAP Workflow Users' Group
Subject: RE: SRM 4.0 Subtype attribute error in starting event


Stephanie, 

You haven't given us any details of your new attribute to work with. 

For instance, is it calculated or a database read?
If its a database read, perhaps the data has not yet been saved at the time the start condition is evaluated? If its calculated - are the values it is reading available at the time the start condition is evaluated? Is it a quantity or value field - in which case have you made sure there is an appropriate unit/currency field linked to it to describe it?

Have you correctly used buffered data by using the correct SRM APIs e.g. BBP_PD_SC_GETDETAIL, or are you doing direct reads against database tables - in which case you may be getting a misleading result?

Remember that SRM checks the start conditions during the save shopping cart process. 

Does it determine the right workflow when you look at the approval preview before saving the shopcart?  This is a good indication of whether the data/calculation makes sense prior to saving. 

Have you tried testing your shopping cart via transaction se37 function module BBP_PDH_WFL_CHECK_START (hope that's the right one - it's something like that anyway, you'll find it fairly quickly)?

Worst case, debug through the save process. 

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. 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Stéphane Bailleul
Sent: Tuesday, 15 November 2005 5:35 AM
To: sap-wug at mit.edu
Subject: SRM 4.0 Subtype attribute error in starting event

Dear Jocelyn

I have put back the answer and question history in the message below I have in fact made the delegation The starting event are based on BUS2121 and on the starting condition 
'browser' I can see my attributes
In SWO1 while testing the object BUS2121 the attributes is appearing so in 
fact the delegation seems to work fine
But the attribute doesn't seem to be understood as valid for the starting 
condition function

Any idea ?
Best regards
Stephane

My Question
I have set up a new attribute in the Shopping cart business object, when I go in transaction SWO1 with my object ZBUS2121 and test it the new attribute is calculated without any problem. I have now added this attributes to my starting condition, and I can see in the trace for the event that the attributes is not calculated (Check FM SWB_2_CHECK_FB_START_COND_EVAL,  Operator 'EQ': The value of the left operand cannot be determined) The error is happening in the form evaluate_rule from the function SWB_COND_EVAL. Your Answer Did you remember to set up the delegation between BUS2121 and ZBUS2121 ? Try testing your attribute using business object BUS2121 - if you have set 
up
the delegation correctly you should be able to do that from SWO1.

Best regards


>From: sap-wug-request at mit.edu
>Reply-To: sap-wug at mit.edu
>To: sap-wug at mit.edu
>Subject: SAP-WUG Digest, Vol 12, Issue 59
>Date: Mon, 14 Nov 2005 12:04:33 -0500
>
>Send SAP-WUG mailing list submissions to
>	sap-wug at mit.edu
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://mailman.mit.edu/mailman/listinfo/sap-wug
>or, via email, send a message with subject or body 'help' to
>	sap-wug-request at mit.edu
>
>You can reach the person managing the list at
>	sap-wug-owner at mit.edu
>
>When replying, please edit your Subject line so it is more specific 
>than "Re: Contents of SAP-WUG digest..."
>
>
>Today's Topics:
>
>    1. RE: One more thing: Start workflow in background without using
>        event - is it possible (R/3 ver 46C) (Kjetil Kilhavn)
>    2. Re: Agent Assignment not active in Production Support
>        (Lalitha Sankaran)
>
>
>----------------------------------------------------------------------
>
>Date: Mon, 14 Nov 2005 17:23:13 +0100
>From: "Kjetil Kilhavn" <KJETILK at statoil.com>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: One more thing: Start workflow in background without using
>  event - is it possible (R/3 ver 46C)
>Message-ID: 
><273AA3C12CC7C54DA3C0C33F3857FE5C616B00 at ST-EXCL03.statoil.net>
>Content-Type: text/plain;
>	charset="iso-8859-1"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 8bit
>Precedence: list
>Reply-To: SAP Workflow Users' Group <sap-wug at mit.edu>
>Message: 1
>
>Thanks for the input, but there are two snags here (one in our solution 
>and
>one in Generic Object Services).
>
>We only have a small workflow which works with the purchase 
>requisition.
>Once we determine it needs to be approved we start a new workflow with a 
>custom object type which is used for all kinds of documents in our approval 
>solutions. Thus the rejection workflow is created once and works for all 
>documents, and there won't be any requisition object there. Saves a lot of 
>work, all I have to do in the custom object (ZBUS2009) is to implement an 
>interface where I have defined four attributes (to set the 
>document-specific identifier fields in the custom object type and a 
>description) and two events.
>
>Secondly, since ME53N publishes Requisition and not Requisition item, 
>the
>workflow overview would be pretty hard to use if workflows for approval and 
>rejection were all in that list (it's going to be bad enough as it is when 
>there are more than a handfull of items). I start the workflow for 
>requisition item, and when it has been determined that approval is required 
>I assign a reference to its aggregate object, which is the requqisition. 
>That was the only solution I found for getting it picked up by GOS.
>
>I remembered that I had read a little about anchors in The Book, so I 
>had a
>glance at that again Saturday evening. I guess I'll have to wait for our 
>upgrade (or a project on one of our systems which already run 6.x) before I 
>look more closely at them.
>--
>Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
>
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> > Behalf Of Dart, Jocelyn
> > Sent: 14. november 2005 09:50
> > To: SAP Workflow Users' Group
> > Subject: RE: One more thing: Start workflow in background without 
> > using event - is it possible (R/3 ver 46C)
> >
> > Kjetil,
> > Yes - SRM exploits ad hoc anchors programmatically.
> > Re viewing the rejection - so long as all of your workflows are 
> > linked to the Requisition object so that they show in Generic Object 
> > Services you could use that to see who has the rejection.
> > So far as displaying the requisition the same applies - you
> > just need the link to the Requisition object.
> > Getting a complete overview of the approval process would
> > require some thought and careful tailoring of the log
> > information displayed - but that's why of course you really
> > want ad hoc anchors.
> >
> >
> > 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
> >
> >
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> > Behalf Of Kjetil Kilhavn
> > Sent: Monday, 14 November 2005 6:45 PM
> > To: SAP Workflow Users' Group
> > Subject: RE: One more thing: Start workflow in background without 
> > using event - is it possible (R/3 ver 46C)
> >
> > Too late.... At 2:30 AM on Sunday I had a new solution in QA. I 
> > slept well when I got home. To my knowledge the responsibilities are 
> > not changed too often, so I think it is acceptable that the logs 
> > will display multiple reporting entries if that happens.
> >
> > I think your suggestion suffers from the same problem as Flavios 
> > suggestion. I wouldn't be able to display a purchase requisition, 
> > look at workflow overview and follow the complete approval process. 
> > With the solution I have, if the document is rejected I can see who 
> > has that rejection for processing. I wouldn't be able too if I did 
> > what you suggested (or would I?).
> >
> > With regards to the ad hoc anchor - is that something one can 
> > exploit programatically? I noticed your mentioning of them in 
> > another post and it seemed they are more of a manual thing. I 
> > suppose I will learn all about it in a couple of years.
> > --
> > Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
> >
> >
> > > -----Original Message-----
> > > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> > > Behalf Of Dart, Jocelyn
> > > Sent: 14. november 2005 02:20
> > > To: SAP Workflow Users' Group
> > > Subject: RE: One more thing: Start workflow in background without 
> > > using event - is it possible (R/3 ver 46C)
> > >
> > > Kjetil,
> > > Too bad you are in 4.6C.  Sounds exactly like an ad hoc anchor 
> > > step scenario - but that's 6.10 and above.
> > >
> > > All I can think of is to possibly implement your subflows as 
> > > separate workflows - passing the main work item id of the main 
> > > workflow, and then have them pass back their results to the main 
> > > workflow, e.g. via a custom event.
> > >
> > >
> > > 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
> >
> > >
> > > -----Original Message-----
> > > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> > > Behalf Of Kjetil Kilhavn
> > > Sent: Sunday, 13 November 2005 6:14 AM
> > > To: SAP Workflow Users' Group
> > > Subject: RE: One more thing: Start workflow in background without 
> > > using event - is it possible (R/3 ver 46C)
> > >
> > > Not a bad idea, but right off the bat I don't think it solves the 
> > > problem, because I would basically just move it somewhere else.
> > >
> > > I think the core of my problem is that I want to have a dynamic 
> > > and changeable number of parallell branches, in essence a dynamic 
> > > fork (requiring all branches to complete), where new branches can 
> > > be added without touching the existing branches. Otherwise it can 
> > > be solved by using dynamic parallell processing.
> > > Basically I want an even more dynamic parallell processing solution.
> > >
> > > I was probably too brief in my explanation as well, but a picture 
> > > or ten should make the design a little clearer. The initial 
> > > workflow is not of interest for this problem. What you can see in 
> > > the "Approve document" workflow is that I have three parallell 
> > > branches. The two rightmost ones are endless loops. The rightmost 
> > > one is in the -02 picture, while the leftmost one is in the -01 
> > > picture.
> > >
> > > So, whenever it is detected by the middle branch that there has 
> > > been a change in responsibility, a "ReportTo" event should occur. 
> > > This is also true for the initial reporting. The left branch waits 
> > > for the workflows which report the document to a specific 
> > > approving object to complete. Thus I can't simply finish the 
> > > Repord document flows by publishing events, because then the left 
> > > branch will complete. Catch 22 again!
> > >
> > > To make things worse I would prefer that the workflow log is 
> > > readable, by having all the "Report document" workflows at the 
> > > same level and by hiding a lot of the steps from the ActiveX 
> > > version of the log.
> > >
> > > The simplest solution is to use a triggering event for the 
> > > workflow, but then the workflow log will be less interesting as it 
> > > will not be possible to see the rejections and read the notes that 
> > > are associated with the rejections.
> > >
> > > I suppose I will have to resort to a dirty trick - modifying the 
> > > container to add a dummy element to the list of approvers, 
> > > stopping and starting workflows and then removing the dummy 
> > > element again.
> > > --
> > > Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
> > >
> > > > -----Original Message-----
> > > > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] 
> > > > On Behalf Of Flavio Oliveira
> > > > Sent: 12. november 2005 18:32
> > > > To: sap-wug at mit.edu
> > > > Subject: RE: One more thing: Start workflow in background 
> > > > without using event - is it possible (R/3 ver 46C)
> > > >
> > > > What if you put your event listener inside your subflow,
> > not on the
> > > > main flow. So, when something changes, the subflow will
> > > finishes and
> > > > the main flow will be called again.
> > > >
> > > > You can have a container element (if necessary) to tell
> > you how the
> > > > sublow has finished (because of the process completion or
> > > because of
> > > > any change).
> > > >
> > > > Then your main flow can reevaluate again and start another
> > > subflow if
> > > > necessary.
> > > >
> > > > I do not know if this can solve your problem, but is what I 
> > > > could think about...
> > > >
> > > > Flavio.
> > > >
> > > >
> > > > >From: "Kjetil Kilhavn" <KJETILK at statoil.com>
> > > > >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> > > > >To: "SAP Workflow User's Group" <sap-wug at mit.edu>
> > > > >Subject: One more thing: Start workflow in background
> > > without using
> > > > >event - is it possible (R/3 ver 46C)
> > > > >Date: Sat, 12 Nov 2005 17:25:40 +0100
> > > > >
> > > > >Before I changed it to parallell processing I tried
> > > another obvious
> > > > >solution, using a starting event on the subworkflow.
> > Then the loop
> > > > >could just create the event and continue and get back to the
> > > > wait step
> > > > >again. There was only one catch, and it was catch 22. With that 
> > > > >solution I lost the possibility to look at the approval
> > > process from
> > > > >the Generic Object Services of the document, because the
> > > > workflows that
> > > > >were started by the events weren't available in the log of
> > > the main
> > > > >workflow.
> > > > >--
> > > > >Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
> > > > >
> > > > >
> > > > > > From: Kjetil Kilhavn
> > > > > > Sent: 12. november 2005 17:08
> > > > > > To: SAP Workflow User's Group
> > > > > > Subject: Start workflow in background without using
> > > event - is it
> > > > >possible (R/3 ver 46C)
> > > > > >
> > > > > > I think I have come across a real show-stopper in the new
> > > > approval
> > > > > > solution I am working on. Since I have now been twisting
> > > > my head for
> > > > > > hours, trying to change the solution to parallell
> > > processing and
> > > > > > realising that that won't work either I now hope someone
> > > > reads this
> > > > > > message has a brilliant idea. Otherwise it is probably
> > > time to go
> > > > > > back to the design stage again.
> > > > > >
> > > > > > One basic idea behind the solution was that workflows
> > > > should not be
> > > > > > stopped unless it was necessary (so attachments would be
> > > > available),
> > > > > > and therefore the design was created so it would listen for 
> > > > > > significant events and then do what should be done
> > > before it went
> > > > > > back to listening again.
> > > > > >
> > > > > > In the design I have a workflow which is started per
> > > > document. This
> > > > > > workflow has to be created for each document type
> > (requisition,
> > > > > > order, service entry and so on). It evaluates the
> > document and
> > > > > > decides if it is ready and needs to be approved at all.
> > > > If approval
> > > > > > is required a generic subworkflow for approval is started.
> > > > > >
> > > > > > The workflow for approval finds out which objects are
> > > responsible
> > > > > > for approval and creates one event for each such
> > > > responsible object.
> > > > > > This event is captured in a parellell branch which
> > > > listens for the
> > > > > > event, starts a subworkflow and loops back to listen for
> > > > the event.
> > > > > > However - and I could kick myself for not thinking about
> > > > this before
> > > > > > now - when the subworkflow is started the main workflow
> > > > waits for it
> > > > > > to complete. So when the document is changed and there
> > > is another
> > > > > > approver in addition to the original one, there is no-one
> > > > listening
> > > > > > for the event because the loop hasn't completed its circle!
> > > > > >
> > > > > > What I need is a multistep task that can be started in
> > > > background so
> > > > > > the flow continues. As far as I can see there is no such
> > > > thing, at
> > > > > > least in version 4.6C.
> > > > > > I've been thinking about ways to circumvent the problem,
> > > > e.g. having
> > > > > > a parallell branch that completes after a minute, but
> > > > that will only
> > > > > > cause the subworkflow to be killed when the other branch
> > > > completes.
> > > > > >
> > > > > > I just changed it to a parallell processing step so all the 
> > > > > > subworkflows can be started in parallell when there are
> > > multiple
> > > > > > approvers at first, but that doesn't solve the real
> > > > problem which is
> > > > > > related to changes. I'm being driven back inch by inch
> > > and it is
> > > > > > rather depressing....
> > > > > >
> > > > > > Right now I only see one solution: if there are any
> > changes in
> > > > > > responsibility, kill all the active subworkflows and
> > > > start new ones.
> > > > > > I'm hoping someone else sees a better solution.
> > > > > > --
> > > > > > Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
>
>
>-------------------------------------------------------------------
>The information contained in this message may be CONFIDENTIAL and is 
>intended for the addressee only. Any unauthorised use, dissemination of 
>the information or copying of this message is prohibited. If you are 
>not the addressee, please notify the sender immediately by return 
>e-mail and delete this message. Thank you.
>
>------------------------------
>
>Date: Mon, 14 Nov 2005 11:42:28 -0500
>From: Lalitha Sankaran <lalisan at gmail.com>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: Re: Agent Assignment not active in Production Support
>Message-ID: 
><cf1e515f0511140842x7575af0ap1a01026a458d183d at mail.gmail.com>
>In-Reply-To: 
><18339.194.215.164.125.1131977914.squirrel at secure.workflowconnections.com>
>References: <cf1e515f0511140347y3fbcf0eaw79d01a53037ad100 at mail.gmail.com>
>	<59690.194.215.164.125.1131970190.squirrel at secure.workflowconnections.com>
>	<cf1e515f0511140429p6a9dd750y35edb0eaa0015d85 at mail.gmail.com>
>	<18339.194.215.164.125.1131977914.squirrel at secure.workflowconnections.com>
>Content-Type: multipart/alternative;
>	boundary="----=_Part_5374_13263583.1131986548719"
>MIME-Version: 1.0
>Precedence: list
>Reply-To: SAP Workflow Users' Group <sap-wug at mit.edu>
>Message: 2
>
>------=_Part_5374_13263583.1131986548719
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: inline
>
>Hi Mike,
>  Had to go and set the Task Attribute as General Task in RPS,
>  That worked and now it is working and sending our workitems, 
>Appreciate your help
>  Thank you
>Lalitha
>
>
>  On 11/14/05, Mike Pokraka <wug.replies at workflowconnections.com> 
> wrote:
> >
> > Hi Lalitha,
> > Set a task to general, if it asks you for a transport then it's 
> > enabled, if not then it isn't. Transaction OOTR, entry 'Trasnport 
> > Switch' controls the task attributes.
> >
> > For agent assignment - such as assigning org units to a task - you 
> > have
>t=
>o
> > dig around HR customising. Actually best you speak to an HR person 
> > as
>you
> > need to consider number ranges and stuff very carefully before 
> > transporting HR relationships.
> >
> > Cheers
> > Mike
> >
> > Lalitha Sankaran wrote:
> > > Hi Mike,
> > > How do I determine Which process is being used, for Agent 
> > > Assignment, whether customizing or Manual. Appreciate your help,
> > > Lalitha
> > >
> > >
> > > On 11/14/05, Mike Pokraka <wug.replies at workflowconnections.com> 
> > > wrote:
> > >>
> > >> Hi Lalitha,
> > >> Agent assignments are either in a separate customising transport 
> > >> or
> > done
> > >> manually in each system, depending on how your system is 
> > >> configured. Cheers Mike
> > >>
> > >> Lalitha Sankaran wrote:
> > >> > Hi All,
> > >> > The Agent Assignment in the task is active in Dev,
> > >> > and the workitems are sent to the correct Agents
> > >> > that are picked using Method and our own logic. Everything was 
> > >> > working fine in Dev, But after moving to PS, The workflow
> > >> > gets started , The agents are picked,
> > >> > but the workitem is not sent,Since the Agent Assignment
> > >> > is not active.
> > >> > What Do I need to check ?
> > >> > Please Advise,
> > >> > Lalitha
> > >> > _______________________________________________
> > >> > SAP-WUG mailing list
> > >> > SAP-WUG at mit.edu
> > >> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > >> >
> > >>
> > >>
> > >> Mike Pokraka
> > >> Senior Consultant
> > >> Workflow Connections Ltd.
> > >> Mobile: +44 (0)7786 910 855 
> > >> _______________________________________________
> > >> 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
> > >
> >
> >
> > Mike Pokraka
> > Senior Consultant
> > Workflow Connections Ltd.
> > Mobile: +44 (0)7786 910 855 
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>
>------=_Part_5374_13263583.1131986548719
>Content-Type: text/html; charset=ISO-8859-1
>Content-Transfer-Encoding: quoted-printable
>Content-Disposition: inline
>
><div>Hi Mike,</div>
><div>&nbsp;</div>
><div>Had to go and&nbsp;set the Task Attribute as &nbsp;General
>Task&nbsp;i=
>n RPS, </div>
><div>&nbsp;</div>
><div>That worked and now it is working and sending our workitems,</div>
><div>Appreciate your help</div>
><div>&nbsp;</div>
><div>Thank you</div>
><div>Lalitha</div>
><div><br><br>&nbsp;</div>
><div><span class=3D"gmail_quote">On 11/14/05, <b 
>class=3D"gmail_sendername"=
> >Mike Pokraka</b> &lt;<a
>href=3D"mailto:wug.replies at workflowconnections.com=
>">wug.replies at workflowconnections.com</a>&gt; wrote:</span> <blockquote 
>class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
>px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Lalitha,<br>Set a task to 
>gen=
>eral, if it asks you for a transport then it's enabled,<br>if not then it 
>i=
>sn't.
><br>Transaction OOTR, entry 'Trasnport Switch' controls the task 
>attributes=
>.<br><br>For agent assignment - such as assigning org units to a task - 
>you=
>  have to<br>dig around HR customising. Actually best you speak to an HR 
>per=
>son as you
><br>need to consider number ranges and stuff very carefully 
>before<br>trans=
>porting HR relationships.<br><br>Cheers<br>Mike<br><br>Lalitha Sankaran 
>wro=
>te:<br>&gt; Hi Mike,<br>&gt;&nbsp;&nbsp;How do I determine Which process 
>is=
>  being used, for Agent Assignment,
><br>&gt; whether customizing or Manual.<br>&gt;&nbsp;&nbsp;Appreciate your 
>=
>help,<br>&gt; Lalitha<br>&gt;<br>&gt;<br>&gt;&nbsp;&nbsp;On 11/14/05, Mike 
>=
>Pokraka &lt;<a 
>href=3D"mailto:wug.replies at workflowconnections.com">wug.repl=
>ies at workflowconnections.com
></a>&gt; wrote:<br>&gt;&gt;<br>&gt;&gt; Hi Lalitha,<br>&gt;&gt; Agent 
>assig=
>nments are either in a separate customising transport or done<br>&gt;&gt; 
>m=
>anually in each system, depending on how your system is configured.<br>
>&gt;&gt; Cheers<br>&gt;&gt; Mike<br>&gt;&gt;<br>&gt;&gt; Lalitha Sankaran 
>w=
>rote:<br>&gt;&gt; &gt; Hi All,<br>&gt;&gt; &gt; The Agent Assignment in 
>the=
>  task is active in Dev,<br>&gt;&gt; &gt; and the workitems are sent to the 
>=
>correct Agents
><br>&gt;&gt; &gt; that are picked using Method and our own 
>logic.<br>&gt;&g=
>t; &gt; Everything was working fine in Dev,<br>&gt;&gt; &gt; But after 
>movi=
>ng to PS, The workflow<br>&gt;&gt; &gt; gets started , The agents are 
>picke=
>d,
><br>&gt;&gt; &gt; but the workitem is not sent,Since the Agent 
>Assignment<b=
>r>&gt;&gt; &gt; is not active.<br>&gt;&gt; &gt; What Do I need to check
>?<b=
>r>&gt;&gt; &gt; Please Advise,<br>&gt;&gt; &gt; Lalitha<br>&gt;&gt; 
>r>&gt;
>__=
>_____________________________________________
><br>&gt;&gt; &gt; SAP-WUG mailing list<br>&gt;&gt; &gt; <a
>href=3D"mailto:S=
>AP-WUG at mit.edu">SAP-WUG at mit.edu</a><br>&gt;&gt; &gt; <a 
>href=3D"http://mail=
>man.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listin=
>fo/sap-wug
></a><br>&gt;&gt; &gt;<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt; Mike 
>Pokraka<br>&=
>gt;&gt; Senior Consultant<br>&gt;&gt; Workflow Connections 
>Ltd.<br>&gt;&gt;=
>  Mobile: +44 (0)7786 910 855<br>&gt;&gt; 
>__________________________________=
>_____________
><br>&gt;&gt; SAP-WUG mailing list<br>&gt;&gt; <a 
>href=3D"mailto:SAP-WUG at mit=
>.edu">SAP-WUG at mit.edu</a><br>&gt;&gt; <a 
>href=3D"http://mailman.mit.edu/mai=
>lman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><=
>br>
>&gt;&gt;<br>&gt; 
>_______________________________________________<br>&gt;
>SA=
>P-WUG mailing list<br>&gt; <a 
>href=3D"mailto:SAP-WUG at mit.edu">SAP-WUG at mit.e=
>du</a><br>&gt; <a href=3D"http://mailman.mit.edu/mailman/listinfo/sap-wug">
>http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>&gt;<br><br><br>Mike=
>  Pokraka<br>Senior Consultant<br>Workflow Connections Ltd.<br>Mobile: +44 
>(=
>0)7786 910 
>855<br>_______________________________________________<br>SAP-WU=
>G mailing list
><br><a href=3D"mailto:SAP-WUG at mit.edu">SAP-WUG at mit.edu</a><br><a 
>href=3D"ht=
>tp://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailm=
>an/listinfo/sap-wug</a><br></blockquote></div><br>
>
>------=_Part_5374_13263583.1131986548719--
>------------------------------
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>End of SAP-WUG Digest, Vol 12, Issue 59
>***************************************


_______________________________________________
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


CONFIDENTIALITY NOTICE: This message (including any attachments) may contain Molex confidential information, protected by law. If this message is confidential, forwarding it to individuals, other than those with a need to know, without the permission of the sender, is prohibited.

This message is also intended for a specific individual. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message or taking of any action based upon it, is strictly prohibited. 

Chinese  Japanese

www.molex.com/confidentiality.html





More information about the SAP-WUG mailing list