Terminating Events Generate Feedback After Error

Wed Jun 11 01:54:08 EDT 2008

Hello again,

to give you some more background:

The instance coupling that you can see in SWEINST is generated/created, when the first work item with such a terminating event is created. So you will need a work item for that. If the instance coupling is missing, after you have created such a work item, there's something wrong either with the definition of the work item, the definition of the business object or the runtime system.

The standard entry in sweinst does have the receiver type WORKITEM and the receiver function module SWW_WI_COMP_EVENT_RECEIVE
It does /not/ have any check function module.

An example is the TS20000159 based on a purchase requisition BUS2105 waiting for the terminating event RELEASED (and others). Usually there is a check-function module in between, but in your case, it is not neccessary.
To create a sample instance of that task, use SWUS and give any purchase requisition (created with transaction ME51N) here. The requisition does not need to have a (correct) release strategy, nor you have to have a correct release code. Check, that you have the task defines as "general task" (transport this to DEV150) and refreshed your organizational environment once.

After the instance is created (the system executes transaction ME54N and possibly gives you a message that the requisition cannot be released) go back again and use SWUE transaction to raise one of the terminating events.

Best wishes,
Florin

-------- Original-Nachricht --------
> Datum: Wed, 11 Jun 2008 11:16:11 +0800
> Von: Sandy <maorriyan.santoso at gmail.com>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: Re: Terminating Events Generate Feedback After Error

> Hi Florin.
> I pressed generate button in test client.
> Execute SWUE for both events ACCEPTED and DECLINED unfortunatelly both
> events doesn't exist in SWEINST with info message "No receiver entered".
> There is no ST22 and SM58 doesn't contains any record.
> SCC1 have auto-transport mechanism from DEV140 -> DEV150
> 
> Does entry in SWEINST really generated automatically? Does this entry
> created automatically upon execution of SWUE?
> Does terminating event only rely on SWEINST to be able to work?
> Do you know SAP standard workflow/ task that has wait step or terminating
> event? Perhaps I can have a look on it and do further investigation
> 
> Should this consider as an issue that need to be sent to OSS?
> 
> Florin & Rick, thanks for your help so far
> 
> On Tue, Jun 10, 2008 at 8:36 PM, Florin Wach <florin.wach at gmx.net> wrote:
> 
> > Hi Sandy,
> >
> > to keep you busy:
> > Go into the test-client, call SWO1 and press the generate-button there.
> You
> > could also think of using transaction SWU_OBUF in the test-client, but
> only
> > as a last resort, as it /may/ corrupt your workflow definition.
> >
> > -------- Original-Nachricht --------
> > > Datum: Tue, 10 Jun 2008 19:41:03 +0800
> > > Von: Sandy <maorriyan.santoso at gmail.com>
> > > An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> > > Betreff: Re: Terminating Events Generate Feedback After Error
> >
> > > Hi Florin.
> > > I tried to simply my issue by involving single workflow task.
> > >
> > > Instead of delete, I created new event "DECLINED" and still part of my
> > > custom object type. I created new asynchronous method and attached to
> my
> > > new
> > > single dialog asynchronous task.
> > > My asynchronous single task has business object type and event in
> > > terminating events tab with binding &_EVT_OBJECT& --> &_WI_OBJECT_ID&
> > > And this time I didn't touch SWEINST.
> > >
> > > For your information, creation of objects (DEV140) and test is in
> > > different
> > > client (DEV150)
> > >
> > > SWUE executed with object key and new event "DECLINED" and event trace
> > > says
> > > "No receiver entered"
> > >
> > > I read correspondence between Paul Baker & Jocelyn D which was similar
> > > issue
> > > with me but the solution doesn't work for my case
> > >
> > >
> > > On Tue, Jun 10, 2008 at 4:37 PM, Florin Wach <florin.wach at gmx.net>
> > wrote:
> > >
> > > > I would first delete the entry (with all dependend entries) of the
> > > instance
> > > > linkage BUS.ACCEPTED using transaction SWEINST.
> > > > Then create a new workflow instance. The instance linkage should
> come
> > > all
> > > > by itself with activated linkage. By the way: The receiver function
> is
> > > > SWW_WI_COMP_EVENT_RECEIVE and not SWW_WI_CREATE_VIA_EVENT.
> > > > To analyze the error, please check transaction SM58 tRFC queue, as
> > well.
> > > > Also check for short dumps, transaction ST22
> > > >
> > > >
> > > > -------- Original-Nachricht --------
> > > > > Datum: Tue, 10 Jun 2008 16:30:12 +0800
> > > > > Von: Sandy <maorriyan.santoso at gmail.com>
> > > > > An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> > > > > Betreff: Re: Terminating Events Generate Feedback After Error
> > > >
> > > > > Well..it seems the simplest one become bottle neck.
> > > > >
> > > > > I believe if the event hasn't been released it won't appear in the
> > > event
> > > > > trace.
> > > > >
> > > > > I try to re-design my workflow.
> > > > > I removed any thing from "Terminating events" tab.
> > > > > I use Fork step with 2 branches (necessary branches = 2) where one
> of
> > > > them
> > > > > is wait step.
> > > > > Inside my wait step contains my business object type as my
> container
> > > > > element
> > > > > and "ACCEPTED" in Event section.
> > > > >
> > > > > I test this from SWUE by populating appropriate object key for
> event
> > > > > "ACCEPTED".
> > > > > Instance linkage has my business object type and event "ACCEPTED"
> > with
> > > > > receiver type WORKITEM and active linkage.
> > > > > I believe nothing wrong in this section...
> > > > >
> > > > > After execution of SWUE still column Handler/Action in event trace
> > > > > contains
> > > > > SWW_WI_CREATE_VIA_EVENT_IBF,  Event put in queue and  error
> >  "Feedback
> > > > > after
> > > > > error"
> > > > >
> > > > > Any clue?
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jun 10, 2008 at 3:28 PM, Florin Wach <florin.wach at gmx.net>
> > > > wrote:
> > > > >
> > > > > > No clue.
> > > > > >
> > > > > > I would suggest to re-create the task. Also check in the
> business
> > > > > object,
> > > > > > if your event is marked as "implemented or released"
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > -------- Original-Nachricht --------
> > > > > > > Datum: Tue, 10 Jun 2008 10:53:50 +0800
> > > > > > > Von: Sandy <maorriyan.santoso at gmail.com>
> > > > > > > An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> > > > > > > Betreff: Re: Terminating Events Generate Feedback After Error
> > > > > >
> > > > > > > Hi Florin & Rick.
> > > > > > >
> > > > > > > Yes the binding on the task level (terminating tab) is there.
> > > > > > > Element _WI_OBJECT_ID and event "ACCEPTED"
> > > > > > >
> > > > > > > Binding details as per standards, &_EVT_CREATOR& -->
> &INITIATOR
> > > and
> > > > > > > &_EVT_OBJECT& --> &_WI_OBJECT_ID&
> > > > > > >
> > > > > > > Linkage will not change on error feedback. So the event
> linkage
> > > > always
> > > > > > > active.
> > > > > > >
> > > > > > > Any other clues?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > On Mon, Jun 9, 2008 at 9:59 PM, Sample, Rick <
> > > > Rick.Sample at graybar.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Check the binding details. What are the settings? Linkage
> still
> > > > show
> > > > > > > > activated? "Behavior upon feedback..."?
> > > > > > > >
> > > > > > > >
> > > > > > > > Rick Sample
> > > > > > > > SAP Business Workflow Developer
> > > > > > > > Graybar, Inc.
> > > > > > > > 11885 Lackland Dr.
> > > > > > > >
> > > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu]
> > > On
> > > > > > Behalf
> > > > > > > > Of Florin Wach
> > > > > > > > Sent: Monday, June 09, 2008 6:45 AM
> > > > > > > > To: SAP Workflow Users' Group
> > > > > > > > Subject: Re: Terminating Events Generate Feedback After
> Error
> > > > > > > >
> > > > > > > > Hello Sandy,
> > > > > > > >
> > > > > > > > in the task-definition (the one with the TS) there's a tab
> > > > > "Terminating
> > > > > > > > events". Please check that there's an entry there for
> > > _WI_OBJECT_ID
> > > > > and
> > > > > > > > event ACCEPTED. Any missing instance-linkages will be
> generated
> > > by
> > > > > the
> > > > > > > > system upon task instantiation.
> > > > > > > >
> > > > > > > > Best wishes,
> > > > > > > >   Florin
> > > > > > > >
> > > > > > > > -------- Original-Nachricht --------
> > > > > > > > > Datum: Mon, 9 Jun 2008 17:58:01 +0800
> > > > > > > > > Von: Sandy <maorriyan.santoso at gmail.com>
> > > > > > > > > An: "SAP Workflow - MIT" <sap-wug at mit.edu>
> > > > > > > > > Betreff: Terminating Events Generate Feedback After Error
> > > > > > > >
> > > > > > > > > Hi All.
> > > > > > > > > My custom workflow has asynchronous task where the
> > terminating
> > > > > events
> > > > > > > > > trigger from ABAP program and passed some data.
> > > > > > > > > This task will completed upon custom event "ACCEPTED"
> raised
> > > in
> > > > > the
> > > > > > > > system
> > > > > > > > > based on certain keyfield and continue next steps.
> > > > > > > > > Terminating events tab contains element _WI_OBJECT_ID and
> my
> > > > > custom
> > > > > > > > event
> > > > > > > > > "ACCEPTED".
> > > > > > > > >
> > > > > > > > > I though this is the only step that I need to do and of
> > course
> > > > > wait
> > > > > > > > step.
> > > > > > > > >
> > > > > > > > > However when I test this terminating event via SWUE with
> > > proper
> > > > > > object
> > > > > > > > > key,
> > > > > > > > > event trace transaction reported event *"ACCEPTED" for
> task
> > > > > > TS95000052
> > > > > > > > not
> > > > > > > > > defined as start/end event*.
> > > > > > > > >
> > > > > > > > > I check in instance linkage transaction, linkage is
> activated
> > > for
> > > > > my
> > > > > > > > > object
> > > > > > > > > type, "ACCEPTED" and receiver type "WORK ITEM".
> > > > > > > > > Event type linkages between event and my asynchronous task
> > > also
> > > > > > > > active.
> > > > > > > > >
> > > > > > > > > Will someone give me a clue, what should I do to resolve
> this
> > > > > issue?
> > > > > > > > >
> > > > > > > > > Many Thanks
> > > > > > > > _______________________________________________
> > > > > > > > SAP-WUG mailing list
> > > > > > > > SAP-WUG at mit.edu
> > > > > > > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > SAP-WUG mailing list
> > > > > > > > SAP-WUG at mit.edu
> > > > > > > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > > > > > > >
> > > > > > _______________________________________________
> > > > > > SAP-WUG mailing list
> > > > > > SAP-WUG at mit.edu
> > > > > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > > > > >
> > > > _______________________________________________
> > > > SAP-WUG mailing list
> > > > SAP-WUG at mit.edu
> > > > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > > >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >