SAP ArchiveLink using a custom object type

[Gregory Kowalik]

I agree with Martin, but do not to direct insert, use the function module I gave
you (ARCHIV_CONNECTION_INSERT).
 
Greg
 
 
 
 
 
Martin Maguth <martin.maguth at ixos.com> on 10/31/2000 02:20:56 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  Re: SAP ArchiveLink using a custom object type
 
 
 
brian:
 
you have basically two options to accomplish this "double link":
(1) copy and change the standard tasks AND the underlying method
(IMAGE.ASSIGN etc.) with a object subtype or something to that extent, based
on the object that the image then is linked to you can trigger a program
that tracks down the fi document and creates the 2nd link to the image ... i
would go that way ;-)
instead ...
(2) create a multistep workflow that contains the standard task (1117 or
1128 whichever scenario you use). after that task in the workflow, out in a
standard task (you will have to create a new method etc.) that will track
down the fi document key and create the link in TOA01 (or which ever
linktable is used).
 
i would go with number (2) since all you have to do is write a short method
that search table RBKP with the field awkey (not a key field !!!), tracks
down the FI document in table BKPF, finds the link table and does the
insert. create a new task with that method and create a WS that combines the
standard and the new task...
 
i hope this helps !
 
  ;-)
 
martin
 
 
-----Original Message-----
From: Brian Bennings [mailto:bennings.bj at pg.com]
Sent: Tuesday, October 31, 2000 10:00 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: SAP ArchiveLink using a custom object type
 
 
Hello Greg,
 
We are doing both early and late archiving.  The reference to the late
archive
task was just an example of one of the two changes we would need to make.
 
*** Regardless of which task is copied, how would I incorporate the FI link
without using a different method in the new task? ***
 
We have successully created both links in other workflow (methods) and batch
programs, but not using the SAP early and late archiving scenarios intiated
by
transaction OAWD.
 
We are trying to do this in SAP 4.5b.
 
The link between the FI and LIV document can be found in the AWKEY field of
the
BKPF record for the FI document.
 
Thanks,
Brian
 
 
 
 
 Internet Mail Message
 Received from host: cherry.ease.lsoft.com
 [209.119.0.109]
 
 
 
 
From: Gregory Kowalik <gkowalik at ashland.com>@MITVMA.MIT.EDU> on 10/31/2000
08:30
      AM
 
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: Brian Bennings-BJ/PGI)
Subject:  Re: SAP ArchiveLink using a custom object type
 
 
I do not understand why you copied TS30001117 and created a new object.
To me it seems like you are still doing the early archiving, you just want
to
add another link to the FI document. Is that correct?
What I would do (if I understand what you trying to accomplish correctly), I
would copy TS30001128 and add linking to the FI document.
You can accomplish that by calling function module ARCHIV_CONNECTION_INSERT
or
ARCHIV_WORKFLOW_COMMIT in 3* releases (seems from the tasks you're using you
are
in rel. 4*).
The problem will be to get the FI document number from LIV posting. Can you
get
that document number?
Let me know if it helped any.
 
Greg
 
 
 
 
 
 
 
 
 
Brian Bennings <bennings.bj at pg.com> on 10/30/2000 03:22:50 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  SAP ArchiveLink using a custom object type
 
 
 
Good afternoon,
 
We are using SAP ArchiveLink to link Accounts Payable invoice images to the
posted SAP documents.  The SAP standard tasks for early and late archiving
(TS30001128 and TS30001117) use methods (IMAGEASSIGNEARLY and
IMAGEASSIGNLATE)
within the business object IMAGE.
 
Because our company uses LIV (Logistics Invoice Verification), the A/P
Processor
posts an MM/LIV document from the invoice image while SAP generates the
associated FI document from the LIV posting.
 
ArchiveLink links the invoice image to the posted MM/LIV document.  However,
we
would like to have it automatically link the image to the MM/LIV document
AND
the associated FI document.
 
To do so for late archiving, we copied TS30001117 to a new task and copied
the
IMAGEASSIGNLATE to a new method within a Z business object.  We then
modified
the ABAP in the new method so that links to both documents would be created.
 
The problem is that when we attempted to link the new task to the archive
document type using transaction SOA0, an error message was displayed
indicating
that the task "is not suitable for SAP ArchiveLink" (message number OW 045).
The reason it gave was that the new task "does not have any import
parameters
with object type IMAGE."
 
It appears that ArchiveLink does not like the fact that we created a new
method
in a Z business object.
 
Does anyone know what we can do to achieve our desired results?
 
Thanks,
Brian Bennings
 
p.s. To those of you who attended the ASUG meeting in Tampa last week... It
is
nice to finally put faces to some of the names for those of you who have
contributed to the email group over the past few months.