Document Imaging and the SAP Content Server 101

[ Document Imaging and the
SAP Content Server 101
JOHN WALLS – Verbella CMG, LLC

[ Speaker Background
 John Walls
 Working with SAP since April 1996 – 16 years
 Document Imaging Solutions April 1999 - 13 years
 Working History:
 IXOS / OpenText
 Dolphin-IT
 Current Position: President of Verbella CMG, LLC
 Document Management solution provider focusing on OpenText
Solutions, such as VIM, and the SAP Content Server with Kofax
Capture.

Real Experience. Real Advantage. 2

[ Learning Points
 A basic understanding of ArchiveLink functionality and what the business
can do with it.

 An understanding of what the SAP Content Server can do and how it can
be used with ArchiveLink and document Imaging.

 An understanding of the Generic Object Services and how it is integrated
into SAP software.

Real Experience. Real Advantage.

[ Today’s Agenda

 Why we image, and the cost involved in not imaging
 Background and typical configuration
 SAP Content Server
 Archiving Scenarios
 Printlist and Outgoing documents
 Generic Object Services
 ROI, Best Practices, and Common Mistakes around an imaging
project.


[ Advantages to a Paperless Office
 Multiple users can access the same documents at the same
time.
 They are available to everyone anywhere any time
 Lower costs
 No floor storage costs, No locked Rooms, No lost documents
 No personnel costs involved in filing and retrieving documents
 Electronic documents can be cross-referenced when they’re
filed
 Not limited to two-dimensional filing
 They can be made available to the web, portal, or emails


[ Advantages to a Paperless Office (cont.)
 Disaster recovery
 Documents are automatically backed up (best practice —
different locations)
 Electronic documents can be used in SAP Workflows
 Electronic documents are easier to produce for audits
 They automatically adhere to system-configured retention
policies
 They can be massed produced
 They can be tracked as to ―Who reviewed what document‖
 You can easily identify what documents you are missing.


[ Common Terms
 ArchiveLink
 A service integrated in the SAP Web Application Server to link
archived documents with the business object entered in the SAP
system
 Knowledge Provider (KPro)
 A cross-application and media-neutral information technology
infrastructure within the SAP R/3 Basis (SAP middleware)
 Provides the general infrastructure for storing and administrating
documents in the SAP Content Server
 Content Server
 Server at the core of SAP’s document storage and
management concept
 Provides the technical infrastructure for all document-centric
applications


[ Common Terms (cont.)
Content Repository (means logical archive)
 A way to logically manage content, usually by retention period or by storage
media
Document types
 Backbone of ArchiveLink customizing
 Are 10 characters in length
 Have several functions:
 Used to describe the actual image
 Security can be base on document type
 Act as pointers to different logical archives
 Workitems are routed to the appropriate processor via document types in the early
archiving scenario
 In some cases, it specifies the SAP t-code to launch


[ The End Results — Displaying a Document from FB03


[ Go to the Generic Object Services — Attachment List


[ Attachment List Shows All the Available Documents


[ How does SAP know what document to display?


[ SAP Process that could have documentation
Quality
Inquiry
Inspection
Quotation
Purchase
Sales Service
Order
Contracts Notification

Sales Production
Orders Good
Orders
Receipt
Vendor
Picking
Master
Customer Packing
Shipment Group
Master Deliveries
Deliveries
Material
Master
Goods
Asset
Issue
Master
Invoice
Equipment
Master Accounting


[ Typical Configuration – Third Party

HP Jukebox
Content Server
OnBase, IXOS, IBM,
Documentum, etc.
SAP R/3

CAS Storage
Server Centera

Clients

Scanning Processing Retrieval
Clients


[ SAP Content Server –

SAP Content Server SAP Cache
HTTP HTTP
File system or database Server
(No optical Media support)

HTTP
SAP R/3

HTTP

No Scanner Interface for
SAP Content Server
Third party document
capture vendors like Kofax Retrieval of documents through the
would be necessary. SAP GUI using the ECL Viewer


[ SAP Content Server – What is it?
 Software for storing structured data (ADK files) and
unstructured documents in repositories.
 Product of SAP Web Application Server
 Administration from within SAP, Using the following T-codes
CSADMIN, & OACO
 Communication through the ArchiveLink HTTP protocol and
K-Pro.
 Multi-OS support including
 Windows
 Various Unix systems (New as of Content Server 6.30)
 Does not support optical Media no direct scanning interface
 Can be installed on VM image (preferred), support 64 bit OS
Windows Server 2008.


[ Create the Content Repository


[ Content Server Administration Overview


[ How Do We Get Documents Archived?
Two most common ways to get information to the archive
server:
 Paper documents
 Can be scanned or faxed into the scan client
 The scan client interfaces with SAP, and is used to archive the
documents into SAP
 Electronic documents
 Such as emails and desktop documents
 Can be kept in their native format and archived from the desktop
without using the scan client
 They can also be programmatically uploaded via ABAP programs
or other external programs


[ Three Most Common SAP Archiving Scenarios
Early archiving
 Uses workflow to route images to processors
 Once processed the image is linked to the newly created SAP
R/3 document
Late archiving
 Uses indexing fields to link image to existing document
Late archiving with barcode
 Uses barcodes to link image to previously created
SAP R/3 document


[ Old, New, and Newest — Scenario Naming Schemes

SAP R/3 4.6C SAP R/3 SAP R/3
and Above 4.5 - 4.6B 4.0 and Older
Early archiving
Storing for subsequent entry Store for entry later
with workflow
Store for
Storing for subsequent
assignment at a N/A
assignment
later time
Store and enter (storing
Store and enter Simultaneous archiving
and entering)

Store and assign (storing
Store and assign N/A
and assigning)

Assign then store (assigning
Assign and store Late archiving
then storing)


[

Early Archiving


[ Early Archiving Scenario

Document
SAP
Image

`

Remote Location 1 Remote Location 2 Vendor 1

A/P Position 1

Right Fax Server
Workflow
SAP Server Workitem Created
FB60/MIRO

Network
Directory A/P Position 2

SAP Content Server
`
A/P Position 3

Kofax Ascent
Capture and
Release Script to
**Optional Back up
SAP
Scenario** Barcode
added to Document or
back up document


[ Scanning with Kofax – Early Archiving Scenario


[ Kofax Ascent Capture


[ Automatic Release to SAP

Released to SAP


[ SAP User Workflow Inbox


[ Process Workitem

POST


[ Kofax to SAP Connection – Remote RFC Call(s)


[ Early Archiving Summary
Advantages
 Distribute work to others and eliminates paper
 Allows for ad hoc approval process
 Standard reporting on end-user processing
Drawbacks
 Most complicated of the standard supplied archive scenarios
 Processing faster with dual monitors
 Uses SAP’s workflow
 Workflow needs to be initialized and
 An organization structure may have to be used


[

Late Archiving


[ Late Archiving with 3rd-Party Solutions


[ Late Archiving – Content Server


[ Late Archiving – Content Server (cont.)


[

Barcode


[ External 3rd Party REQUIRED for Barcode Archiving
Requires an External Scanning Client
 If 3rd Party Content Management solutions are being used, their Scan
Clients will be able to handle barcode archiving, If they are ArchiveLink
Certified.
 Example of this include
OnBase, IXOS/OpenText, IBM/FileNet, Documentum, etc.*

 If the SAP Content Server is being used.
 Since there is no Scanning interface supplied a stand alone imaging software
application that has an Archivelink Certified interface is required.
 Example of this include
Kofax Ascent Capture with AR4ERP**
Kxscent Capture**

* Partial List
** There may be other vendors, unknown to speaker. Please do your own research


[ Barcode Scenario- Explained

1 Barcode Number and
SAP Key fields
Barcode is
IIIIIIIII entered With Added to
SAP transaction BDS_BAR_IN Table

Matching barcode
entries are deleted and
2 an entry in the Link
Table TOA01 is made

3
Image is Stored
on Content
Server 4 Doc and ID and Bar
code are sent to
SAP BDS_BAR_EX
Table

[ Enter Barcode

POST


[ Manual Bar Code Entry


[ Processing Solution Steps

Images

SAP
Scan Recognition Release
Validate Content
Server

Barcode is Barcode and
read image are
released
to SAP


[ Classification and Extraction of Index Fields

Recognition


[ Automatic Release to SAP — AR4ERP

Released to SAP


[ Late Archiving with Barcode Summary
Advantages
 Does not change the existing Business process
 Requires very little training
 Scanning is much more efficient
 No indexing
 No scanning separator sheets
 Identifies documents that have not been scanned
 Multiple SAP objects can be linked to a scanned document
 Individual document indexing/categorizing is eliminated
Drawback
 Need to manage and print/buy barcodes


[ Outgoing Documents – Customer Invoices
 Snap shot in time.
 Saves on Processing time.
 Pull up the exact copy of the invoice that was sent to the
customer.
 Used heavily in Data Archiving .
 (Retrieval Strategy)
 It is very difficult to re-print outgoing documents if they have
been archived.
 Once stored, they can be accessed through a customer self-
service portal.


[ GOS – Attachment List


[ Printlists - Reports
 Snap shot in time
 Saves on Processing time, the report is run once and archived.
Printlist report is viewed instead of online version.
 Saves paper and toner
 Used as a report distribution tool
 Used heavily as a Data Archiving Retrieval Strategy.
 Can be used with Hyperlinks- Links to other archived
documents


[ Printlist with HyperLinks


[ Results of the HyperLink


[ Overview
 Create Attachment
 Create Note & Private Notes
 Create External Document (URL)
 Store Business Documents
 Enter Barcode
 Attachment List
 Send
 Relationships
 Workflow
 Subscribe To Object


[ Generic Object Services (GOS)
What is it?

The generic Object Services offer functions that are available in
various SAP applications. The functions are always called and
used in the same way in order to keep the learning burden for
end users low.


[ Create Attachment


[ Displaying an Attachment


[ Create Notes


[ Create Notes - Display


[ Create Private Notes


[ Storing a Business Document


[ Subscription of an object – Delivery Note
Deleted


[ SAP E-mail notification


[ Today’s Agenda

 Why we image, and the cost involved in not imaging
 Background and typical configuration
 SAP Content Server
 Archiving Scenarios
 Printlist and Outgoing documents
 Generic Object Services
 ROI, Best Practices, and Common Mistakes around an
imaging project.


[ Return on Investment
 Companies spend $20 in labor to file a document, $120 in
labor to find a misfiled document, and $220 in labor to
reproduce a lost document (does not include any legal
penalties)
 The average document gets copied 19 times.
 Professionals spend 5-15% of their time reading information,
but up to 50% looking for it.
 7.5% of all documents are lost (1 in 20) 3% of the remainder
get misfiled
 90% of corporate information resides on paper
 There are over 4 trillion paper documents in the United States
alone – growing at a rate of 22% per year .
Source: Coopers and Lybrand/Lawrence Livermore


[ Best Practices
 Single POC for producing and monitoring barcodes
 Choose the correct scanner for the volume and
scanning scenario
 Stay with the same brand of scanner
 Use USB 2.0 over SCSI and ISIS drivers over TWAIN
 Know your retention periods,
 Inquire about document security, before Configuration
 Archive outgoing documents whenever possible
 Create a test Content Repository, or Content Server


[
Virtual Re-Scan (VRS) Eliminates
Rescanning

Low Contrast
Logo

Dot Matrix
Text

Highlighter

Carbon Copy
Handprint

Coffee Cup
Stain

Shaded
background


Kofax VirtualReScan™ (VRS)
[

Image File Size = 213 KB


[ Common Mistakes
 Not Monitoring the Open Barcode tables
 Too many desktop scanners in one location
 Multiple makes and models of Scanners
 Too many document types and inconsistency in naming
 Too many individuals with ―Delete‖ access
 Allowing users to ―Create Attachments‖ through the Generic
Object Services using K-Pro and storing the attachments on
the SAP database


[ SOFFCONT1 AND CRMORDERCONT TABLES


[ A Word About Using Attachments
 Technically speaking, notes, PC attachments, and URLs are
treated as SAP office documents
 They result in corresponding entries in the SOOD and
SOFM tables
 Contents of the attachments are stored in the SOC3 table
 Contents of the PC attachments are written to the
SOFFCONT1 table
 See Note 530792 for more information
 See Note 389366 if you need to move documents from the
database to an external content server


[ Key Points to Take Home
 Electronic images are easier and cheaper to manage
 Document imaging can be implemented quickly and cost-
effectively using standard SAP scenarios
 SAP Content Server can be used as a reliable document
management system
 Third-party content servers have some features that provide
advantages over the SAP Content Server


[ Reference Slide
 For More Information Please Contact:
 John Walls – Verbella CMG, LLC
 484-888-2199
 John.walls@verbellacmg.com
 http://www.verbellacmg.com
 http://help.sap.com
 http://www.kofax.com


[
 Thank you for participating.
Please remember to complete and return your
evaluation form following this session.
For ongoing education on this area of focus, visit the
Year-Round Community page at www.asug.com/yrc
]
JOHN WALLS
VERBELLA CMG, LLC
[ SESSION CODE:
0713

John.Walls@VerbellaCMG.com


Document Imaging and the SAP Content Server 101

Recommended

More Related Content

What's hot (20)

Similar to Document Imaging and the SAP Content Server 101 (20)

Recently uploaded (20)

Document Imaging and the SAP Content Server 101