Problem with start condition

[Mark Pyc]

G'day Tony,

Be sure to always reply to list rather than an individual respondant. No
point taking this offline where others can't benefit and someone else may
(likely) have a better response than what follows...

It would seem that your start condition is behaving as you expect. Have a
look at the instanciated Workflows and look at the object instance and
eyeball the values you're checking in the start condition - make sure it's
not just a typo. You can try using the test options within the condition
editor of the SWB_COND.

Good luck,
Mark


On 6/23/06, Hoodak, Anthony J. <AHoodak at gleason.com> wrote:
>
>  Hi Mark -
>
> Thanks for the quick reply. I did misspeak here. Yes, I meant the event
> log. And no, I do not see anything that indicates that the exception was
> raised. In the type linkages table, I see the following:
>
> Receiver Function Module         SWW_WI_CREATE_VIA_EVENT_IBF
> Check Function Module            SWB_CHECK_FB_START_COND_EVAL
> So the check function appears to be there. However, in the event log, I am
> seeing the following:
>
> Event Instance ID    20184571
>
> Object Type          AFVC_PM
> Object Key           000050911400000005
> Event                FINALCONFIRMATION
>
> Event Creator        US SHFLROCH       Acsis Shop Floor Data Colle
> Creation Time        06/23/2006 08:10:14 EST
>
>
> Receiver Type        WS90200067
>
> Object Type          WORKITEM
> Object Key           000009861148
>
> Receiver FM          SWW_WI_CREATE_VIA_EVENT_IBF
> RFC Destination      WORKFLOW_LOCAL_410
>
> Check FM             SWB_CHECK_FB_START_COND_EVAL
> Receiver Type FM
>
>
> Trace Date/Time      06/23/2006 08:10:15 EST
> User Name            SHFLROCH       Acsis Shop Floor Data Collecti
> Main Program         RSM13000
> Action               Receiver started correctly
>
>
> I don't see any indication that the check FM did it's job. I see the WF
> get started and this is what I wanted to avoid.
>
> Hope this makes sense to you and thank you in advance Mark.
> Tony
>
>  ------------------------------
> *From:* Mark Pyc [mailto:mark.pyc at gmail.com]
> *Sent:* Friday, June 23, 2006 9:17 AM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: Problem with start condition
>
>
>  G'day Tony,
>
> Firstly SWEL is the event log, it's not to be confused with the event
> queue.
>
> If an event is raised, and the event log is turned on, then it will be
> logged. If you have a start condition which prevents it you should see a red
> light in the log and a message to indicate the check function (which is how
> the start condition is implemented) raised an exception.
>
> If this isn't the case for you, make sure the start condition is active
> and you can further check that in SWETYPV that there is a check function in
> place which checks the start condition (this should be there automatically).
>
>
> Have fun,
> Mark
>
>
> On 6/23/06, Hoodak, Anthony J. <AHoodak at gleason.com> wrote:
> >
> >  Greetings -
> >
> > Background:
> >
> > I have a WF that I have created that monitors a specific BO. The WF is
> > triggered by a an event that gets raised, and this is working properly. Too
> > properly in fact because I have an issue where our shop floor data
> > collection system is sending a bunch of records to SAP to process. Each
> > record is triggering the WF and this should not be the case, as I only want
> > records created by specific sources. So to prefilter events, I used a start
> > condition to NOT process any of the events that are triggered by the shop
> > floor system. The problem is, I am still seeing those event transactions
> > appear in the SWEL queue.
> >
> > Questions:
> >
> > 1. Should I still see these events in the SWEL queue?
> > 2. If not, I am using SWB_COND to set a start condition for this WF. The
> > precheck is pretty simple (if the creator of the record is NOT = SFDC, then
> > start the WF). In theory these should be the exceptions. What am I doing
> > wrong?
> >
> > Hope this all makes sense and someone can point out the error in my
> > ways.
> >
> > Thanks in advance,
> >
> > Tony Hoodak
> > Gleason Corp
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060623/1f69f7cc/attachment.htm