workflow task not started

[Kjetil Kilhavn]

I am not sure about version 4.6, but in version 3.1 the menu path (>>> means you
go to a new menu) shown below will take you to a window where you can specify
tasks to be started when error situations other than InputErrorOccured arise.
Technical errors such as missing partner profiles etc. is one example of such
errors (applies to both inbound and outbound). You will find the 8068 task
there, along with some others, and can specify your own task instead.
Tools -> Administration >>> Administration -> Process technology >>> IDoc ->
IDoc basis >>> Control -> System process code
 
After writing all this I realised that you actually specificially said that the
IDocs are in status 51, so this is not a matter of the type of error that
occurs. The only thing I then can think of is that you are experiencing these
problems on an IDoc type which has been developed or extended internally. If
that is the case, check that your customisation is complete for the IDoc type.
We had a problem like the one you describe, and it turned out that for an IDoc
type (or perhaps message type) we had not specified the event that should be
created when application posting failed. Unfortunately I have (after trying for
an hour now, not been able to find out where this customisation is done).
--
KjetilK
 
 
 
From:  "Svanikier, Helena" <helena.svanikier at sap.com>@MITVMA.MIT.EDU> on
       28.09.2000 08:20
 
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:     (bcc: Kjetil Kilhavn)
Subject:  Re: workflow task not started
 
Hello Lynn
 
I know this might sound a stupid question, but have you defined and
activated the event linkage for the event 'inputerroroccured' within your
new task ?
I checked one of our 4.6c systems to see which task you had copied, but
couldn't find any Task 8086. So I thought maybe you copied the task 8068,
which is launched directly by the ALE-Application, without event. So you
wouldn't have any event linkage to copy.
 
Helena Svanikier
SAP (Schweiz) AG
 
-----Original Message-----
From: Gordy, Lynn L. [mailto:LLGORDY at GAPAC.com]
Sent: Dienstag, 26. September 2000 20:06
To: SAP-WUG at MITVMA.MIT.EDU
Subject: workflow task not started
 
 
We are in the processes of upgrading from 3.0f to 4.6c.  For our inbound
orders we have a custom single step task cloned from the SAP task 8086.
Intermittenly when the idoc encounters an application error (status 51) it
does not show up in the inbox.  When I look for the workitem it does not
exist anywhere.  If I run the task manually (SWUS) then it shows up in the
inbox.   Any ideas?
 
-------------------------------------------------------------------
Statoil: The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete this
message.
Thank you.