Update of TOA01 for ArchiveLink

[Former Member]

Hello,

We are changing an implementation of ArchiveLink using 'Early' archiving to 'Late' achiving. This has caused a change to the workflow.

In the new process, the implementation of the SAP RFC interface for archiving is called with an IDOC number. After archiving the file/document we then want to update SAP's TOA01 table to link the new ID created by the archive with the IDOC ID.

What is the simplest way to get this data updated in SAP? We're not sure of the process to call back into SAP. If we write an ABAP procedure, how can it be called from 'outside' SAP? Is there a reference for how to programatically update a row in an SAP table?

Thanks

[Former Member]

Hi Dick,

I haven't undestood your question, yet. You've got an image that you want to store via CMS in your archive system. So you get a tuple (ARC_DOC_ID, ARCHIV_ID). For this tuple, you've got a corresponding IDOC (what is the Business object?) which you want to link with this document. For this, you can use ARCHIV_CONNECTION_INSERT, for example? If you need to call it from outside create a RFC wrapper.

Best regards

Torsten

[Former Member]

Hi,

Yes. We have available the ARCHIV_ID and ARC_DOC_ID for the document archived in the repository.

On the SAP side, either an SAP Document Id OR IDOC ID is available.

The IDoc types are FI IDOC and MM IDOC RTP invoices.

What are the columns of the TOA01 table -- do they distinguish the IDOC type?

Can yuo please reference an example where ARCHIV_CONNECTION_INSERT is used?

Is there an example you can reference for creating an RFC wrapper?

Thanks

[Former Member]

Hi Dick,

I'm not an expert on IDOC. Generally speaking, an archiveLink image can be linked to any BOR (Business object repository) instance.

If your IDOC types are represented by different BOR types (transaction SWO1) then they can be attached to those. The archiveLink link table means the following:

SAP_OBJECT: Business object type (TA SWO1)

OBJECT_ID: business object ID (instance of Business object)

ARCHIV_ID: content repository ID

ARC_DOC_ID: archive doc ID

AR_OBJECT: archiveLink document type (OAC2)

AR_DATE: archiving date

RESERVE: document class (PDF,...)

What I mean with a wrapper is: Write a (RFC) function module that calls the ARCHIV_CONNECTION_INSERT in the way you need for your specific application.

Best regards

Torsten