Configuring SAP R/3 for Content Services for SAP - Dell EMC · PDF filesap_print_listisatthetopofpdfandhtml.ThisisnotrequiredifPDForHTML renditionsarenotcreated.SeeContentServicesforSAPAdministrationGuide

Conguring SAP R/3 for ContentServices for SAP

Version 5.3 SP1October 2005

Copyright © 1994-2005 EMC Corporation. All rights reserved.

Table of Contents

Preface ........................................................................................................................... 7

Chapter 1 Introducing Content Services for SAP ................................................... 13Overview ................................................................................................... 13Understanding the Content Services for SAP architecture ............................. 14Supported SAP document formats............................................................... 16Understanding SAP and Content Services for SAP terms .............................. 16

Chapter 2 Conguring the ArchiveLink Interface for Content Servicesfor SAP .................................................................................................. 19Overview ................................................................................................... 19oac0 — Defining a logical ArchiveID............................................................ 20oag1 – Configuring basic settings................................................................. 20oanr – Configuring number ranges .............................................................. 21oaqi - Creating queues ................................................................................ 21oaat - Scheduling jobs ................................................................................. 22spad – Configuring optical archives as output devices................................... 22sm50 – Verifying spool processes ................................................................. 24sole - Maintaining OLE applications ............................................................ 25oaa4 - Maintaining applications and configuring communicationsprotocol ..................................................................................................... 26Special protocols..................................................................................... 29Protocol for anonymous logins ............................................................ 29Protocol for the SAP Inline Print List Viewer ........................................ 30Protocol for HTTP display................................................................... 31

Chapter 3 Customizing SAP Document Classes .................................................... 33oac0 – Configuring content repositories........................................................ 33sm59 – RFC destination archives.................................................................. 36sm59 - Testing connections ...................................................................... 37

oac2 - Defining document types................................................................... 38oac3 - Defining links ................................................................................... 39ALF Reports/Print Lists............................................................................... 40Testing archiving reports......................................................................... 40

Deleting archived and linked documents ..................................................... 42Customizing FAX - scanned documents ....................................................... 42oaws – Settings....................................................................................... 42Optional for SAP workflow ..................................................................... 43Optional for bar code .............................................................................. 44

Testing scanning documents........................................................................ 44

Conguring SAP R/3 for Content Services for SAP 3

Table of Contents

Chapter 4 Creating Custom BAPIs ......................................................................... 49

Chapter 5 Conguring the DMS Interface for the Manage and ViewComponents .......................................................................................... 53Configuring the Manage component............................................................ 53Configuring the Manage and View components ....................................... 53Opening the Document Management Control Data window ..................... 54

Configuring Document Management Control Data ....................................... 55Defining number ranges for document numbers....................................... 56Defining document types ........................................................................ 56Defining and Maintaining Object Link descriptions .................................. 59

Configuring general data ............................................................................ 60Defining Data Carrier and Data Carrier Types .......................................... 61Defining external DMS........................................................................ 61Defining data carrier type “server, front end” ....................................... 62Identifying Front-end computers ......................................................... 63

Defining workstation application............................................................. 64Defining workstation applications in network ...................................... 65

Maintaining CAD systems ...................................................................... 67Configuring CAD integration ...................................................................... 67Configuring general data sub-levels............................................................. 69Defining functions .................................................................................. 69Allocating field sets ................................................................................ 70Defining field sets (CAD->SAP) ............................................................... 70

Chapter 6 Conguring SAP for PP-PI .................................................................... 71Configuring the Process Instruction category................................................ 71Defining Process Instruction category DCTM ............................................... 72Configuring the Characteristics/Process Instruction category......................... 72

4 Conguring SAP R/3 for Content Services for SAP

Table of Contents

List of Figures

Figure 1–1. Content Services for SAP and SAP ................................................................... 14


Table of Contents

List of Tables

Table 1–1. Terms and definitions ..................................................................................... 16Table 2–1. Field descriptions of change output device screen............................................. 23Table 2–2. Field descriptions of change output device screen............................................. 24Table 2–3. Field descriptions ........................................................................................... 25Table 2–4. Field descriptions ........................................................................................... 26Table 2–5. Field descriptions ........................................................................................... 27Table 2–6. Field descriptions ........................................................................................... 28Table 2–7. Field descriptions ........................................................................................... 29Table 2–8. Field descriptions ........................................................................................... 30Table 2–9. Field descriptions ........................................................................................... 32Table 3–1. Field descriptions ........................................................................................... 34Table 3–2. Field descriptions of New Entries table ............................................................ 39Table 5–1. Number ranges .............................................................................................. 56Table 5–2. Field descriptions ........................................................................................... 57Table 5–3. Field descriptions ........................................................................................... 59Table 5–4. Object Link descriptions.................................................................................. 59Table 5–5. Object Link descriptions.................................................................................. 60Table 5–6. Function values .............................................................................................. 69Table 5–7. CAD field sets ................................................................................................ 70Table 6–1. Field descriptions ........................................................................................... 73


Preface

Purpose of this guideThis guide explains how to configure SAP to use Content Services for SAP 5.3 SP1 (CSfor SAP 5.3 SP1 or Content Services 5.3 SP1). It provides task-based instructions forconfiguring SAP, so that it works together with Content Services.

Intended audienceIn order to address the manuals to the correct audience, the roles of the users of themanuals have been defined as follows:

• System Administrator - This role covers users who install and configure ContentServices. The Content Services application integrates Documentum and the SAP R/3system. Therefore, system administrators may require experience with:

— Windows XP, 2000, 2003, or HP-UX 11i

— UNIX (if Documentum Content Server or SAP R/3 are installed on a UNIX-basedplatform).

— Documentum Technologies like Content Server and DFC

— SAP R/3 versions 4.6c or 4.7

— The following databases, depending on your system platform:

— DB2

— Oracle

— SQL Server

— Sybase• Content Services Administrator - This role covers users who manage Content Services

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 Content Services.This manual is intended for system administrators.


Preface

Revision historyThis section contains a description of this document’s revision history.

Revision history

Revision Date Description

January 2004 Initial publication of document forContent Services for SAP 5.2.5.

Changed product name from eConnectorto Content Services for SAP. Changedproduct version to 5.2.5

March 2004 Revised publication for Content Servicesfor SAP 5.2.5 SP1

January 2005 Revised publication for Content Servicesfor SAP 5.2.5 SP3

June 2005 Revised publication of document for CSfor SAP - Archiving Server 5.3

October 2005 Revised publication for Content Servicesfor SAP 5.3 SP1

Organization of this guideThis guide contains the following chapters. The table below lists the information thatyou can expect to find in each.

Organization of this guide

Chapter Contents

Chapter 1, Introducing Content Servicesfor SAP

Provides an overview of Content Servicesfor SAP.

Chapter 2, Configuring the ArchiveLinkInterface for Content Services for SAP

Describes how to configure SAP fordocument, report and, data archiving.

Chapter 3, Customizing SAP DocumentClasses

Describes how to customize SAPdocument classes.

Chapter 4, Creating Custom BAPIs Describes how to create custom BAPIs forlinking and querying.


Preface

Chapter Contents

Chapter 5, Configuring the DMS Interfacefor the Manage and View Components

Describes how to configure SAP’s DMSinterface for the Manage and Viewcomponents of Content Services.

Chapter 6, Configuring SAP for PP-PI Describes how to configure SAP PP-PI forContent Services.

Typographic conventionsThis 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 youmust provide a value, or a defined term.

Information in this fontRepresents code samples, user input, andcomputer output.

[] square brackets Used in method command syntaxspecifications, square brackets indicate anoptional argument.

{} curly brackets Used in method command syntaxspecifications, curly brackets indicate anoptional argument that can be repeatedmore than once.

Related documentationThis manual forms part of a documentation suite designed to support those who install,configure, and use Content Services for SAP. The product and documentation suite canbe found on Documentum’s download center: https://documentum.subscribenet.com.

From Subscribenet, you can download the latest version of Content Services for SAP andthe related documentation suite. To access the contents in Subscribenet, you will need toprovide the login credentials assigned to you when you first applied for access.

Note: Your login ID, by default, is your email address. If you cannot locate yourpassword, use the password finder at the bottom of the login page.


https://documentum.subscribenet.com

Preface

If you’re accessing Subscribenet for the first time, you will need to apply for access andobtain a user name and password. Refer to Applying for access.

Content Services for SAP — documentation suite

Title Description Target role

Content Services for SAPRelease Notes

Provides an overviewof new and amendedfeatures, known bugs,limitations, miscellaneoustechnical notes, anddocumentation correctnessand clarifications.

Standard User, SystemAdministrator, SystemAdministrator (SAP),and Content ServicesAdministrator

Content Services for SAPInstallation Guide

Provides the proceduresfor installing ContentServices.

System Administrator

Configuring SAP R/3 forContent Services for SAP

Describes the configurationtasks that need to beperformed in SAP so thatSAP can communicate withContent Services.

System Administrator(SAP)

Content Services for SAPAdministration Guide

Describes how to configureContent Services using theWebAdmin tool.

Content ServicesAdministrator

Content Services for SAPUser Guide

Describes how SAP usersview documents.

Standard User

Note: Content Services extensively uses SAP’s ArchiveLink component. Please refer toSAP ArchiveLink’s documentation for information on how you can perform advancedtasks.

Applying for access

To apply for access to Support online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Click the Request Access link.

4. Complete the form and send it.Documentum will respond to your request within two business days.


http://help.sap.com/saphelp_47x200/helpdata/en/5e/566039b85f9443e10000000a114084/frameset.htm

http://www.documentum.com

Preface

Accessing documentation online

Customers with a Software Support Agreement can read our product documentationat the Documentum Web site. You must have a valid user name and password, andAdobe Acrobat Exchange or Acrobat Reader installed on your system in order to viewthe documentation.

To access documents online:

1. In your Web browser, open http://www.documentum.com

2. Click the Support link.

3. Log on to the Support page.

4. Click the Documentation link.

5. Select how you want to display the documentation.

6. Click List.

7. Click the name of the document.

Purchasing bound paper manuals

Our product documentation is available for purchase as bound paper manuals. Toplace an order, call the Documentation Order Line at (925) 600-6666. You can pay witha purchase order, check, or credit card.


http://www.documentum.com

Preface


Chapter 1Introducing Content Services for SAP

OverviewThe Content Services for SAP application integrates the Documentum contentmanagement system with the SAP R/3 system. It is an interface to the SAP R/3 systembased on SAP’s standard DMS and ArchiveLink interfaces.

Content Services for SAP provides the following functionalities:

• Enables users to easily access and display documents stored in a Documentumrepository from a variety of SAP modules.

• Links documents stored in Documentum to a variety of SAP documents.• Archives SAP data, reports, and documents through ArchiveLinkTM certified

interfaces in Documentum.• Stores and manages reports and outgoing documents in DocumentumThis chapter covers the following topics:• Understanding the Content Services for SAP architecture, page 14• Supported SAP document formats, page 16• Understanding SAP and Content Services for SAP terms, page 16


Introducing Content Services for SAP

Understanding the Content Services for SAParchitectureFigure 1-1. Content Services for SAP and SAP

Content Services for SAP consists of the following components:

• RFC Archiving Server

A server component that enables you to archive reports, data, incoming andoutgoing documents from SAP to the Documentum repository. The archivedreports and documents can later be retrieved and viewed through SAPGUI andDocumentum clients. This component uses SAP Remote Function Calls (RFCs) tocommunicate with SAP.

• Agent services



A server component that allows you to automate the linking process between SAPobjects and documents, as well as maintain those links. This substantially improvesproductivity, information integrity, and information availability.

• Capture

Enables you to scan documents, store the images in a Documentum repository, andcreate a link to the appropriate transaction documents in SAP. Once this link iscreated, the document is accessible from SAPGUI, the SAP client interface. TheCapture component is part of Documentum’s integration to ArchiveLink.

• Manage

Enables you to release Documentum documents to SAP, and to maintain thosereleased documents.

• View

Enables you to view released Documentum documents from inside SAP.

The View component supports the following operating systems:

— Windows 2000

— Windows XP

— Windows 2003

The View component must be installed on every R/3 client computer that needsto access reports, drawings and other documents stored in a Documentumrepository.

• Rendition Services

Build-in filters that provide the following renditions::

— PDF rendition

— ASCII text rendition

— HTML rendition

When one of these built-in filters are used, the desired document rendition isgenerated when the document is archived in the repository.

• WebAdmin

An administrative console that allows you to:

— Create, configure, and manage archives

— Manage certificates for the archive

— Create repository connections for Content Services

— Configure document archival for Content Services



Note: Please refer to the Content Services for SAP Release Notes for detailed informationabout specific OS versions and supported software environments.

Supported SAP document formatsDocumentum 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)

Understanding SAP and Content Services forSAP terms

This section presents some terms and their definitions, as used in this guide.

Table 1-1. Terms and denitions

Term Definition

Content Services for SAP Product that connects Documentum toSAP and vice versa.

Archiving Server Server component that, using an HTTPconnection to SAP, enables you to archivereports, data, incoming and outgoingdocuments from SAP to the Documentumrepository. Archiving Server is a J2EEWeb application based on the SAPArchiveLink interface. The archivedreports and documents can later beretrieved and viewed through SAPGUIand Documentum clients.

ArchiveLink Cross-functional interface that is partof the SAP Basis System. ArchiveLinkhandles storing and retrieving documentsand data to and from a repository externalto SAP.



Term Definition

WebAdmin An administrative console that allows youto:• Create and manage archives• Manage certificates for the archive• Create repository connections for theContent Services

Capture Scanning module for Documentum andSAP that is part of the Content Servicesfor SAP suite.

Capture Import Module that allows you to import scanneddocuments (or other documents) to SAPusing the SAP ArchiveLink front-endinterface. This module is used with thirdparty scanning applications like InputSoftware. The import module is part ofthe same application as Content ServicesCapture. The Content Services Capturecan operate in two different modes (scanand import).

SAP DMS Document Management System that ispart of the SAP Basis System. Presentsa logical layer to integrate with externalsystems like AutoCAD or Documentum.Not directly related to ArchiveLink.

SAP PLM Product Life-Cycle Management (PLM).SAP PLM provides an integratedenvironment that ensures all peopleinvolved in product development,manufacturing, and service have quickand secure access to current information.It provides a set of BAPI calls thatcan be used by external systems likeDocumentum.

SAP Master Record A set of master data, such as customer orvendor data, which is used in the creationof SAP documents.

SAPGUI SAP Graphical User Interface. Graphicalmenu/screen tool that connects a client tothe SAP server.



Term Definition

Original Document Paper based version of a document.

Example 1-1.An invoice may consist of two sheetsof paper received from a supplier.Paper documents are scanned in andstored as electronic documents in EMCDocumentum.

SAP Document An electronic transactional record ofheader data and line items in SAP.


Chapter 2Conguring the ArchiveLink Interfacefor Content Services for SAP

OverviewThe Archiving Server component is the part of the Content Services for SAP applicationthat handles archive requests for a repository. This means that you can store and retrievedocuments, reports, and data through SAP ArchiveLink and DMS interfaces.

Once a document is released to Documentum, it is accessible from SAPGUI (the SAPclient interface). It is also accessible from a Documentum Client such as Webtop.

Prior to running the Content Services, the SAP R/3 system must also be configured. Thischapter describes how to configure your R/3 ArchiveLink and other related transactionsthrough SAPGUI and the R/3 system.

Note: The configuration steps often reference direct transaction codes. These codesallow you to navigate directly to the correct configuration screen. Most of the systemconfiguration is performed in the SAP Implementation Guide for R/3 customizing (IMG).You can navigate to this screen using the following transaction code: spro.

When configuring Archive Services, you can configure either an HTTP-based ArchiveServer or an RFC (Remote Function Call) Archive Server.

Note: Documentum recommends that all new installations are based on the HTTP-basedArchive Server. The primary reason is that SAP will focus future development at theHTTP-based archive protocol.

The configuration steps are different for RFC and HTTP based archiving. Configurationsteps have been marked as being relevant only to RFC- or HTTP-based archiving.

The various configuration tasks that you have to perform are described in the followingsections:

• oac0 — Defining a logical ArchiveID, page 20• oag1 – Configuring basic settings, page 20• oanr – Configuring number ranges, page 21• oaqi - Creating queues, page 21• oaat - Scheduling jobs, page 22• spad – Configuring optical archives as output devices, page 22


Conguring the ArchiveLink Interface for Content Services for SAP

• sm50 – Verifying spool processes, page 24• sole - Maintaining OLE applications, page 25• oaa4 - Maintaining applications and configuring communications protocol, page 26

oac0 — Dening a logical ArchiveIDNote: The name of the logical ArchiveID must be the same as the ArchiveID createdusing WebAdmin (refer to the Configuring, Viewing, and Editing Archives section of theContent Services for SAP Administration Guide).

To dene 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 contentrepository (specifically whose Storage type is HTTP content server.

3. In the Display Content Repositories: Detail page, click the Display/Change iconThe Copy as ... button is now enabled.

4. Click the Copy as ... button.

5. Edit the Content Rep. field so that it’s the same as ArchiveID created usingWebAdmin (refer to the Configuring, Viewing, and Editing Archives section of theContent Services for SAP Administration Guide).

6. In the Transfer drctry field, enter the directory path where SAP can write the PrintList till it is in the Storage Queue.

7. In the HTTP Server field, type your system name.

Note: You are recommended to type the IP address of your system in this field.

8. In the HTTP Script field, type the following:/archivelink/archivelink/<name-of-repository>

9. To save the logical ArchiveID configuration, choose Content Repository→Save.

oag1 – Conguring basic settingsYou must define the basic settings for ArchiveLink.

To congure the basic settings:

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

2. Ensure that the Deactivate Print List Management in DMS box is checked.



3. Save your changes.

oanr – Conguring number rangesYou must configure the number ranges for ArchiveLink.

To congure the number ranges:

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

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

3. Configure the Number Range 01 with default values.


oaqi - Creating queuesWhen Print Lists are archived, the SAP print spooler puts the document into theasynchronous queue. The scheduler then picks up the document and sends it to thearchive. The queue serves as a buffer for everything sent to an SAP archive. Otherqueues are used for outgoing documents and barcodes. These queues can be seen onthe ArchiveLink Monitor screen (transaction code: oam1). If this screen shows the wordMISSING instead of zeros, you must create queues and specify an administrator. Definean SAP user with the proper ArchiveLink administrator profile as the administrator forthis queues. Defining an administrator will automatically create the queues. Check thatthe queues have been created by reviewing transaction oam1.

To create queues:

1. Execute the following transaction in the transaction code field: oaqiThe SAP ArchiveLink: Create All Queues (CFBC, CARA, CGDA) screen appears.

2. Fill in all the options with ‘x’.

3. Enter a valid SAP login name in the Queue Administrator field.

4. Choose Program>Execute.

5. Click Cancel to exit this window.



oaat - Scheduling jobsThe SAP schedule job periodically checks the output queue and sends all the items inthe queues to the archive. You must configure the schedule job to successfully archivedocuments to an SAP archive.

To schedule a job:

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

2. Create a new job.

3. Type ILQBATCH in the ABAP Program field.

4. To verify that there are no errors, click Check.


6. Click Back to return to the Define Background Job window.

7. Click the Start Date button.

8. Set Start Time to Immediate.

9. Select the Periodic Job checkbox.

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

11. Save your changes

12. Click Exit.

spad – Conguring optical archives as outputdevices

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

To congure 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 the Output Devices button.

4. Click the pencil button to edit settings.

Note: You can only have one printer and that printer must be named ARCH. Ifyou are already using a printer named ARCH you can either delete it or using theexisting ARCH device.

5. In case ARCH already exists, select device ARCH and click the Delete button.

6. Click the New Entries button to create a new output device.The Change Output Device screen is displayed.

7. Fill in the following information:

Table 2-1. Field descriptions of change output device screen

Field name Value

Output Device ARCHIVE

Short Name ARCH

Device Type ARCHLINK

Spool Server Select spool server from drop down list.Usually there is only one spool serverlisted

Device Class Type A, for archive program

Access Method Fill I, for archive service

Location Fill Archive

Message Fill ArchiveLink Device

8. Click Enter and the dialog box changes.

9. Save your changes.For this version, you will need to enter additional information after you have configuredyour archives.

10. Execute the following transaction in the in the transaction code field: oac0.

11. Click the pencil button to edit the settings.

12. Click New entries.TheMaintain View for Archive Device screen is displayed.

13. Fill in the ArchiveID you plan to use for Print lists. For example, AA.Type ARCH into the Output Device field.



Repeat step 13 for each archive.

14. Save your changes.The archive device name changes from ARCH to Archive device.

To congure an optical archive as the output device for the Documentum installation for 4.x:

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

2. Click the Output Devices button.

3. Click the pencil button to edit settings.

Note: You can only have one printer and that printer must be named ARCH. Ifyou are already using a printer named ARCH you can either delete it or using theexisting ARCH device.

4. In case ARCH already exists, select device ARCH and click the Delete button.

5. To create a new output device, click the New Entries button.The Change Output Device window opens.


Table 2-2. 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 drop-down list

7. Click Enter and the dialog box changes.


sm50 – Verifying spool processesContent Services uses the standard SAP print spooler to send reports to the ArchiveLinkqueue. To successfully archive a document, the print spooler must be running.

To verify if a spool process is running:

1. Execute the following transaction in the transaction code field: 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 applicationsYou must configure the OLE communications so that Content Services and SAPGUI cancommunicate with each other. OLE allows SAPGUI to display stored documents and toread the list of scanned documents in Content Services Capture’s linking queue.

To congure OLE communication for Content Services Capture for 4.X:

1. Start SAPGUI.

2. Execute the following transaction in the transaction code field: sole.TheMaintenance View for OLE Applications screen opens.

3. To configure Content Services Capture OLE communication, click the Edit button.

4. Click New Entries to create a new entry for a supported OLE application.

5. Enter the OLE application, click enter, then double-click the selected entry(highlighted in red).The Details screen opens.


Table 2-3. 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 Content Services Capture


8. Click Back to return to the main OLE configuration screen.

9. Click Edit again to configure another Content Services OLE communication.

10. Click New Entries to create a new entry for a supported OLE application.



11. Click Enter, then double-click the selected entry (highlighted in red).The Details screen opens.

12. Fill in the following configuration information:


Field name Value

OLE Application DMVIEW.DOCUMENT

CLSID {B8192AB0-DB3A-11D0-9741-0060974A8A8D}

Type Info Key NO_TYPELIB

Language EN [English]

Text Documentum Content Services View

Enter the above information exactly as it is displayed. All other fields should beleft blank.


14. Execute the following transaction in the transaction code field: soli.The Type Info Loaded screen opens. Both the OLE applications you configuredin the previous steps should be listed.

15. To load the configuration, double-click each new entry DMVIEW.DOCUMENT andDOCLINKSCAN.DOCUMENT (or in SAP 3.x, click Load TypeInfo).

16. Check to see if you configured these items correctly.

a. A list of 32 items (NO_TYPELIB) displays if you configured these items correctly.

b. If nothing opens:• Click the Change Language button (either on a menu or right click the item)• Select EN for English and then click Execute• Repeat steps 13-15

Note: You must see the 32 lines of NO_TYPELIB for the OLE to work.

oaa4 - Maintaining applications and conguringcommunications protocol

Complete the following procedure to map the OLE 2 methods just defined underSOLE that are called when a document is archived from Content Services Capture orwhen 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 toan archive (these are described and ). For example, when a document is archived, thedocument type and object type point to an archive. The archive in turn is configuredto use a certain protocol. From the protocol the SAPGUI determines how documentsare to be scanned and viewed via OLE.

To congure applications’ maintenance and the communications protocol to associate thecorrect OLE 2 method to an SAP archive for 4.x:

1. Execute the following transaction in the transaction code field: oaa4.A window opens, listing the available applications configured for your SAP system.

2. Choose Application Create.The Application Maintenance dialog opens.

3. Type DCTM in the Application field and click Back.DCTM is added to the list of available applications in the Applications Maintenancewindow.

4. Select DCTM in the Applications list (usually by double-clicking).

5. Select Displayed Stored Document (usually by double-clicking).

6. 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 checked.

8. Go back to the previous window and select Archive From Frontend (usually bydouble-clicking).

9. 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 checked.

11. Return to the previous screen and save your configuration.

12. Display the changes made to transaction oaa4 and be sure that Display StoredDocument and Archive From Frontend showMaintained.

13. Execute the following transaction: oa3.You should see a screen for SAP ArchiveLink: Communications interfaceadministration.

14. Choose Create.The New Protocol dialog box opens. For example, you may wish to define theprotocol name as CONSVC53SP1 for Content Services fro SAP 5.3 SP1.

15. Enter the appropriate version of the protocol depending on whether you will beneeding RFC based archiving, version 0031 or HTTP based archiving, version 0045.You may need a protocol for each type if you plan to use RFC and HTTP archivingfor example, ECONRFC and ECONHTTP.

16. Save your changes.TheOverview of a Protocolwindow 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 Protocoll dialog box opens.

20. Type OPEN in the Communication Type field to view linked documents throughdesktop applications. If HTTP archiving is used, the Communication Type HTTPcan also be selected here to view linked documents directly in SAPGUI.

21. Press the [Enter] key.

22. Type DCTM in the Application field, and click Continue.

23. Save your changes.You are returned to the Overview of a Protocol window.



Note: This Protocol defines what method SAP will use to display an object. TheDCTM application requires Content Services View to be installed on all PC’s thatwant to display Print lists (for other options look under SPECIAL PROTOCOLS). Inthis case the Web Admin Client has to be configured to make sure the Best Formatsap_print_list is at the top of pdf and html. This is not required if PDF or HTMLrenditions are not created. See 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.



29. Save your changes.If you repeat step 18 and 23, you should see that the * document class and the ALFdocument class are indicated asMaintained Explicitly. All other document classesshould be indicated as Not Maintained Explicitly.

Special protocols

You have options for special use protocols which are configured slightly different fromthe standards described above. Anonymous login allows your name and password to beprovided each time a login would normally be required. Another option is that you maywish to have Print lists displayed in the native proprietary format from SAPGUI insteadof viewing them via Documentum renditions as described above.

Protocol for anonymous logins

To create a protocol for anonymous logins:

1. Fill in the following information:• Application: DMVIEW.DOCUMENT



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. Thencontinue with the remaining steps.

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

G @ETX=ERRORTEXT

G @DID=DOCID

2. Click Continue.

3. Ensure that the Release generated object after call checkbox is selected. Thencontinue with the remaining steps.

Protocol for the SAP Inline Print List Viewer

SAP R/3 includes a Print List viewing feature that allows you to view saved Print listswith SAPGUI in their native ALF format. To enable SAPGUI viewing you must configurethe protocol to support the viewer.

Note: If you convert Print List to PDF with renditioning, they can be viewed andannotated without SAPGUI.



To congure the Print List viewer to display the Print Lists in SAPGUI for 4.x:

1. Choose Create.The New Protocol dialog box opens. For example, you may wish to define theprotocol name as ECONALF for Content Services for SAP with ALF Viewer.

2. Enter the appropriate version of the protocol depending on whether you will beneeding RFC based archiving, version 0031 or HTTP based archiving, version 0045.You may need a protocol for each type if you plan to use RFC and HTTP archivingfor example, ECONRFCA and ECONHTTPA.

3. Save your changes.TheOverview of a Protocolwindow 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.

6. Click the pencil button.The Overview of a Protocol dialog box opens.

7. Type OPEN in the Communication Type field.



10. In the Overview of a Protocol window showing the list of document classes, selectthe ALF document class.

11. Click the pencil button.The Overview of Protocol dialog box opens.

12. Type R/3 in the Communication Type field then press the [Enter] key.No application is entered here.

13. Save your changes.You are returned to the Overview of a Protocol window.If you repeat step 4 and 11, you should see that the * document class is MaintainedExplicitly as well as the ALF document class. All other document classes shouldshow Not Maintained Explicitly.

Protocol for HTTP display

To create a protocol for HTTP display:




• Application: DMVIEW.DOCUMENT



S DOCBASE=<Your_Repository_Name>

M Display @DID

G @EID=ERRORCODE

G @ETX=ERRORTEXT


Chapter 3Customizing SAP Document Classes

The following sections describe how to archive document classes from SAP. The customization ofeach SAP setup is different depending on which document class the archived document belongs to.The document classes are:

• ALF• FAX• OTF• REOFor all classes you must configure a minimum of:

• OAC0• OAC2• OAC3plus any specific customizations. These customizations are described in the following sections:

• oac0 – Configuring content repositories, page 33• sm59 – RFC destination archives, page 36• oac2 - Defining document types, page 38• oac3 - Defining links, page 39• ALF Reports/Print Lists, page 40• Deleting archived and linked documents, page 42• Customizing FAX - scanned documents, page 42• Testing scanning documents, page 44

oac0 – Conguring content repositoriesSAP allows you to define a content repository (previously known as a logical archive).This content repository is mapped to a Documentum archive via WebAdmin. The


Customizing SAP Document Classes

Documentum archive links to a set of rules such as content folders, Documentumdocument types, and so on in the Documentum repository. It is recommended thatyou store each document type in a separate archive. Using WebAdmin, you mustcreate a matching archive for each ArchiveID defined in SAP. This ArchiveID defineswhat actions (types, folders, retention, and so on) are applied on a SAP document whenit is archived. The following sections explain how to create an archive in SAP for eachrepresented document class.

When configuring Archives, you can configure either an HTTP-based Archives or RFC(Remote Function Call) Archives. The configuration steps are different for RFC vs. HTTPbased archives. The configuration steps below have been listed as being relevant only toRFC- or HTTP-based archiving.

Note: Documentum recommends that all new installations are based on the HTTP-basedArchive Server. The primary reason is that SAP will focus future development at theHTTP-based archive protocol. However legacy RFC archives are still supported.

To dene a SAP content repository (archive) for 4.x:

1. Execute one of the folliwng transactions:• oac0

• spro

2. Select SAP Reference IMG from the menu bar.The IMG window opens.

3. Navigate to Basis Components>Basic Services>SAP>ArchiveLink>BasicSettings>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 A meaningful name. For example, SAP Print lists (AA)

Storage Type Select HTTP or RFC

Protocol The previously configured protocol.



Field name Value

Version No. 0045 for HTTP or 0031 for RFC

Output Device ARCHIVE

8. The next few fields are configured based on whether HTTP or RFC was selected.• For HTTP:

— HTTP srvr:p: <ip>:<port> For example, 192.169.1.165:8080 uses port 8080 IPis the IP address or name of the Web Server which is running the ContentServices HTTP Content Server and the port number being used (default is80). If you use a server name here, ensure that you can ping the server byname from the SAP server. If you use a port other than 80, use <ip>:<port>.

— Program Content Services/archive/<repository>.asp Enter ContentServices/archive/<repository>.asp where <repository> is the name of therepository that you will be archiving content into. You must have an HTTPservice installed with Content Services for this repository. If you have notalready done so, after specifying the program, you will need to create theHTTP service for a repository with a user name and password via theContent Services installation program.

• For RFC:

— RFC destination: Enter the RFC destination from /nSM59, Content ServicesServices, and WebAdmin. Refer to sm59 – RFC destination archives, page 36for a description of how to create the Content Services RFC destination.

• For HTTP and RFC:

— Basic path: Type the network path to the location where SAP will putarchived documents to be picked up by Content Services Archive.This directory should be referenced in the WebAdmin RFC destinationconfiguration screen. NT Example: m:\sapshare\ UNIX Example:/sapmnt/DV2/global/archive/ This path must match the shared drive in theWebAdmin RFC Destination configuration screen. There must be a slash atthe end of the path specification. For example, /sapshare/ or on Windows NTsystems using a mapped network drive, for example, M:\. The path mustalways be terminated with / for Unix or \ for NT.

— Arch path: Usually the same as the Basic path. Repeat this procedureto define the additional example archives BB and CC. You may use thisprocedure to define any Documentum archives in SAP.



sm59 – RFC destination archivesThis section applies to RFC archiving only.

The SAP server considers Content Services for SAP an external RFC service or RFCdestination. The destination is identified with a symbolic name that was configured inDocumentum during the Content Services Archive Service installation. The name of theRFC destination must be unique for each repository/SAP client connection and identicalin the Content Services Archive Services and WebAdmin configurations.

To congure the RFC destination:

1. Start SAPGUI and connect to your R/3 server.

2. Execute the folliwng transaction: sm59.

3. Select the folder icon labeled TCP/IP connections.

4. Click Create.

5. Type in a name for the RFC destination.Use the naming conventions that uniquely identify Documentum Content ServicesArchive connections, such as <DCTMHOSTNAME>_<SAPSYSID_CLIENT>.You must use the same destination name configured in the WebAdmin.

Note: It is important that an exact match is made for the RFC connection tocommunicate. The ID is case sensitive and should not contain any spaces.

6. Type T in the Connection Type field.This specifies a TCP/IP connection.

7. Leave the Login parameters field blank.

8. Enter a description in the Description field.

9. Press [Enter].

10. Click Registration.START is not correct here and will invalidate the program ID entry.

11. Copy the RFC destination name into the Program ID field.Documentum recommends that you copy and paste the name between WebAdminand transaction code sm59 because the value of this field must correspond tothe configuration parameter RFC Program ID in the WebAdmin ArchiveLinkconfiguration tab RFC Destination parameter RFC Program ID.If you have not yet installed Content Services, you will need to make a note ofthis value so that you can configure your RFC destination in Content ServicesWebAdmin, and when the RFC services are installed on the Content Services hostserver. This value must be unique for each repository/SAP client connection which



is why the RFC destination name <DCTMHOSTNAME>_<SAPSYSID_CLIENT>is recommended.If two Content Services archive processes register under the same ID or name thesecond one connected receives all requests from SAP. The first process will notreceive an error message so it will wait indefinitely for RFC requests that never come.


13. Click Back to exit.You return to the RFC Destination window.

14. Verify that the parameters have not changed.This is a check to make sure the save operation succeeded.

15. Run the test described in sm59 - Testing connections, page 37.

sm59 - Testing connections

You must have created SM59 RFC destination, WebAdmin RFC config, and ContentServices RFC services via the Content Services installation program and started withthe SHARE user ID (refer to Installing Content Services for SAP) before you begin thisprocedure.

To test the ArchiveLink RFC connection to Content Services archive:

1. Switch on debugging before processes or services are started the first time by settingthe debug level:• Windows NT In the registry: Set HKEY_LOCAL_

MACHINE\SOFTWARE\Documentum\Doclink\Archive\Docbase\<Name_Of_Repository> to 3.

• UNIX In the dmal.ini file: Set the debug level to 3.2. Start your Content Services services or processes.

3. Start SAPGUI and connect to your R/3 system.

4. Execute the following transaction: sm59.A new window opens, listing the folder hierarchy.

5. Click on the plus symbol in front of the folder labeled TCP/IP Connections.A list of all RFC Destinations opens.

6. Double-click on the RFC destination that links SAP to the repository via ContentServices.

7. Click on Test Connection.



A message appears on the status bar, stating that the connection is OK. A newwindow opens, displaying some performance figures (similar to ping).

8. Verify the connection by checking the Content Services log files.The following entries should appear in the log file on the Content Services serverwhich may be located in C:\temp\dmalaxxxxxx.log::>>> SAP open>>> Running RfcEnvironment>>> Running RfcInstallFunction>>> SAP event handler ok, entering event loop...>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...>>> RfcDispatch returned 0>>> Calling RfcDispatch...:

Note: If you receive errors, check back through the configuration on SAP,WebAdmin, and the services or processes to verify there are no typos. You can turnon the RFC trace via the checkbox on SM59, and look for information in your logs.You may need to check the SAP gateway in your .../etc/services file.

oac2 - Dening document typesYou must select which document types you will be archiving, and correlate those to SAPdocument classes, such as FAX, ALF, OTF, and REO, The list of document types providedby SAP, when using transaction OAC2, are the templates to be used for categorizing yourSAP documents for archiving. You can customize the standard document types byusing 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 dene document types for SAP:

1. Execute the following transaction in the transaction code field: 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. Enter information in the Description and Doc. class fields as appropriate for yourconfiguration.

5. When you have finished selecting document types, save your changes.

oac3 - Dening linksUsing the link table, you can categorize SAP documents to define what combination ofSAP 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 SAPdocument type (for example, ALF, OTF, REO) which determines how the document isproduced and linked. For example, the ALF class refers to reports, FAX to scanneddocuments, and OTF to outgoing SAPSCRIPT documents.

To dene links:

1. Execute the following transaction in the transaction code field: oac3.The Display View “Links for Content Repositories": Overview screen appears.

2. Select Table View > Display -> Change.

3. Fill in the following information in the New Entries table:

Table 3-2. Field descriptions of New Entries table

Field name Value

Object Type Use legitimate object type such as SOODfor Print Lists, and BKPF for accountingdocuments

Document Type The SAP doc type as defined in OAC2above such as GENPRILIS

S (Status) Enter an “x” in this column

Arch. ID Enter the archive ID of a newly createdarchives for example, AA

Link Enter the name of the link tables wherelinks will be maintained. TOA01-TOA03

Ret Prd. 0




ALF Reports/Print ListsTo customize ALF - Reports/Print lists you must perform the following procedures:

• oac0 – Configuring content repositories, page 33• oac2 - Defining document types, page 38• oac3 - Defining links, page 39Then perform the test.

Testing archiving reports

Once you have completed the configuration procedures in this section, you should testthe new Print List archive by:

• archiving a Print List• displaying the archived Print ListThe following section explains how to perform these tasks.

To archive a Print List:

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

2. Click the Execute button.

3. In the List of Customer Open Items page that appears, select List>Print.The Print Screen List dialog box appears.

4. Click the Properties button.The Spool Request Attributes dialog box appears.

5. In the Parameters name column, click Output Options.

6. From the Storage Mode drop-down menu, select Archive only.

Note: Whenever you edit a parameter in this dialog box, we recommend that youcheck the Show Selected Print Parameters on Initial Screen checkbox. This ensuresthat 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, asconfigured in the New Entries table (refer to oac3 - Defining links, page 39). Pickthe following values for example: SOOD GENPRILIS.If your Document Type is incorrectly configured, refer to the following proceduresfor configuring document types in SAP archives:oac2 - Defining document types,page 38 and oac3 - Defining links, page 39.

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 drop-down list, 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 followingtransaction 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 itto the archive.oaat - Scheduling jobs, page 22, contains information about configuring theArchiveLink scheduler.

15. To accelerate the transfer of the Print List from the queue to the archive in therepository, click Storage Queue.The Queue: Content server (CARA) screen appears. You should now see an entryfor the newly-archived Print List in this screen.

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.

To display the newly-archived Print List in SAPGUI:

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

2. To find a particular Print List, type appropriate search parameters in the appropriatefields.The ArchiveLink: Hit List for Stored Print Lists page appears.

3. Double-click an item in the list to select it.

4. Choose Print List>Display From Content Server.SAP executes the GET command to retrieve the document from the Documentumarchive. The retrieved document is displayed in SAPGUI and has the DocumentIDof the Print List in Documentum.



Deleting archived and linked documentsIn a repository, if you delete version 1.0 of a document that is linked to SAP or archivedfrom SAP, the link to SAP is also deleted. This is because the dm_relation object whichcreates the link to SAP is deleted when the parent object (which is always version 1.0)is deleted.

We recommend that you do not delete the original version of objects that are linked toSAP if you want to maintain their link to SAP. If you need to delete version 1.0 of adocument, but want to keep the link to SAP, then, after deleting the document, you mustrelink the object to SAP, outside of Content Services.

Customizing FAX - scanned documentsTo customize FAX - Scanned Documents, you must perform the following procedures:

• oac0 – Configuring content repositories, page 33• oac2 - Defining document types, page 38• oac3 - Defining links, page 39Then you can make specific customizations using the following procedures:

• oaws – Settings, page 42• Optional for SAP workflow, page 43• Optional for bar code, page 44

oaws – Settings

OAWS contains the settings for routing and linking newly scanned FAX documents inSAP. 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 SAPinbox, you can specify what organizational object will be used for routing (like User) andthen what specific organizational object to route to (like the SAP User ID).

To display/change SAP settings for document types for 4.X:

1. Type /NOAWS (previously /NSOA6) in the command field.



In earlier versions of SAP a Get Settings dialog opens if settings have been entered.If no Get Settings dialog opens, select Edit>Insert doc. type and build your ownlist of settings.When the new settings are saved, a name has to be specified under which the settingsare stored. You may also have to create duplicate settings for early, simultaneousand 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. Choose the setting for the application where you wish to link scanned documentsand select Entries.The Maintenance screen opens.

4. Select New Entries to choose an item from the Document Type list which matchesyour 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 maywant to integrate these entries with the SAP organizational roles, see your workflowconsultant for details).

6. Make sure that each checkbox is checked 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.You will need these values to complete later configuration steps. For example,Incoming Invoice Preliminary Posting has an object type BKPF and object typeFIIINPREL.

Optional for SAP workow

To configure all SAP object type/document type combinations you want to use withStoring for Subsequent Entry, please coordinate configuration with your SAP workflowconsultant.

• SWU3 - Workflow Initialization• SOA0 - Workflow Document Types• OACA - Workflow Parameters



Optional for bar code

Bar codes are a good way to automatically scan and link documents that have alreadybeen entered into SAP transactions from paper. For example, you can enter an invoicewith a bar code sticker, type or wand the bar code number and later, when all theinvoices 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 codeconfiguration object in WebAdmin. If you have not yet done this, refer to Content Servicesfor SAP Administration Guide. This section explains how to configure SAP R/3 object typesand document types to accept bar code on transactions in SAP to be later linked withscanned documents stored in a repository.

• OAC5 - Bar Code SettingsTo congure all SAP object type/document type/User ID combinations you want to usewith bar codes for 4.x.

1. Type /NOAC5 in the command window.

2. Click Edit.

3. Click New Entries.The Details of Added Entries window opens.

4. Enter any SAP object types for which you want a bar code dialog to open uponsaving of that object.

5. Enter any SAP document types for which you want a bar code dialog to open uponsaving of that document.

6. Enter any User IDs for which you want a bar code dialog to open upon saving underthat user ID.


8. Enter your object, document, and user ID to test your bar code.

Testing scanning documentsOnce you have completed the customizing described above, you can test documentscanning, linking and viewing the archived images. Refer to Content Services for SAP UserGuide for Scanner Operators for information on the Capture component.

To test scan and link documents:

1. Start Content Services Capture from Programs>Documentum Content Services forSAP.



2. Type your username and password for the repository.

3. In Content Services Capture, scan or import a few pages and fill in the defaultattributes.

4. From the Document Type drop-down list, select Sap_invoice (or other validDocumentum document type).

5. Click the Scan button.

6. Click OK to the message “No Scanner Available”.

7. Choose 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 displays in Content Services Image Viewer, fill in the attributes.

10. Click the Add to Queue button from Content Services Capture and the image shoulddisappear from the Viewer.

11. Minimize Content Services Capture.

12. In SAP, use transactions OAC2, SOA0, OACA, OAC3, OAC0 and OAWS to reviewthe 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 whichmatches the Archive ID information found via OAC3 and OAC0.You can copy and modify an existing incoming document archive.

14. On your Content Services Server, make sure that the Archive Services are startedwith the correct:• RFC Destination• Share user ID• and that you IIS is up and running with HTTP, and certificates have been 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> <yourOAWS 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 the Store For Subsequent Entry icon.

21. Replace the existing text with meaningful text so you will be able to recognize thefile in a later step.

22. Select Continue (Check).



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 Typedialog box opens.

27. Click the Process button.You may need to move the image to see the SAP dialog.The SAP transaction displays.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. Click Enter.

30. In the Amount field, enter any amount you like.

31. In the Doc Header Text field, enter your Vendor Name.

32. Scroll to the bottom of the form and enter the following:• PstKy: 40 Account: 491000

33. Click Enter.

34. In the Amount field, enter the same amount entered in step 7 above 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, enter the display version of the transaction above.

39. Select List and your User ID and Execute.The document you parked above should be displayed.

40. Choose this document.



41. From your displayed document, select Environment>Object Links.

42. Select Archived Documents.The original document now displays.




Chapter 4Creating Custom BAPIs

Content Services for SAP enables you to create and install custom configuration objects — known asBAPIs — for linking and querying SAP data.

To create a custom BAPI you must modify the custom.xml file that is included with the ContentServices for SAP installation files. The installation files are available for downloading fromsubscribenet.com (see the Installation Guide for more details on downloading the release). Aftermodifying the custom.xml file as shown in the example below, when you install Content Services forSAP, the custom BAPI will be available for linking and querying via the Web Admin tool.

In the following example, we are creating a custom BAPI to link and query purchase orders. Thequery 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 ContentServices for SAP. The custom BAPI is installed with the release and is available toend-users only after product installation.

1. Download and install the current release of Content Services for SAP Server. Detailsfor downloading the release are provided in the 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 asappropriate to create your own custom BAPIs. You may copy/paste this sample codeinside 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>


Creating Custom BAPIs

</ATTRIBUTE><ATTRIBUTE NAME="parameter_defaults" IS_REPEATING="true"></ATTRIBUTE><ATTRIBUTE NAME="result_parameters" IS_REPEATING="true"><VALUE>Client=MANDT</VALUE><VALUE>Document_Number=EBELN</VALUE><VALUE>Item_Number=EBELP</VALUE></ATTRIBUTE><ATTRIBUTE NAME="key_attributes" IS_REPEATING="true"><VALUE>Document_Number=EBELN</VALUE></ATTRIBUTE><ATTRIBUTE NAME="methods" IS_REPEATING="true"><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 separateXML elements in the custom.xml file for each custom BAPI.

6. To install the custom BAPIs into your repository, run the Content Services for SAPServer setup.exe file, choose Docbase Configuration, then for the version numberchoose Custom.XML.If you are creating custom BAPI of type "sap_query_type_plm" make sure the keyname for the description field in the result parameters is called "Description" asshown 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 ofthis attribute will be shown as the description in the query result dialog in Manageas shown in the following screenshot. In this example, EKPO_Table is used.






Chapter 5Conguring the DMS Interface for theManage and View Components

The procedures in this chapter assume that the software is installed on at least one PC and that theDocumentum repository is configured according to your business needs. It is assumed that a defaultinstallation of SAP has been performed. If this is not the case, you may find that the installationsteps differ in your R/3 system.

You must customize SAP before you can link documents to it. The customization work is necessary toconfigure the CAD Interface to your needs. Additionally, you must verify a number of parametersand certify that everything is configured properly. This chapter discusses the following topics:

• Configuring the Manage component, page 53• Configuring Document Management Control Data, page 55• Configuring general data, page 60• Configuring CAD integration, page 67• Configuring general data sub-levels, page 69The examples in this chapter also assume a SAP default installation.

Conguring the Manage componentThe complete customization is done in the same SAP menu from SAPGUI.

Conguring the Manage and View components

To congure the Manage and View components for 3.x:

1. Start SAPGUI and connect to R/3.The SAP R/3 window appears.


Conguring the DMS Interface for the Manage and View Components

2. Type /nspro in the command field.A dialog box may or may not be displayed.

3. Click Enter.

4. Click the Enterprise IMG button, F5 or click on the button for your specific project ifyou configure your system on a project basis.The Implementation Guide for R/3 Customizing screen appears:

5. Click on Cross-Application Components, then click on Document Managementfrom the expanded list of items.

To congure the Manage and View components for 4.0:



3. Click Enter.

4. Select Implement Projects>SAP Reference IMG (or click on the button for yourspecific project if you configure your system on a project basis).The Implementation Guide for R/3 Customizing screen appears:

5. Click on Cross-Application Components, then click on Document ManagementSystem from the expanded list of items.

Opening the Document Management Control Datawindow

To open this window for 3.x:


2. Click Enter.

3. Click the Enterprise IMG button, F5 (or click on the button for your specific project ifyou configure your system on a project basis).The Implementation Guide for R/3 Customizingscreen appears:

4. Click on Cross-Application Components, then click on Document Managementfrom the expanded list of items.



To open this window for 4.x:

1. Type /nspro in the command field.

2. Select SAP Reference IMG (or click on the button for your specific project if youconfigure your system on a project basis).The Implementation Guide for R/3 Customizing window appears:

3. Click on Cross-Application Components, then click on Document ManagementSystem from the expanded list of items.This window is the starting point for all configurations described in this chapter.

Conguring Document Management ControlData

You must verify several parameters in Document Management Control Data for 3.x.

1. To navigate there, single-click on the cabinet icons to expand the selection:

2. Cross-Application Components>Document Management>Control Data.The following four items appear in a list:• Define number ranges for document numbers• Define document types• Maintain object link descriptions• Define object links

3. Click on each item (marked with a green tick and a clock) to configure it.The following sections explain how to do this.

You must verify several parameters in Document Management Control data for 4.0.

1. To navigate there, single-click on the cabinet icons to expand the selection:Cross-Application Components>Document Management>Control Data.The following four items appear in a list:• Define number ranges for document numbers• Define document types




You must verify several parameters in Document Management Control data for 4.x.

1. If necessary, open the Implementation Guide for R/3 Customizing window andnavigate to the Document Management System cabinet. (See Opening the DocumentManagement Control Data window, page 54.)

2. To navigate there, single-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


Dening number ranges for document numbers

To check the number ranges:

1. To edit the configuration, click on the Intervals button (marked with a red pen).The Display Number Range Intervals window appears:

2. You should see number ranges configured as in the following example:

Table 5-1. Number ranges

No. From number To number Ext.

01 00000000000000000001 00000000000000999999 Checked

02 00000000010000000000 00000009999999999999 Unchecked

03 00000010000000000000 99999999999999999999 Checked

04 00000000000001000000 00000000009999999999 Checked

3. Save changes if necessary.

4. Click the Back button twice. This returns you to the Document Management ControlData window.

Dening document types

To dene document types for 3.x and 4.0:

1. Start SAPGUI and connect to R/3.



The SAP R/3 window appears.


3. Click Enter.

4. Select Implement Projects>SAP Reference IMG Cross-ApplicationComponents>Document Management>Define Document Types.A list of your configured Document types appears.

5. Starting with the document type DRW, define the parameters for each documenttype.

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 theSAP Query Composer (refer to the “Creating, Viewing, and Editing an SAP Query”section of the 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 thefollowing:• DocumentType=*• DocumentType=

In this case, no value has been assigned to the parameter. The value for theparameter has been set to blank.

6. Click the box at the beginning of the document type line.

7. Click the magnifying glass button.Define the parameters for DRW as described below. Leave other fields blank.


Parameter Setting

Doc. type desc Engin/Des. Drawing

Version Assign. Checked

Ass. of rev. lev Checked

Archiving authorization Checked

Change docs Checked

Internal number range 02

External number range 01



Parameter Setting

Number exit MCDOKZNR

Vers. no. incr. 1

File size 0


9. Click Back twice.This returns you to the Document Management Control Data screen.

To dene document types for 4.x:

1. If necessary, open the Implementation Guide for R/3 Customizing window andnavigate to the Document Management System cabinet. To navigate there,single-click on the cabinet icons to expand the selection: Cross-ApplicationComponents > 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 documenttype 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 theSAP Query Composer (refer to the “Creating, Viewing, and Editing an SAP Query”section of the Content Services for SAP Administration Guide).

Example 5-2.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 thefollowing:• DocumentType=*• DocumentType=

In this case, no value has been assigned to the parameter. The value for theparameter has been set to blank.

4. Click the box at the beginning of the document type line.

5. Click the magnifying glass button.Define the parameters for DRW as described below. Leave all other fields blank.




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


7. Click Back twice.You are returned to the Document Management Control Data window.

Dening and Maintaining Object Link descriptions

To dene and maintain object link descriptions for 3.x:

1. Verify that the following three items are configured and the names are spelledexactly as follows:

Table 5-4. Object Link descriptions

Lang. Object Name

E EQUI Equipment master

E IFLOT Functional location

E MARA Material master

2. Click Back.This returns you to the Document Management Control Data screen.

To dene and maintain object link descriptions for 4.0 and 4.x:

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 spelledexactly as follows:

Table 5-5. Object Link descriptions

Lang. Object Name

EN EQUI Equipment master

EN IFLOT Functional location

EN MARA Material master

4. Click Back twice.You are returned to the Document Management Control Data window.

Conguring general dataThis section explains how to configure several required parameters that are usually notconfigured in a default R/3 installation.

To congure general data for 3.x and 4.0:



3. Click Enter.

4. Select Implement Projects>SAP Reference IMG Cross-ApplicationComponents>Document Management>General Data.

5. Close the Document Management Control Data screen and navigate to the GeneralData level.The following items are listed:• Define data carrier types• Define data carriers• Identify front-end computers• Define workstation applications• Define workstation applications in network

6. Click on each item (marked with a green tick and a clock) to configure it.



The following sections explain how to do this.

To congure general data for 4.x:

1. If necessary, open the Implementation Guide for R/3 Customizing window andnavigate to the Document Management System cabinet. (To navigate there,single-click on the cabinet icons to expand the selection: Cross-ApplicationComponents>Document Management>General Data.)

2. Select General Data.The following items are listed:• Define data carrier• Define workstation application• Maintain CAD systems


Dening 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 DataCarrier Type window:

• Define data carrier type “external DMS”• Define “external DMS” (document management system)• Define data carrier type “server, front end”• Identify frontend computers

Dening external DMS

To congure the DMS for 4.0:

1. Click the New Entries Button.

2. Define the following parameters:• Data Car. = DOCUMENTUM• TY = EX• Description = Documentum

3. Save the new entry. You should then go on to define the data carrier type “server,front end”.



To congure the DMS for 4.x:

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”.

Dening data carrier type “server, front end”

Use the following procedure to congure a new carrier type for 3.x:

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 the New Entries button and set the parameters

as listed in step 2.2. Define the following parameters:

• Data car. type = PC• Online = checked• Printer = unchecked• Vault = unchecked• Ex = checked• CAD System = DEMO• Description = External DMS


4. Exit this dialog.

5. Click Back.You should then go on to define the data carrier

Use the following procedure to congure a new carrier type for 4.0 and 4.x

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 the New Entries button and set the parameters

as listed in step 2.2. Define the following parameters:

• Type = PC• Description = Windows PC• Online = Checked• The Path entry should be left blank.



5. Click Back.You should then go on to define the data carrier.

Identifying Front-end computers

Use the following procedure to congure a default front-end computer (if not alreadycongured) for 3.x:

1. Click the New Entries button.

2. Define the following parameters:• DataCar = DEFAULT• Ty = PC• Net address = DEFAULT• Description = Windows View component for default PC.



5. Click Back.You should then go on to define the workstation applications.

Use the following procedure to congure a default front-end computer (if not alreadycongured) for 4.0 and 4.x:

1. Navigate to the Define data carrier type “server, front end” option and select thetype 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 adifferent data carrier. If this is the case, continue to use this data carrier fromnow on, instead of PC.



6. Click Back.You should then go on to define the workstation applications.

Dening workstation application

This section describes how to configure the following settings under the DocumentManagement System Control Data window[Symbol_ZapfDingbats_228] GeneralData[Symbol_ZapfDingbats_228]Define workstation application section. The followingentries must be configured in this window:

• Define workstation application• Define workstation applications in networkTo congure a workstation application for 3.x:


2. Define the following parameters:• WS application = DCM• StartAut = checked• Description = Documentum View component• All the other check boxes must be unchecked



5. Click Back.You should then proceed to define the Workstation Applications in a Network.

To congure a workstation application for 4.0 and 4.x:

1. Navigate to the “Define workstation application” settings in the WorkstationApplication dialog.




3. Define the following parameters:• 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.


Dening workstation applications in network

To congure a workstation application in the network for 3.x:

1. Click the New Entries Button.Define the following parameters:• DataCar type = PC• Applic. = DCM• ApplTyp = 1 (Display)You can configure Content Services to provide a print button in addition to a viewone. This option is not available under WebView. To configure printing, add anidentical entry which has the ApplTyp = 3 (Print) and define the program asdmview.exe /print %f

• Program = dmview.exeIf you have installed the View component somewhere other than the default SAPmain program directory, you must define the path.If you installed WebView for viewing documents, you should define the Program as:dmwebview.exe %f host/rs-bin/RightSite.dll

This configuration may look different for a UNIX Web server.• SourcePath = [leave this field empty]• StartAuth = Yes• Description = Documentum View component



4. Click Back.This is the final task for document management customization.



To congure a workstation application in the network for 4.0:

1. Navigate to the “Define workstation applications” settings in the WorkstationApplication dialog.

2. Select the DCM entry and navigate to “Define workstation applications in network”.

3. Click New Entries and enter the following parameters:• WS application = DCM (this entry is read only)• Data carr. type = PC• Application Type = 1 (Display)You can configure Content Services to provide a print button in addition to a viewone. This option is not available under WebView. To configure printing, add anidentical entry which has the Application Type = 3 (Print) and define the program asdmview.exe /print %f

• Path with prog. name = dmview.exeIf you have installed the View component somewhere other than the default SAPmain program directory, you must define the path.If you installed WebView for viewing documents, you should define the Program as:dmwebview.exe %f host/rs-bin/RightSite.dll

This configuration may look different for a UNIX Web server.• Path for ref. file = [leave this field empty]• Start Authorization = Yes



6. Click Back.

To congure a workstation application in the network for 4.x:

1. Navigate to the “Define workstation applications” settings in the WorkstationApplication dialog.

2. Select the DCM entry and navigate to “Define workstation applications in network”.

3. Click New Entries.Under 4.6, it is not possible to pass program arguments. For example, this meansthat it is not possible to launch dmview.exe with program arguments such as /PRINTto trigger the print function or the arguments required to use anonymous login. Toget around this problem, see OSS notes: 0135155 and 0105208.

4. Enter the following parameters:• WS application = DCM (this entry is read-only)



• Data carr. type = PC• Application Type = 1 (Display)• Path with prog. name = dmview.exeIf you have installed the View component somewhere other than the default SAPmain program directory, you must define the path.If you have installed WebView for viewing documents, you must define the programas dmwebview.exe. (The previous note about passing program arguments appliesalso to dmview.exe. For example, If webview.exe is called without command lineparameters, the user is prompted to fill in the host name under which the Webapplication 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 congure and verify the CAD systems for 4.x:

1. Select Maintain CAD Systems.

2. Click New Entries.

3. Enter the following parameters:• CAD System = DEMO• Description = Documentum.



Conguring CAD integrationGo up one level and enter the CAD Integration configuration area of the IMG guide.

Select the Define control parameters entry.



To congure and verify the control parameters for 3.x and 4.0:


2. Type /NSPRO in the command field.A dialog box may or may not be displayed.

3. Click Enter.

4. Select Implement Projects>SAP Reference IMG Cross-ApplicationComponents>Document Management>CAD Integration.

5. Edit or verify the following parameters:• Max. number of matchcode recs = 50• Separator in data-string = @ (hex 40)• Max. length of send string = 03001The remaining parameters on this screen are not relevant and do not need to beedited.


7. Exit this dialog.Save the settings even if nothing was modified. The parameters given above arethe default parameters.You may receive an error message here stating that control parameters are notdefined for the current client. If this happens, save the settings even if you havenot modified anything.

To congure and verify the control parameters for 4.x:

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 = 03001The remaining parameters on this window are not relevant and do not need to beedited.


4. Exit this dialog.Save the settings even if nothing was modified. The parameters given above arethe default parameters.



You may receive an error message here stating that control parameters are notdefined for the current client. If this happens, save the settings even if you havenot modified anything.

Conguring general data sub-levelsThis section describes how to verify the basic configuration values for the sub-levelsassociated with the CAD Integration General Data level.

Verifying the values in the general data sub-levels ensures that the CAD Interface isproperly configured. This interface is defined with a number of tables that are configuredfor client 000 for 3.x and 100 for 4.x when the SAP server is installed. Because these tablesare not always duplicated to other clients it’s important to verify them.

Note: The lists displayed in this manual do not show the complete tables but they showitems that must be there. If the number of items in your tables is much lower than thenumbers given in this manual, then your tables may not be complete. In this case, copy anew set of tables from client 000. Do not try to enter these values manually.

Dening functions

Use the Position button to verify that the following items in the table are defined. Thistable must contain about 180 entries:.

Table 5-6. Function values

Proc. Code Sub-process code

DOCCH DO

DOCCR MR

DOCRQ CL

EQUIRQ MR

MATRQ MR



Allocating eld sets

The following entries must be configured. This step allows you to verify whether theCAD system name as configured in Defining Data Carrier and Data Carrier Types,page 61 is correct.

Use the position button to find the following items:

• CAD system = DEMO• Proc. Code = DOCCR• Sub -process code = MR• Direction = U• Set name = DCCRDAT

Dening eld sets (CAD->SAP)

Choose General Data>Define field sets>CAD>SAP to define CAD Field Sets. This tablecontains more than 300 items. The following items must be configured:

Table 5-7. CAD eld 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


Chapter 6Conguring SAP for PP-PI

Documentum Content Services for SAP allows you to link documents stored in a Documentumrepository to an SAP PP-PI (Production Planning for Process Industries) instruction sheet. Documentsare thus directly accessible from SAP PP-PI sheets.

SAP PP-PI modules control the manufacturing process in process industry environments. PP-PIallows you to define hyperlinks to external applications, enabling you to retrieve documents (such asrecipes or SOPs) from a Documentum repository by using a configurable query together with specificparameters. This mechanism is very flexible and is independent of the Documentum or ArchiveLinksystem. Documents are linked to SAP PP-PI with a query stored in Documentum.

This information in this chapter assumes that the Content Services View is installed on at least one PCand 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 sectionexplains how to create and configure the mandatory new process instruction categories. Theseconcepts are described in the following sections:

• Configuring the Process Instruction category, page 71• Defining Process Instruction category DCTM, page 72• Configuring the Characteristics/Process Instruction category, page 72

Conguring the Process Instruction categoryTo get into the SAP customization menu follow these steps:

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. Click Enter to exit the dialog box.

4. Click the Enterprise IMG button (or click your specific project if you configure yoursystem on a project base).


Conguring SAP for PP-PI

This brings you to Implementation Guide for R/3 Customizing window.

5. Navigate to the process instruction categories subfolder.To get there, click Production Planning for Process Industries folder>Processmanagement>Process instructions>Process instruction categories for the R/3 PI sheet.

6. Click on Define Process Instruction Categories.

Dening Process Instruction category DCTMTo congure 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.

Conguring the Characteristics/ProcessInstruction category

To congure the Characteristics/Process Instruction category:You must have a screen resolution of at least 600x800 to be able to enter characteristicsof the new process instruction category.

1. Click on Characteristics/Process instruction category.

2. Enter the value for PPPI_FUNCTION_NAME.The default value for this field is WS_EXECUTE

3. Enter the value for PPPI_BUTTON_TEXT.The default value is Show Related Documents. This text can be changed to reflectyour customized installation.

4. Enter the value for PPPI_EXPORT_PARAMETER.The default value for this field is ‘PROGRAM’

5. Enter the value for PPPI_STRING_CONSTANT.This field specifies the absolute path or relative path (if installation directory is in thePATH environment variable on every PC) of the Content Services View executable.



The default location of the Content Services View executable is the SAPGUIinstallation directory. This is a system-wide setting.The maximum numbers of characters is 30.

6. Enter the value for PPPI_EXPORT_PARAMETER.The default value for this field is COMMANDLINE.

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

8. Enter the value for the characteristics described below.


Characteristic Default characteristic value

/ Comments

PPPI_FUNCTION_NAME WS_EXECUTE

PPPI_BUTTON_TEXT Show Related Documents

This text can be changed to reflect yourcustomized installation.

PPPI_EXPORT_PARAMETER PROGRAM

PPPI_STRING_CONSTANT This field specifies the absolute path orrelative path (if installation directory is inthe PATH environment variable on everyPC) of the Content Services View executable.The default location of the Content ServicesView executable is the SAPGUI installationdirectory. This is a system-wide setting.

The maximum numbers of characters is 30.



Characteristic Default characteristic value

/ Comments

PPPI_EXPORT_PARAMETER COMMANDLINE

PPPI_STRING_CONSTANT The value of this field is the command linepassed to Content Services View. You mayeither leave this field blank for now, or enterthe repository name and the query name. Thecommand line has some constraints:

• The maximum string length is 30 characters.• All letters are capitalized.




Index

AAdministrative Console, 15Agent services, 15ALF, 38, 40ALF class, 16ALF format, 16Anonymous Login

protocol, 29archived and deleting documents,

deleting, 42archived data, 16archived Print List

displaying in SAPGUI, 41ArchiveLink Monitor window, 41archiving

Print List, 40archiving reports

testing, 40Archiving request window, 41Archiving Server, 14asynchronous queue, 21

Bbar codes, 44basic settings, configuring, 20

CCAD field sets, 70CAD Integration, configuring, 67capture operator, 7class

ALF, 16FAX, 16OTF, 16REO, 16

configuration procedures, 36, 67configuring

basic settings, 20Manage, 53

number ranges, 21optical archive as output device, 22

content repositories, 33Content Services, see Content Services for

SAPContent Services for SAP, 7

defined, 13Content Services for SAP administrator, 7Content Services server, 38creating

queues, 21creating links, 7CS for SAP, see Content Services for SAP

DDB2, 7defining

document types, 38links, 39logical ArchiveID, 20

deletingarchived and linked documents, 42

displayingarchived Print List in SAPGUI, 41

dmview.exe, 65 to 67document

incoming, 16outgoing, 16scanned, 16supported formats in SAP, 16

document controller, 7document formats, supported in SAP, 16Document Management General Data, 64

to 66, 69document types

ALF, 38defining, 38FAX, 38OTF, 38REO, 38


Index

documents, 42, 55

Ff.21, 40FAX, 38, 42FAX class, 16field sets, allocating, 70format

ALF, 16PDF, 16REO, 16Tiff, 16

frequency of archival, 22

GGeneral Data, 69 to 70

IInline Print List Viewer

protocol, 30intended audience, 7

Jjobs, scheduling, 22

Llinking, 42links

defining, 39logical ArchiveID

defining, 20

Mmaintaining links, 7Manage, 53 to 55

Nnumber ranges, configuring, 21

Ooaa4, 27oaat, 22oac0, 20, 33OAC0, 34

oac2, 38oac3, 39oadr, 41oag1, 20oam1, 21oanr, 21oaq1, 21oaqi, 21OAWS, 42OLE, application, 25optical archive, configuring as output

device, 22Oracle, 7OTF, 38OTF class, 16output device

configuring logical archive as, 22

PPDF format, 16prerequisites

system administrator, 7Print List, 40

archived, displaying in SAPGUI, 41archiving, 40

Print Lists, 16ALF class, 16ALF format, 16

protocolAnonymous Login, 29Inline Print List Viewer, 30

purpose of the guide, 7

Qqueues, creating, 21

Rreleasing documents to SAP, 7REO, 38REO class, 16REO format, 16Reports, see Print ListsRFC destination archive, 36

SSAP

print spooler, 24


Index

supported document formats in, 16transaction code, f.21, 40transaction code, oaat, 22transaction code, oac0, 20, 33transaction code, oac2, 38transaction code, oac3, 39transaction code, oadr, 41transaction code, oag1, 20transaction code, oam1, 21transaction code, oanr, 21transaction code, oaq1, 21transaction code, oaqi, 21transaction code, sm50, 24transaction code, spad, 22transaction code, spro, 19

SAP Document Classescustomizing, 33

SAP Server, 53 to 55SAP Workflow, 43SAPGUI

ArchiveLink Monitor window, 41Archiving request window, 41displaying archived Print List in, 41Queue Administrator field, 21

scanning documents, 7scheduling

jobs, 22settings, 42sm50, 24SM59, 36 to 37SOLE, 25spad, 22SPO process, 24spool process, 24spool processes, verifying, 24spro, 19SQL Server, 7standard user, 7supported databases, 7

DB2, 7Oracle, 7SQL Server, 7Sybase, 7

supported document formats in SAP, 16ALF class, 16

ALF format, 16FAX class, 16OTF class, 16PDF format, 16REO class, 16REO format, 16Tiff format, 16

Sybase, 7system administrator, 7

prerequisites, 7

Ttest scanning, 44testing the connection, 37Tiff format, 16transaction code

f.21, 40oaat, 22oac0, 20, 33oac2, 38oac3, 39oadr, 41oag1, 20oam1, 21oanr, 21oaq1, 21oaqi, 21sm50, 24spad, 22spro, 19

Transfer drctry field, 20

Uueue Administrator field, 21user roles, 7

Vverifying, spool processes, 24View, 53 to 55

WWebAdmin, 15
