SapArchivelink - panagon

Van der Burg, Jeroen JA SITI-ITPSEE Jeroen.J.vanderBurg at si.shell.com
Wed Jun 19 07:49:14 EDT 2002


Sosthene,
 
Not sure what exactly is your question. Easiest solution (if I =
understood
what your are asking): directly look at the contents of the linkage =
table
you are using through SE16 and check if a new link is created after the
document assignment was completed (whatever archiving scenario you are
using). You can enter the document number from Filenet (shown to you =
after
the document was indexed; or through the Panagon maintenance tools) for =
the
ARC_DOC_ID field, the SAP document number, object and object key can =
then be
seen in their relevant fields.=20
 
...but the easiest way to check if your assignment was succesful it =
just try
to retrieve the assigned document from the object it was assigned to.
 
 
Regards,
 
 
 
Jeroen
 
-----Original Message-----
From: ASSY, SOSTHENE [mailto:S.ASSY at AFDB.ORG]
Sent: 19 June 2002 12:30
To: SAP-WUG at MITVMA.MIT.EDU
Subject: SapArchivelink - panagon
 
 
HI workflow gurus,
 
I'm working  on SapArchiveLink and PANAGON using one method to link my
document. I need to check if the document from PANAGON is assigned.
Only the opened document is assigned.
For this reason, I need to get the image key (Image number and storage
location) to check if the link is made in one of the link table TOA01 =
or
TOA02.
=20
Any Idea ?
 
Thank you for your suggestions
 
 
This e-mail and any attachment sent with it are confidential and =
intended
solely for the use of the individual to whom it is addressed. If you =
have
received this e-mail by error please delete it immediately. No =
reference
should be made of the information contained in this e-mail.  The views =
or
opinions expressed in this message, unless otherwise clearly indicated, =
are
solely those of its author and do not necessarily represent those of =
the
ADB.  Unauthorized publication, use, dissemination, forwarding, =
printing or
copying of this e-mail and its associated attachments is strictly
prohibited.  ADB believes but does not warrant that this e-mail and any
attachments are virus-free.  You must therefore take full =
responsibility for
checking for viruses therein. ADB disclaims any responsibility and =
liability
arising from your unauthorized use of the contents of this e-mail or =
your
failing to ensure that it is virus-free. =20
Ce message =E9lectronique et tous les documents attach=E9s qu'il =
contient sont
confidentiels et destin=E9s exclusivement =E0 la personne =E0 laquelle =
ils ont =E9t=E9
envoy=E9s.  Si vous avez re=E7u ce message par erreur, veuillez le =
d=E9truire
imm=E9diatement; vous voudrez  bien =E9galement vous abstenir de toute =
r=E9f=E9rence
aux informations qui y figurent.  Sauf  mention  expresse, les id=E9es =
et
opinions pr=E9sent=E9es dans ce message sont celles de son auteur, et =
n'engagent
pas la BAD.  La  publication, l'usage,  la distribution, l'impression =
ou la
copie non autoris=E9e de ce message et des fichiers attach=E9s qu'il =
contient
sont strictement interdits.  La BAD a pris toute pr=E9caution pour =
=E9viter la
pr=E9sence de virus, mais nous ne pouvons vous garantir l'absence de =
virus.
Vous devez donc prendre toute disposition utile pour la v=E9rification =
de
l'absence de virus. La  BAD d=E9gage toute responsabilit=E9 en cas de =
probl=E8me
pos=E9 par des virus.=20
 


More information about the SAP-WUG mailing list