topic ABAP Objects, BOR Objects, and ArchiveLink, in Application Development and Automation Discussions

ABAP Objects, BOR Objects, and ArchiveLink,

mike_mcinerney — Wed, 29 May 2013 19:57:54 GMT

We have developed a process that combines

A web-dynpro based interactive form delivered/routed through the universal worklist
A workflow based approval cycle with subsequent business processing based on the form's content
And an abap object (ZCLnn) sitting between them that encapsulates the underlying form data, and associated communication between the UI and the WF

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

Re: ABAP Objects, BOR Objects, and ArchiveLink,

custodio_deoliveira — Wed, 29 May 2013 23:28:44 GMT

Hi Mike,

Pretty sure you need the BOR for AL. This is exactly the same as I did last year.

Cheers,

Custodio

Re: ABAP Objects, BOR Objects, and ArchiveLink,

janosdezsi — Fri, 07 Jun 2013 14:55:04 GMT

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:

Client
Business Object Type (object type for short)
Business object ID (Object ID for short)

The stored document identification consists of:

Content Repository ID
Document ID

The diagram below illustrates all the link entry data in the link entry table: