Opentext Documentum Content Services For Sap: Configuration Guide

OpenText ™ Documentum ®
Content Services for SAP ®

Version 7.3
Configuration Guide
Legal Notice
This documentation has been created for software version 7.3.

It is also valid for subsequent software versions as long as no new document version is published.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
For more information, visit https://www.opentext.com
Copyright 2017 Open Text. All Rights Reserved.
Trademarks owned by Open Text.
Adobe and Adobe PDF Library are trademarks or registered trademarks of Adobe Systems Inc. in
the U.S. and other countries.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this
publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no
warranty whether expressed or implied, for the accuracy of this publication.
Table of Contents
Preface ................................................................................................................................. 7
Chapter 1 Introducing Content Services for SAP ......................................................... 11

Overview ......................................................................................................... 11
CS SAP architecture .......................................................................................... 12
Supported SAP document formats ..................................................................... 14
SAP and CS SAP terms ..................................................................................... 14
Chapter 2 Configuring the ArchiveLink Interface for CS SAP ...................................... 17

Overview ......................................................................................................... 17
oac0—Defining a logical ArchiveID ................................................................... 17
oag1—Configuring basic settings ....................................................................... 18
oanr—Configuring number ranges .................................................................... 18
oaqi—Creating queues ...................................................................................... 19
oaat—Scheduling jobs ....................................................................................... 19
spad—Configuring optical archives as output devices......................................... 20
Configuring an optical archive as the output device ........................................ 20
Configuring an optical archive as output device for a Documentum
installation ................................................................................................... 21
sm50—Verifying spool processes ....................................................................... 22
sole—Maintaining OLE applications .................................................................. 22
Configuring CS SAP Capture ........................................................................ 22
Configuring CS SAP View ............................................................................. 23
Verifying OLE application configuration ........................................................ 24
oaa4—Maintaining applications and configuring communications
protocol ........................................................................................................... 24
Special protocols........................................................................................... 26
Protocol for anonymous login ................................................................... 27
Protocol for anonymous capture login ....................................................... 27
Protocol for the SAP Inline Print List viewer ............................................... 28
Protocol for HTTP display ......................................................................... 29
Chapter 3 Customizing SAP Document Classes .......................................................... 31

oac0—Configuring content repositories.............................................................. 31
oac2—Defining document types ........................................................................ 33
oac3—Defining links ......................................................................................... 33
ALF Reports/Print Lists..................................................................................... 34
Testing archiving reports............................................................................... 34
Displaying a newly archived Print List ........................................................... 36
Deleting archived and linked documents ........................................................... 36
Customizing FAX–scanned documents .............................................................. 36
3
Table of Contents
oaws—Settings ............................................................................................. 37
Optional for SAP workflow ........................................................................... 38
Optional for barcode ..................................................................................... 38
OAC5—Bar Code Settings ......................................................................... 38
Testing scanning documents .............................................................................. 39
Chapter 4 Creating Custom BAPIs ............................................................................... 43

Chapter 5 Configuring the DMS Interface for the Manage and View
Components ................................................................................................ 47
Configuring the Manage component .................................................................. 47
Configuring the Manage and View components ............................................. 47
Opening the Document Management Control Data window ........................... 48
Configuring Document Management Control data ............................................. 48
Defining number ranges for document numbers ............................................. 48
Defining document types .............................................................................. 49
Defining and maintaining object link descriptions .......................................... 50
Configuring general data .................................................................................. 50
Defining Data Carrier and Data Carrier Types ................................................ 51
Defining external DMS.............................................................................. 51
Defining data carrier type “server, front end” ............................................. 52
Identifying front-end computers ................................................................ 52
Defining workstation application ................................................................... 53
Defining workstation applications in network ............................................ 53
Maintaining CAD systems ............................................................................ 54
Configuring CAD integration ............................................................................ 54
Configuring general data sub-levels ................................................................... 55
Defining functions ........................................................................................ 55
Allocating field sets ...................................................................................... 55
Defining field sets (CAD > SAP)..................................................................... 56
Chapter 6 Configuring SAP for PP-PI .......................................................................... 57

Configuring the Process Instruction category...................................................... 57
Defining Process Instruction category DCTM ..................................................... 58
Configuring the Characteristics/Process Instruction category ............................... 58
Appendix A Configuration and Usability notes ............................................................... 61

WebTop integration – JRE causes slow performance ............................................ 61
Limitations found concerning SAPGUI for HTML configuration ......................... 61
Custom BAPIs .................................................................................................. 61
WebAdmin simplified Chinese localization pack installation ............................... 62
4
Table of Contents
List of Figures
Figure 1. CS SAP and SAP................................................................................................... 12
5
Table of Contents
List of Tables
Table 1. Terms and definitions ........................................................................................... 14

Table 2. Field descriptions of change output device screen ................................................... 20
Table 3. Field descriptions of change output device screen ................................................... 22
Table 4. Field descriptions ................................................................................................. 23
Table 12. Field descriptions of New Entries table .................................................................. 34
Table 13. Number ranges .................................................................................................... 49
Table 15. Object Link descriptions........................................................................................ 50
Table 16. Function values .................................................................................................... 55
Table 17. CAD field sets ...................................................................................................... 56
6
Preface
Purpose of this guide

This guide explains how to configure SAP for use with Documentum Content Services for SAP
(CS SAP) 7.3. This guide provides task-based instructions for configuring SAP, so that SAP works
together with CS SAP.
Intended audience
In order to address the manuals to the correct audience, the roles of the users of the manuals have
been defined as follows:
• System Administrator — This role covers users who install and configure CS SAP. The Content
Services for SAP application integrates Documentum and the SAP R/3 system. Therefore, system
administrators must have experience with the software products listed in the Documentum Content
Services for SAP Release Notes.
• Content Services Administrator — This role covers users who manage CS SAP using WebAdmin.
• Document Controller — This role covers those who release documents to SAP and maintain the
links to those documents.
• Capture Operator — This role covers users who scan documents and create links to the
appropriate records in SAP.
• Standard User — This role covers users who view documents using SAPGUI and the View
component of CS SAP.
This manual is intended for system administrators.
Revision history
This section contains a description of this document’s revision history.
Revision history
Revision date Description

May 2017 Initial publication
7
Preface
Typographic conventions
This guide uses the following text conventions.
Typographic conventions used in this guide
Convention Description
> Represents a pop-up or pull-down menu.
<Text enclosed within angle brackets> Represents a variable name for which you must
provide a value, or a defined term.
Represents code samples, user input, and
Information in this font
computer output.
[] square brackets Used in method command syntax specifications,
square brackets indicate an optional argument.
{} curly brackets Used in method command syntax specifications,
curly brackets indicate an optional argument
that can be repeated more than once.
Related documentation
This manual forms part of a documentation suite designed to support those who install, configure,
and use CS SAP. The product and documentation suite can be found on Online Support at
https://support.emc.com.
Content Services for SAP—documentation suite
Title Description Target role

Documentum Content Services for Provides an overview of Standard User, System
SAP Release Notes new and amended features, Administrator, System
known bugs, limitations, and Administrator (SAP), and
documentation correctness and Content Services Administrator
clarifications.
Documentum Content Services for Provides the procedures for System Administrator
SAP Installation Guide installing Content Services.
Documentum Content Services for Describes the configuration System Administrator (SAP)
SAP Configuration Guide tasks that need to be performed
in SAP so that SAP can
communicate with Content
Services.
Documentum Content Services for Describes how to configure Content Services Administrator
SAP Administration Guide Content Services using the
WebAdmin tool.
8
Preface
Title Description Target role

Documentum Content Services for Describes how SAP users view Standard User
SAP User Guide documents.
Documentum Content Services for Describes how the SAP Document Control User
SAP Document Controller User document controller releases
Guide documents to SAP and
maintains the links to those
documents.
Documentum Content Services Describes how SAP document Scanner Operator User
for SAP Scanner Operator User scanners scan documents and
Guide create links to the appropriate
records in SAP.
Note: CS SAP extensively uses the SAP ArchiveLink component. Your SAP ArchiveLink
documentation has more information on how to perform advanced tasks.
9
Preface
10
Chapter 1
Introducing Content Services for SAP
Overview
The ®Documentum® Content Services for SAP (CS SAP) application integrates the Documentum
content management system with the SAP R/3 or ECC system. It is an interface to the SAP R/3 or ECC
system based on SAP standard Document Management System (DMS) and ArchiveLink interfaces.
CS SAP provides the following functions:
• Enables users to easily access and display documents stored in a Documentum repository from
a variety of SAP modules.
• Links documents stored in Documentum to a variety of SAP documents.
• Archives SAP data, reports, and documents through ArchiveLink certified interfaces in
Documentum.
Note: To use CS SAP with HTTP archiving services, install AS SAP, as described in the
Documentum Archive Services for SAP Installation Guide.
• Stores and manages reports and outgoing documents in Documentum.
11
CS SAP architecture
Figure 1. CS SAP and SAP
Note: Content Services for SAP capture component is not present in the 7.2 release.
12
CS SAP consists of the following components:

• WebAdmin
An administrative console that allows you to:
— Perform archiving services.
Using WebAdmin, you can perform the following archiving services:
— Create, configure, and manage archives.
— Manage certificates for the archive.
— Configure document archival for CS SAP.
— Perform DMS-related services. You can:
— Configure batch jobs for linking and replication tasks.
— Schedule and manage the execution of linking and replication jobs.
• High Volume Processing Server (HVPS)
A server component that allows you to automate the linking between SAP objects and documents,
as well as maintain those links. This automation improves productivity, information integrity,
and information availability. This replaces the CS SAP Agent component present in 5.3 and 6.0
releases. Unlike the previous Agent, HVPS is completely a Java-based component. The following
are the two main components:
— HVP Controller: This server component is packaged as the HVPS.dar file. HVP Controller
runs in the realm of the method server and delegates the jobs executed from the WebAdmin to
the registered HVP Workers.
— HVP Worker: The Worker is a .war file which can be installed on any supported application
server (Release notes provide information on the supported application servers). The jobs
delegated by the controller are executed by the HVP Worker. The HVP Worker packages DFC
libraries that is used to communicate with the repository. It communicates with SAP using the
SAP JCo v3.0.x libraries. The JCo libraries have to be downloaded from the SAP marketplace
into the lib directory of HVP Worker.
• View
View is a thick client which must be installed on every client computer that needs to access
reports, drawings, and other documents stored in a Documentum repository.
The View component supports the following operating systems:
— Windows 2000
— Windows XP
— Windows 2003
• WebView
This is a Web-based View application which could be installed on any supported application
server. The advantage of using WebView over View is that the user need not have to install the
View application on every client computer and the documents reports are rendered on to the
browser window. Unlike View, WebView supports UNIX-based operating systems also. WebView
also has Daeja viewer plugin which enables users to open TIFF and PDF documents inside the
browser window and provides tools to annotate.
• Manage
13
Enables you to release Documentum documents to SAP, and to maintain those released
documents.
Note: The Documentum Content Services for SAP Release Notes provides detailed information about
specific OS versions and supported software environments.
Supported SAP document formats

Documentum supports the following SAP document classes/formats:
• Incoming or scanned documents (FAX class, TIFF format)
• Outgoing documents (OTF class, PDF format)
• Archived data (REO class, REO format)
• Reports or print lists (ALF class, ALF format)
SAP and CS SAP terms

The following table presents the SAP and CS SAP terms and their definitions used in this guide.
Table 1. Terms and definitions
Term Definition
CS SAP Product that connects Documentum to and from
SAP.
ArchiveLink Cross-functional interface that is part of the SAP
Basis System. ArchiveLink handles the storing
and retrieval of documents and data to and from
a repository external to SAP.
WebAdmin An administrative console that allows you to
perform:
• Archiving services:
— Create, configure, and manage archives.
— Manage certificates for the archive.
— Configure document archival for CS SAP.
• DMS-related services:
— Configure batch jobs for linking and

replication tasks.
— Schedule and manage the execution of

linking and replication jobs.
14
Term Definition
HVPS A server component that allows you to automate
the linking between SAP objects and documents,
as well as maintain those links. This automation
improves productivity, information integrity,
and information availability. This replaces the
CS SAP Agent component present in 5.3 and 6.0
releases. Unlike the previous Agent, HVPS is
completely a Java-based component.
SAP DMS Document Management System that is part
of the SAP Basis System. Presents a logical
layer to integrate with external systems like
AutoCAD or Documentum. Not directly related
to ArchiveLink.
SAP PLM Product Lifecycle Management (PLM). SAP
PLM provides an integrated environment
that ensures all personnel involved in product
development, manufacturing, and service have
quick and secure access to current information.
It provides a set of BAPI calls that can be used
by external systems like Documentum.
SAP Master Record A set of master data, such as customer or vendor
data, which is used in the creation of SAP
documents.
SAP GUI SAP graphical user interface. Graphical
menu/screen tool that connects a client to the
SAP server.
Original document Paper-based version of a document.
For example, an invoice can consist of two

sheets of paper received from a supplier.
Paper documents are scanned in and stored as
electronic documents in Documentum.
SAP document An electronic transactional record of header data
and line items in SAP.
15
16
Chapter 2
Configuring the ArchiveLink Interface
for CS SAP
Overview
You can store and retrieve documents, reports, and data through SAP ArchiveLink and DMS
interfaces.
Once a document is released to Documentum, it is accessible from SAPGUI (the SAP client interface).
It is also accessible from a Documentum Client such as Webtop.
Prior to running CS SAP, the SAP R/3 system must also be configured. This chapter describes how to
configure your R/3 ArchiveLink and other related transactions through SAPGUI and the R/3 system.
Note: The configuration steps often reference direct transaction codes. These codes allow you to
navigate directly to the correct configuration screen. Most of the system configuration is performed in
the SAP Implementation Guide for R/3 customizing (IMG). You can navigate to this screen using
the following transaction code: spro.
Archive Services are configured as an HTTP-based Archive Server.
Note: Documentum recommends that all installations be based on the HTTP-based Archive Server
because SAP has focused development on the HTTP-based archive protocol.
The various configuration tasks that you have to perform are described in the following sections:
• oac0—Defining a logical ArchiveID, page 17
• oag1—Configuring basic settings, page 18
• oanr—Configuring number ranges, page 18
• oaqi—Creating queues, page 19
• oaat—Scheduling jobs, page 19
• spad—Configuring optical archives as output devices, page 20
• sm50—Verifying spool processes, page 22
• sole—Maintaining OLE applications, page 22
• oaa4—Maintaining applications and configuring communications protocol, page 24
oac0—Defining a logical ArchiveID

Note: The name of the logical ArchiveID must be the same as the ArchiveID created using
WebAdmin, as described in the Documentum Content Services for SAP Administration Guide.
17
Configuring the ArchiveLink Interface for CS SAP
To define a logical ArchiveID in SAP:

1. Execute the following transaction in the transaction code field:
oac0
2. In the Display Content Repositories: Overview page, click on any content repository, specifically
whose Storage type is HTTP content server.
3. In the Display Content Repositories: Detail page, click Display/Change.
The Copy as ... is enabled.
4. Click Copy as ... .
5. Edit the Content Rep. field so that it is the same as the ArchiveID created using WebAdmin, as
described in the Documentum Content Services for SAP Administration Guide.
6. In the Transfer drctry field, type the directory path where SAP can write the Print List until
it is in the Storage Queue.
7. In the HTTP Server field, type your system name.
Note: Type the IP address of your system in this field.
8. In the HTTP Script field, type the following:
/<virtual_directory>/archivelink/<name-of-repository>
<virtual_directory> refers to the AS SAP virtual installation directory.
9. To save the logical ArchiveID configuration, select Content Repository > Save.
oag1—Configuring basic settings

You must define the basic settings for ArchiveLink.
To configure the basic settings:

oag1.
2. Ensure that Deactivate Print List Management in DMS is selected.
3. Save your changes.
oanr—Configuring number ranges

You must configure the number ranges for ArchiveLink.
To configure the number ranges:

oanr.
2. To edit the configuration, click Intervals (marked with a pencil).
18
The Display Number Range Intervals window opens.

3. Configure the Number Range 01 with default values.
oaqi—Creating queues
When Print Lists are archived, the SAP print spooler puts the document into the asynchronous queue.
The scheduler then picks up the document and sends it to the archive. The queue serves as a buffer
for everything sent to an SAP archive. Other queues are used for outgoing documents and barcodes.
These queues can be seen on the ArchiveLink Monitor screen (transaction code: oam1). If this screen
shows the word MISSING instead of zeros, you must create queues and specify an administrator.
Define an SAP user with the proper ArchiveLink administrator profile as the administrator for this
queues. Defining an administrator will automatically create the queues. Check that the queues have
been created by reviewing transaction oam1.
To create queues:
oaqi
The SAP ArchiveLink: Create All Queues (CFBC, CARA, CGDA) screen appears.
2. Fill in all the options with x.
3. Type a valid SAP login name in the Queue Administrator field.
4. Select Program > Execute.
5. Click Cancel to close the window.
oaat—Scheduling jobs
The SAP schedule job periodically checks the output queue and sends all the items in the queues to
the archive. You must configure the schedule job to successfully archive documents to an SAP archive.
To schedule a job:
oaat
2. Create a new job.
3. Type the following in the ABAP Program field:
ILQBATCH
4. To verify that there are no errors, click Check.
6. Click Back to return to the Define Background Job window.
19
7. Click Start Date.

8. Set Start Time to Immediate.
9. Select Periodic Job.
10. Click Period Values and specify an interval such as 20 minutes.
This value should be determined by the following factors:
• Frequency of archival.
• Time taken to archive your largest document; for example, your largest Print List.
12. Click Exit.
spad—Configuring optical archives as output

devices
An output device is the driver software for the logical output device which archives documents using
the ArchiveLink interface. To correctly archive a document to SAP, you must define the output device
as an optical archive. Configuring an output device includes defining the type, the device, the spool
server, and so on. There should be only ONE ARCH device; therefore, prior to defining a device with
the ARCH short name, you should delete any existing ARCH devices such as ARCHIXOS.
Configuring an optical archive as the output device

To configure an optical archive as the output device:
1. Start SAPGUI and connect to your R/3 server.
2. Execute the following transaction in the in the transaction code field:
spad.
3. Click Output Devices.
4. Click the pencil button to edit settings.
Note: You can only have one printer and that printer must be named ARCH. If you are already
use a printer named ARCH you can either delete it or using the existing ARCH device.
5. In case ARCH already exists, select device ARCH and click Delete.
6. Click the New Entries button to create a new output device.
The Change Output Device screen appears.
7. Fill in the fields listed below:
Table 2. Field descriptions of change output device screen
Field name Value

Output Device ARCHIVE
20
Field name Value

Short Name ARCH
Device Type ARCHLINK
Spool Server Select spool server from the list box. Usually
there is only one spool server listed
Device Class Type A, for archive program
Access Method Fill I, for archive service
Location Fill Archive
Message Fill ArchiveLink Device
8. Press Enter.
The dialog box changes.
For this version, you will need to type additional information after you have configured your
archives.
oac0
11. Click the pencil button to edit the settings.
12. Click New entries.
The Maintain View for Archive Device screen appears.
13. Fill in the ArchiveID you plan to use for Print lists. For example, AA.
14. Type ARCH in the Output Device field.
Repeat steps 13 and 14 for each archive.
The archive device name changes from ARCH to Archive device.
Configuring an optical archive as output device for a

Documentum installation
To configure an optical archive as the output device for the Documentum installation:

spad
2. Click Output Devices.
3. Click the pencil button to edit settings.
Note: You can only have one printer and that printer must be named ARCH. If you are already
using a printer named ARCH, you can either delete it or use the existing ARCH device.
4. In case ARCH already exists, select device ARCH and click Delete.
21
5. To create a new output device, click New Entries.

The Change Output Device window opens.
6. Fill in the fields listed below.
Table 3. Field descriptions of change output device screen
Field name Value

Host Printer a
Device Class A
Access Method to Host Spool I
Device Type ARCHLINK SAP ArchiveLink Archiver
Spool Server Select spool server from the list box.
7. Press Enter and the dialog box changes.

sm50—Verifying spool processes

CS SAP uses the standard SAP print spooler to send reports to the ArchiveLink queue. To successfully
archive a document, the print spooler must be running.
To verify if a spool process is running:

sm50
2. Verify that a process named SPO is waiting or running.
If you do not have a spool process running, contact your SAP system administrator. Starting a
spool process usually involves restarting the SAP server.
sole—Maintaining OLE applications

You must configure the OLE communications so that CS SAP and SAPGUI can communicate with
each other. OLE allows SAPGUI to display stored documents and to read the list of scanned
documents in the CS SAP Capture linking queue.
Configuring CS SAP Capture

To configure OLE communication for CS SAP Capture:
1. Start SAPGUI.
22
sole
The Maintenance View for OLE Applications screen opens.
3. Click Edit.
4. Click New Entries to create a new entry for a supported OLE application.
5. Type the OLE application, press Enter, then double-click the selected entry.
The Details screen opens.
Table 4. Field descriptions
Field name Value

OLE Application DOCLINKSCAN.DOCUMENT
CLSID {135C6154-BFC0-11D0-B569- 00C04FD88E1E}
Type Info Key NO_TYPELIB
Language EN [English]
Text Documentum CS SAP Capture
Configuring CS SAP View

To configure OLE communication for CS SAP View:
1. Start SAPGUI.
sole
The Maintenance View for OLE Applications screen opens.
3. Click Edit.
4. Click New Entries to create a new entry for a supported OLE application.
5. Type the OLE application, press Enter, then double-click the selected entry.
The Details screen opens.
Field name Value

OLE Application DMVIEW.DOCUMENT
CLSID {B8192AB0-DB3A-11D0-9741-0060974A8A8D}
Type Info Key NO_TYPELIB
23
Field name Value

Language EN [English]
Text Documentum CS SAP View
Type the above information exactly as it is displayed, leaving the other fields blank.
Verifying OLE application configuration

To verify the CS SAP Capture or CS SAP View configuration:
soli
The Type Info Loaded screen opens. The OLE applications you configured should be listed.
2. Double-click DMVIEW.DOCUMENT or DOCLINKSCAN.DOCUMENT.
3. Check to see if you configured the OLE application correctly:
A list of 32 items (NO_TYPELIB) appears for each OLE application configured correctly.
4. If the OLE application does not open for inspection:
• Right-click the OLE application and click Change Language.
• Select EN for English and click Execute.
• Save any changes made and execute transaction code:
soli
Note: You must see the 32 lines of NO_TYPELIB for the OLE to work.
oaa4—Maintaining applications and

configuring communications protocol
Complete the following procedure to map the OLE 2 methods just defined under SOLE that are called
when a document is archived from CS SAP Capture or when a document is displayed. The OLE 2
methods are assigned when the archive is configured via PROTOCOL. Each pair of document type
and SAP object type maps to an archive. For example, when a document is archived, the document
type and object type point to an archive. The archive in turn is configured to use a certain protocol.
From the protocol the SAPGUI determines how documents are to be scanned and viewed through
OLE.
To configure applications’ maintenance and the communications protocol to associate the correct OLE
2 method to an SAP archive:
oaa4
24
A window opens, listing the available applications configured for your SAP system.
2. Select Application Create.
The Application Maintenance dialog box appears.
3. Type DCTM in the Application field and click Back.
DCTM is added to the list of available applications in the Applications Maintenance window.
4. Select DCTM in the Applications list (usually by double-clicking).
5. Select Displayed Stored Document (usually by double-clicking).
6. For the View application, fill in the following information:
• Application: DMVIEW.DOCUMENT
Radio button Command

S DOCBASE=<Your_Repository_Name>
M Display @DID
G @EID=ERRORCODE
G @ETX=ERRORTEXT
7. Ensure that the Release generated object after call box is selected.
8. Return to the previous window and select Archive From Frontend (usually by double-clicking).
9. For the Scan application, fill in the following information:
• Application: DOCLINKSCAN.DOCUMENT

M Scan
G @EID=ERRORCODE
G @ETX=ERRORTEXT
G @DID=DOCID
10. Ensure that the Release generated object after call box is selected.
11. Return to the previous screen and save your configuration.
12. Display the changes made to transaction oaa4 and be sure that Display Stored Document and
Archive From Frontend show Maintained.
13. Execute the following transaction:
oa3
You should see a screen for SAP ArchiveLink: Communications interface administration.
14. Select Create.
The New Protocol dialog box opens. For example, you may wish to define the protocol name as
CONSVC65 for CS SAP 6.5.
25
15. Type the HTTP-based archiving version of the protocol:

0045
Note: You need an HTTP archiving protocol such as, ECONHTTP.
The Overview of a Protocol window opens, displaying your newly defined protocol.
17. Select Display Stored Document (usually by double-clicking).
The Overview of a Protocol window opens showing a list of document classes.
18. Select the * row which indicates all document classes.
19. Click the pencil button.
The Overview of a Protocol dialog box opens.
20. Type OPEN in the Communication Type field to view linked documents through desktop
applications. Select the Communication Type HTTP to view linked documents directly in
SAPGUI.
21. Press Enter.
22. Type DCTM in the Application field, and click Continue.
You are returned to the Overview of a Protocol window.
Note: This Protocol defines what method SAP will use to display an object. The DCTM
application requires CS SAP View to be installed on all PCs needed to display Print lists.
Additional options are under SPECIAL PROTOCOLS. In this case the Web Admin Client has to
be configured to make sure the Best Format sap_print_list is at the top of pdf and html. This is
not required if PDF or HTML renditions are not created. More information is in the Documentum
Content Services for SAP Administration Guide.
24. Double-click Archive from frontend.
25. Select the document class “*” and double-click.
The Overview of Protocol dialog box opens.
26. Type OPEN in the Communication Type field.
27. Press Enter.
Repeat steps 18 and 23 to verify that the * document class and the ALF document class are
indicated as Maintained Explicitly. All other document classes should be indicated as Not
Maintained Explicitly.
Special protocols
You have options for special use protocols which are configured slightly different from the standards
described earlier. Anonymous login allows your name and password to be provided each time a login
would normally be required. Another option is that you may wish to have Print Lists displayed in
26
the native proprietary format from SAPGUI instead of viewing them using Documentum renditions
as described earlier.
Protocol for anonymous login

To create a protocol for anonymous logins:
1. Fill in the following information:

S USER=<username>
S PASSWORD=<password>
M Display @DID
G @EID=ERRORCODE
G @ETX=ERRORTEXT
2. Ensure that the Release generated object after call checkbox is selected. Then continue with
Protocol for anonymous capture login.
Protocol for anonymous capture login

To create a protocol for anonymous capture logins:
1. Fill in the following information:
• Application: DOCLINKSCAN.DOCUMENT

S DOCBASE=<repository>
S USER=<username>
S PASSWORD=<password>
S DOMAIN=<domain>
S CLIENT=<client>
S SYSTEM=<system>
M Scan
G @EID=ERRORCODE
27

G @ETX=ERRORTEXT
G @DID=DOCID
2. Click Continue.
3. Ensure that the Release generated object after call checkbox is selected. Then continue with
Protocol for the SAP Inline Print List viewer.
Protocol for the SAP Inline Print List viewer
SAP R/3 includes a Print List viewing feature that allows you to view saved Print lists with SAPGUI
in their native ALF format. To enable SAPGUI viewing, you must configure the protocol to support
the viewer.
Note: If you convert Print List to PDF with renditioning, they can be viewed and annotated without
SAPGUI.
To configure the Print List viewer to display the Print Lists in SAPGUI:
1. Select Create.
The New Protocol dialog box opens. For example, you may wish to define the protocol name
as ECONALF for Content Services for SAP with ALF viewer.
2. Type the HTTP-based archiving version of the protocol:
0045
Note: Type the HTTP archiving protocol, for example, ECONHTTPA.
The Overview of a Protocol window opens, displaying your newly defined protocol.
4. Select Display Stored Document (usually by double-clicking).
The Overview of a Protocol window opens showing a list of document classes.
5. Select the * row which indicates all document classes.
The Overview of a Protocol dialog box opens.
7. Type OPEN in the Communication Type field.
8. Press Enter.
10. In the Overview of a Protocol window showing the list of document classes, select the ALF
document class.
The Overview of Protocol dialog box opens.
12. Type R/3 in the Communication Type field, and then press Enter.
No application is entered here.
28

You are returned to the Overview of a Protocol window.
Repeat steps 4 and 11 to verify that the * document class is Maintained Explicitly as well as the
ALF document class. All other document classes should show Not Maintained Explicitly.
Protocol for HTTP display

To create a protocol for HTTP display:
Fill in the following information:

S DOCBASE=<Your_Repository_Name>
M Display @DID
G @EID=ERRORCODE
G @ETX=ERRORTEXT
1.
29
30
Chapter 3
Customizing SAP Document Classes
This chapter describes how to archive document classes from SAP. The customization of each SAP
setup is different depending on which document class the archived document belongs to. The
document classes are:
• ALF
• FAX
• OTF
• REO
For all classes you must configure a minimum of:
• OAC0
• OAC2
• OAC3
Plus any specific customizations.
These customizations are described in the following sections:
• oac0—Configuring content repositories, page 31
• oac2—Defining document types, page 33
• oac3—Defining links, page 33
• ALF Reports/Print Lists, page 34
• Deleting archived and linked documents, page 36
• Customizing FAX–scanned documents, page 36
• Testing scanning documents, page 39
oac0—Configuring content repositories

SAP allows you to define a content repository (previously known as a logical archive). This content
repository is mapped to a Documentum archive using WebAdmin. The Documentum archive links to
a set of rules such as content folders, Documentum document types, and so on in the Documentum
repository. Store each document type in a separate archive. Using WebAdmin, you must create a
matching archive for each ArchiveID defined in SAP. This ArchiveID defines what actions (types,
31
folders, retention, and so on) are applied on a SAP document when it is archived. The following
sections explain how to create an archive in SAP for each represented document class.
You can configure HTTP-based archives.
To define a SAP content repository (archive):
1. Execute the following transaction:

oac0
2. Select SAP Reference IMG from the menu bar.
The IMG window opens.
3. Navigate to Basis Components > Basic Services > SAP > ArchiveLink > Basic Settings >
Maintain content repositories.
4. Click the pencil button to edit the table.
5. Click New Entries.
6. Select Full administration.
The Change Content Repositories window opens.
7. Fill in the following information in the Change Content Repositories window.
Field name Value

Content rep Specify a two-letter archive name. For example, AA
Description Meaningful name. For example, SAP Print Lists (AA)
Storage Type Select HTTP or RFC
Protocol Previously configured protocol.
Version No. 0045 for HTTP or 0031 for RFC
Output Device ARCHIVE
8. Type appropriate values in the following fields:

• HTTP server
Type the hostname or IP address of the Archive Services host. If you use a server name here,
ensure that you can ping the server by name from the SAP server.
• Port Number
Type the port number being used (default is 80).
When using a default Tomcat configuration, this value is usually 8080.
• HTTP Script
Type the following value in this field: <virtual-directory>/archivelink/<repository>
<virtual-directory> is the directory on which the software is installed.
where <repository> is the name of the repository into which you will be archiving content. You
must configure a corresponding archive in the Archive Services, using WebAdmin.
32
• Basic path
Type the file system path to the location where SAP will put archived documents to be picked
up by Archive Services.
• Arch path
Usually, the same as the Basic path.
Repeat this procedure to define additional archives. You may use this procedure to define any
Documentum archives in SAP.
oac2—Defining document types

You must select which document types you will be archiving, and correlate those to SAP document
classes, such as FAX, ALF, OTF, and REO. The list of document types provided by SAP, when using
transaction OAC2, are the templates to be used for categorizing your SAP documents for archiving.
You can customize the standard document types by using the SAP XYZ naming conventions:
• FAX documents are documents that will be scanned and linked to SAP.
• ALF are reports produced and linked from SAP.
• OTF are outgoing SAPSCRIPT documents produced and linked from SAP.
• REO documents are data archive files which are compressed by the SAP ADK and stored
externally in that format.
To define document types for SAP:

oac2
2. If you are defining a new document type, select New Entries.
You may also copy existing document types.
3. If you are modifying an existing document type, use Change and Details.
4. Type information in the Description and Doc. class fields as appropriate for your configuration.
5. When you have finished selecting document types, save your changes.
oac3—Defining links
Using the link table, you can categorize SAP documents to define what combination of SAP object
type (for example, SOOD) and SAP document type (for example, GENPRILIS) are stored and linked
to which archive.
The SAP document type is linked to the SAP document class, previously known as SAP document
type (for example, ALF, OTF, REO) which determines how the document is produced and linked.
For example, the ALF class refers to reports, FAX to scanned documents, and OTF to outgoing
SAPSCRIPT documents.
33
To define links:
oac3
The Display View “Links for Content Repositories": Overview screen appears.
2. Select Table View > Display > Change.
Table 12. Field descriptions of New Entries table
Field name Value

Object Type Use legitimate object type such as SOOD
for Print Lists, and BKPF for accounting
documents.
Document Type The SAP doc type, as defined earlier in OAC2,
such as GENPRILIS.
S (Status) Type an x in this column.
Arch. ID Type the archive ID of a newly created archive,

for example, AA.
Link Type the name of the link tables where links
will be maintained. TOA01-TOA03.
Ret Prd. 0
ALF Reports/Print Lists

To customize ALF Reports/Print Lists, perform the following procedures:
Then perform the test.
Testing archiving reports

Once you have completed the configuration procedures in this section, you should test the new
Print List archive by:
• Archiving a Print List
• Displaying the archived Print List
34
The following section explains how to perform these tasks.
To archive a Print List:

f.21
2. Click Execute.
3. In the List of Customer Open Items page that appears, select List > Print.
The Print Screen List dialog box appears.
4. Click Properties.
The Spool Request Attributes dialog box appears.
5. In the Parameters name column, click Output Options.
6. From the Storage Mode list box, select Archive only.
Note: Whenever you edit a parameter in this dialog box, select Show Selected Print Parameters
on Initial Screen. This ensures that the customized settings are available in the initial Print
Screen List dialog box.
7. Verify that the Object Type and Document Type fields contain the correct values, as configured
in the New Entries table in oac3—Defining links, page 33. Pick the following values for example:
SOOD GENPRILIS
If your Document Type is incorrectly configured, refer to the following procedures for configuring
document types in SAP archives:oac2—Defining document types, page 33 and oac3—Defining
links, page 33.
8. Type additional information in the Information field.
This label may be anything you wish; for example, your initials.
9. Optionally, type a description of the Print List in the Text field.
10. In the Parameter name column, select General attributes > Time of printing.
11. From the Time of print list box, select Print out immediately.
12. Click Continue in the Spool Request Attributes dialog box.
13. Click Continue in the Print Screen List dialog box.
14. To verify that the Print List is in the archiving queue, execute the following transaction in the
transaction code field:
oam1
The ArchiveLink Monitor screen appears.
The Print List is now queued, waiting for the scheduler to pick it up and transfer it to the archive.
oaat—Scheduling jobs, page 19, contains information about configuring the ArchiveLink
scheduler.
15. To accelerate the transfer of the Print List from the queue to the archive in the repository, click
Storage Queue.
The Queue: Content server (CARA) screen appears. You should now see an entry for the newly
archived Print List in this screen.
35
16. To view the archiving parameter details, double-click the Print List entry.
The Archiving request window opens.
Verify that the details are correct
17. To archive the Print List in an archive located in a repository, click Execute.
You should see a confirmation message that the queue has been processed.
If no errors occur, you can continue testing by displaying the archived Print List.
Displaying a newly archived Print List

To display the newly archived Print List in SAPGUI:

oadr
2. To find a particular Print List, type appropriate search parameters in the appropriate fields.
The ArchiveLink: Hit List for Stored Print Lists page appears.
3. Double-click an item in the list to select it.
4. Select Print List > Display From Content Server.
SAP executes the GET command to retrieve the document from the Documentum archive.
The retrieved document is displayed in SAPGUI and has the DocumentID of the Print List in
Documentum.
Deleting archived and linked documents

In a repository, if you delete version 1.0 of a document that is linked to SAP or archived from SAP, the
link to SAP is also deleted. This is because the dm_relation object which creates the link to SAP is
deleted when the parent object (which is always version 1.0) is deleted.
Do not delete the original version of objects that are linked to SAP if you want to maintain their link
to SAP. If you need to delete version 1.0 of a document, but want to keep the link to SAP, then, after
deleting the document, you must relink the object to SAP, outside of Content Services.
Customizing FAX–scanned documents

To customize FAX–scanned documents, you must perform the following procedures:
36
Then you can make specific customizations using the following procedures:
• oaws—Settings, page 37
• Optional for SAP workflow, page 38
• Optional for barcode, page 38
oaws—Settings
OAWS contains the settings for routing and linking newly scanned FAX documents in SAP. For each
document type, you can specify which type of archiving is available:
• Store for subsequent entry (Early)
• Store and Enter (Simultaneous)
• Assign and Store (Late)
For storing for subsequent entry which uses SAP workflow to move the image to the SAP inbox, you
can specify what organizational object will be used for routing (like User) and then what specific
organizational object to route to (like the SAP User ID).
To display/change SAP settings for document types:

1. Type /NOAWS (previously /NSOA6) in the command field.
In earlier versions of SAP a Get Settings dialog box opens if settings have been entered. If no Get
Settings dialog box opens, select Edit > Insert doc. type and build your own list of settings.
When the new settings are saved, a name has to be specified under which the settings are stored.
You may also have to create duplicate settings for early, simultaneous, and late archiving instead
of using the checkboxes described below.
2. Select a setting from the list of available settings, or create a new setting.
3. Select the setting for the application where you wish to link scanned documents and select Entries.
The Maintenance screen opens.
4. Select New Entries to select an item from the Document Type list box which matches your entries
for OAC2 and OAC3.
5. For testing purposes, type US (USER) and your SAP ID in the Agent ID field.
This enables you to send scanned documents to your SAP workflow inbox. (You may want to
integrate these entries with the SAP organizational roles. See your workflow consultant for
details.)
6. Make sure that each checkbox is selected to use:
• Storing For Subsequent Entry
• Early Archiving (SAP workflow)
• Store and Enter Simultaneous Archiving (no workflow)
• Assign then Store Late Archiving (no workflow)
7. Make sure to note the values of document type and object type fields.
37
You will need these values to complete later configuration steps. For example, Incoming Invoice
Preliminary Posting has an object type BKPF and object type FIIINPREL.
Optional for SAP workflow

To configure all SAP object type/document type combinations you want to use with Storing for
Subsequent Entry, coordinate configuration with your SAP workflow consultant:
• SWU3 - Workflow Initialization
• SOA0 - Workflow Document Types
• OACA - Workflow Parameters
Optional for barcode

Barcodes are a good way to automatically scan and link documents that have already been entered
into SAP transactions from paper. For example, you can enter an invoice with a barcode sticker, type
or scan the barcode number, and later, when all the invoices are scanned, they can be automatically
linked with their entry transactions.
The information in this section assumes that you have already set up a bar code configuration object
in WebAdmin. If you have not yet done this, the Documentum Content Services for SAP Administration
Guide has complete information. This section explains how to configure SAP R/3 object types and
document types to accept bar code on transactions in SAP to be later linked with scanned documents
stored in a repository.
OAC5—Bar Code Settings
To configure all SAP object type/document type/User ID combinations for use with bar codes:
1. Type /NOAC5 in the command window.
2. Click Edit.
The Details of Added Entries window opens.
4. Type any SAP object types for which you want a barcode dialog box to open upon saving of
that object.
5. Type any SAP document types for which you want a barcode dialog box to open upon saving of
that document.
6. Type any User IDs for which you want a barcode dialog box to open upon saving under that
user ID.
8. Type your object, document, and user ID to test your barcode.
38
Testing scanning documents

Once you have completed the customizing described earlier, you can test document scanning, linking,
and viewing the archived images. The Documentum Content Services for SAP Scanner Operator User
Guide has more information on the Capture component.
To test scan and link documents:

1. Start CS SAP Capture from Programs > Documentum Content Services for SAP.
2. Type your username and password for the repository.
3. In CS SAP Capture, scan or import a few pages and fill in the default attributes.
4. From the Document Type list box, select Sap_invoice (or other valid Documentum document
type).
5. Click Scan.
6. Click OK to the message “No Scanner Available.”
7. Select File > Import in Content Services Image Viewer.
8. Select an example TIFF image file from any directory on your file system.
9. While the image appears in Content Services Image viewer, fill in the attributes.
10. Click Content Services Capture > Add to Queue and the image disappears from the viewer.
11. Minimize Content Services Capture.
12. In SAP, use transactions OAC2, SOA0, OACA, OAC3, OAC0, and OAWS to review the settings
for the doc type you are planning to use. For example, FIIINPREL.
13. In WebAdmin, make sure you have set up an Archive for incoming fax which matches the
Archive ID information found with OAC3 and OAC0.
You can copy and modify an existing incoming document archive.
14. On your Content Services Server, make sure that:
• Archive Services are started with the correct share user ID.
• IIS is running with HTTP.
• Certificates are installed.
15. To link the document with SAP workflow and remove it from the queue.
16. Maximize Content Services Capture.
17. Capture and select the document in the linking queue.
18. Start SAPGUI and select Office > Business Documents > Documents > Move > <your OAWS
setting>.
Size the windows so that you can see both SAP and Capture.
19. Select the SAP document type which points to your user ID.
20. Click Store For Subsequent Entry.
21. Replace the existing text with meaningful text so you will be able to recognize the file in a later
step.
39
22. Select Continue.

The item is removed from the Content Services Capture Queue.
23. Exit out of the SAP dialog box.
24. Close Content Services Capture.
To process the document in SAP, post it and link it to an SAP record.
25. In the SAP inbox type /NSIN1.
26. Go to Workflow and double-click to launch a workitem.
The image should be retrieved from Documentum. The Process Document Type dialog box opens.
27. Click Process.
You may need to move the image to see the SAP dialog box.
The SAP transaction appears.
You may need to rearrange windows to see both image and SAPGUI.
28. Fill in the sap document with data appropriate to your installation. For example:
• Document date: today’s date
• Company code: 3000
• Currency/date: USD
• Doc type: KR
• PstKy: 31 Account: 3980
29. Press Enter.
30. In the Amount field, type any amount you like.
31. In the Doc Header Text field, type your Vendor Name.
32. Scroll to the bottom of the form and type the following:
• PstKy: 40 Account: 491000.
33. Press Enter.
34. In the Amount field, type the same amount entered in step 7, or *.
35. Save the SAP Document.
36. Refresh the inbox.
The workitem should have disappeared.
37. Close the Content Services Image viewer.
38. From SAPGUI, type the display version of the transaction earlier.
39. Select List and your User ID and Execute.
The document you marked earlier should appear.
40. Select this document.
41. From your displayed document, select Environment > Object Links.
42. Select Archived Documents.
40
The original document now appears.
41
42
Chapter 4
Creating Custom BAPIs
CS SAP enables you to create and install custom configuration objects—known as BAPIs—for linking
and querying SAP data.
To create a custom BAPI, you must modify the custom.xml file that is included with the CS SAP
installation files. After modifying the custom.xml file as shown in the example below, when you
install CS SAP, the custom BAPI will be available for linking and querying using WebAdmin.
The following example details creating a custom BAPI to link and query purchase orders. The query
type for this custom BAPI is EKPO Table.
To create a custom BAPI:

Note: This procedure must be done prior to installing the current release of CS SAP. The custom
BAPI is installed with the release and is available to end-users only after product installation.
1. Download and install the current release of CS SAP Server, as described in the Documentum
Content Services for SAP Installation Guide.
2. Locate the file named custom.xml in the Server folder of the installation files.
3. Open the custom.xml file in a text editor or XML edtior.
4. Add the following sample XML code to the custom.xml file. Modify this code as appropriate
to create your own custom BAPIs. You may copy/paste this sample code inside the Request
ON_ERROR tag of the custom.xml file:
<OBJECT_CREATE ON_EXIST="version">
<API_CONFIG TYPE="sap_query_plm_type_table" CLASS="sap">
<ATTRIBUTE NAME="object_name" IS_KEY="true">EKPO_Table</ATTRIBUTE>
<ATTRIBUTE NAME="table_name">EKPO</ATTRIBUTE>
<ATTRIBUTE NAME="function_module">RFC_READ_TABLE</ATTRIBUTE>
<ATTRIBUTE NAME="sap_object_type">EKPO</ATTRIBUTE>
<ATTRIBUTE NAME="query_parameters" IS_REPEATING="true">
<VALUE>Client=MANDT</VALUE>
<VALUE>Document_Number=EBELN</VALUE>
<VALUE>Item_Number=EBELP</VALUE>
</ATTRIBUTE>
<ATTRIBUTE NAME="parameter_defaults" IS_REPEATING="true"></ATTRIBUTE>
<ATTRIBUTE NAME="result_parameters" IS_REPEATING="true">
<VALUE>Client=MANDT</VALUE>
<VALUE>Item_Number=EBELP</VALUE>
</ATTRIBUTE>
<ATTRIBUTE NAME="key_attributes" IS_REPEATING="true">
</ATTRIBUTE>
<ATTRIBUTE NAME="methods" IS_REPEATING="true">
43
<VALUE>Link</VALUE>
</ATTRIBUTE>
<ATTRIBUTE NAME="descriptive_field">EBELP</ATTRIBUTE>
</API_CONFIG>
</OBJECT_CREATE>
Save the custom.xml file and close it.

5. Repeat these steps to create as many custom BAPIs as you need, creating separate XML elements
in the custom.xml file for each custom BAPI.
6. To install the custom BAPIs into your repository, run the CS SAP Server setup.exe file, choose
Docbase Configuration, then for the version number choose Custom.XML.
If you are creating custom BAPI of type sap_query_type_plm make sure the key name for the
description field in the result parameters is called "Description" as shown in following sample
code:
<ATTRIBUTE NAME="result_parameters" IS_REPEATING="true">
<VALUE>Description=MATL_DESC,18,40</VALUE>
</ATTRIBUTE>
The attribute descriptive_field is used by Content Services Manage. The value of this
attribute will be shown as the description in the query result dialog box in Manage as shown in
the following screenshot. In this example, EKPO_Table is used.
44
45
46
Chapter 5
Configuring the DMS Interface for the
Manage and View Components
The procedures in this chapter assume that the software is installed on at least one PC and that the
Documentum repository is configured according to your business needs. It is assumed that a default
installation of SAP has been performed. If this is not the case, you may find that the installation
steps differ in your R/3 system.
You must customize SAP before you can link documents to it. The customization work is necessary to
configure the CAD Interface to your needs. Additionally, you must verify a number of parameters
and certify that everything is configured properly. This chapter discusses the following topics:
• Configuring the Manage component, page 47
• Configuring Document Management Control data, page 48
• Configuring general data, page 50
• Configuring CAD integration, page 54
• Configuring general data sub-levels, page 55
The examples in this chapter also assume a SAP default installation.
Configuring the Manage component

The complete customization is done in the same SAP menu from SAPGUI.
Configuring the Manage and View components

To configure the Manage and View components:
1. Start SAPGUI and connect to R/3.

The SAP R/3 window appears.
2. Type /nspro in the command field.
3. Press Enter.
47
Configuring the DMS Interface for the Manage and View Components
4. Select Implement Projects > SAP Reference IMG (or click the button for your specific project if
you configure your system on a project basis).
The Implementation Guide for R/3 Customizing screen appears.
5. Click Cross-Application Components, then click Document Management from the expanded
list of items.
Opening the Document Management Control Data

window
To open the Document Management Control Data window:
1. Type /nspro in the command field.

2. Select SAP Reference IMG (or click on the button for your specific project if you configure your
system on a project basis).
The Implementation Guide for R/3 Customizing window appears.
3. Click Cross-Application Components, then click on Document Management System from
the expanded list of items.
This window is the starting point for all configurations described in this chapter.
Configuring Document Management Control

data
To verify parameters in Document Management Control data:
1. If necessary, open the Implementation Guide for R/3 Customizing window and navigate to
the Document Management System cabinet described in Opening the Document Management
Control Data window, page 48.)
2. To navigate there, click on the cabinet icons to expand the selection:
Cross-Application Components > Document Management > Control Data.
The following items appear in a list:
• Define number ranges for document numbers.
• Define document types.
3. Click on each item to configure, as described in the following procedures.
Defining number ranges for document numbers

To define the number ranges:
1. To edit the configuration, click on Intervals (marked with a pen icon).
48
The Display Number Range Intervals window appears, showing number ranges configured as
shown below.
Table 13. Number ranges
No. From number To number Ext.

01 00000000000000000001 00000000000000999999 Checked
02 00000000010000000000 00000009999999999999 Unchecked
03 00000010000000000000 99999999999999999999 Checked
04 00000000000001000000 00000000009999999999 Checked
2. Save changes if necessary.

3. Click Back twice. This returns you to the Document Management Control Data window.
Defining document types

To define document types:
1. If necessary, open the Implementation Guide for R/3 Customizing window and navigate to the
Document Management System cabinet. Click on the cabinet icons to expand Cross-Application
Components > Document Management > Control Data.
2. Select Define Document Types.
A list of your configured Document types appears.
3. Starting with the document type DRW, define the parameters for each document type you intend
to store within Documentum.
Note: Since the PLM type objects are usually drawings, a default value of “DRW” is used. You
can always override this setting in the Query Conditions field of the SAP Query Composer, as
described in the Documentum Content Services for SAP Administration Guide.
Example 5-1.
You can assign the value of DocumentType as DES for a DES document type.
For all document types, you can set the value of DocumentType as one of the following:
• DocumentType=*
• DocumentType=
In this case, no value has been assigned to the parameter. The value for the parameter has
been set to blank.
4. Click the box at the beginning of the document type line.
5. Click the magnifying glass button.
6. Define the parameters for DRW as described below. Leave all other fields blank.
49
Parameter Setting
Doc. type desc Engin/Des. Drawing

Version Assign. Checked (optional)
Ass. of rev. lev Checked (optional)
Archiving authorization Checked
Change docs Checked (optional)
Internal number range 02
External number range 01
Number exit MCDOKZNR
Vers. no. incr. 1
File size 0

8. Click Back twice.
You are returned to the Document Management Control Data window.
Defining and maintaining object link descriptions

To define and maintain object link descriptions:
1. Select the document type.
2. Select Document Types > Maintain Object Link Descriptions.
3. Verify that the following three items are configured and the names are spelled exactly as follows:
Table 15. Object Link descriptions
Lang. Object Name

EN EQUI Equipment master
EN IFLOT Functional location
EN MARA Material master
4. Click Back twice.

The Document Management Control Data window reappears.
Configuring general data

This section explains how to configure several required parameters that are usually not configured
in a default R/3 installation.
50
To configure general data:

1. If necessary, open the Implementation Guide for R/3 Customizing window and navigate to the
Document Management System cabinet. Click on the cabinet icons to expand Cross-Application
Components > Document Management > General Data.
2. Select General Data.
The following items are listed:
• Define data carrier.
• Define workstation application.
• Maintain CAD systems.
3. Click on each item (marked with a tick and a clock) to configure it.
The following sections explain how to do this.
Defining Data Carrier and Data Carrier Types

Select Define data carrier from the list.
This section describes how to configure the following settings under the Define Data Carrier Type
window:
• Define data carrier type “external DMS.”
• Define “external DMS” (document management system).
• Define data carrier type “server, front end.”
• Identify front-end computers.
Defining external DMS

To configure the DMS:
1. Select Define external DMS.
3. Define the following parameters:
• TY = EX
• Description = Documentum
• Online and EX checked
4. Select Define External DMS.
5. Create a Data Carrier called Documentum of type EX with description = Documentum.
6. Save the new entry. You should then go on to define the data carrier type “server, front end.”
51
Defining data carrier type “server, front end”

To configure a new carrier type:
1. Verify that type PC exists in the listing:
• If the type PC exists, verify the parameters listed in step 2.
• If the type PC does not exist, click New Entries and set the parameters as listed in step 2.
• Type = PC
• Description = Windows PC
• Online = Checked
• The Path entry should be left blank.
4. Close the dialog box.
5. Click Back.
You should then go on to define the data carrier.
Identifying front-end computers

To configure a default front-end computer that is not already configured:
1. Navigate to the Define data carrier type “server, front end” option and select the type PC.
2. Select Identify frontend computers from the navigation area.
3. Make sure that the following entry is defined:
• FrontendComputer. = DEFAULT
• Data carr. type = PC
• Netw. address = DEFAULT
• Description = Default for local PC.
Note: If DEFAULT is not defined, check to see if it has been defined under a different data
carrier. If this is the case, continue to use this data carrier from now on, instead of PC.
6. Click Back.
You should then go on to define the workstation applications.
52
Defining workstation application

This section describes how to configure the following settings under the Document Management
System Control Data window > General Data > Define workstation application section. The following
entries must be configured in this window:
• Define workstation application
• Define workstation applications in network
To define a workstation application:
1. Navigate to Define workstation application settings in Workstation Application.

• WS application = DCM
• Description = Documentum View component
• Start authorization = checked
• All other fields should be left empty.
• All the other check boxes must be unchecked
4. Save your new entry.
Defining workstation applications in network
To define a workstation application in the network:
1. Navigate to the Define workstation applications settings in the Workstation Application.

2. Select the DCM entry and navigate to Define workstation applications in network.
Under 4.6, it is not possible to pass program arguments. For example, this means that it is not
possible to launch dmview.exe with program arguments such as /PRINT to trigger the print
function or the arguments required to use anonymous login. To get around this problem, see OSS
notes: 0135155 and 0105208.
4. Type the following parameters:
• WS application = DCM (this entry is read-only)
• Data carr. type = PC
• Application Type = 1 (Display)
• Path with prog. name = dmview.exe
If you have installed the View component somewhere other than the default SAP main program
directory, you must define the path.
53
If you have installed WebView for viewing documents, you must define the program as
dmwebview.exe. (The previous note about passing program arguments applies also to
dmview.exe. For example, If webview.exe is called without command line parameters, the user
is prompted to fill in the host name under which the Web application runs. To get around this
problem, see OSS notes: 0135155 and 0105208.)
This configuration may look different for a UNIX Web server.
• Path for ref. file = [leave this field empty]
• Start Authorization = X (yes)
7. Click Back.
Maintaining CAD systems

To configure and verify the CAD systems:
1. Select Maintain CAD Systems.
3. Enter the following parameters:
• CAD System = DEMO
• Description = Documentum.
Configuring CAD integration

Go up one level and type the CAD Integration configuration area of the IMG guide.
Select the Define control parameters entry.
To configure and verify the control parameters:

1. Select CAD Integration.
2. Edit or verify the following parameters:
• Max. number of matchcode recs = 50
• Separator in data-string = @ (hex 40)
• Max. length of send string = 03001
The remaining parameters on this window are not relevant and do not need to be edited.
54
Save the settings even if nothing was modified. The parameters given earlier are the default
parameters.
You may receive an error message here stating that control parameters are not defined for the
current client. If this happens, save the settings even if you have not modified anything.
Configuring general data sub-levels

This section describes how to verify the basic configuration values for the sub-levels associated
with the CAD Integration General Data level.
Verifying the values in the general data sub-levels ensures that the CAD Interface is properly
configured. This interface is defined with a number of tables that are configured for client 100
when the SAP server is installed. Because these tables are not always duplicated to other clients it
is important to verify them.
Note: The lists displayed in this manual do not show the complete tables but they show items that
must be there. If the number of items in your tables is much lower than the numbers given in this
manual, then your tables may not be complete. In this case, copy a new set of tables from client
000. Do not try to type these values manually.
Defining functions
Use the Position button to verify that the following items in the table are defined. This table must
contain about 180 entries.
Table 16. Function values
Proc. Code Sub-process code

DOCCH DO
DOCCR MR
DOCRQ CL
EQUIRQ MR
MATRQ MR
Allocating field sets

The following entries must be configured. This step allows you to verify whether the CAD system
name as configured in Defining Data Carrier and Data Carrier Types, page 51 is correct.
Use the position button to find the following items:
• CAD system = DEMO
• Proc. Code = DOCCR
55
• Sub -process code = MR

• Direction = U
• Set name = DCCRDAT
Defining field sets (CAD > SAP)

Select General Data > Define field sets > CAD > SAP to define CAD Field Sets. This table contains
more than 300 items. The following items must be configured.
Table 17. CAD field sets
Field set Field name

DCCRDAT DOC_NUMBER
DCCRDAT DOC_TYPE
DCCRDAT DOC_PART
DCCRDAT DOC_VERS
DCCRDAT DESCRIPT_D
DCCRDAT DISP_APPL
DCCRDAT DATA_CARR
DCCRDAT ORIGINAL
DCCRDAT PROTOCOL
56
Chapter 6
Configuring SAP for PP-PI
CS SAP allows you to link documents stored in a Documentum repository to an SAP Production
Planning for Process Industries (PP-PI) instruction sheet. Documents are directly accessible from
SAP PP-PI sheets.
SAP PP-PI modules control the manufacturing process in process industry environments. PP-PI
allows you to define hyperlinks to external applications, enabling you to retrieve documents (such as
recipes or SOPs) from a Documentum repository by using a configurable query together with specific
parameters. This mechanism is very flexible and is independent of the Documentum or ArchiveLink
system. Documents are linked to SAP PP-PI with a query stored in Documentum.
This information in this chapter assumes that CS SAP View is installed on at least one PC and that the
Documentum repository is configured according to your business needs.
You must customize the SAP server before you can use hyperlinks from a PP-PI sheet. This section
explains how to create and configure the mandatory new process instruction categories. These
concepts are described in the following sections:
• Configuring the Process Instruction category, page 57
• Defining Process Instruction category DCTM, page 58
• Configuring the Characteristics/Process Instruction category, page 58
Configuring the Process Instruction category

To get into the SAP customization menu:
1. Start SAPGUI and connect to R/3.
2. To invoke the SAP configuration tool, type /nspro into the command field.
A dialog box appears.
3. Press Enter to close the dialog box.
4. Click Enterprise IMG (or click your specific project if you configure your system on a project
base).
The Implementation Guide for R/3 Customizing window appears.
5. Navigate to the process instruction categories subfolder as follows:
Production Planning for Process Industries\Process management\Process
instructions\Process instruction categories for the R/3 PI sheet
57
6. Click Define Process Instruction Categories.
Defining Process Instruction category DCTM

To configure a new Process Instruction category:
2. Define the category DCTM:
• Process Instr.type’ type must be 6.
• Description is ‘Documentum Content Services’.
3. Save the new item.
4. Click Back to return to the previous window.
Configuring the Characteristics/Process

Instruction category
To configure the Characteristics/Process Instruction category:
Note: You must have a screen resolution of at least 600x800 to be able to enter characteristics of
the new process instruction category.
1. Click Characteristics/Process instruction category.

2. Type the value for PPPI_FUNCTION_NAME.
The default value for this field is WS_EXECUTE
3. Type the value for PPPI_BUTTON_TEXT.
The default value is Show Related Documents. This text can be changed to reflect your
customized installation.
4. Type the value for PPPI_EXPORT_PARAMETER.
The default value for this field is ‘PROGRAM’
5. Type the value for PPPI_STRING_CONSTANT.
This field specifies the absolute path or relative path (if installation directory is in the PATH
environment variable on every PC) of the Content Services View executable. The default
location of the Content Services View executable is the SAPGUI installation directory. This is a
system-wide setting.
The maximum numbers of characters is 30.
6. Type the value for PPPI_EXPORT_PARAMETER.
The default value for this field is COMMANDLINE.
7. Type the value for PPPI_STRING_CONSTANT.
58
The value of this field is the command line passed to Content Services View. You may either
leave this field blank for now, or enter the repository name and the query name. The command
line has some constraints:
• The maximum string length is 30 characters.
• All letters are capitalized.
8. Type the value for the characteristics listed below.
Characteristic Default characteristic value/comments

PPPI_FUNCTION_NAME WS_EXECUTE
PPPI_BUTTON_TEXT Show Related Documents
This text can be changed to reflect your customized

installation.
PPPI_EXPORT_PARAMETER PROGRAM
PPPI_STRING_CONSTANT This field specifies the absolute path or relative path
(if installation directory is in the PATH environment
variable on every PC) of the Content Services View
executable. The default location of the Content
Services View executable is the SAPGUI installation
directory. This is a system-wide setting.
The maximum numbers of characters is 30.

PPPI_EXPORT_PARAMETER COMMANDLINE
PPPI_STRING_CONSTANT The value of this field is the command line passed
to Content Services View. You may either leave this
field blank for now, or enter the repository name
and the query name. The command line has some
constraints:
• The maximum string length is 30 characters.
• All letters are capitalized.

59
60
Appendix A
Configuration and Usability notes
WebTop integration – JRE causes slow

performance
If a Java Runtime Environment (JRE) is installed on the same workstation with Content Services for
SAP View, the performance of viewing linked objects from SAP GUI using Webtop is significantly
slower. When JRE is running on the same workstation the user should not use the View preference
using Webtop.
Limitations found concerning SAPGUI for

HTML configuration
Protocols are not allowed when displaying via SAPGUI for HTML, only FAX doc class (images)
loaded via Agents (barcode or workflow) without protocols defined in OAC0, can be displayed.
Content Repositories (OAC0) that require protocols for scanning via Capture or for displaying via
the thick SAPGUI client can not currently be displayed via SAPGUI for HTML. Protocol is currently
still required by Content Services Capture as described in the Content Services for SAP ArchiveLink
configuration (OAA3 and OAA4).
SAPGUI for HTML cannot display ArchiveLink stored documents unless Protocol is removed from
the OAC0 (Content Repository) configuration. Be aware that the HTTP OAC0/protocol combination
which works for SAPGUI display may not work for SAPGUI for HTML display and visa versa. This
means that for one Content Repository all clients must view either from SAPGUI or from SAPGUI
for HTML. Currently there are difficulties in mixing the two clients when viewing from a single
repository since the thick client requires protocols and the thin client appears to prohibit them.
Also be advised that although archived documents display via SAPGUI for HTML from OAAD
and OADR, they may not display from other transaction codes such as FBV3 and instead you may
receive a runtime error. Please understand that the same functional performance is expected by
Documentum when displaying archived documents from different transactions within SAP. You
may wish to take up the issues listed above with SAP via OSS.
Custom BAPIs
BAPI table queries the SAP API on the client side and loads the whole result table into memory.
You can easily calculate be required (number of rows * row-length) and for large tables this will
not be possible.
61
Configuration and Usability notes
If there are too many rows, the work around is to write a BAPI on the SAP server side which returns
a smaller number of rows.
Implementing this bapi requires coding a a custom BAPI functional module in ABAP which is
RFC-enabled to take any number of input parameters and return a table of results.
As an example BAPI, please look at BAPI_COSTCENTER_GETLIST1 in SE37 which has 13 input
parameters and one result table. Such a custom bapi can then easily be configured on the Content
Services for SAP side via building a custom bapi configuration to match using the CUSTOM.XML
feature of the installer.
Another way to avoid this limitation is to create a custom filter and parse a printlist for the attributes
needed, then modify the Documentum object attributes via this filter when archiving the relevant
printlist.
WebAdmin simplified Chinese localization

pack installation
Use the following steps to install the WebAdmin simplified Chinese localization pack:
Note: Ensure that the WebAdmin is installed in Documentum Administrator (DA) before you install
simplified Chinese localization pack.
1. For Microsoft Windows, download the Content_Services_for_SAP_6.7_SP1_server
_Windows.zip. For Unix, download the Content_Services_for_SAP_6.7_SP1_server
_Unix.tar. These zip files contain the following files:
• SAP_ WebAdmin_Language_Pack_SCh_zh_CN.zip
• Limited_Administrator_Language_Pack_Chinese_zh_CN.zip
2. Extract the files of SAP_ WebAdmin_Language_Pack_SCh_zh_CN.zip and
Limited_Administrator_Language_Pack_Chinese_zh_CN.zip to the Documentum
Administrator (DA) folder created during the DA installation.
3. Open DA\Custom\app.xml in a text editor and add the locale zh_CN in <supported_locales>. For
example:
<supported_locales>
<locale>en_US</locale>
<locale>zh_CN</locale>
<supported_locales>
4. Save and close the file.
5. Restart the application.
62
Index
A optical archive as output device, 20

Administrative Console, 13 content repositories, 31
ALF, 33 to 34 Content Services. See Content Services for
ALF class, 14 SAP
ALF format, 14 Content Services for SAP, 7
Anonymous Login defined, 11
protocol, 27 Content Services for SAP administrator, 7
archived and deleting documents, creating
deleting, 36 queues, 19
archived data, 14 creating links, 7
archived Print List CS for SAP. See Content Services for SAP
displaying in SAPGUI, 36
ArchiveLink Monitor window, 35 D
archiving
defining
Print List, 35
document types, 33
archiving reports
links, 34
testing, 34
logical ArchiveID, 18
Archiving request window, 36
deleting
asynchronous queue, 19
archived and linked documents, 36
displaying
B archived Print List in SAPGUI, 36
bar codes, 38 dmview.exe, 53
basic settings, configuring, 18 document
incoming, 14
outgoing, 14
C scanned, 14
CAD field sets, 56 supported formats in SAP, 14
CAD Integration, configuring, 54 document controller, 7
capture operator, 7 document formats, supported in SAP, 14
class Document Management General Data, 53,
ALF, 14 55
FAX, 14 document types
OTF, 14 ALF, 33
REO, 14 defining, 33
configuration procedures, 54 FAX, 33
configuring OTF, 33
basic settings, 18 REO, 33
Manage, 47 documents, 37
number ranges, 18
63
Index
F OAC0, 32
f.21, 35 oac2, 33
FAX, 33, 36 oac3, 33
FAX class, 14 oadr, 36
field sets, allocating, 55 oag1, 18
format oam1, 19
ALF, 14 oanr, 18
PDF, 14 oaq1, 19
REO, 14 oaqi, 19
Tiff, 14 OAWS, 37
frequency of archival, 20 OLE, application, 22
optical archive, configuring as output
device, 20
G OTF, 33
General Data, 55 to 56 OTF class, 14
output device
configuring logical archive as, 20
H
High Volume Processing System, 13
P
PDF format, 14
I prerequisites
Inline Print List Viewer system administrator, 7
protocol, 28 Print List, 34
intended audience, 7 archived, displaying in SAPGUI, 36
archiving, 35
J Print Lists, 14
ALF class, 14
jobs, scheduling, 19
ALF format, 14
protocol
L Anonymous Login, 27
linking, 37 Inline Print List Viewer, 28
links purpose of the guide, 7
defining, 34
logical ArchiveID Q
defining, 18
queues, creating, 19
M R
maintaining links, 7
releasing documents to SAP, 7
Manage, 47 to 48
REO, 33
REO class, 14
N REO format, 14
number ranges, configuring, 18 Reports. See Print Lists
O S
oaa4, 24 SAP
oaat, 19 print spooler, 22
oac0, 17, 31 supported document formats in, 14
64
Index
transaction code, f.21, 35 REO class, 14

transaction code, oaat, 19 REO format, 14
transaction code, oac0, 17, 31 Tiff format, 14
transaction code, oac2, 33 system administrator, 7
transaction code, oac3, 33 prerequisites, 7
transaction code, oadr, 36
transaction code, oag1, 18
transaction code, oam1, 19
T
transaction code, oanr, 18 test scanning, 39
transaction code, oaq1, 19 Tiff format, 14
transaction code, oaqi, 19 transaction code
transaction code, sm50, 22 f.21, 35
transaction code, spad, 20 oaat, 19
transaction code, spro, 17 oac0, 17, 31
SAP Document Classes oac2, 33
customizing, 31 oac3, 33
SAP Server, 47 to 48 oadr, 36
SAP Workflow, 38 oag1, 18
SAPGUI oam1, 19
ArchiveLink Monitor window, 35 oanr, 18
Archiving request window, 36 oaq1, 19
displaying archived Print List in, 36 oaqi, 19
Queue Administrator field, 19 sm50, 22
scanning documents, 7 spad, 20
scheduling spro, 17
jobs, 19 Transfer drctry field, 18
settings, 37
sm50, 22 U
spad, 20 ueue Administrator field, 19
SPO process, 22 user roles, 7
spool process, 22
spool processes, verifying, 22
spro, 17 V
standard user, 7 verifying, spool processes, 22
supported document formats in SAP, 14 View, 47 to 48
ALF class, 14
ALF format, 14
FAX class, 14
W
OTF class, 14 WebAdmin, 13
PDF format, 14
65
Copyright © 2015 EMC Corporation. All rights reserved. Published in USA.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or
warranties of any kind with respect to the information in this publication, and specifically disclaims
implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution
of any EMC software described in this publication requires an applicable software license.
EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the
United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support
(https://support.emc.com).

Opentext Documentum Content Services For Sap: Configuration Guide

Uploaded by

Copyright:

Available Formats

Opentext Documentum Content Services For Sap: Configuration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Opentext Documentum Content Services For Sap: Configuration Guide

Uploaded by

Copyright:

Available Formats

OpenText ™ Documentum ®

Content Services for SAP ®

This documentation has been created for software version 7.3.

Chapter 1 Introducing Content Services for SAP ......................................................... 11

Chapter 2 Configuring the ArchiveLink Interface for CS SAP ...................................... 17

Chapter 3 Customizing SAP Document Classes .......................................................... 31

Chapter 4 Creating Custom BAPIs ............................................................................... 43

Chapter 6 Configuring SAP for PP-PI .......................................................................... 57

Appendix A Configuration and Usability notes ............................................................... 61

Figure 1. CS SAP and SAP................................................................................................... 12

Table 1. Terms and definitions ........................................................................................... 14

Purpose of this guide

Revision date Description

Typographic conventions used in this guide

Content Services for SAP—documentation suite

Title Description Target role

Title Description Target role

CS SAP consists of the following components:

Supported SAP document formats

SAP and CS SAP terms

Table 1. Terms and definitions

— Create, configure, and manage archives.

— Manage certificates for the archive.

— Configure document archival for CS SAP.

— Configure batch jobs for linking and

— Schedule and manage the execution of

For example, an invoice can consist of two

oac0—Defining a logical ArchiveID

To define a logical ArchiveID in SAP:

oag1—Configuring basic settings

To configure the basic settings:

oanr—Configuring number ranges

To configure the number ranges:

The Display Number Range Intervals window opens.

7. Click Start Date.

spad—Configuring optical archives as output

Configuring an optical archive as the output device

Table 2. Field descriptions of change output device screen

Field name Value

Field name Value

Configuring an optical archive as output device for a

1. Execute the following transaction in the transaction code field:

5. To create a new output device, click New Entries.

Table 3. Field descriptions of change output device screen

Field name Value

7. Press Enter and the dialog box changes.

sm50—Verifying spool processes

To verify if a spool process is running:

sole—Maintaining OLE applications

Configuring CS SAP Capture

Table 4. Field descriptions

Field name Value

7. Save your changes.

Configuring CS SAP View

Table 5. Field descriptions

Field name Value

Field name Value

Verifying OLE application configuration

oaa4—Maintaining applications and