Error in event receiver

Wed Apr 3 18:03:41 EST 2002

Hi Jocelyn,

thanks for your suggestion.

We are using version 4.6c. The check functions that we are using also check
if the event creator is "enabled" for workflow (attribute in object type
USR01 that calls fucntion RH_GET_ACTORS to resolve the rule for 'workflow
disabled' users). If the user doesn't require workflow then the function
set the parked document release flag in the header so the posting function
is available (calls a method in FIPP).

I'm not sure if start condition would handle this sort of requirement?

As I said, I am pretty new to the workflow arena and I'm amending the work
of another collegue that resigned; so I'm trying to follow the same logic
as he used in the previous workflows...

Any ideas on why I am getting the error?

Thanks and regards,

Cristiana

PS. You probably don't remember me but I was one of the SAP HR consultants
in the Westpac project!

"Dart, Jocelyn" <jocelyn.dart at sap.com>@MITVMA.MIT.EDU> on 03/04/2002
06:32:26 PM

Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>

Sent by:    SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>

To:    SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:    Re: Error in event receiver

Hi Cristiana,
Just as a general observation:
Your check function modules cover classic start condition stuff.

If you are in 4.6C or above (you don't mention your release?)
you might want to swap to start conditions - that
should reduce some of the problems and cut down the development
work for changing your checking conditions.

If you are ina lower release, at the very least it's worthwhile
to mark this as something to be changed when you upgrade, to
cut down the hassle factor.
Regards,
        Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880

-----Original Message-----
From: Cristiana d'Agosto [mailto:cristiana.dagosto at au.pwcglobal.com]
Sent: Saturday, 30 March 2002 11:09 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Error in event receiver

Hope there is somenone else working on the long weekend!

When event FIPP.CREATED in published (it will only be published for doc
types DR, DG, KR, KG) we use to have 2 workflows that would be receivers of
it, and depending on the document type, one out of the two would start. For
that to work we  have written a check function module and its working fine:

WS90000016 - Z_WF_EVENT_REC_PAYVOUCH_CHECK -> if doc type diff from KR, KG
then raise exception and this workflow doesn't start
WS90000033 - Z_WF_EVENT_REC_CUST_INV_CHECK    -> if doc type diff from DR,
DG then raise exception and this workflow doesn't start

I had to create another workflow that it is also a receiver for
FIPP.CREATED. This 3rd workflow should start if document type is ( DR or DG
or KR or KG ) and document has at least one item where cost center is
blank.

I changed the other 2 check function modules so they will also raise an
exception if there is any blank cost center.

WS90000016 - Z_WF_EVENT_REC_PAYVOUCH_CHECK -> if doc type diff from KR, KG
or is_cc_blank = TRUE, then raise exception and this workflow doesn't start
WS90000033 - Z_WF_EVENT_REC_CUST_INV_CHECK    -> if doc type diff from DR,
DG or is_cc_blank = TRUE, then raise exception and this workflow doesn't
start

I created a new function module for my new workflow:
WS90000045 - Z_WF_EVENT_REC_BLANK_CC_CHECK -> if is_cc_blank = FALSE, then
raise exception and this worklfow doesn't start.

When I create my doc to test WS90000045, I get the following error:
Error in event receiver

Error processing following linkage:
FIPP CREATED WS90000045

Following error occurred:
OL 356
_SWC_TRACE_HANDLE

Message text:
Element  _SWC_TRACE_HANDLE is not available in the container

Any ideas in how to fix it??? I'm quite new in the workflow area!

Thanks in advance for your help and have a happy Easter!

Cristiana

----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.

----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.