‎2013 May 29 8:57 PM
We have developed a process that combines
At the end of our process, we render a smartform image of the completed form, and we print it to a content repository, using a custom BOR object, ZBOnn.
Is there a way to archive directly to an SE24 type object, or must we continue to create analogous SWO1 objects for this?
Thanks… …Mike
‎2013 Jun 07 3:55 PM
Hello Mike,
ArchiveLink stores the connection entries to one of the ArchiveLink connection tables. (These tables are listed in the table TOACO.)
So if you would like to store a document via ArchiveLink you need a business object, because ArchiveLink connects an instance of a business object (identified by it's type and concatenation of keyfields) and a business document (identified by the name of the content repository and the document ID).
Best regards,
Janos
http://help.sap.com/saphelp_nw73/helpdata/en/4c/e65a717e173ec6e10000000a42189b/frameset.htm
The business object and stored document must be uniquely identified for the link. The business object identification consists of:
The stored document identification consists of:
The diagram below illustrates all the link entry data in the link entry table:

‎2013 May 30 12:28 AM
Hi Mike,
Pretty sure you need the BOR for AL. This is exactly the same as I did last year.
Cheers,
Custodio
‎2013 Jun 07 3:55 PM
Hello Mike,
ArchiveLink stores the connection entries to one of the ArchiveLink connection tables. (These tables are listed in the table TOACO.)
So if you would like to store a document via ArchiveLink you need a business object, because ArchiveLink connects an instance of a business object (identified by it's type and concatenation of keyfields) and a business document (identified by the name of the content repository and the document ID).
Best regards,
Janos
http://help.sap.com/saphelp_nw73/helpdata/en/4c/e65a717e173ec6e10000000a42189b/frameset.htm
The business object and stored document must be uniquely identified for the link. The business object identification consists of:
The stored document identification consists of:
The diagram below illustrates all the link entry data in the link entry table:
