Event trigger in inbound IDoc processing

[Bormans, Raf]

Thanks a lot Darlene,
I indeed never thought of using these events triggered by ALE
 
Because I need a field which is available in an IDoc segment, and not the
IDoc number, I'll have to find a way of getting the correct object key
available (without having to read the IDoc I hope). Maybe it is even
possible to give additional events back to the ALE layer (it is a non
standard IDoc, so I have full control to the processing process)  I'll try
those possibilities out tomorrow morning.
 
Greets, Raf
 
 
-----Original Message-----
From: Benson, Darlene [mailto:darlene.benson at sourcenetsolutions.com]
Sent: woensdag 22 augustus 2001 19:32
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event trigger in inbound IDoc processing
 
 
 
Hi Raf,
 
We are currently doing something similar to what you are trying to do.  What
I have done is use the event that gets raised form the processing of the
idoc to trigger a task for which I have created method to do what I need it
to do.  For example my triggering event for the task is
IDPKINVOIC.MASSINPUTFINISHED.  Because I needed to use the document number
that was created by the idoc I had to put my code outside of the FM that
processes the idoc so that the tables would already be updated.  I hope this
helps even a little.
 
Darlene
 
-----Original Message-----
From: Bormans, Raf [ mailto:Raf.Bormans at thevisionweb.be
<mailto:Raf.Bormans at thevisionweb.be> ]
Sent: Wednesday, August 22, 2001 8:57 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event trigger in inbound IDoc processing
 
 
Hi,
 
We have an inbound IDoc processed by a function module. In this processing,
an object is created (entry written on a table). On this object, I want to
trigger an event to start a workflow (after the update).
 
Because the object does not exist before the end of the IDoc processing
(after the commit performed by the ALE layer), I see two possibilities:
 
[1] trigger the event using the function module SWE_EVENT_CREATE in a form,
called as PERFORM ... ON COMMIT
 
[2] trigger the event using the function module
SWE_EVENT_CREATE_FOR_UPD_TASK
 
I am not sure that using solution [1], the object is already created at the
time the event is raised. Concerning solution [2], the update of the object
is not done in update task (because of IDoc inbound processing), so I am not
 
sure I can use this function module.
 
Anybody can help me out?
 
Thanks, Raf
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010822/687917c9/attachment.htm