SAP Workflow & ArchiveLink Tables

[phillips, tim]

Gregory Kowalik wrote:
 
You can only use instance independed methods, CREATEINVOICE is not one of
them.
Why don't you check what transaction is called via CREATE in your release
(check
the code of that method).
This will tell you if it is the right method to call your transaction.
I'm on 46B and in this release MIRO is called which is an enjoy LIV
transaction.
If it's not available, just create a custom method to call M1RM.
___________________________
 
For object type BUS2081, CREATE does not exist - CREATEINVOICE does, and
calls transaction MR1M.
 
Why the latter should not be a possible entry in transaction SOA0, I do not
know - CREATE is available in the drop-down, however, even though it does
not exist for the object type!!!!! - I believe this to be the reason why I
could not access the transaction through SAP workflow.
 
Interestingly, if you maintain a document type through the WF DocType
Wizard, CREATEINVOICE is available, but the name is too long for the 10
character field.
 
So, I have created a new method for BUS2081 called CREATEINV (a copy of
CREATEINVOICE), and selected this as my method using the wizard.
 
I can now branch to the desired transaction - this must surely be a bug in
the SAP standard!!!!!!
 
However, even with using object BUS2081 (which creates the correct work
item, branches to the correct transaction etc), the link table is STILL not
updated.
 
I really am at a loss!!!!!
___________________________
 
Greg:
 
If you have TS30001128 available please use it in SOA0.
You will also have to enter BUS2081 and your doc. type in OAC3 (links to
external storage)
___________________________
 
TS3000128 is not available in my release.  I have, however, created the link
in OAC3 as follow:
 
BUS2081   ZMMINVPAP (my document type)   X    I3    TOA01       0
 
___________________________
 
Greg:
 
Seems like in your release the link is created for the MM document only. If
you
need to link to FI as well, you will need to create a workflow and in
subsequent
steps get the FI doc number and link the image to it yourself.
 
___________________________
 
A link to the MM document is sufficient.
 
I do, however, need to write an ABAP report querying table TOA01 - this will
require linking the MM document to its FI counterpart.  However, I have
noticed the field AWKEY in BKPF is a concatenation of the key fields of the
MM document - this should provide the link I require for reporting purposes.
 
Best Regards,
 
Tim (who is continuing to appreciate your help on this matter :-))