A Question about Event Creation Using Message Control

[Christian Buhr]

Hi David,
maybe I'm not exactly understand everything what you wrote, but I think we had
at least a related requirement.

The event-linkage for one event "CREATED" was included into 15 workflow
templates.
Our first attempt was to create one check function module to be used in each and
every linkage. Based on a customizing table and the information in the
event-container, only one event-linkage was correct and this kicked off the
appropriate process. The other fourteen events didn't make it through the
check.

This may result in performance issues if you're dealing with a lot of workflow
templates and loads of events.

This lead to our second attempt we're using now:
Instead of using the check function module, we've created a custom receiver type
function module. We could utilize the customizing table already existing from
our first attempt. But with this solution only one function module call is
executed per event (not 15 as with our initial solution) to determine the
correct workflow template. Actually the situation is satisfying (we're not
productive, but at a very late stage of development).

Our reason for going down this route: We didn't want to code all the
event-creating ourselfes but use the SAP-delivered standards. Thus only the
"CREATED" event was existing for us to know that a workflow should be
triggered.

Regards
Christian

Consultant
SAP Business Workflow
SAP IS-U/CCS


Zitat von David Holland <mggq59 at dsl.pipex.com>:

> Mike,
> As far as distinguishing between the two, I noticed that the 3rd output type
> I created (ZWF3) using the already created CREATED event actually triggered
> another workflow already in operation.
> I'm not sure why the output type (ZWF1) configured for VBRK.CREATED didn't
> get created when I created a normal bill because ZWF1 is configured for
> VBRK.CREATED for Normal Bills billing type.
>
> I think I might play safe and go for a new ZCREATED event.
>
> Thanks
> Dave
>
> ----- Original Message -----
> From: "Mike Pokraka" <wug.replies at workflowconnections.com>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Sent: Thursday, August 04, 2005 10:53 PM
> Subject: Re: A Question about Event Creation Using Message Control
>
>
> > Hi David,
> > An event is something that happens and should semantically match the
> > process. So there is no point in having CREATED and ZCREATED because they
> > mean the same thing...
> >
> > Other than maintenance, there are no technical issues of going down either
> > route. Do you need to distinguish between the two? Is it a different
> > workflow? I've done both, I try to keep things together for better
> > visibility and ease of maintenance, unless there are specific reasons to
> > separate them (perhaps they're maintained by different departments?). If
> > your business processes are that vastly different it may make sense to
> > have ZCREATED_EU and ZCREATED_NONEU.
> >
> > My conclusion: it depends......  :-)
> >
> > Cheers
> > Mike
> >
> > David Holland wrote:
> >> Hi Workflowers
> >> I currently have two message types configured in our system through V/40
> >> (e.g. ZWF1 and ZWF2).
> >>
> >> I have a requirement to trigger a workflow based on Sales Org and the
> >> Bill To party e.g. for object VBRK
> >>
> >> Currently ZWF2 has config. for VBRK event Created (a custom created event
> >> for another workflow triggered through message types).
> >>
> >> I am proposing to create a new event on VBRK called 'ZCREATED' and create
> >> a new output type e.g. ZWF3 and enter the config. in VV31 for Sales
> >> org./Bill to. for VBRK.ZCREATED
> >>
> >> My question is, are there any general standards as to what should be done
> >> here ?
> >> i.e. Should I create a new Output Type or use and existing one and enter
> >> the config. in VV31 for Sales org./Bill to
> >>
> >> Should I be creating a new event on VBRK or using an existing event e.g.
> >> VBRK.CREATED ?
> >>
> >> Many Thanks
> >> Dave
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> 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
> >
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>