Event for IDOC (object type IDOCORDCHG) not triggered

[Xue Jing]

Mike,
 
We are unfortunately on 4.0B. I have checked several SAP functions for
inbound IDoc creation, but they contain no logic to raise the event, so I
presume the event is not raised, but I'm not 100% sure of my investigation
here. I'll try to do some testing in our 4.6C system.
 
As you said, if possible, I may choose to raise the event manually.
 
Xue
 
 
 
 
 
 
Michael Pokraka <workflow at quirky.me.uk>@MITVMA.MIT.EDU> on 17/12/2002
11:24:44 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: Event for IDOC (object type IDOCORDCHG) not triggered
 
 
Hi,
You don't mention what release you're working with. But I have
nevertheless had a similar problem in a 4.0b system: If I remember
correctly, the event was raised by object type IDOC, not IDOCORDCHG. In my
case it was in fact with orders, and I ended up using the BUS2032.CREATED
event instead, with a check function to determine whether it was created by
an IDOC.
Another alternative is to manually reise the event in an IDOC userexit.
 
HTH
Cheers
Mike
 
 
On Mon, Dec 16, 2002 at 12:33:59PM +1100, Xue Jing wrote:
> Hi all,
>
> I have been trying to implement a simple workflow for inbound IDoc type
> ORDCHG, but I 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 opinion.
>
>
> *_*   !!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.
> =====================================================================
 
 
====================================================================
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.
=====================================================================