KNA1 vs KNVV events

[Chatterjee, Partha (US - San Ramon)]

Hi Michael,
 
You have probably already thought of this but in situations like this, I
like using a combination of Start conditions/Check function modules.  I
have not worked with KNA1 or KNVV specifically but I have run into
multiple events firing with change documents.  The start
conditions/check function modules can help refine your document triggers
without to much coding.
 
Best regards,
 
Partha Chatterjee
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Michael Pokraka
Sent: Wednesday, May 19, 2004 9:41 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: KNA1 vs KNVV events
 
Hi,
I'm setting up custom ZCREATED events for customers. The theory is
simple,
BUT... I also need to handle specific sales areas, requiring object KNVV
rather than KNA1. My predecessor has done the decent thing and tweaked
SWED/SWEC to link changedoc DEBI to object KNVV with a new key that
includes
sales area etc.
 
Problem: I have another workflow that does NOT have a sales area. So we
have
to use KNA1-ZCREATED. So methinks just copy the SWEC entry for
KNVV-ZCREATED
and plug in KNA1 as the object. It whines a little bit about
incompatible
keys but since it's really just an extra bit at the end I try it anyway.
Doesn't work. Looks like I can raise events for KNA1 or KNVV but not
both.
 
Now, I can work around this with event containers and some fluff, but
it's
not not nice and I'm curious if there is a neater way that anyone has
dealt
with both KNA1 and KNVV. There's excellent functionality for customizing
the
events with own FM's, but through all that flexibility it seems that a
change document can only be set to a single key.
Also, even more curious is that configuring it with the default KNA1
will
result in multiple CREATED events with the same key as each sales area
is
created....
 
Any comments appreciated...
Cheers
Mike
 
 
 
This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly =
prohibited.