EMC Documentum ContentServicesforSAP · ContentServicesforSAP—documentationsuite Title...

EMC® Documentum®

Content Services for SAPVersion 6.0

Configuration GuideP/N 300005495 Rev A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748‑91031‑508‑435‑1000www.EMC.com

Copyright © 2004 ‑ 2007 EMC Corporation. All rights reserved.

Published September 2007

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up‑to‑date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Table of Contents

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

Chapter 1 Introducing Content Services for SAP ................................................... 11Overview ................................................................................................... 11Content Services for SAP architecture .......................................................... 12Supported SAP document formats............................................................... 14SAP and Content Services for SAP terms...................................................... 14

Chapter 2 Configuring 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 ................................................................. 25sole ‑ Maintaining OLE applications ............................................................ 25oaa4 ‑ Maintaining applications and configuring communicationsprotocol ..................................................................................................... 27Special protocols..................................................................................... 29Protocol for anonymous logins ............................................................ 30Protocol for the SAP Inline Print List viewer......................................... 31Protocol for HTTP display................................................................... 32

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

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

Deleting archived and linked documents ..................................................... 42Customizing FAX ‑ scanned documents ....................................................... 43oaws – Settings....................................................................................... 43Optional for SAP workflow ..................................................................... 44Optional for barcode............................................................................... 44OAC5 ‑ Bar Code Settings ................................................................... 45

EMC Documentum Content Services for SAP Version 6.0 Configuration Guide 3

Table of Contents

Testing scanning documents........................................................................ 45

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

Chapter 5 Configuring 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 ....................................... 54Defining number ranges for document numbers....................................... 55Defining document types ........................................................................ 55Defining and maintaining object link descriptions .................................... 56

Configuring general data ............................................................................ 57Defining Data Carrier and Data Carrier Types .......................................... 57Defining external DMS ....................................................................... 58Defining data carrier type “server, front end” ....................................... 58Identifying front‑end computers.......................................................... 59

Defining workstation application............................................................. 59Defining workstation applications in network ...................................... 60

Maintaining CAD systems ...................................................................... 61Configuring CAD integration ...................................................................... 61Configuring general data sub‑levels............................................................. 62Defining functions .................................................................................. 62Allocating field sets ................................................................................ 62Defining field sets (CAD > SAP) .............................................................. 63

Chapter 6 Configuring SAP for PPPI .................................................................... 65Configuring the Process Instruction category ............................................... 65Defining Process Instruction category DCTM ............................................... 66Configuring the Characteristics/Process Instruction category......................... 66

4 EMC Documentum Content Services for SAP Version 6.0 Configuration Guide

Table of Contents

List of Figures

Figure 1. Content Services for SAP and SAP ................................................................... 12


Table of Contents

List of Tables

Table 1. Terms and definitions ..................................................................................... 15Table 2. Field descriptions of change output device screen............................................. 23Table 3. Field descriptions of change output device screen............................................. 24Table 4. Field descriptions ........................................................................................... 25Table 5. Field descriptions ........................................................................................... 26Table 6. Field descriptions ........................................................................................... 27Table 7. Field descriptions ........................................................................................... 28Table 8. Field descriptions ........................................................................................... 30Table 9. Field descriptions ........................................................................................... 30Table 10. Field descriptions ........................................................................................... 32Table 11. Field descriptions ........................................................................................... 34Table 12. Field descriptions of New Entries table ............................................................ 40Table 13. Number ranges .............................................................................................. 55Table 14. Field descriptions ........................................................................................... 56Table 15. Object Link descriptions.................................................................................. 57Table 16. Function values .............................................................................................. 62Table 17. CAD field sets ................................................................................................ 63Table 18. Field descriptions ........................................................................................... 67


Preface

Purpose of this guideThis guide explains how to configure SAP to use EMC® Documentum® Content Servicesfor SAP 6.0 (CS for SAP 6.0 or Content Services 6.0). This guide provides task‑basedinstructions for configuring SAP, so that SAP 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 for SAP. The Content Services for SAP application integrates EMCDocumentum and the SAP R/3 system. Therefore, system administrators musthave experience with the software products listed in the EMC Documentum ContentServices for SAP Release Notes.

• Content Services Administrator — This role covers users who manage ContentServices using WebAdmin.

• Document Controller — This role covers those who release documents to SAP andmaintain the links to those documents.

• Capture Operator — This role covers users who scan documents and create links tothe appropriate records in SAP.

• Standard User — This role covers users who view documents using SAPGUI and theView component of Content Services.

This manual is intended for system administrators.

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


Preface

Revision history

Revision date Description

September 2007 Initial publication of document forContent Services for SAP 6.0.

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 EMC Powerlink, located at: http://powerlink.emc.com.

From Powerlink, you can download the latest version of Content Services for SAP andthe related documentation suite. To access the contents in Powerlink, 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.

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


https://documentum.subscribenet.com

Preface

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 the SAP ArchiveLink component. Refer to yourSAP ArchiveLink documentation for information on how you can perform advancedtasks.


Preface


Chapter 1Introducing Content Services for SAP

OverviewThe EMC® Documentum® Content Services for SAP application integrates theDocumentum content management system with the SAP R/3 system. It is an interface tothe SAP R/3 system based on SAP standard Document Management System (DMS) andArchiveLink 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 ArchiveLink certified interfaces

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


Introducing Content Services for SAP

Content Services for SAP architectureFigure 1. Content Services for SAP and SAP

Content Services for SAP consists of the following components:

• Agent services

A server component that allows you to automate the linking between SAP objectsand 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 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 client computer that needsto access reports, drawings, and other documents stored in a Documentumrepository.

• Rendition Services

Built‑in filters that provide the following renditions:

— PDF rendition

— ASCII text rendition

— HTML rendition

When one of these built‑in filters is used, the appropriate document rendition isgenerated when the Print List is archived in the repository.

Note: This component is only relevant when your environment includes parallelinstallations of Content Services for SAP and Archive Services for SAP.



• WebAdmin

An administrative console that allows you to:

— Perform archiving services.

Note: Your environment should have coexisting installations of Content Servicesfor SAP and Archive Services for SAP in order to leverage these services.

Using WebAdmin, you can perform the following archiving services:

— Create, configure, and manage archives.

— Manage certificates for the archive.

— Create repository connections for Content Services.

— Create workflows and associate the same with archived documents.

— Configure document archival for Content Services.

— Perform DMS‑related services. You can:

— Configure batch jobs for linking and replication tasks.

— Schedule and manage the execution of linking and replication jobs.

Note: The EMC Documentum Content Services for SAP Release Notes provides detailedinformation about 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)

SAP and Content Services for SAP termsThis section presents terms and definitions used in this guide.



Table 1. Terms and definitions

Term Definition

Content Services for SAP Product that connects Documentum toand from SAP.

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

WebAdmin An administrative console that allows youto:• Perform archiving services.

Note: Your environment should havecoexisting installations of ContentServices for SAP and Archive Services forSAP in order to leverage these services.Using WebAdmin, you can perform thefollowing archiving services:

— Create, configure, and managearchives.

— Manage certificates for the archive.— Create repository connections forContent Services.

— Create workflows and associate thesame with archived documents.

— Configure document archival forContent Services.

• Perform DMS‑related services. Youcan:



Term Definition

— Configure batch jobs for linking andreplication tasks.

— Schedule and manage the executionof linking and replication jobs.

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 withthird‑party scanning applications likeEMC Captiva® InputAccel®. The importmodule is part of the same application asContent Services Capture. The ContentServices Capture can operate in twodifferent modes (scan and 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 personnelinvolved 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 11.An invoice can 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 2Configuring the ArchiveLink Interfacefor Content Services for SAP

OverviewYou can store and retrieve documents, reports, and data through SAP ArchiveLinkand 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 be 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• sm50 – Verifying spool processes, page 25


Configuring the ArchiveLink Interface for Content Services for SAP

• sole ‑ Maintaining OLE applications, page 25• oaa4 ‑ Maintaining applications and configuring communications protocol, page 27

oac0 — Defining a logical ArchiveIDNote: The name of the logical ArchiveID must be the same as the ArchiveID createdusing WebAdmin, as described in the EMC Documentum Content Services for SAPAdministration Guide.

To define a logical ArchiveID in SAP:

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

2. In the Display Content Repositories: Overview page, click on any 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 iti s the same as ArchiveID created usingWebAdmin, as described in the EMC Documentum Content Services for SAPAdministration Guide).

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

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

Note: Type the IP address of your system in this field.

8. In the HTTP Script field, type the following:/<virtual_directory>/archivelink/<nameofrepository>

<virtual_directory> refers to the AS SAP virtual installation directory.

9. To save the logical ArchiveID configuration, select Content Repository > Save.

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

To configure 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 – Configuring number rangesYou must configure the number ranges for ArchiveLink.

To configure 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. Enter the following in the ABAP Program field:ILQBATCH

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


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

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.


12. Click Exit.

spad – Configuring 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 device



includes 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 configure an optical archive as the output device:

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

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

3. Click Output Devices.

4. Click the pencil button to edit settings.

Note: You can only have one printer and that printer must be named ARCH. 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 Delete.

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

7. Fill in the fields listed below:

Table 2. Field descriptions of change output device screen

Field name Value

Output Device ARCHIVE

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

13. Fill in the ArchiveID you plan to use for Print lists. For example, AA.

14. Type ARCH into the Output Device field.Repeat steps 13 and 14 for each archive.

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

To configure an optical archive as the output device for the Documentuminstallation:

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

2. Click Output Devices.

3. Click the pencil button to edit settings.

Note: You can only have one printer and that printer must be named ARCH. 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 New Entries.The Change Output Device window opens.

6. Fill in the fields listed below.

Table 3. Field descriptions of change output device screen

Field name Value

Host Printer a

Device Class A

Access Method to Host Spool I

Device Type ARCHLINK SAP ArchiveLink Archiver

Spool Server Select spool server from 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 configure 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.The Details screen opens.


Table 4. Field descriptions

Field name Value

OLE Application DOCLINKSCAN.DOCUMENT



Field name Value

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.The Details screen opens.



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, leaving the other fields 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.DOCUMENTand DOCLINKSCAN.DOCUMENT.

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 configuringcommunications protocol

Complete the following procedure to map the OLE 2 methods just defined under SOLEthat are called when a document is archived from Content Services Capture or when adocument is displayed. The OLE 2 methods are assigned when the archive is configuredvia PROTOCOL. Each pair of document type and SAP object type maps to an archive.For example, when a document is archived, the document type and object type point toan archive. The archive in turn is configured to use a certain protocol. From the protocolthe SAPGUI determines how documents are to be scanned and viewed through OLE.

To configure applications’ maintenance and the communications protocolto associate the correct OLE 2 method to an SAP archive:

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. Return 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 for SAP 5.3 SP3.

15. Enter the appropriate version of the protocol as follows:• RFC‑based archiving — version 0031• HTTP based archiving — version 0045

Note: You may need a protocol for each type if you plan to use RFC and HTTParchiving for 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 Protocol 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 Enter.

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.

27. Press the [Enter] key.


29. Save your changes.If you repeat steps 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 using 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 next procedure.

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 next procedure.

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 configure the Print List viewer to display the Print Lists in SAPGUI:

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 as follows:• RFC based archiving — version 0031• HTTP based archiving — version 0045

Note: You may need a protocol for each type if you plan to use RFC and HTTParchiving for 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.

8. Press Enter.


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.



No application is entered here.

13. Save your changes.You are returned to the Overview of a Protocol window.If you repeat steps 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:

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



S DOCBASE=<Your_Repository_Name>

M Display @DID

G @EID=ERRORCODE

G @ETX=ERRORTEXT


Chapter 3Customizing SAP Document Classes

This chapter describes how to archive document classes from SAP. The customization of each SAPsetup is different depending on which document class the archived document belongs to. Thedocument 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 34• sm59 – RFC destination archives, page 36• oac2 ‑ Defining document types, page 39• oac3 ‑ Defining links, page 39• ALF Reports/Print Lists, page 40• Deleting archived and linked documents, page 42• Customizing FAX ‑ scanned documents, page 43• Testing scanning documents, page 45


Customizing SAP Document Classes

oac0 – Configuring content repositoriesSAP allows you to define a content repository (previously known as a logical archive).This content repository is mapped to a Documentum archive using WebAdmin. TheDocumentum archive links to a set of rules such as content folders, Documentumdocument types, and so on in the Documentum repository. Store each document typein a separate archive. Using WebAdmin, you must create a matching archive for eachArchiveID defined in SAP. This ArchiveID defines what actions (types, folders, retention,and so on) are applied on a SAP document when it is archived. The following sectionsexplain how to create an archive in SAP for each represented document class.

When configuring Archives, you can configure either an HTTP‑based Archives or RFC(Remote Function Call) Archives. The configuration steps differ between RFC‑ andHTTP‑based archives. The configuration steps below have been listed as being relevantonly to RFC‑ or HTTP‑based archiving.

Note: Documentum recommends that all new installations be 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 define a SAP content repository (archive):

1. Execute one of the following transactions:• oac0

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 Meaningful name. For example, SAP Print Lists (AA)

Storage Type Select HTTP or RFC



Field name Value

Protocol Previously configured protocol.

Version No. 0045 for HTTP or 0031 for RFC

Output Device ARCHIVE

8. For HTTP– or RFC–based archiving, type appropriate values in the following fields:• For HTTP–based archiving:

— HTTP server

Type the hostname or IP address of the Archive Services host. If you use aserver name here, ensure that you can ping the server by name from theSAP server.

— Port Number

Type the port number being used (default is 80).

When using a default Tomcat configuration, this value is usually 8080.

— HTTP Script

Type the following value in this field: <virtual‑directory>/archivelink/<repository>

<virtual‑directory> is the directory on which the software is installed.

where <repository> is the name of the repository into which you will bearchiving content. You must configure a corresponding archive in theArchive Services, using WebAdmin.

— Basic path

Type the file system path to the location where SAP will put archiveddocuments to be picked up by Archive Services.

— Arch path

Usually, the same as the Basic path.



• For RFC–based archiving:

— RFC destination

Type the RFC destination that you created previously. Refer to sm59 – RFCdestination archives, page 36.

— Basic path

Type the file system path to the location where SAP will put archiveddocuments to be picked up by Archive Services.

— Arch path

Usually, the same as the Basic path.Repeat this procedure to define additional archives. You may use this procedure todefine any EMC 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 configure the RFC destination:

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

2. Execute the following 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 whichis 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 using the Content Services installation program and started withthe SHARE user ID, as described in the EMC Documentum Content Services for SAPInstallation Guide) before you begin this procedure.

Note: Content Services for SAP does not include the RFC archiving services component;this component has been moved to Archive Services for SAP 5.3 SP3. The instructionscontained in this section are relevant only if you have parallel installations of ContentServices for SAP 5.3 SP3 and Archive Services for SAP 5.3 SP3 in your environment.



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:• For Microsoft Windows NT, in the registry:

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

• For 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 using ContentServices.

7. Click 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 using 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 Defining 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 define 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 Defining 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 define 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.


Table 12. 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 tableswhere links will be maintained.TOA01‑TOA03.

Ret Prd. 0


ALF Reports/Print ListsTo customize ALF ‑ Reports/Print Lists perform the following procedures:

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

Testing archiving reports

Once you have completed the configuration procedures in this section, you shouldtest the 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 Execute.

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

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

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

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

Note: Whenever you edit a parameter in this dialog box, check the Show SelectedPrint Parameters on Initial Screen checkbox. This ensures that the customizedsettings are available in the initial Print Screen List dialog box.

7. Verify that the Object Type and Document Type fields contain the correct values,as configured in the New Entries table in oac3 ‑ Defining links, page 39. Pick thefollowing 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 39 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 newlyarchived 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.

Do not delete the original version of objects that are linked to SAP if you want tomaintain their link to SAP. If you need to delete version 1.0 of a document, but want tokeep the link to SAP, then, after deleting the document, you must relink the object toSAP, outside of Content Services.



Customizing FAX scanned documentsTo customize FAX ‑ scanned documents, you must perform the following procedures:

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

• oaws – Settings, page 43• Optional for SAP workflow, page 44• Optional for barcode, 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 workflow

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

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

Optional for barcode

Barcodes are a good way to automatically scan and link documents that have alreadybeen entered into SAP transactions from paper. For example, you can enter an invoicewith a barcode sticker, type or wand the barcode number and later, when all the invoicesare 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 Settings

To configure all SAP object type/document type/User ID combinations for use withbar codes:

1. Type /NOAC5 in the command window.

2. Click Edit.


The Details of Added Entries window opens.

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

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

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


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

Testing scanning documentsOnce you have completed the customizing described above, you can test documentscanning, linking and viewing the archived images. Refer to EMC Documentum ContentServices for SAP Scanner Operator User Guide for information on the Capture component.

To test scan and link documents:

1. Start Content Services Capture from Programs > Documentum Content Servicesfor SAP.

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

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 Content Services Capture > Add to Queue and the image disappears fromthe 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 with 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> <your OAWS setting>.Size the windows so that you can see both SAP and Capture.

19. Select the SAP document type which points to your user ID.

20. Click Store For Subsequent Entry.

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

22. Check Continue.The item is removed from the Content Services Capture Queue.

23. Exit out of the SAP dialog box.

24. Close Content Services Capture.To process the document in SAP, post it and link it to an SAP record.

25. In the SAP inbox type /NSIN1.

26. Go to Workflow and double‑click to launch a workitem.



The image should be retrieved from Documentum. The Process Document Typedialog box opens.

27. Click Process.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. After modifying the custom.xml file as shown in the examplebelow, when you install Content Services for SAP, the custom BAPI will be available for linkingand querying via the Web Admin tool.

The following example details creating a custom BAPI to link and query purchase orders. The querytype 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></ATTRIBUTE>


Creating Custom BAPIs

<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 5Configuring 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 54• Configuring general data, page 57• Configuring CAD integration, page 61• Configuring general data sub‑levels, page 62The examples in this chapter also assume a SAP default installation.

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

Configuring the Manage and View componentsTo configure the Manage and View components for :

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


Configuring the DMS Interface for the Manage and View Components

2. Type /nspro in the command field.

3. Press 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 Cross‑Application Components, then click Document Management from theexpanded list of items.

Opening the Document Management Control Datawindow

To open this window:

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

Configuring Document Management Controldata

You must verify several parameters in Document Management Control data:

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

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

3. Click on each item to configure, as described in the following procedures.



Defining number ranges for document numbersTo check the number ranges:

1. To edit the configuration, click on Intervals (marked with a pen icon).The Display Number Range Intervals window appears, showing number rangesconfigured as shown below.

Table 13. Number ranges

No. From number To number Ext.

01 00000000000000000001 00000000000000999999 Checked

02 00000000010000000000 00000009999999999999 Unchecked

03 00000010000000000000 99999999999999999999 Checked

04 00000000000001000000 00000000009999999999 Checked

2. Save changes if necessary.

3. Click Back twice. This returns you to the Document Management Control Datawindow.

Defining document typesTo define document types:

1. If necessary, open the Implementation Guide for R/3 Customizing window andnavigate to the Document Management System cabinet. Click on the cabinet icons toexpand Cross‑Application Components > Document Management > Control Data.

2. Select Define Document Types.A list of your configured Document types appears.

3. Starting with the document type DRW, define the parameters for each 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, as described in the EMC Documentum Content Services forSAP Administration Guide.

Example 51.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.

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


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

Defining and maintaining object link descriptionsTo define and maintain object link descriptions:

1. Select the document type.

2. Select Document Types >Maintain Object Link Descriptions.

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



Table 15. Object Link descriptions

Lang. Object Name

EN EQUI Equipment master

EN IFLOT Functional location

EN MARA Material master

4. Click Back twice.The Document Management Control Data window reappears.

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

To configure general data:

1. If necessary, open the Implementation Guide for R/3 Customizing window andnavigate to the Document Management System cabinet. Click on the cabinet icons toexpand Cross‑Application Components > Document Management > General Data.

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

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

Defining Data Carrier and Data Carrier Types

Select Define data carrier from the list.

This section describes how to configure the following settings under the Define DataCarrier Type window:

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



• Identify fron‑tend computers.

Defining external DMS

To configure the DMS:

1. Select Define external DMS.


3. Define the following parameters:• TY = EX• Description = Documentum• Online and EX checked

4. Select Define External DMS.

5. Create a Data Carrier called Documentum of type EX with description =Documentum.

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

Defining data carrier type “server, front end”

To configure a new carrier type:

1. Verify that type PC exists in the listing:• If the type PC exists, verify the parameters listed in step 2.• If the type PC does not exist, click New Entries and set the parameters as listed

in step 2.2. Define the following parameters:

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


4. Exit this dialog.

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



Identifying frontend computers

To configure a default frontend computer (if not already configured):

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.

Defining workstation application

This section describes how to configure the following settings under the DocumentManagement System Control Data window > General Data > Define workstationapplication section. The following entries must be configured in this window:

• Define workstation application• Define workstation applications in network

To configure a workstation application:

1. Navigate to 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.


Defining workstation applications in network

To configure a workstation application in the network:

1. Navigate to the Define workstation applications settings in theWorkstationApplication 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 systemsTo configure and verify the CAD systems:

1. Select Maintain CAD Systems.


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



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

Select the Define control parameters entry.

To configure and verify the control parameters:

1. Select CAD Integration.

2. Edit or verify the following parameters:• Max. number of matchcode recs = 50• Separator in data‑string = @ (hex 40)• Max. length of send string = 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.



Configuring general data sublevelsThis 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 100 when the SAP server is installed. Because these tables are not alwaysduplicated 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.

Defining functions

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

Table 16. Function values

Proc. Code Sub‑process code

DOCCH DO

DOCCR MR

DOCRQ CL

EQUIRQ MR

MATRQ MR

Allocating field sets

The following entries must be configured. This step allows you to verify whether theCAD system name as configured in Defining Data Carrier and Data Carrier Types,page 57 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

Defining field 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 17. CAD field sets

Field set Field name

DCCRDAT DOC_NUMBER

DCCRDAT DOC_TYPE

DCCRDAT DOC_PART

DCCRDAT DOC_VERS

DCCRDAT DESCRIPT_D

DCCRDAT DISP_APPL

DCCRDAT DATA_CARR

DCCRDAT ORIGINAL

DCCRDAT PROTOCOL


Chapter 6Configuring SAP for PPPI

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 65• Defining Process Instruction category DCTM, page 66• Configuring the Characteristics/Process Instruction category, page 66

Configuring the Process Instruction categoryTo get into the SAP customization menu:

1. Start SAPGUI and connect to R/3.

2. To invoke the SAP configuration tool, type /nspro into the command field.A dialog box appears.

3. Click Enter to exit the dialog box.

4. Click Enterprise IMG (or click your specific project if you configure your systemon a project base).


Configuring SAP for PPPI

The Implementation Guide for R/3 Customizing window appears.

5. Navigate to the process instruction categories subfolder as follows:Production Planning for Process Industries\Process management\Processinstructions\Process instruction categories for the R/3 PI sheet.

6. Click on Define Process Instruction Categories.

Defining Process Instruction category DCTMTo configure a new Process Instruction category:


2. Define the category DCTM:• Process Instr.type’ type must be 6.• Description is ‘Documentum Content Services’.

3. Save the new item.

4. Click Back to return to the previous window.

Configuring the Characteristics/ProcessInstruction category

To configure 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 listed below.


Characteristic Default characteristic value/Comments

PPPI_FUNCTION_NAME WS_EXECUTE

PPPI_BUTTON_TEXT Show Related Documents

This text can be changed to reflect 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.The command line has some constraints:

• The maximum string length is 30characters.

• All letters are capitalized.




Index

AAdministrative Console, 14Agent services, 12ALF, 39 to 40ALF class, 14ALF format, 14Anonymous Login

protocol, 30archived and deleting documents,

deleting, 42archived data, 14archived Print List

displaying in SAPGUI, 42ArchiveLink Monitor window, 41archiving

Print List, 41archiving reports

testing, 40Archiving request window, 42asynchronous queue, 21

Bbar codes, 44basic settings, configuring, 20

CCAD field sets, 63CAD Integration, configuring, 61capture operator, 7class

ALF, 14FAX, 14OTF, 14REO, 14

configuration procedures, 36, 61configuring

basic settings, 20Manage, 53number ranges, 21

optical archive as output device, 23content repositories, 34Content Services, see Content Services for

SAPContent Services for SAP, 7

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

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

Ddefining

document types, 39links, 39logical ArchiveID, 20

deletingarchived and linked documents, 42

displayingarchived Print List in SAPGUI, 42

dmview.exe, 60document

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

document controller, 7document formats, supported in SAP, 14Document Management General Data, 59

to 60, 62document types

ALF, 39defining, 39FAX, 39OTF, 39REO, 39

documents, 43


Index

Ff.21, 41FAX, 39, 43FAX class, 14field sets, allocating, 62format

ALF, 14PDF, 14REO, 14Tiff, 14

frequency of archival, 22

GGeneral Data, 62 to 63

IInline Print List Viewer

protocol, 31intended audience, 7

Jjobs, scheduling, 22

Llinking, 43links

defining, 39logical ArchiveID

defining, 20

Mmaintaining links, 7Manage, 53 to 54

Nnumber ranges, configuring, 21

Ooaa4, 27oaat, 22oac0, 20, 34OAC0, 34oac2, 39oac3, 39oadr, 42

oag1, 20oam1, 21oanr, 21oaq1, 21oaqi, 21OAWS, 43OLE, application, 25optical archive, configuring as output

device, 23OTF, 39OTF class, 14output device

configuring logical archive as, 23

PPDF format, 14prerequisites

system administrator, 7Print List, 40

archived, displaying in SAPGUI, 42archiving, 41

Print Lists, 14ALF class, 14ALF format, 14

protocolAnonymous Login, 30Inline Print List Viewer, 31

purpose of the guide, 7

Qqueues, creating, 21

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

SSAP

print spooler, 25supported document formats in, 14transaction code, f.21, 41transaction code, oaat, 22transaction code, oac0, 20, 34


Index

transaction code, oac2, 39transaction code, oac3, 39transaction code, oadr, 42transaction code, oag1, 20transaction code, oam1, 21transaction code, oanr, 21transaction code, oaq1, 21transaction code, oaqi, 21transaction code, sm50, 25transaction code, spad, 22transaction code, spro, 19

SAP Document Classescustomizing, 33

SAP Server, 53 to 54SAP Workflow, 44SAPGUI

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

scanning documents, 7scheduling

jobs, 22settings, 43sm50, 25SM59, 36, 38SOLE, 25spad, 22SPO process, 25spool process, 25spool processes, verifying, 25spro, 19standard user, 7supported document formats in SAP, 14

ALF class, 14ALF format, 14FAX class, 14OTF class, 14PDF format, 14REO class, 14

REO format, 14Tiff format, 14

system administrator, 7prerequisites, 7

Ttest scanning, 45testing the connection, 37Tiff format, 14transaction code

f.21, 41oaat, 22oac0, 20, 34oac2, 39oac3, 39oadr, 42oag1, 20oam1, 21oanr, 21oaq1, 21oaqi, 21sm50, 25spad, 22spro, 19

Transfer drctry field, 20

Uueue Administrator field, 21user roles, 7

Vverifying, spool processes, 25View, 53 to 54

WWebAdmin, 14


EMC Documentum ContentServicesforSAP · ContentServicesforSAP—documentationsuite Title...

Documents

Transcript of EMC Documentum ContentServicesforSAP · ContentServicesforSAP—documentationsuite Title...