infinite loop of TS7869 (ImageAssign)

[Hassine, Felix]

Yan,
 
A lady just told me about your response on the phone.
Actually, it is true that in 3.1H you do have the problem of the non
availability of the wizard.
 
So.. let me propose you a trick.
 
Connect your workflow document type with the standard task TS7869.
This standard task actually creates the link in table TOA01 with a FM in the
check FM of the event linkage (you see this in SWE2, go to IMAGE.ASSIGN).
Then the trick consist in copying the ARCHIV_WORKFLOW_ASSIGN FM into your
own FM, let's say ZARCHIV_WORKFLOW_ASSIGN, and
then just add at the end of it the beginning of your own workflow (using the
API SWW_WI_CREATE_SIMPLE) which will start the remaining part of your
workflow. The drawback of this solution is that it will require adjusting
the FM for every new document type scenario. Plus you will need to review it
when you upgrade to version > 4.
 
Regards, I hope this helps,
 
        Felix
 
 
> -----Original Message-----
>> From: Liu, Yan Y SSI [SMTP:YD186300 at MSXSSC.SHELL.COM]
> Sent: Friday, January 28, 2000 4:13 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: infinite loop of TS7869 (ImageAssign)
>
> Felix,
>
> Thanks for the information.  It's a big help.  However, I am in version
> 3.1h
> which doesn't have the WF wizard.  How do I get a copy of the WF replacing
> TS7869 for 3.1h?  ... contact SAP?
>
> Regards,  Yan
>
> > -----Original Message-----
> > From: Hassine, Felix [SMTP:Hassine.Felix at PMINTL.CH]
> > Sent: Thursday, January 27, 2000 8:48 PM
> > To:   SAP-WUG at MITVMA.MIT.EDU
> > Subject:      Re: infinite loop of TS7869 (ImageAssign)
> >
> > Yan,
> >
> >         I have had similar problems a few months ago. After a strong
> > debugging, I havce realized that the terminating event for the TS7869 is
> > not
> > receiving the proper IMAGE key, on purpose. The TS7869 is async, and
> > requires the key of the image to terminate, but instead it receives the
> > key
> > of IMAGE + an append of the document CLASS. After opening a OSS note,
> > someone in Walldorf - on the phone - said to me that TS7869 is not
> > supposed
> > to be used inside a WF. For this, they have created a wizard which
> > generates
> > you a full WF replacing the functionality of TS7869.
> >
> > This is the one you should use, as a SubFlow in your workflow. I did,
> and
> > it
> > worked. I hope this helps.
> >
> > Regards,
> >
> >         Felix
> >
> > > -----Original Message-----
> > > From: Liu, Yan Y SSI [SMTP:YD186300 at MSXSSC.SHELL.COM]
> > > Sent: Thursday, January 27, 2000 8:40 PM
> > > To:   SAP-WUG at MITVMA.MIT.EDU
> > > Subject:      infinite loop of TS7869 (ImageAssign)
> > >
> > > Hello,
> > >
> > > This is a question related to both Optical Archiving and Workflow.
> > >
> > > I am encountering an infinite loop of TS7869 after calling it from my
> > WF.
> > > After the executing TS7869, the R/3 document was posted and an entry
> was
> > > made to the link table.  However, a new workitem (TS7869) appears in
> > > users'
> > > inbox.  The task carried all the parameters assigned via task binding
> > > within
> > > the WF.
> > >
> > > Any Advice?  This only happens when we link WF to a global document
> type
> > > and
> > > call TS7869 within the WF....  no problem if we link TS7869 directly
> to
> > a
> > > global document type.
> > >
> > > Here are the task (TS7869) binding with WF:
> > >
> > > ArchiveLink image       <==     &IMAGE&
> > >
> > > SAP ArchiveLink         <==     &IMAGE.IMAGELINKARCHIVEID&
> > >
> > > Archive doc. ID         <==     &IMAGE.ARCHIVEDOCID&
> > >
> > > Document type           <==     ZIAPINER02
> > > Description             <==     Invoice Processing
> > > Document class          <==     FAX
> > > _WI_Object_Id           <==     &IMAGE&
> > >
> > >
> > > Here is the WF Document Type(ZIAPINER02) definition: (SOA0)
> > >
> > > Document type   ZIAPINER02
> > > Description        A/P Services Maintenance Invoices - Park
> > > Process type      NCI_INPUT
> > > Object type        BKPF
> > > Method              CREATE
> > > Task                  nothing here
> > >
> > > We have applied following OSS Notes:
> > >         85778  TS7869: no link after document type changed
> > >       94502  Two work items after document type changed
> > >
> > > But the problem remains.
> > >
> > > Thanks, Yan