EMC Documentum External Viewing Services for SAP

Transcription

1 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide P/N Rev A01 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright 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 change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. 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.

3 Table of Contents Preface... 7 Chapter 1 Introducing External Viewing Services for SAP Overview Understanding the External Viewing Services for SAP Architecture Supported SAP document formats SAP and External Viewing Services for SAP terms Chapter 2 Configuring SAP for Archive Services for SAP Overview Configuring the ArchiveLink interface for Archive Services for SAP Overview oac0 Defining a logical ArchiveID oag1 Configuring basic settings oanr Configuring number ranges oaqi Creating queues oaat Scheduling jobs spad Configuring optical archives as output devices sm50 Verifying spool processes oaa3 Configuring the SAP inline Print List viewer protocol Customizing SAP document classes Overview oac0 Configuring content repositories sm59 RFC destination archives sm59 Testing connections oac2 Defining document types oac3 Defining links Testing the archiving process using a Print List Overview Creating a document type in SAP Testing connection between SAP and Archive Services Archiving a Print List Displaying the archived Print List in SAPGUI Deleting archived and linked documents Chapter 3 Configuring SAP for Content Services for SAP Overview Configuring the ArchiveLink Interface for Content Services for SAP Overview oac0 Defining a logical ArchiveID oag1 Configuring basic settings oanr Configuring number ranges oaqi Creating queues oaat Scheduling jobs spad Configuring optical archives as output devices EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 3

4 Table of Contents sm50 Verifying spool processes oaa3 Configuring the SAP inline Print List viewer protocol Customizing SAP Document Classes oac0 Configuring content repositories sm59 RFC destination archives sm59 Testing connections oac2 Defining document types oac3 Defining links ALF Reports/Print Lists Testing archiving reports Deleting archived and linked documents Customizing FAX scanned documents oaws Settings Optional for SAP workflow Optional for barcode Creating Custom BAPIs EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

5 Table of Contents List of Figures Figure 1. External Viewing Services for SAP EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 5

6 Table of Contents List of Tables Table 1. Terms and definitions Table 2. Field descriptions of Change Output Device screen Table 3. Field descriptions of Change Content Repositories screen Table 4. Field descriptions of New Entries table Table 5. Field descriptions of change output device screen Table 6. Field descriptions of change output device screen Table 7. Field descriptions Table 8. Field descriptions of New Entries table EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

7 Preface Purpose of this guide This guide explains how to configure SAP to use External Viewing Services for SAP 6.0. ( EVS for SAP 6.0). It provides task based instructions for configuring SAP, so that it works together with EVS for SAP. Intended audience In order to address the manuals to the correct audience, EMC Documentum defines the roles of the users of the manuals as follows: System Administrator This role covers users who install and configure External Viewing Services for SAP. The External Viewing Services for SAP application integrates EMC Documentum and the SAP R/3 system. Therefore, system administrators must have experience with the software products listed in the Software requirements section of the EMC Documentum External Viewing Services for SAP Release Notes. External Viewing Services for SAP Administrator This role covers users who manage External Viewing Services for SAP using WebAdmin. Standard User This role covers users who view archived documents. This manual is intended for system administrators. Revision history This section contains a description of this document s revision history. Revision history Revision date September 2007 Description Initial publication of document for External Viewing Services for SAP 6.0. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 7

8 Preface Typographic conventions This guide uses the following text conventions: Typographic conventions used in this guide Convention Description > Represents a pop up or pull down menu. <Text enclosed within angle brackets> Information in this font Represents a variable name for which you must provide a value, or a defined term. Represents code samples, user input, and computer output. [] square brackets Used in method command syntax specifications, square brackets indicate an optional argument. {} curly brackets Used in method command syntax specifications, curly brackets indicate an optional argument that can be repeated more than once. Related documentation This manual forms part of a documentation suite designed to support those who install, configure, and use External Viewing Services for SAP. The product and documentation suite can be found on Documentum s download center: From Powerlink, you can download the latest version of External Viewing Services for SAP and the related documentation suite. To access the contents in Powerlink, you will need to provide the login credentials assigned to you when you first applied for access. Note: Your login ID, by default, is your address. If you cannot locate your password, 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 and obtain a user name and password. 8 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

9 Preface External Viewing Services for SAP Documentation suite Title Description Target role External Viewing Services for SAP Release Notes External Viewing Services for SAP Installation Guide Configuring SAP R/3 for External Viewing Services for SAP Provides an overview of new and amended features, known bugs, limitations, miscellaneous technical notes, and documentation corrections and clarifications. Provides the procedures for installing EVS for SAP. Describes the configuration tasks that need to be performed in SAP so that SAP can communicate with EVS for SAP. Standard User, System Administrator, System Administrator (SAP), and Archive Services Administrator System Administrator System Administrator (SAP) External Viewing Services for SAP Administration Guide External Viewing Services for SAP User Guide Describes how to configure EVS for SAP using the WebAdmin tool. Describes how SAP users view documents. EVS for SAP Administrator Standard User EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 9

10 Preface 10 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

11 Chapter 1 Introducing External Viewing Services for SAP Overview External Viewing Services for SAP integrates the EMC Documentum content management system with the SAP R/3 system. It is an interface to the SAP R/3 system based on SAP s standard DMS and ArchiveLink interfaces. EVS for SAP consists of the server components of Content Services for SAP. Additionally, External Viewing Services for SAP is dependent on Archive Services for SAP. Understanding the External Viewing Services for SAP Architecture, page 12provides more information. External Viewing Services for SAP provides the following functionalities: Archiving SAP data, reports, and documents through ArchiveLink certified interfaces in EMC Documentum. Configuring rendition services. Configuring EMC Documentum workflows. Configuring SAP queries. Replicating SAP objects to an EMC Documentum repository. Configuring agents and jobs. Accessing and displaying documents stored in an EMC Documentum repository from a variety of SAP modules. Viewing archived documents through Webtop. This chapter covers the following topics: Understanding the External Viewing Services for SAP Architecture, page 12 Supported SAP document formats, page 14 SAP and External Viewing Services for SAP terms, page 14 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 11

12 Introducing External Viewing Services for SAP Understanding the External Viewing Services for SAP Architecture Figure 1. External Viewing Services for SAP External Viewing Services for SAP consists of the server components of Content Services for SAP. The Content Services for SAP server components consist of the following: Agent A component that provides automatic means of linking and replicating objects between SAP and EMC Documentum. This substantially improves productivity, information integrity, and information availability. 12 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

13 Introducing External Viewing Services for SAP Rendition Services Built 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 is generated when the document is archived in the repository. WebAdmin (ASP based) An administrative console that allows you to: Perform archiving services. Using WebAdmin, you can perform the following archiving services: Create, configure, and manage archives Manage certificates for the archive Create repository connections for Content Services for SAP Create workflows and associate the same with archived documents Configure document archival for Content Services for SAP Perform Document Management System (DMS) related services. You can: Configure batch jobs for linking and replication tasks Schedule and manage the execution of linking and replication jobs Additionally, External Viewing Services for SAP is dependent on Archive Services for SAP. Archive Services for SAP consists of the following components: HTTP Archiving Services A server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the Documentum repository using an HTTP connection to SAP. Archive Services is a J2EE servlet that communicates with SAP ArchiveLink. The reports and archived documents can later be retrieved and viewed through SAPGUI. RFC Archiving Services A server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the EMC Documentum repository. The archived reports and documents can later be retrieved and viewed through SAPGUI and Documentum clients. This component uses SAP Remote Function Calls (RFCs) to communicate with SAP. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 13

14 Introducing External Viewing Services for SAP WebAdmin (JSP based) An administrative console that allows you to: Create, configure, and manage archives Manage certificates for the archive Create repository connections for Archive Services Configure document archival for Archive Services Supported SAP document formats EMC Documentum supports the following SAP document classes or 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 External Viewing Services for SAP terms This section presents some terms and their definitions, as used in this guide. Table 1. Terms and definitions Term External Viewing Services for SAP HTTP Archiving Server Definition Product that connects EMC Documentum to SAP and from SAP. Server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the EMC Documentum repository using an HTTP connection to SAP. Archiving Server is a J2EE Web application based on the SAP ArchiveLink interface. The archived reports and documents can later be retrieved and viewed through SAPGUI and EMC Documentum clients. 14 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

15 Introducing External Viewing Services for SAP Term RFC Archiving Server ArchiveLink Archive Services for SAP WebAdmin Content Services for SAP WebAdmin Definition A server component that enables you to archive reports, data, incoming and outgoing documents from SAP to the EMC Documentum repository. The archived reports and documents can later be retrieved and viewed through SAPGUI and Documentum clients. This component uses SAP Remote Function Calls (RFCs) to communicate with SAP. Cross functional interface that is part of the SAP Basis System. ArchiveLink handles storing and retrieving documents and data to and from a repository external to SAP. An administrative console that allows you to: Create, configure, and manage archives Manage certificates for the archive Create repository connections for Archive Services for SAP Configure document archival for Archive Services for SAP An administrative console that allows you to: Perform archiving services.using WebAdmin, you can perform the following archiving services: Create, configure, and manage archives Manage certificates for the archive Create repository connections for Content Services for SAP Create workflows and associate the same with archived documents Configure document archival for Content Services for SAP Perform Document Management System (DMS) related services. You can: EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 15

16 Introducing External Viewing Services for SAP Term SAP DMS SAP PLM SAP Master Record SAPGUI Original Document Definition Configure batch jobs for linking and replication tasks Schedule and manage the execution of linking and replication jobs Document Management System that is part of the SAP Basis System. Presents a logical layer to integrate with external systems like AutoCAD or EMC Documentum. Not directly related to ArchiveLink. Product Life Cycle Management (PLM). SAP PLM provides an integrated environment that ensures all people involved in product development, manufacturing, and service have quick and secure access to current information. It provides a set of BAPI calls that can be used by external systems like EMC Documentum. A set of master data, such as customer or vendor data, that is used in the creation of SAP documents. SAP Graphical User Interface. Graphical tool that connects a client to the SAP server. Paper based version of a document. Example 1 1. An invoice may consist of two sheets of paper received from a supplier. Paper 16 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

17 Introducing External Viewing Services for SAP Term SAP Document Definition documents are scanned and stored as electronic originals in EMC Documentum. An electronic transactional record of header data and line items in SAP. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 17

18 Introducing External Viewing Services for SAP 18 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

19 Chapter 2 Configuring SAP for Archive Services for SAP Overview You can store and retrieve documents, reports, and data through SAP ArchiveLink and DMS interfaces. Prior to using Archive Services, the SAP R/3 system must be configured. This section contains the following topics: Configuring the ArchiveLink Interface for Content Services for SAP, page 37 Customizing SAP Document Classes, page 44 Testing archiving reports, page 52 Configuring the ArchiveLink interface for Archive Services for SAP Overview The Archiving Server component is the part of the Archive Services for SAP application that handles archive requests for a repository. This means that you can store and retrieve documents, reports, and data through SAP ArchiveLink and DMS interfaces. Prior to running the Archive Services, the SAP R/3 system must also be configured. This chapter describes how to configure your R/3 ArchiveLink and other related transactions through SAPGUI and the R/3 system. Note: The configuration steps often reference direct transaction codes. These codes allow you to navigate directly to the correct configuration screen. Most of the system configuration is performed in the SAP Implementation Guide for R/3 customizing (IMG). You can navigate to this screen using the following transaction code: spro. When configuring Archive Services, you can configure either an HTTP based Archive Server or an RFC (Remote Function Call) Archive Server. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 19

20 Configuring SAP for Archive Services for SAP Note: Documentum recommends that all new installations must be based on the HTTP based Archive Server. The primary reason is that SAP will focus future development on the HTTP based archive protocol. The configuration steps are different for RFC and HTTP based archiving. Configuration steps 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 following sections: oac0 Defining a logical ArchiveID, page 20 oag1 Configuring basic settings, page 39 oanr Configuring number ranges, page 39 oaqi Creating queues, page 39 oaat Scheduling jobs, page 40 spad Configuring optical archives as output devices, page 41 sm50 Verifying spool processes, page 43 oaa3 Configuring the SAP inline Print List viewer protocol, page 43 oac0 Defining a logical ArchiveID Note: The name of the logical ArchiveID must be the same as the ArchiveID created using WebAdmin, as defined in the EMC Documentum Archive Services for SAP Administration 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 any content repository whose Storage type is HTTP content server. 3. In the Display Content Repositories: Detail page, click the Display/Change icon The Copy as... button is now enabled. 4. Click the Copy as... button. 5. Edit the Content Rep. field so that it is the same as ArchiveID created using WebAdmin, as described in the EMC Documentum Archive Services for SAP Administration Guide). 6. In the Transfer drctry field, enter the directory path where SAP can write the Print List till 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. 20 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

21 Configuring SAP for Archive Services for SAP 8. In the HTTP Script field, type the following: /<virtual_directory>/archivelink/<nameofrepository> Where <virtual_directory> refers to the EVS SAP virtual installation directory. 9. To save the logical ArchiveID configuration, choose Content Repository > Save. oag1 Configuring basic settings You must define the basic settings for ArchiveLink. To configure the basic settings: 1. Execute the following transaction in the transaction code field: oag1. 2. Ensure Deactivate Print List Management in DMS is selected. 3. Save your changes. oanr Configuring number ranges You must configure the number ranges for ArchiveLink. To configure the number ranges: 1. Execute the following transaction in the transaction code field: oanr. 2. To edit the configuration, click Intervals (marked with a pencil). The Display Number Range Intervals window opens. 3. Configure the Number Range 01 with default values. 4. Save your changes. oaqi Creating queues When Print Lists are archived, the SAP print spooler puts the document into the asynchronous queue. The scheduler then picks up the document and sends it to the archive. The queue serves as a buffer for everything sent to an SAP archive. Other queues are used for outgoing documents and barcodes. These queues can be seen on the ArchiveLink Monitor screen (transaction code: oam1). If this screen shows the word MISSING instead of zeros, you must create queues and specify an administrator. Define EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 21

22 Configuring SAP for Archive Services for SAP an SAP user with the proper ArchiveLink administrator profile as the administrator for these queues. Defining an administrator will automatically create the queues. Check that the queues have been created by reviewing transaction oam1. To create queues: 1. Execute the following transaction in the transaction code field: oaqi The 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 close the window. oaat Scheduling jobs The SAP schedule job periodically checks the output queue and sends all the items in the queues to the archive. You must configure the schedule job to successfully archive documents to an SAP archive. To schedule a job: 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. 5. Save your changes. 6. Click Back to return to the Define Background Job window. 7. Click Start Date. 8. Set Start Time to Immediate. 9. Select Periodic Job. 10. Click Period Values and specify an interval such as 20 minutes. This value should be determined by the following factors: Frequency of archival Time taken to archive your largest document; for example, your largest Print List 22 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

23 Configuring SAP for Archive Services for SAP 11. Save your changes. 12. Click Exit. spad Configuring optical archives as output devices An output device is the driver software for the logical output device that archives documents using the ArchiveLink interface. To correctly archive a document to SAP, you must define the output device as an optical archive. Configuring an output device includes defining the type, the device, the spool server, and so on. There should be only ONE ARCH device; therefore, prior to defining a device with the ARCH short name, you should delete any existing ARCH devices such as ARCHIXOS. 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 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. If you are already using a printer named ARCH you can either delete it or use the existing 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 fields. Table 2. Field descriptions of Change Output Device screen Field name Output Device Short Name Device Type Spool Server Device Class Type Access Method Fill Value ARCHIVE ARCH ARCHLINK Select spool server from the list box. Usually there is only one spool server listed A, for archive program I, for archive service EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 23

24 Configuring SAP for Archive Services for SAP Field name Location Fill Message Fill Value Archive ArchiveLink Device 8. Click Enter and the dialog box changes. 9. Save your changes. sm50 Verifying spool processes Archive Services uses the standard SAP print spooler to send reports to the ArchiveLink queue. To successfully archive a document, the print spooler must be running. To verify if a spool process is running: 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. oaa3 Configuring the SAP inline Print List viewer protocol SAP R/3 includes a Print List viewing feature that allows you to view saved Print Lists, in SAPGUI, in their native ALF format. To view saved Print Lists in SAPGUI, you must configure the protocol to support the viewer. To configure the Print List viewer to display the Print Lists in SAPGUI: 1. In the transaction code field, execute the following transaction: oaa3 The SAP ArchiveLink: Communications interface administration page appears. 2. Click Create. The New Protocol dialog box appears. Example 2 1. You may wish to define the protocol name as DCTMALF; this could refer to Archive Services with ALF Viewer. 24 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

25 Configuring SAP for Archive Services for SAP 3. Type version 0045 for HTTP based archiving. 4. Save your changes. The Overview of a Protocol window appears, displaying your newly defined protocol. 5. Double click Display Stored Document. The Overview of a Protocol window appears, showing a list of Document Classes. 6. Select the * row which indicates all document classes. 7. Click the pencil button. The Overview of a Protocol dialog box appears. 8. Type OPEN in the Communication Type field. 9. Press the [Enter] key. 10. Type DCTM in the Application field. 11. Click Continue. 12. In the Overview of a Protocol window showing the list of document classes, select the ALF document class. 13. Click the pencil button. The Overview of Protocol dialog box appears. 14. Type R/3 in the Communication Type field. 15. Press the [Enter] key No application is entered here. 16. Save your changes. The Overview of a Protocol window appears. If you repeat steps 4 and 11, you should see that the * document class and the ALF document class are indicated as Maintained Explicitly. All other document classes should be indicated as Not Maintained Explicitly. Customizing SAP document classes Overview The following sections describe how to archive document classes from SAP. The customization of each SAP setup is different depending on which document class the archived document belongs to. The document classes are: EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 25

26 Configuring SAP for Archive Services for SAP ALF FAX OTF REO For all classes, you must configure, at least: oac0 oac2 oac3 plus any specific customizations. These customizations are described in the following sections: oac0 Configuring content repositories, page 45 oac2 Defining document types, page 50 oac3 Defining links, page 51 oac0 Configuring content repositories SAP allows you to define a content repository (previously known as a logical archive). This content repository is mapped to a Documentum archive via WebAdmin. The Documentum archive links to a set of rules such as content folders, Documentum document types, and so on in the Documentum repository. It is recommended that you store each document type in a separate archive. Using WebAdmin, you must create a matching archive for each ArchiveID defined in SAP. This ArchiveID defines what actions (types, folders, retention, and so on) are applied on an SAP document when it is archived. The following sections explain how to create an archive in SAP for each represented document class. When configuring archives, you can configure either HTTP based or RFC (Remote Function Call) archives. The configuration steps are different for RFC compared to HTTP based archives. The configuration steps below have been listed as being relevant only to RFC or HTTP based archiving. Note: Documentum recommends that all new installations are based on the HTTP based Archive Server. The primary reason is that SAP will focus future development at the HTTP based archive protocol. However, legacy RFC archives are still supported. To define an SAP content repository: 1. Execute the following transaction in the transaction code field: oac0 2. Click the pencil button to edit the table. 26 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

27 Configuring SAP for Archive Services for SAP 3. Click New Entries. 4. Select Full administration. The Change Content Repositories window opens. 5. Fill in the fields, as listed below, in the Change Content Repositories window. Table 3. Field descriptions of Change Content Repositories screen Field name Content rep Description Storage Type Protocol Version No. Output Device Value Specify a two letter archive name. For example, AA A meaningful name. For example, SAP Print Lists (AA) Select HTTP or RFC The previously configured protocol for HTTP or 0031 for RFC ARCHIVE 6. Depending on whether you selected HTTP or RFC based archiving, type appropriate values in the following fields. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 27

28 Configuring SAP for Archive Services for SAP For HTTP based archiving: HTTP server Type the hostname or IP address of the Archive Services host. If you use a server name here, ensure that you can ping the server by name from the SAP server. Port Number Type the port number being used (default is 80). When using a default Tomcat configuration, this value is usually HTTP Script Type the following value in this field: <virtual directory>/archivelink/ <repository> <virtual directory> is the directory on which the software is installed. <repository> is the name of the repository into which you will be archiving content. You must configure a corresponding archive in the Archive Services, using WebAdmin. Basic path Type the file system path to the location where SAP will put archived documents to be picked up by Archive Services. Arch path Usually, the same as the Basic path. For RFC based archiving: RFC destination Type the RFC destination that you created previously (refer to sm59 RFC destination archives, page 48). Basic path Type the file system path to the location where SAP will put archived documents to be picked up by Archive Services. Arch path Usually, the same as the Basic path. Repeat this procedure to define the additional archives. You may use this procedure to define any Documentum archives in SAP. 28 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

29 Configuring SAP for Archive Services for SAP sm59 RFC destination archives This section applies to RFC archiving only. The SAP server considers Content Services for SAP as an external RFC service or RFC destination. The destination is identified with a symbolic name that was configured in Documentum during the Content Services Archive Service installation. The name of the RFC destination must be unique for each repository/sap client connection and identical in 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 Services Archive 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 to communicate. 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 WebAdmin and transaction code sm59 because the value of this field must correspond to the configuration parameter RFC Program ID in the WebAdmin ArchiveLink configuration tab RFC Destination parameter RFC Program ID. If you have not yet installed Content Services, you will need to make a note of this value so that you can configure your RFC destination in Content Services WebAdmin, and when the RFC services are installed on the Content Services host EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 29

30 Configuring SAP for Archive Services for SAP server. 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, the second process connected receives all requests from SAP. The first process will not receive an error message, so it will wait indefinitely for RFC requests that never come. 12. Save your changes. 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 49. sm59 Testing connections You must have created SM59 RFC destination, WebAdmin RFC config, and Content Services RFC services via the Content Services installation program and started with the SHARE user ID, as described in the EMC Documentum Content Services for SAP Installation Guide, before beginning this procedure. To test the ArchiveLink RFC connection to Content Services archive: 1. Switch on debugging before processes or services are started the first time by setting the debug level: Windows NT: In the registry: Set HKEY_LOCAL_ MACHINE\SOFTWARE\Documentum\Doclink\ Archive\Docbase\<Name_Of_Repository> to 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 the plus symbol in front of the folder labeled TCP/IP Connections. A list of all RFC destinations opens. 6. Double click the RFC destination that links SAP to the repository via Content Services. 7. Click Test Connection. 30 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

31 Configuring SAP for Archive Services for SAP A message appears on the status bar, stating that the connection is OK. A new window 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 server which 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 turn on 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 types You must select which document types you will be archiving, and correlate those to SAP document classes, such as FAX, ALF, OTF, and REO. The list of document types provided by SAP, when using transaction oac2, are the templates to be used for categorizing your SAP documents for archiving. You can customize the standard document types by using the SAP XYZ naming conventions. FAX documents are documents that will be scanned and linked to SAP. ALF are reports produced and linked from SAP. OTF are outgoing SAPSCRIPT documents produced and linked from SAP. REO documents are data archive files which are compressed by the SAP ADK and stored externally in that format. To define document types for SAP: 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. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 31

32 Configuring SAP for Archive Services for SAP 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 your configuration. 5. When you have finished selecting document types, save your changes. oac3 Defining links Using the link table, you can categorize SAP documents to define what combination of SAP object type (for example, SOOD) and SAP document type (for example, GENPRILIS) are stored and linked to which archive. The SAP document type is linked to the SAP document class, previously known as SAP document type (for example, ALF, OTF, REO), which determines how the document is produced and linked. For example, the ALF class refers to reports, FAX to scanned documents, and OTF to outgoing SAPSCRIPT documents. 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. 3. Fill in the fields, as listed below, in the New Entries table. Table 4. Field descriptions of New Entries table Field name Object Type Document Type S (Status) Value Use legitimate object type such as SOOD for Print Lists, and BKPF for accounting documents The SAP doc type as defined in OAC2 above such as GENPRILIS Enter an x in this column Arch. ID Link Ret Prd. 0 Enter the archive ID of a newly created archives for example, AA Enter the name of the link tables where links will be maintained. TOA01 TOA03 32 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

33 Configuring SAP for Archive Services for SAP 4. Save your changes. Testing the archiving process using a Print List Overview Once you have completed the configuration procedures described previously in this guide, you should test the archiving process by: Defining an ArchiveID in WebAdmin. More information is in the EMC Documentum Archive Services for SAP Administration Guide. Testing the connection between SAP and Archive Services. Creating a document type in SAP. Archiving a Print List. Displaying the archived Print List in SAPGUI. This chapter contains the following topics: Creating a document type in SAP, page 33 Testing connection between SAP and Archive Services, page 34 Archiving a Print List, page 34 Displaying the archived Print List in SAPGUI, page 35 Deleting archived and linked documents, page 54 Creating a document type in SAP To fully test the archival and retrieval cycle, a simple Print List can be configured by following the instructions given below: 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. From the list, select any item with the ObjectType SOOD. 4. Click the Copy As... icon and execute. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 33

34 Configuring SAP for Archive Services for SAP 5. In the page that appears, enter any piece of text starting with the alphabet Z in the Document type field. Thus, Z<your_text> will be the document type. 6. In the Storage system field, enter the name of the logical ArchiveID that you created earlier (refer to oac0 Defining a logical ArchiveID, page 20), where the documents will be archived. 7. Save your changes. Testing connection between SAP and Archive Services 1. Execute the following transaction in the transaction code field: oac0. 2. In the Display Content Repositories: Overview page, click any content repository (specifically whose Storage type is HTTP content server). 3. In the Display Content Repositories: Detail page, click the Test connection button. An information messages appears at the bottom of the page, indicating that the connection test has been successful. Archiving a Print List To archive a Print List: 1. Execute the following transaction in the transaction code field: f Click Execute. 3. In the List of Customer Open Items page that appears, select List > Print. The Print Screen List dialog box appears. 4. Click Properties. The Spool Request Attributes dialog box appears. 5. In the Parameters name column, click Output Options. 6. From the Storage Mode list box, select Archive only. Note: Whenever you edit a parameter in this dialog box, we recommend that you check the Show Selected Print Parameters on Initial Screen checkbox. This ensures that the customized settings are available in the initial Print Screen List dialog box. 34 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

35 Configuring SAP for Archive Services for SAP 7. Verify that the Object Type and Document Type fields contain the correct values, as configured in the New Entries table (refer to oac3 Defining links, page 51). Pick the following values for example: SOOD GENPRILIS. If your Document Type is incorrectly configured, refer to the following procedures for configuring document types in SAP archives: oac2 Defining document types, page 50 and oac3 Defining links, page Type additional information in the Information field. This label may be anything you wish; for example, your initials. 9. Optionally, type a description of the Print List in the Text field. 10. In the Parameter name column, select General attributes > Time of printing. 11. From the Time of print list box, select Print out immediately. 12. Click Continue in the Spool Request Attributes dialog box. 13. Click Continue in the Print Screen List dialog box. 14. To verify that the Print List is in the archiving queue, execute the following transaction in the transaction code field: oam1. The ArchiveLink Monitor screen appears. The Print List is now queued, waiting for the scheduler to pick it up and transfer it to the archive. oaat Scheduling jobs, page 40, contains information about configuring the ArchiveLink scheduler. 15. To accelerate the transfer of the Print List from the queue to the archive in the repository, click Storage Queue. The Queue: Content server (CARA) screen appears. You should now see an entry for the newly archived Print List in this screen. 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. A confirmation displays the message that the queue has been processed. If no errors occur, you can continue testing by displaying the archived Print List. Displaying the archived Print List in SAPGUI To display the newly archived Print List in SAPGUI: 1. Execute the following transaction in the transaction code field: oadr. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 35

36 Configuring SAP for Archive Services for SAP 2. To find a particular Print List, type appropriate search parameters in the appropriate fields. The ArchiveLink: Hit List for Stored Print Lists page appears. 3. Double click an item in the list to select it. 4. Choose Print List > Display From Content Server. SAP executes the GET command to retrieve the document from the Documentum archive. The retrieved document is displayed in SAPGUI and has the DocumentID of the Print List in Documentum. Deleting archived and linked documents In a repository, if you delete version 1.0 of a document that is linked to SAP or archived from SAP, the link to SAP is also deleted. This is because the dm_relation object which creates the link to SAP is deleted when the parent object (which is always version 1.0) is deleted. We recommend that you do not delete the original version of objects that are linked to SAP if you want to maintain their link to SAP. If you need to delete version 1.0 of a document, but want to keep the link to SAP, then, after deleting the document, you must relink the object to SAP, outside of Archive Services. 36 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

37 Chapter 3 Configuring SAP for Content Services for SAP Overview This section contains the following topics: Configuring the ArchiveLink Interface for Content Services for SAP, page 37 Customizing SAP Document Classes, page 44 Creating Custom BAPIs, page 56 Configuring the ArchiveLink Interface for Content Services for SAP Overview You can store and retrieve documents, reports, and data through SAP ArchiveLink and DMS interfaces. Once a document is released to Documentum, it is accessible from SAPGUI (the SAP client interface). It is also accessible from a Documentum Client such as Webtop. Prior to running the Content Services for SAP, the SAP R/3 system must also be configured. This chapter describes how to configure your R/3 ArchiveLink and other related transactions through SAPGUI and the R/3 system. Note: The configuration steps often reference direct transaction codes. These codes allow you to navigate directly to the correct configuration screen. Most of the system configuration is performed in the SAP Implementation Guide for R/3 customizing (IMG). You can navigate to this screen using the following transaction code: spro. When configuring Archive Services, you can configure either an HTTP based Archive Server or an RFC (Remote Function Call) Archive Server. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 37

38 Configuring SAP for Content Services for SAP Note: Documentum recommends that all new installations must be based on the HTTP based Archive Server. The primary reason is that SAP will focus future development on the HTTP based archive protocol. The configuration steps are different for RFC and HTTP based archiving. Configuration steps 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 following sections: oac0 Defining a logical ArchiveID, page 38 oag1 Configuring basic settings, page 39 oanr Configuring number ranges, page 39 oaqi Creating queues, page 39 oaat Scheduling jobs, page 40 spad Configuring optical archives as output devices, page 41 sm50 Verifying spool processes, page 43 oaa3 Configuring the SAP inline Print List viewer protocol, page 43 oac0 Defining a logical ArchiveID Note: The name of the logical ArchiveID must be the same as the ArchiveID created using WebAdmin (refer to the Configuring, Viewing, and Editing Archives section of the External Viewing Services for SAP Administration 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 any content repository whose Storage type is HTTP content server. 3. In the Display Content Repositories: Detail page, click the Display/Change icon The Copy as... button is now enabled. 4. Click the Copy as... button. 5. Edit the Content Rep. field so that it is the same as the ArchiveID created using WebAdmin, as described in the EMC Documentum External Viewing Services for SAP Administration Guide. 6. In the Transfer drctry field, enter the directory path where SAP can write the Print List till 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. 38 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

39 Configuring SAP for Content Services for SAP 8. In the HTTP Script field, type the following: /<virtual_directory>/archivelink/<name of repository> Where <virtual_directory> refers to the EVS SAP virtual installation directory. 9. To save the logical ArchiveID configuration, choose Content Repository Save. oag1 Configuring basic settings You must define the basic settings for ArchiveLink. To configure the basic settings: 1. Execute the following transaction 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 ranges You 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 Intervals (marked with a pencil). The Display Number Range Intervals window opens. 3. Configure the Number Range 01 with default values. 4. Save your changes. oaqi Creating queues When Print Lists are archived, the SAP print spooler puts the document into the asynchronous queue. The scheduler then picks up the document and sends it to the archive. The queue serves as a buffer for everything sent to an SAP archive. Other queues are used for outgoing documents and barcodes. These queues can be seen on the ArchiveLink Monitor screen (transaction code: oam1). If this screen shows the word MISSING instead of zeros, you must create queues and specify an administrator. Define an SAP user with the proper ArchiveLink administrator profile as the administrator for EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 39

40 Configuring SAP for Content Services for SAP these queues. Defining an administrator will automatically create the queues. Check that the queues have been created by reviewing transaction oam1. To create queues: 1. Execute the following transaction in the transaction code field: oaqi The 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 jobs The SAP schedule job periodically checks the output queue and sends all the items in the queues to the archive. You must configure the schedule job to successfully archive documents to an SAP archive. To schedule a job: 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. 5. Save your changes. 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. 40 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

41 Configuring SAP for Content Services for SAP 12. Click Exit. spad Configuring optical archives as output devices An output device is the driver software for the logical output device that archives documents using the ArchiveLink interface. To correctly archive a document to SAP, you must define the output device as an optical archive. Configuring an output device includes defining the type, the device, the spool server, and so on. There should be only ONE ARCH device; therefore, prior to defining a device with the ARCH short name, you should delete any existing ARCH devices such as ARCHIXOS. 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 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. If you are already using a printer named ARCH, you can either delete it or use the existing 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 fields as listed below. Table 5. Field descriptions of change output device screen Field name Output Device Short Name Device Type Spool Server Device Class Type Access Method Fill Value ARCHIVE ARCH ARCHLINK Select spool server from the list box. Usually there is only one spool server listed A, for archive program I, for archive service EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 41

42 Configuring SAP for Content Services for SAP Field name Location Fill Message Fill Value Archive 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 configured your archives. 10. Execute the following transaction in the transaction code field: oac0 11. Click the pencil button to edit the settings. 12. Click New entries. The Maintain 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 configure an optical archive as the output device for the Documentum installation: 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. If you are already using a printer named ARCH, you can either delete it or use the existing ARCH device. 4. In case ARCH already exists, select device ARCH and click the Delete button. 5. To create a new output device, click the New Entries button. The Change Output Device window opens. 6. Fill in the fields as listed below. Table 6. Field descriptions of change output device screen Field name Host Printer Value a 42 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

43 Configuring SAP for Content Services for SAP Field name Device Class Access Method to Host Spool Device Type ARCHLINK Spool Server Value A I SAP ArchiveLink Archiver Select spool server from the list box. 7. Click Enter and the dialog box changes. 8. Save your changes. sm50 Verifying spool processes Content Services for SAP uses the standard SAP print spooler to send reports to the ArchiveLink queue. To successfully archive a document, the print spooler must be running. To verify if a spool process is running: 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. oaa3 Configuring the SAP inline Print List viewer protocol SAP R/3 includes a Print List viewing feature that allows you to view saved Print Lists, in SAPGUI, in their native ALF format. To view saved Print Lists in SAPGUI, you must configure the protocol to support the viewer. To configure the Print List viewer to display the Print Lists in SAPGUI: 1. In the transaction code field, execute the following transaction: oaa3 The SAP ArchiveLink: Communications interface administration page appears. 2. Click Create. The New Protocol dialog box appears. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 43

44 Configuring SAP for Content Services for SAP Example 3 1. You may wish to define the protocol name as DCTMALF; this could refer to Content Services for SAP with ALF Viewer. 3. Type version 0045 for HTTP based archiving. 4. Save your changes. The Overview of a Protocol window appears, displaying your newly defined protocol. 5. Double click Display Stored Document. The Overview of a Protocol window appears, showing a list of Document Classes. 6. Select the * row which indicates all document classes. 7. Click the pencil button. The Overview of a Protocol dialog box appears. 8. Type OPEN in the Communication Type field. 9. Press Enter. 10. Type DCTM in the Application field. 11. Click Continue. 12. In the Overview of a Protocol window showing the list of Document Classes, select the ALF document class. 13. Click the pencil button. The Overview of Protocol dialog box appears. 14. Type R/3 in the Communication Type field. 15. Press Enter. No application is entered here. 16. 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 and the ALF document class are indicated as Maintained Explicitly. All other document classes should be indicated as Not Maintained Explicitly. Customizing SAP Document Classes The following sections describe how to archive document classes from SAP. The customization of each SAP setup is different depending on which document class the archived document belongs to. The document classes are: 44 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

45 Configuring SAP for Content Services for SAP ALF FAX OTF REO For all classes you must configure a minimum of: oac0 oac2 oac3 plus any specific customizations. These customizations are described in the following sections: oac0 Configuring content repositories, page 45 sm59 RFC destination archives, page 48 oac2 Defining document types, page 50 oac3 Defining links, page 51 ALF Reports/Print Lists, page 52 Deleting archived and linked documents, page 54 Customizing FAX scanned documents, page 54 oac0 Configuring content repositories SAP allows you to define a content repository (previously known as a logical archive). This content repository is mapped to a Documentum archive via WebAdmin. The Documentum archive links to a set of rules such as content folders, Documentum document types, and so on in the Documentum repository. It is recommended that you store each document type in a separate archive. Using WebAdmin, you must create a matching archive for each ArchiveID defined in SAP. This ArchiveID defines what actions (types, folders, retention, and so on) are applied on an SAP document when it is archived. The following sections explain how to create an archive in SAP for each represented document class. When configuring Archives, you can configure either HTTP based Archives or RFC (Remote Function Call) Archives. The configuration steps are different for RFC and HTTP based archives. The configuration steps below have been listed as being relevant only to RFC or HTTP based archiving. Note: Documentum recommends that all new installations must be based on the HTTP based Archive Server. The primary reason is that SAP will focus future development on the HTTP based archive protocol. However, legacy RFC archives are still supported. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 45

46 Configuring SAP for Content Services for SAP To define an SAP content repository (archive): 1. Execute the following transaction: oac0 2. Select SAP Reference IMG from the menu bar. The IMG window opens. 3. Navigate to Basis Components > Basic Services > SAP > ArchiveLink > Basic Settings > Maintain content repositories. 4. Click the pencil button to edit the table. 5. Click New Entries. 6. Select Full administration. The Change Content Repositories window opens. 7. Fill in the fields, as listed below, in the Change Content Repositories window. Table 7. Field descriptions Field name Content rep Description Storage Type Protocol Version No. Output Device Value Specify a two letter archive name. For example, AA A meaningful name. For example, SAP Print lists (AA) Select HTTP or RFC The previously configured protocol for HTTP or 0031 for RFC ARCHIVE 8. Depending on whether you selected HTTP or RFC based archiving, type appropriate values in the following fields: 46 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

47 Configuring SAP for Content Services for SAP For HTTP based archiving: HTTP server Type the hostname or IP address of the Archive Services host. If you use a server name here, ensure that you can ping the server by name from the SAP server. Port Number Type the port number being used (default is 80). When using a default Tomcat configuration, this value is usually HTTP Script Type the following value in this field: <virtual directory>/archivelink/ <repository> <virtual directory> is the directory on which the software is installed. <repository> is the name of the repository into which you will be archiving content. You must configure a corresponding archive in the Archive Services, using WebAdmin. Basic path Type the file system path to the location where SAP will put archived documents to be picked up by Archive Services. Arch path Usually, the same as the Basic path. For RFC based archiving: RFC destination Type the RFC destination that you created previously (refer to sm59 RFC destination archives, page 48). Basic path Type the file system path to the location where SAP will put archived documents to be picked up by Archive Services. Arch path Usually, the same as the Basic path. Repeat this procedure to define additional archives. Use this procedure to define any EMC Documentum archives in SAP. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 47

48 Configuring SAP for Content Services for SAP sm59 RFC destination archives This section applies to RFC archiving only. The SAP server considers Content Services for SAP as an external RFC service or RFC destination. The destination is identified with a symbolic name that was configured in Documentum during the Content Services Archive Service installation. The name of the RFC destination must be unique for each repository/sap client connection and identical in 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 folliwng transaction: sm 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 Services Archive 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 to communicate. 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 WebAdmin and transaction code sm59 because the value of this field must correspond to the configuration parameter RFC Program ID in the WebAdmin ArchiveLink configuration tab RFC Destination parameter RFC Program ID. If you have not yet installed Content Services, you will need to make a note of this value so that you can configure your RFC destination in Content Services WebAdmin, and when the RFC services are installed on the Content Services host server. This value must be unique for each repository/sap client connection which 48 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

49 Configuring SAP for Content Services for SAP is why the RFC destination name <DCTMHOSTNAME>_<SAPSYSID_CLIENT> is recommended. If two Content Services archive processes register under the same ID or name, the second process connected receives all requests from SAP. The first process will not receive an error message so it will wait indefinitely for RFC requests that never come. 12. Save your changes. 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 49. sm59 Testing connections You must have created SM59 RFC destination, WebAdmin RFC config, and Content Services RFC services using the Content Services installation program and started with the SHARE user ID, as described in the EMC Documentum Content Services for SAP Installation Guide, before beginning this procedure. To test the ArchiveLink RFC connection to Content Services archive: 1. Switch on debugging before processes or services are started the first time by setting the debug level: Windows NT: In the registry: Set HKEY_LOCAL_ MACHINE\SOFTWARE\Documentum\Doclink\ Archive\Docbase\<Name_Of_Repository> to 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 the plus symbol in front of the folder labeled TCP/IP Connections. A list of all RFC Destinations opens. 6. Double click the RFC destination that links SAP to the repository via Content Services. 7. Click Test Connection. A message appears on the status bar, stating that the connection is OK. A new window opens, displaying some performance figures (similar to ping). EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 49

50 Configuring SAP for Content Services for SAP 8. Verify the connection by checking the Content Services log files. The following entries should appear in the log file on the Content Services server which 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 turn on 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 Defining document types You must select which document types you will be archiving, and correlate those to SAP document classes, such as FAX, ALF, OTF, and REO. The list of document types provided by SAP, when using transaction OAC2, are the templates to be used for categorizing your SAP documents for archiving. You can customize the standard document types by using the SAP XYZ naming conventions. FAX documents are documents that will be scanned and linked to SAP. ALF are reports produced and linked from SAP. OTF are outgoing SAPSCRIPT documents produced and linked from SAP. REO documents are data archive files which are compressed by the SAP ADK and stored externally in that format. To define document types for SAP: 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. 50 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

51 Configuring SAP for Content Services for SAP 4. Enter information in the Description and Doc. class fields as appropriate for your configuration. 5. When you have finished selecting document types, save your changes. oac3 Defining links Using the link table, you can categorize SAP documents to define what combination of SAP object type (for example, SOOD) and SAP document type (for example, GENPRILIS) are stored and linked to which archive. The SAP document type is linked to the SAP document class, previously known as SAP document type (for example, ALF, OTF, REO) which determines how the document is produced and linked. For example, the ALF class refers to reports, FAX to scanned documents, and OTF to outgoing SAPSCRIPT documents. 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. 3. Fill in the fields, as listed below, in the New Entries table. Table 8. Field descriptions of New Entries table Field name Object Type Document Type S (Status) Value Use legitimate object type such as SOOD for Print Lists, and BKPF for accounting documents The SAP doc type as defined in OAC2 above such as GENPRILIS Enter an x in this column Arch. ID Link Ret Prd Save your changes. Enter the archive ID of a newly created archives for example, AA Enter the name of the link tables where links will be maintained. TOA01 TOA03 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 51

52 Configuring SAP for Content Services for SAP ALF Reports/Print Lists To customize ALF Reports/Print lists you must perform the following procedures: oac0 Configuring content repositories, page 45 oac2 Defining document types, page 50 oac3 Defining links, page 51 Then perform the test. Testing archiving reports Once you have completed the configuration procedures in this section, you should test the new Print List archive by: Archiving a Print List Displaying the archived Print List The following section explains how to perform these tasks. To archive a Print List: 1. Execute the following transaction in the transaction code field: f Click Execute. 3. In the List of Customer Open Items page that appears, select List > Print. The Print Screen List dialog box appears. 4. Click Properties. The Spool Request Attributes dialog box appears. 5. In the Parameters name column, click Output Options. 6. From the Storage Mode list box, select Archive only. Note: Whenever you edit a parameter in this dialog box, we recommend that you check the Show Selected Print Parameters on Initial Screen checkbox. This ensures that the customized settings are available in the initial Print Screen List dialog box. 7. Verify that the Object Type and Document Type fields contain the correct values, as configured in the New Entries table (refer to oac3 Defining links, page 51). Pick the following values for example: SOOD GENPRILIS. If your Document Type is incorrectly configured, refer to the following procedures for configuring document types in SAP archives: oac2 Defining document types, page 50 and oac3 Defining links, page EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

53 Configuring SAP for Content Services for SAP 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 following transaction in the transaction code field: oam1. The ArchiveLink Monitor screen appears. The Print List is now queued, waiting for the scheduler to pick it up and transfer it to the archive. oaat Scheduling jobs, page 40, contains information about configuring the ArchiveLink scheduler. 15. To accelerate the transfer of the Print List from the queue to the archive in the repository, click Storage Queue. The Queue: Content server (CARA) screen appears. You should now see an entry for the newly archived Print List in this screen. 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 appropriate fields. 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 Documentum archive. The retrieved document is displayed in SAPGUI and has the DocumentID of the Print List in Documentum. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 53

54 Configuring SAP for Content Services for SAP Deleting archived and linked documents In a repository, if you delete version 1.0 of a document that is linked to SAP or archived from SAP, the link to SAP is also deleted. This is because the dm_relation object which creates the link to SAP is deleted when the parent object (which is always version 1.0) is deleted. We recommend that you do not delete the original version of objects that are linked to SAP if you want to maintain their link to SAP. If you need to delete version 1.0 of a document, but want to keep the link to SAP, then, after deleting the document, you must relink the object to SAP, outside of Content Services for SAP. Customizing FAX scanned documents To customize FAX scanned documents, you must perform the following procedures: oac0 Configuring content repositories, page 45 oac2 Defining document types, page 50 oac3 Defining links, page 51 Then you can make specific customizations using the following procedures: oaws Settings, page 54 Optional for SAP workflow, page 55 Optional for barcode, page 56 oaws Settings OAWS contains the settings for routing and linking newly scanned FAX documents in SAP. For each document type, you can specify which type of archiving is available: Store for subsequent entry (Early) Store and Enter (Simultaneous) Assign and Store (Late) For storing for subsequent entry which uses SAP workflow to move the image to the SAP inbox, you can specify what organizational object will be used for routing (like User) and then what specific organizational object to route to (like the SAP User ID). To display/change SAP settings for document types for 4.X: 1. Type /NOAWS (previously /NSOA6) in the command field. 54 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

55 Configuring SAP for Content Services for SAP In earlier versions of SAP the Get Settings dialog box opens if settings have been entered. If the Get Settings dialog box does not open, select Edit > Insert doc. type to build your own list of settings. When the new settings are saved, a name has to be specified under which the settings are stored. You may also have to create duplicate settings for early, simultaneous, and late archiving instead of using the checkboxes described below. 2. Select a setting from the list of available settings, or create a new setting. 3. Choose the setting for the application where you wish to link scanned documents and select Entries. The Maintenance screen opens. 4. Select New Entries to choose an item from the Document Type list which matches your entries for OAC2 and OAC3. 5. For testing purposes, type US (USER) and your SAP ID in the Agent ID field. This enables you to send scanned documents to your SAP workflow inbox. You may want to integrate these entries with the SAP organizational roles; see your workflow consultant for details. 6. Make sure that each checkbox is selected to use: Storing For Subsequent Entry Early Archiving (SAP workflow) Store and Enter Simultaneous Archiving (no workflow) Assign then Store Late Archiving (no workflow) 7. Make sure to note the values of document type and object type fields. You will need these values to complete later configuration steps. For example, Incoming Invoice Preliminary Posting has an object type BKPF and object type FIIINPREL. Optional for SAP workflow To configure all SAP object type/document type combinations you want to use with Storing for Subsequent Entry, please coordinate configuration with your SAP workflow consultant: SWU3 Workflow Initialization SOA0 Workflow Document Types OACA Workflow Parameters EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 55

56 Configuring SAP for Content Services for SAP Optional for barcode Barcodes are a good way to automatically scan and link documents that have already been entered into SAP transactions from paper. For example, you can enter an invoice with a barcode sticker, type or wand the barcode number and later, when all the invoices are scanned they can be automatically linked with their entry transactions. The information in this section assumes that you have already set up a barcode configuration object in WebAdmin. If you have not yet done this, refer to EMC Documentum Content Services for SAP Administration Guide. This section explains how to configure SAP R/3 object types and document types to accept bar code on transactions in SAP to be linked later with scanned documents stored in a repository. OAC5 Barcode Settings To configure all SAP object type/document type/user ID combinations you want to use with barcodes: 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 barcode dialog box to open upon saving of that object. 5. Enter any SAP document types for which you want a barcode dialog box to open upon saving of that document. 6. Enter any User ID for which you want a barcode dialog box to open upon saving under that user ID. 7. Save your changes. 8. Enter your object, document, and user ID to test your barcode. Creating Custom BAPIs Content Services for SAP enables you to create and install custom configuration objects known as BAPIs for linking and querying SAP data. To create a custom BAPI you must modify the custom.xml file that is included with the Content Services for SAP installation files. The installation files are available for downloading from subscribenet.com (see the Installation Guide for more details on downloading the release). After modifying the custom.xml file as shown in the example 56 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

57 Configuring SAP for Content Services for SAP below, when you install Content Services for SAP, the custom BAPI will be available for linking and querying using the Web Admin tool. In the following example, we are creating a custom BAPI to link and query purchase orders. The query type for this custom BAPI is EKPO Table. To create a custom BAPI: Note: This procedure must be done prior to installing the current release of Content Services for SAP. The custom BAPI is installed with the release and is available to end users only after product installation. 1. Download and install the current release of Content Services for SAP Server. Details for 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 as appropriate to create your own custom BAPIs. You may copy/paste this sample code inside the Request ON_ERROR tag of the custom.xml file: <OBJECT_CREATE ON_EXIST="version"> <API_CONFIG TYPE="sap_query_plm_type_table" CLASS="sap"> <ATTRIBUTE NAME="object_name" IS_KEY="true">EKPO_Table</ATTRIBUTE> <ATTRIBUTE NAME="table_name">EKPO</ATTRIBUTE> <ATTRIBUTE NAME="function_module">RFC_READ_TABLE</ATTRIBUTE> <ATTRIBUTE NAME="sap_object_type">EKPO</ATTRIBUTE> <ATTRIBUTE NAME="query_parameters" IS_REPEATING="true"> <VALUE>Client=MANDT</VALUE> <VALUE>Document_Number=EBELN</VALUE> <VALUE>Item_Number=EBELP</VALUE> </ATTRIBUTE> <ATTRIBUTE NAME="parameter_defaults" IS_REPEATING="true"></ATTRIBUTE> <ATTRIBUTE NAME="result_parameters" IS_REPEATING="true"> <VALUE>Client=MANDT</VALUE> <VALUE>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 separate XML elements in the custom.xml file for each custom BAPI. EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 57

58 Configuring SAP for Content Services for SAP 6. To install the custom BAPIs into your repository, run the Content Services for SAP Server setup.exe file, choose Docbase Configuration, and then for the version number choose Custom.XML. If you are creating custom BAPI of type ʺsap_query_type_plmʺ make sure the key name for the description field in the result parameters is called ʺDescriptionʺ as shown in following sample code: <ATTRIBUTE NAME="result_parameters" IS_REPEATING="true"> <VALUE>Description=MATL_DESC,18,40</VALUE> </ATTRIBUTE> The attribute ʺdescriptive_fieldʺ is used by Content Services Manage. The value of this attribute will be shown as the description in the query result dialog box in Manage as shown in the following screenshot. In this example, EKPO_Table is used. 58 EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide

59 Configuring SAP for Content Services for SAP EMC Documentum External Viewing Services for SAP Version 6.0 Configuration Guide 59