idoc stalls at status 62

[Mark Huffman]

It isn't clear to me why you want the task to be dialog-oriented.
You can change a flag to make the task background if you want.
That will ensure that it doesn't show up in anybody's inbox, but still
won't necessarily ensure that it will execute correctly.
 
I have also seen cases where table buffering was still in action and the
workitem could not be executed so it is thrown into an inbox. By the
time the user fishes it out of course the buffering is finished and the
task can execute as per normal.
 
Gordy, Lynn L. wrote:
>
> Hi Mark,
>         Thanks for responding.  It is a a single step customer task that is
> designated as a general task.
>
> thks
> Lynn
>
> > ----------
> > From:         Mark Huffman[SMTP:m.r.huffman at worldnet.att.net]
> > Reply To:     SAP Workflow Users' Group
> > Sent:         Tuesday, August 08, 2000 5:19 PM
> > To:   SAP-WUG at MITVMA.MIT.EDU
> > Subject:      Re: idoc stalls at status 62
> >
> > Gordy,
> >
> > Sounds to me that you need to give the WUG-detectives a few more clues
> > to solve the crime.
> >
> > However, a few things spring to mind:
> >
> > 1) there is a new "Advance with Dialog" flag in 4.6 that controls
> > behavior within a multi-step workflow.
> >
> > 2) the workflow engine will send a task to the inboxes of all valid
> > agents when no single user or group of users can be determined at
> > runtime as agents. This can occur for various reasons.
> >
> > So for troubleshooting you might check the Agent Assignment sub-screen
> > and report back what is there. Also tell us who the task is assigned to
> > - is it a general task etc. Is it called from within a multistep
> > workflow or like many IDOCish tasks is it triggered standalone?
> >
> > Mark
> >
> >
> >
> > Gordy, Lynn L. wrote:
> > >
> > > Hello,
> > > We are upgrading from 3.0f to 4.6C.  Currently we have a process that
> > takes
> > > an inbound idoc and sends a text message.  In 3.0f this process goes all
> > the
> > > way to a status 53 without any manual intervention.  When testing in 4.6
> > it
> > > shows up in the inbox under the task titled 'Read IDOC and send text
> > > message'.  The idoc is in a status 62 as this point.   The process is
> > > completed once the workitem is executed. The completed process sends a
> > > message to SAPmail. The config is processing w/o ALE service, processing
> > by
> > > task.  We don't want to have to manually execute these and have not been
> > > able to figure out how to get these to process to status 53 without
> > > stopping.  Any help would be greatly appreciated.
> > >
> > > thanks
> > > Lynn Gordy
> > > Ga-Pacific
> >