AW: Creating an event to invoke a workflow each time a field valu e changes

Thu Aug 7 05:50:18 EDT 2003

Hi Manju.

do you have enterd the Events in EventLinkage (tx  swetypv) and it is
activated right ?

You can test event-launching with tx swu0 (simulate) and swue (create
event).

mabe this helps.

regards

Heinz

-----Urspr=FCngliche Nachricht-----
Von: Manju Thangudu [mailto:manjuwf at yahoo.co.in]
Gesendet am: Mittwoch, 6. August 2003 17:09
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Creating an event to invoke a workflow each time a field
valu e changes

Thanks Phil,

Yes I understand VIQMEL-PRIORK and that there is a view.  I even went
further into the Customizing, found that MELDUNG is the defined change =
doc
OBJECT that invokes change documents for QMEL.

I have done the following and the event still does not trigger the =
workflow.
Any help/leads appreciated.

But I am still not doing something right.  I thought I got all the =
pieces
together and have done the right things but the event is not getting
invoked.  Please see what I have done.

1.  Copied BUS2080  to ZBUS2080A
2.  To ZBUS2080A - Added an event CPICHGSTARTWF (implemented and =
released
correctly)
3.  Went to SWEC and added the following:
     (MELDUNG/ZBUS2080A/CPICHGSTARTWF On create
    (MELDUNG/ZBUS2080A/CPICHGSTARTWF On change
    Condition record:
     (&QMEL_PRIORK_NEW& =3D 1 or
      &QMEL_PRIORK_NEW& =3D 2) or
    (&QMEL_ERLDAT_NEW& > ' ' or
     &QMEL_ERLNAM_NEW& >  ' ') and
    (&QMEL_QMART_NEW& =3D C1)

I go to iw51 to create a new notification.  Did set the priority to 1.  =
But
the event was not triggered.

I go to iw52 to change the notfication.  Set priority to 2.  But the =
event
is not triggered.

What could be the reasons?
 thanks
manju

"Soady, Phil" <phil.soady at sap.com> wrote:
Dear Manju,

The priority field on the notification is QMEL-PRIOK .
The VIQMEL is view. There is no field PRIORK.

The change document does support the field.
The customizing of change documents does support
condition field value triggering.
Please revisit the customizing and help.

You should be able to achieve what was originally described
via transaction SWEC.

hth

Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com

-----Original Message-----
From: Dart, Jocelyn
Sent: Tuesday, August 05, 2003 6:45 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Creating an event to invoke a workflow each time a field =
valu e
changes

Manju
There are lots of ways to raise events. Perhaps you should do a bit =
more
reading... there's a fair bit on this in the SAP Library help under =
Basis >
Business Management > Workflow. You'll also find info on the change
documents there. If the field is not part of the change document is
generally for a good reason so suggest you look elsewhere. Status =
management
is always a good one for notifications. Regards,
Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax: +61 2 9935 4880

-----Original Message-----
From: Manju Thangudu [mailto:manjuwf at yahoo.co.in]
Sent: Tuesday,5 August 2003 12:08 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Creating an event to invoke a workflow each time a field =
valu e
changes

No VIQMEL-PRIORK is not part of the change document. I am trying to get =
that
in place by going to SCDO. However, I was wondering if there was any =
other
alternative.

Any other ways of invoking an event other than change document? Also =
looks
like a defining in SCDO forces all fields to be on the change documents
created. Can I restrict to VIQMEL-PRIORK only on the change document? =
thanks
manju "Dart, Jocelyn" wrote: Of course if VIQMEL-PRIORK is part of a =
change
document you could simply use the change document event creation
configuration (its in the workflow menu > definition tools > events) =
instead
of coding stuff. Regards, Jocelyn Dart Consultant (SRM, EBP, Workflow) =
and
co-author of the book "Practical Workflow for SAP" SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax: +61 2 9935 4880

-----Original Message-----
From: Kouw, FA - SPLTX [mailto:fa.kouw at td.klm.com]
Sent: Saturday,2 August 2003 12:14 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Creating an event to invoke a workflow each time a field =
value
changes

Manju,

A WAPI is a workflow API (application programming interface) that =
performs a
specific function (peace of code that does something related to =
workflow).
Within an ABAP program you can use this f.i. to trigger an event. Maybe
there is a simpler solution to trigger your event in case the field has =
been
changed, I do not know. Hope someone else can help you out with this =
one.

Regards,

Fred Kouw

Manju Thangudu wrote:

> thanks a bunch but I dod not know how to trigger the newly created
> event after the field Projk has been changed. What is WAPI?
>
> "Kouw, FA - SPLTX" wrote:Hi Manju,
>
> If the logic in the method is able to determine what to do based on
> the value(s) of PRIORK then that part is covered. You still have to
> trigger your newly created event after the field PRIORK has been
> changed. Do you already know how to do that (change document, WAPI)?
>
> Regards,
>
> Fred
>
> Manju Thangudu wrote:
>
> > For Any changes to the field VIQMEL-PRIORK (Priority) i want a
> > workflow to be kicked off.
> >
> > My approach was going to be as follows:
> > 1. Copy object BUS2080 to Z_BUS2080.
> > 2. Add an event called PRIORCHGED.
> > 3. Add a method PRIORCHGED_METHOD
> > 3. Put the event in a workflow templates triggering event. 4. In
> > that workflow put a task that points to object Z_BUS2080 and method
> > PRIORCHGED_METHOD. THe logic in the method will determine what =
needs
> > to be done depending ont he values of PRIORK.
> >
> > Is this right?
> >
> > SMS using the Yahoo! Messenger;Download latest version.
> >
> > =
____________________________________________________________________
> > _____________________
> > This inbound message from KPN has been checked for all known =
viruses by
KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >
________________________________________________________________________=
____
_________________
>
> =
**********************************************************************
> This e-mail and any attachment may contain confidential and =
privileged
> material intended for the addressee only. If you are not the
> addressee, you are notified that no part of the e-mail or any
> attachment may be disclosed, copied or distributed, and that any =
other
> action related to this e-mail or attachment is strictly prohibited,
> and may be unlawful. If you have received this e-mail by error, =
please
> notify the sender immediately by return e-mail, and delete this
> message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> subsidiaries and/or its employees shall not be liable for the
> incorrect or incomplete transmission of this e-mail or any
> attachments, nor responsible for any delay in receipt.
> =
**********************************************************************
>
> =
______________________________________________________________________
> _______________________
> This outbound message from KPN has been checked for all known viruses =
by
KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
>
________________________________________________________________________=
____
_________________
>
> SMS using the Yahoo! Messenger;Download latest version.
>
> =
______________________________________________________________________
> ___________________
> This inbound message from KPN has been checked for all known viruses =
by
KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
>
________________________________________________________________________=
____
_________________

**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, =
you
are notified that no part of the e-mail or any attachment may be =
disclosed,
copied or distributed, and that any other action related to this e-mail =
or
attachment is strictly prohibited, and may be unlawful. If you have =
received
this e-mail by error, please notify the sender immediately by return =
e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), =
its
subsidiaries and/or its employees shall not be liable for the incorrect =
or
incomplete transmission of this e-mail or any attachments, nor =
responsible
for any delay in receipt.
**********************************************************************

________________________________________________________________________=
____
_________________
This outbound message from KPN has been checked for all known viruses =
by KPN
IV-Scan, powered by MessageLabs. For further information visit:
http://www.veiliginternet.nl
________________________________________________________________________=
____
_________________

SMS using the Yahoo! Messenger;Download latest version.