Configuring ArchiveLink for Scanned Documents
Configuring ArchiveLink for
Scanned Documents
Authro
The SAP Records Management example in the article
“Consolidate and Integrate All of Your SAP and
Non-SAP Documents, Transactions, Workflows,
and Data with SAP Records Management” (SAP
Professional Journal, January/February 2005) incor-
porates scanned invoices that are stored in TIFF for-
mat in an external storage system. In the example,
the storage system is connected to the SAP R/3 system
via SAP ArchiveLink. If you don’t have an existing
archiving system or use ArchiveLink, you can still
get the example to work by following these simple
configuration steps:
1. Define a content repository in ArchiveLink.
Scanned originals can be physically stored in an
external storage system like a certified third-
party archiving system or in the Content Server
included as a part of SAP Web AS. See SAP Note
595563 for details on how to set this up.
2. Create a document type for ArchiveLink. From
within the SAP Implementation Guide (transac-
tion SPRO), choose SAP Web Application Server
→ Basis Services → ArchiveLink → Basic
Customizing. Double-click on the IMG activity
Edit Document Types, create a new document
type called ZFIINVOICE, and assign the docu-
ment type the name Invoice Demo and the docu-
ment class TIF.
3. Link document type ZFIINVOICE to a busi-
ness object and the defined content repository.
For site licenses and volume subscriptions, call 1-781-751-8799.
Following the same IMG path outlined in step 2,
double-click on the IMG activity Edit Links.
Assign document type ZFIINVOICE to a
business object — e.g., business object BKPF for
documents in FI. Next, set the link status to
active. Finally, enter the content repository
you defined in step 1 as the storage system,
and then choose table TOA01 as the link table.
Table TOA01 is the default that should be used
unless you need to divide a large amount of
document links among several tables. Save
your settings.
4. Activate the TIFF display. To be able to display
TIFF documents, call transaction OAG4 and
activate the ECL Control. If you do not have a
complete Windows GUI installed on your PC —
this might be the case if your system administrator
installed only obligatory GUI components — you
need to install the full version before you can test
this configuration example. The Windows GUI
installation wizard will detect any missing compo-
nents and offer to install a complete version.
Now you have a technically working repository
that you can use to store documents via ArchiveLink.
You next need to maintain the element type for
ArchiveLink documents, as described in the article.
You can then add ArchiveLink documents simply by
uploading them into the system, and view them
in your SAP Records Management system (see
Figure 1 on the next page).
1
SAP Professional Journal January/February 2005

Figure 1 Displaying a Scanned ArchiveLink Document in SAP Records Management

2 www.SAPpro.com ©2005 SAP Professional Journal. Reproduction prohibited. All rights reserved.