Tying Transactions to Starting Events in Workflow -SAP Version 4.7

Wed Oct 25 15:58:51 EDT 2006

Larry,

I did exactly what you did and nothing.
If I manually create the starting event CHANGE_ZCIP with transaction
SWUE it works.
The problem is the link between the transaction KO04 and the event. I
can't get it to work in my system.
I hate taking up more of your time with this.

Thanks,

Roberto.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of lianghuan.x.hu at accenture.com
Sent: Wednesday, October 25, 2006 3:27 PM
To: sap-wug at mit.edu
Subject: RE: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

I just created a very simple workflow, and at the Workflow Builder's
Triggering Event tab specify the object and event, then click the square
button to make it green(actvie). All the details you mentioned was done
automatically for me.

Larry

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of DeLeon, Roberto C.
Sent: Wednesday, October 25, 2006 3:21 PM
To: SAP Workflow Users' Group
Subject: RE: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

Larry,

just a few more questions and then I'll give it a try:

1. Did you also create a link for the event and the workflow with
transaction SWETYPV or only with SWEC?
2. If yes, did you use the Receiver Function Module
SWW_WI_CREATE_VIA_EVENT and activate the linkage?
3. What did you use as a starting task?Asynchronous or synchronous
object method? Do you think this has something to do with the fact
    that the system is not letting me start the task immediately?

Thanks,

Roberto.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of lianghuan.x.hu at accenture.com
Sent: Wednesday, October 25, 2006 3:12 PM
To: sap-wug at mit.edu
Subject: RE: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

Roberto:

I used RKAUFTRAG, and it worked.

Larry Hu

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of DeLeon, Roberto C.
Sent: Wednesday, October 25, 2006 3:09 PM
To: SAP Workflow Users' Group
Subject: RE: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

Larry,

I don't quite understand what you mean by how did I do the change table.
Are you referring to setting up the events with the wizard SWU_EWCD?

If that is the case, I set it up as follows (let's take the Change_ZCIP
event):

1. Object type ZBUS2075
2. Choose event "Change_ZCIP"
3. Choose change document type "ORDER". I only have 2 options here:
ORDER or RKAUFTRAG
4. Choose "Event upon change"

Are you supposed to have event linkages set up in both transaction SWEC
and SWETYPV or only in one?
What did you do?

Thanks,

Roberto.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of lianghuan.x.hu at accenture.com
Sent: Wednesday, October 25, 2006 2:49 PM
To: sap-wug at mit.edu
Subject: RE: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

S: Events can also be raised via change table method, which might be
preferred than user exit code.

Roberto: I just tried the things you did, and I can trigger my workflow
when I change an internal order via KO04 without problem. How did you do
the change table?

Larry Hu

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Stefaan Vermeulen
Sent: Wednesday, October 25, 2006 9:21 AM
To: SAP Workflow Users' Group
Subject: Re: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7

Roberto,

Two things are bothering me ;
-You created new events, which off-course have to be triggered by you're
own coding.
You should use function SWE_EVENT_CREATE' somewhere in a user-exit.
-You created a type linkage on the ZBUS object, you should do this on
the BUS object instead to be able to use all functionality and history.

kind regards,
S.

2006/10/24, Dave Weston <Dave.Weston at clockwork.ca>: 

	just as a follow up, have you checked if KO04 generates any
change documents ?

	Dave

________________________________

	From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu
<mailto:sap-wug-bounces at mit.edu> ] On Behalf Of DeLeon, Roberto C.
	Sent: Tuesday, October 24, 2006 4:01 PM
	To: SAP Workflow Users' Group
	Subject: RE: Tying Transactions to Starting Events in Workflow
-SAP Version 4.7

	Dave,

	Same problem.
	I can create the event manually with SWUE but if I go in and
change an internal order using KO04, it will not start it....
	Back to the drawing board...

	Thanks,

	Roberto.

________________________________

	From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu
<mailto:sap-wug-bounces at mit.edu> ] On Behalf Of Dave Weston
	Sent: Tuesday, October 24, 2006 3:49 PM
	To: SAP Workflow Users' Group
	Subject: RE: Tying Transactions to Starting Events in Workflow
-SAP Version 4.7

	Seems like you need to check out if KO04 creates any change
docs, then you may be may be able to use transaction SWEC and SWU_EWCD
(wizard for change docs) to configure your object, change doc object and
your event so an event is triggered. 

	Cheers
	Dave

________________________________

	From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu
<mailto:sap-wug-bounces at mit.edu> ] On Behalf Of DeLeon, Roberto C.
	Sent: Tuesday, October 24, 2006 3:36 PM
	To: sap-wug at mit.edu
	Subject: Tying Transactions to Starting Events in Workflow -SAP
Version 4.7
	Importance: High

	To whom it may concern:

	I just recently signed up for this user group to see if one of
you can help me out.

	I am currently designing a workflow that is to be triggered
when:

	a) An internal order is CREATED for a specific internal order
type (transaction KO04)
	b) An existing internal order is CHANGED for a specific internal
order type (transaction KO04 as well)

	1. I've created both events in my BOR object type ZBUS2075 which
is a subtype of the standard supertype or object type BUS2075 (internal
Order)

	2. I've set up both my event linkage types as follows using
transaction SWETYPV:

	    Object Category    Object Type        Event
Receiver Type

	    BO                       ZBUS2075         CREATE_ZCIP
WS90000001 (my workflow)

	    BO                       ZBUS2075         CHANGE_ZCIP
WS90000001 (my workflow)

	       Linkage settings for both events (Event Receiver)

	       Receiver Call:                        Function Module

	       Receiver Function Module:      SWW_WI_CREATE_VIA_EVENT

	       Linkage Activated                   X (activated)     

	3. If I trigger the event with transaction SWUE or SWUS it will
start the workflow correctly.  However, if I go into KO04 and create
	   an internal order type ZCIP (custom to business) or change an
existing order it will not trigger the CREATE_ZCIP or CHANGE_ZCIP event
	   and hence the workflow.

	4. I put a trace on the event it will give me a warning message
"Task CER Notification of creation cannot be started immediately" which
	    is the first task on my workflow.

	Help would be greatly appreciated regarding how to link a
transaction to a starting event.

	Thank you,

	Sincerely,

	Roberto. 

	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061025/e82873a4/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 11986 bytes
Desc: Outlook.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20061025/e82873a4/attachment.jpg