Event for IDOC (object type IDOCORDCHG) not triggered

[Soady, Phil]

IDOCORDCHG events will be triggered assuming an earlier IDOC issue / event
didn't happen.
 
Make sure the event trace is on...  Just checking...
 
Then you may find...
the object IDOC and events where triggered.
Perhaps even IDOCAPPL events.
 
I can certainly trigger,
 
IDOCORDCHG event INPUTERROROCCURRED with an empty IDOC.
 
I assume others can be triggered if the idoc gets far enough.
That I didn't try since I didn't have time to set up test data.
 
hth
Phil
 
 
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Xue Jing [mailto:Xue.Jing at weirwarman.com]
Sent: Tuesday, 17 December 2002 10:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event for IDOC (object type IDOCORDCHG) not triggered
 
 
Hi all,
 
I have been trying to implement a simple workflow for inbound IDoc type ORDCHG, but seem to encounter unsurmountable problem.
 
To be more specific, I have created my own task to run a customised report. My workflow contains this task only and the workflow should be triggered by the event that an inbound IDoc of type ORDCHG is coming into our system and ready for process.  The event I'm expecting is
"IDOC.processStateReached" for object type "IDOCORDCHG". However, this event is not triggered when an Idoc is created. I checked the event via event trace SWEL.
 
My question is:
 
1. Does any one know if the above event is correct for the above business scenario? If not, which one shall I use? 2. If yes to question 1, how can this event be triggerred? Why it's not triggered when the Idoc was created?
 
Look forward to your help.
 
 
Have a nice day,
 
*_*   !!0_0!!   //^_^\\   ||*_*||   [o_o]   .'^_^'.
 
 
******************************
Xue Jing
 
Application Programmer
SAP Service
Weir Warman Limited
Tel :    00 61 2 9934 5363
Fax :   00 61 2 9934 5199
http://www.warman.com
****************************** ====================================================================
The information contained in this message and any attached files is confidential, subject to copyright and is intended for the addressee(s) only.  If you have received this message in error please delete it and notify the originator immediately.  The unauthorised use, disclosure, copying or
alteration of this message is strictly forbidden. Weir Warman Ltd. will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any virus being passed on. Internet communications are not secure
and therefore Weir Warman Ltd. does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of Weir Warman Ltd. =====================================================================