WF status error in : Condition step ?

[Mark Pyc]

Always reply to list Priya, not to the individual.

Sorry, but that's more application specific than I have time to help with.

Have fun,
Mark


On 7/10/07, Priya Sharma <priya.sharma at tcs.com> wrote:
>
>
> Hi Mark,
> I want one more favour from you .
> In FIPP all the key fields and attributes are refrenced to table - VBKPF ,
> but amount field ( WRBTR ) doesn't exist in VBKPF .
> Instead WRBTR exist  in INVFO.
> Pls guide me, can I create an attribute with refrence table as INVFO ??
>
> Many Thanks..
>
> Best Regards
> Priya
>
>
>
>   *"Mark Pyc" <mark.pyc at gmail.com>*
>
> 07/10/2007 05:19 PM
>    To
> "Priya Sharma" <priya.sharma at tcs.com>   cc
>   Subject
> Re: WF status error in : Condition step ?
>
>
>
>
>
> You should add an Amount attribute to your subtyped/delegated version of
> FIPP and use that in the Condition.
>
> Good luck,
> Mark
>
>
> On 7/10/07, *Priya Sharma* <*priya.sharma at tcs.com* <priya.sharma at tcs.com>>
> wrote:
>
> Thanks Mark for the reply.
> I have not assigned any value to the container element 'Amount' prior to
> the condition step.
> I have not used this element in binding as condition step doesn't provide
> us the option for binding . In my scenario:
> 1) Document is parked (FIPP - created), In FV60 invoice amount is filled.
> 2)condition : 'Amount' > 2500.
> 3)Condition true - go to approver1 (agent determination through Rule)
>   Condition false - go to approver2 (agent determination through Rule)
>
> I am not sure whether this element 'Amount' in WF container get filled
> with the data entered in FV60 or  binding is required in some step ?
> or do I need to add 'amount' in attributes in BO ?
> In my graphical WF log, process has stopped in condition step.
>
> Pls advice, n help me to proceed further ...
>
>
> Best Regards
> Priya
>
>
>
>   *"Mark Pyc" <**mark.pyc at gmail.com* <mark.pyc at gmail.com>*>*
> Sent by: *sap-wug-bounces at mit.edu* <sap-wug-bounces at mit.edu>
>
> 07/10/2007 02:21 PM
>   Please respond to
> "SAP Workflow Users' Group" <* sap-wug at mit.edu* <sap-wug at mit.edu>>
>
>
>   To
> "SAP Workflow Users' Group" <*sap-wug at mit.edu* <sap-wug at mit.edu>>  cc
>   Subject
> Re: WF status error in : Condition step ?
>
>
>
>
>
> G'day Priya,
>
> Yes logically you probably want to use an attribute of your business
> object. Just declaring a container element in the Workflow will not
> automatically populate it with a value.
>
> I'm not sure that a condition would fail to error simply because the
> container element was empty, so it may not be the issue anyway.
>
> Do you assign a value to the container element prior to the condition?
>
> Have fun,
> Mark
>
>
> On 7/10/07, *Priya Sharma* <*priya.sharma at tcs.com* <priya.sharma at tcs.com>> wrote:
>
> Hi All,
>
> My condition step is not working fine , Pls help me out.
> I am designing WF for parking invoice (tcode- FV60, BO -FIPP),there I need
> to give following condition:
> If Invoice Amount > 2500 USD then mail is sent to some particular approver
> otherwise some other approver.
>
> I have declared one variable 'Amount' in WF container with refrence to
> table- INVFO and field - WRBTR.(this is a currency field.)
> and in condition step in WF, I am giving a condition .i.e - 'Amount' >
> 2500
> After activating WF and while testing it ,WF gives "status : Error "
> I hv seen in WF log , Process has stopped in condition step.
> Is there something missed or wrong in condition step ?
>
> I doubt  - if my way of declaring element 'Amount' in WF container is ok ?
>
>            Do I need to add this field as an attribute in the Bus Obj n
> then take it  in  condition editor.
>
> Pls advice how to go about it ??
>
>
> Best Rgds
> Priya
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>
> _______________________________________________
> SAP-WUG mailing list *
> **SAP-WUG at mit.edu* <SAP-WUG at mit.edu>*
> **http://mailman.mit.edu/mailman/listinfo/sap-wug *<http://mailman.mit.edu/mailman/listinfo/sap-wug>
>
> _______________________________________________
> SAP-WUG mailing list*
> **SAP-WUG at mit.edu* <SAP-WUG at mit.edu>*
> **http://mailman.mit.edu/mailman/listinfo/sap-wug*<http://mailman.mit.edu/mailman/listinfo/sap-wug>
>
> ForwardSourceID:NT00007BF2
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>
> ForwardSourceID:NT00007C4E
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070710/6a571061/attachment.htm