Professional Documents
Culture Documents
SAP Archiving - Archive Vs DMS PDF
SAP Archiving - Archive Vs DMS PDF
Preface ........................................................................................................................... 7
List of Figures
List of Tables
Intended audience
In order to address the manuals to the correct audience, the roles of the users of the
manuals have been defined as follows:
• System Administrator - This role covers users who install and configure Content
Services. The Content Services application integrates Documentum and the SAP R/3
system. Therefore, system administrators may require experience with:
— Windows XP, 2000, 2003, or HP-UX 11i
— UNIX (if Documentum Content Server or SAP R/3 are installed on a UNIX-based
platform).
— Documentum Technologies like Content Server and DFC
— SAP R/3 versions 4.6c or 4.7
— The following databases, depending on your system platform:
— DB2
— Oracle
— SQL Server
— Sybase
• Content Services Administrator - This role covers users who manage Content Services
using WebAdmin.
• Document Controller - This role covers those who release documents to SAP and
maintain the links to those documents.
• Capture Operator - This role covers users who scan documents and create links to
the appropriate records in SAP.
• Standard User - This role covers users who view documents using SAPGUI and the
View component of Content Services.
This manual is intended for system administrators.
Revision history
This section contains a description of this document’s revision history.
Revision history
Chapter Contents
Chapter 1, Introducing Content Services Provides an overview of Content Services
for SAP for SAP.
Chapter 2, Configuring the ArchiveLink Describes how to configure SAP for
Interface for Content Services for SAP document, report and, data archiving.
Chapter 3, Customizing SAP Document Describes how to customize SAP
Classes document classes.
Chapter 4, Creating Custom BAPIs Describes how to create custom BAPIs for
linking and querying.
Chapter Contents
Chapter 5, Configuring the DMS Interface Describes how to configure SAP’s DMS
for the Manage and View Components interface for the Manage and View
components of Content Services.
Chapter 6, Configuring SAP for PP-PI Describes how to configure SAP PP-PI for
Content Services.
Typographic conventions
This guide uses the following text conventions:
Convention Description
> Represents a pop-up or pull-down menu.
<Text enclosed within angle brackets> Represents a variable name for which you
must provide a value, or a defined term.
Represents code samples, user input, and
Information in this font
computer output.
[] square brackets Used in method command syntax
specifications, square brackets indicate an
optional argument.
{} curly brackets Used in method command syntax
specifications, curly brackets indicate an
optional argument that can be repeated
more than once.
Related documentation
This manual forms part of a documentation suite designed to support those who install,
configure, and use Content Services for SAP. The product and documentation suite can
be found on Documentum’s download center: https://documentum.subscribenet.com.
From Subscribenet, you can download the latest version of Content Services for SAP and
the related documentation suite. To access the contents in Subscribenet, 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 email address. If you cannot locate your
password, use the password finder at the bottom of the login page.
If you’re accessing Subscribenet for the first time, you will need to apply for access and
obtain a user name and password. Refer to Applying for access.
Note: Content Services extensively uses SAP’s ArchiveLink component. Please refer to
SAP ArchiveLink’s documentation for information on how you can perform advanced
tasks.
A server component that allows you to automate the linking process between SAP
objects and documents, as well as maintain those links. This substantially improves
productivity, information integrity, and information availability.
• Capture
Enables you to scan documents, store the images in a Documentum repository, and
create a link to the appropriate transaction documents in SAP. Once this link is
created, the document is accessible from SAPGUI, the SAP client interface. The
Capture component is part of Documentum’s integration to ArchiveLink.
• Manage
Enables you to release Documentum documents to SAP, and to maintain those
released documents.
• View
Enables you to view released Documentum documents from inside SAP.
The View component supports the following operating systems:
— Windows 2000
— Windows XP
— Windows 2003
The View component must be installed on every R/3 client computer that needs
to access reports, drawings and other documents stored in a Documentum
repository.
• Rendition Services
Build-in filters that provide the following renditions::
— PDF rendition
— ASCII text rendition
— HTML rendition
When one of these built-in filters are used, the desired document rendition is
generated when the document is archived in the repository.
• WebAdmin
An administrative console that allows you to:
— Create, configure, and manage archives
— Manage certificates for the archive
— Create repository connections for Content Services
— Configure document archival for Content Services
Note: Please refer to the Content Services for SAP Release Notes for detailed information
about specific OS versions and supported software environments.
This section presents some terms and their definitions, as used in this guide.
Term Definition
Content Services for SAP Product that connects Documentum to
SAP and vice versa.
Archiving Server Server component that, using an HTTP
connection to SAP, enables you to archive
reports, data, incoming and outgoing
documents from SAP to the Documentum
repository. 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 Documentum clients.
ArchiveLink 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.
Term Definition
WebAdmin An administrative console that allows you
to:
• Create and manage archives
• Manage certificates for the archive
• Create repository connections for the
Content Services
Capture Scanning module for Documentum and
SAP that is part of the Content Services
for SAP suite.
Capture Import Module that allows you to import scanned
documents (or other documents) to SAP
using the SAP ArchiveLink front-end
interface. This module is used with third
party scanning applications like Input
Software. The import module is part of
the same application as Content Services
Capture. The Content Services Capture
can operate in two different modes (scan
and import).
SAP DMS Document Management System that is
part of the SAP Basis System. Presents
a logical layer to integrate with external
systems like AutoCAD or Documentum.
Not directly related to ArchiveLink.
SAP PLM Product 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
Documentum.
SAP Master Record A set of master data, such as customer or
vendor data, which is used in the creation
of SAP documents.
SAPGUI SAP Graphical User Interface. Graphical
menu/screen tool that connects a client to
the SAP server.
Term Definition
Original Document Paper based version of a document.
Example 1-1.
An invoice may consist of two sheets
of paper received from a supplier.
Paper documents are scanned in and
stored as electronic documents in EMC
Documentum.
SAP Document An electronic transactional record of
header data and line items in SAP.
To create queues:
To schedule a job:
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 using 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 information:
To congure an optical archive as the output device for the Documentum installation for 4.x:
1. Execute the following transaction in the in the transaction code field: spad.
2. Click the Output Devices button.
3. Click the pencil button to edit settings.
Note: You can only have one printer and that printer must be named ARCH. If
you are already using a printer named ARCH you can either delete it or using 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 following information:
1. Start SAPGUI.
2. Execute the following transaction in the transaction code field: sole.
The Maintenance View for OLE Applications screen opens.
3. To configure Content Services Capture OLE communication, click the Edit button.
4. Click New Entries to create a new entry for a supported OLE application.
5. Enter the OLE application, click enter, then double-click the selected entry
(highlighted in red).
The Details screen opens.
6. Fill in the following information:
11. Click Enter, then double-click the selected entry (highlighted in red).
The Details screen opens.
12. Fill in the following configuration information:
configured via PROTOCOL. Each pair of document type and SAP object type maps to
an archive (these are described and ). For example, when a document is archived, the
document type and object type point to an archive. The archive in turn is configured
to use a certain protocol. From the protocol the SAPGUI determines how documents
are to be scanned and viewed via OLE.
7. Ensure that the Release generated object after call box is checked.
8. Go back to the previous window and select Archive From Frontend (usually by
double-clicking).
9. Fill in the following information:
• Application: DOCLINKSCAN.DOCUMENT
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 Stored
Document and Archive From Frontend show Maintained.
13. Execute the following transaction: oa3.
You should see a screen for SAP ArchiveLink: Communications interface
administration.
14. Choose Create.
The New Protocol dialog box opens. For example, you may wish to define the
protocol name as CONSVC53SP1 for Content Services fro SAP 5.3 SP1.
15. Enter the appropriate version of the protocol depending on whether you will be
needing RFC based archiving, version 0031 or HTTP based archiving, version 0045.
You may need a protocol for each type if you plan to use RFC and HTTP archiving
for example, ECONRFC and ECONHTTP.
16. Save your changes.
The Overview of a Protocol window opens, displaying your newly-defined protocol.
17. Select Display Stored Document (usually by double-clicking).
The Overview of a Protocol window opens showing a list of document classes.
18. Select the * row which indicates all document classes.
19. Click the pencil button.
The Overview of a Protocoll dialog box opens.
20. Type OPEN in the Communication Type field to view linked documents through
desktop applications. If HTTP archiving is used, the Communication Type HTTP
can also be selected here to view linked documents directly in SAPGUI.
21. Press the [Enter] key.
22. Type DCTM in the Application field, and click Continue.
23. Save your changes.
You are returned to the Overview of a Protocol window.
Note: This Protocol defines what method SAP will use to display an object. The
DCTM application requires Content Services View to be installed on all PC’s that
want to display Print lists (for other options look under SPECIAL PROTOCOLS). In
this case the Web Admin Client has to be configured to make sure the Best Format
sap_print_list is at the top of pdf and html. This is not required if PDF or HTML
renditions are not created. 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.
28. Type DCTM in the Application field, and click Continue.
29. Save your changes.
If you repeat step 18 and 23, 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.
Special protocols
You have options for special use protocols which are configured slightly different from
the standards described above. Anonymous login allows your name and password to be
provided each time a login would normally be required. Another option is that you may
wish to have Print lists displayed in the native proprietary format from SAPGUI instead
of viewing them via Documentum renditions as described above.
2. Ensure that the Release generated object after call checkbox is selected. Then
continue with the remaining steps.
2. Click Continue.
3. Ensure that the Release generated object after call checkbox is selected. Then
continue with the remaining steps.
SAP R/3 includes a Print List viewing feature that allows you to view saved Print lists
with SAPGUI in their native ALF format. To enable SAPGUI viewing you must configure
the protocol to support the viewer.
Note: If you convert Print List to PDF with renditioning, they can be viewed and
annotated without SAPGUI.
To congure the Print List viewer to display the Print Lists in SAPGUI for 4.x:
1. Choose Create.
The New Protocol dialog box opens. For example, you may wish to define the
protocol name as ECONALF for Content Services for SAP with ALF Viewer.
2. Enter the appropriate version of the protocol depending on whether you will be
needing RFC based archiving, version 0031 or HTTP based archiving, version 0045.
You may need a protocol for each type if you plan to use RFC and HTTP archiving
for example, ECONRFCA and ECONHTTPA.
3. Save your changes.
The Overview of a Protocol window opens, displaying your newly-defined protocol.
4. Select Display Stored Document (usually by double-clicking).
The Overview of a Protocol window opens showing a list of document classes.
5. Select the * row which indicates all document classes.
6. Click the pencil button.
The Overview of a Protocol dialog box opens.
7. Type OPEN in the Communication Type field.
8. Press the [Enter] key.
9. Type DCTM in the Application field, and click Continue.
10. In the Overview of a Protocol window showing the list of document classes, select
the ALF document class.
11. Click the pencil button.
The Overview of Protocol dialog box opens.
12. Type R/3 in the Communication Type field then press the [Enter] key.
No application is entered here.
13. Save your changes.
You are returned to the Overview of a Protocol window.
If you repeat step 4 and 11, you should see that the * document class is Maintained
Explicitly as well as the ALF document class. All other document classes should
show Not Maintained Explicitly.
• Application: DMVIEW.DOCUMENT
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:
• 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 33
• sm59 – RFC destination archives, page 36
• oac2 - Defining document types, page 38
• oac3 - Defining links, page 39
• ALF Reports/Print Lists, page 40
• Deleting archived and linked documents, page 42
• Customizing FAX - scanned documents, page 42
• Testing scanning documents, page 44
8. The next few fields are configured based on whether HTTP or RFC was selected.
• For HTTP:
— HTTP srvr:p: <ip>:<port> For example, 192.169.1.165:8080 uses port 8080 IP
is the IP address or name of the Web Server which is running the Content
Services HTTP Content Server and the port number being used (default is
80). If you use a server name here, ensure that you can ping the server by
name from the SAP server. If you use a port other than 80, use <ip>:<port>.
— Program Content Services/archive/<repository>.asp Enter Content
Services/archive/<repository>.asp where <repository> is the name of the
repository that you will be archiving content into. You must have an HTTP
service installed with Content Services for this repository. If you have not
already done so, after specifying the program, you will need to create the
HTTP service for a repository with a user name and password via the
Content Services installation program.
• For RFC:
— RFC destination: Enter the RFC destination from /nSM59, Content Services
Services, and WebAdmin. Refer to sm59 – RFC destination archives, page 36
for a description of how to create the Content Services RFC destination.
• For HTTP and RFC:
— Basic path: Type the network path to the location where SAP will put
archived documents to be picked up by Content Services Archive.
This directory should be referenced in the WebAdmin RFC destination
configuration screen. NT Example: m:\sapshare\ UNIX Example:
/sapmnt/DV2/global/archive/ This path must match the shared drive in the
WebAdmin RFC Destination configuration screen. There must be a slash at
the end of the path specification. For example, /sapshare/ or on Windows NT
systems using a mapped network drive, for example, M:\. The path must
always be terminated with / for Unix or \ for NT.
— Arch path: Usually the same as the Basic path. Repeat this procedure
to define the additional example archives BB and CC. You may use this
procedure to define any Documentum archives in SAP.
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 3.
• UNIX In the dmal.ini file: Set the debug level to 3.
2. Start your Content Services services or processes.
3. Start SAPGUI and connect to your R/3 system.
4. Execute the following transaction: sm59.
A new window opens, listing the folder hierarchy.
5. Click on the plus symbol in front of the folder labeled TCP/IP Connections.
A list of all RFC Destinations opens.
6. Double-click on the RFC destination that links SAP to the repository via Content
Services.
7. Click on 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).
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.
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.
To dene links:
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 22, 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.
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).
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 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 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 type
FIIINPREL.
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 below, when you install Content Services for
SAP, the custom BAPI will be available for linking and querying via the Web Admin tool.
In the following example, we are creating a custom BAPI to link and query purchase orders. The
query type for this custom BAPI is EKPO Table.
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>
The procedures in this chapter assume that the software is installed on at least one PC and that the
Documentum repository is configured according to your business needs. It is assumed that a default
installation of SAP has been performed. If this is not the case, you may find that the installation
steps differ in your R/3 system.
You must customize SAP before you can link documents to it. The customization work is necessary to
configure the CAD Interface to your needs. Additionally, you must verify a number of parameters
and certify that everything is configured properly. This chapter discusses the following topics:
• Configuring the Manage component, page 53
• Configuring Document Management Control Data, page 55
• Configuring general data, page 60
• Configuring CAD integration, page 67
• Configuring general data sub-levels, page 69
The examples in this chapter also assume a SAP default installation.
You must verify several parameters in Document Management Control data for 4.0.
You must verify several parameters in Document Management Control data for 4.x.
1. If necessary, open the Implementation Guide for R/3 Customizing window and
navigate to the Document Management System cabinet. (See Opening the Document
Management Control Data window, page 54.)
2. To navigate there, single-click on the cabinet icons to expand the selection:
Cross-Application Components>Document Management>Control Data.
The following items appear in a list:
• Define number ranges for document numbers
• Define document types
3. Click on each item (marked with a green tick and a clock) to configure it.
The following sections explain how to do this.
1. To edit the configuration, click on the Intervals button (marked with a red pen).
The Display Number Range Intervals window appears:
2. You should see number ranges configured as in the following example:
Example 5-1.
You can assign the value of DocumentType as DES for a DES document type.
For all document types, you can set the value of DocumentType as one of the
following:
• DocumentType=*
• DocumentType=
In this case, no value has been assigned to the parameter. The value for the
parameter has been set to blank.
6. Click the box at the beginning of the document type line.
7. Click the magnifying glass button.
Define the parameters for DRW as described below. Leave other fields blank.
Parameter Setting
Doc. type desc Engin/Des. Drawing
Version Assign. Checked
Ass. of rev. lev Checked
Archiving authorization Checked
Change docs Checked
Internal number range 02
External number range 01
Parameter Setting
Number exit MCDOKZNR
Vers. no. incr. 1
File size 0
1. If necessary, open the Implementation Guide for R/3 Customizing window and
navigate to the Document Management System cabinet. To navigate there,
single-click on the cabinet icons to expand the selection: Cross-Application
Components > Document Management > Control Data.
2. Select Define Document Types.
A list of your configured Document types appears.
3. Starting with the document type DRW, define the parameters for each document
type you intend to store within Documentum.
Note: Since the PLM type objects are usually drawings, a default value of “DRW”
is used. You can always override this setting in the Query Conditions field of the
SAP Query Composer (refer to the “Creating, Viewing, and Editing an SAP Query”
section of the Content Services for SAP Administration Guide).
Example 5-2.
You can assign the value of DocumentType as DES for a DES document type.
For all document types, you can set the value of DocumentType as one of the
following:
• DocumentType=*
• DocumentType=
In this case, no value has been assigned to the parameter. The value for the
parameter has been set to blank.
4. Click the box at the beginning of the document type line.
5. Click the magnifying glass button.
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
1. Verify that the following three items are configured and the names are spelled
exactly as follows:
2. Click Back.
This returns you to the Document Management Control Data screen.
To dene and maintain object link descriptions for 4.0 and 4.x:
1. If necessary, open the Implementation Guide for R/3 Customizing window and
navigate to the Document Management System cabinet. (To navigate there,
single-click on the cabinet icons to expand the selection: 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 green tick and a clock) to configure it.
The following sections explain how to do this.
Use the following procedure to congure a new carrier type for 3.x:
Use the following procedure to congure a new carrier type for 4.0 and 4.x
Use the following procedure to congure a default front-end computer (if not already
congured) for 3.x:
Use the following procedure to congure a default front-end computer (if not already
congured) for 4.0 and 4.x:
1. Navigate to the Define data carrier type “server, front end” option and select the
type PC.
2. Select Identify frontend computers from the navigation area.
3. Make sure that the following entry is defined:
• FrontendComputer. = DEFAULT
• Program = dmview.exe
If you have installed the View component somewhere other than the default SAP
main program directory, you must define the path.
If you installed WebView for viewing documents, you should define the Program as:
dmwebview.exe %f host/rs-bin/RightSite.dll
To congure and verify the control parameters for 3.x and 4.0:
You may receive an error message here stating that control parameters are not
defined for the current client. If this happens, save the settings even if you have
not modified anything.
Dening functions
Use the Position button to verify that the following items in the table are defined. This
table must contain about 180 entries:.
Documentum Content Services for SAP allows you to link documents stored in a Documentum
repository to an SAP PP-PI (Production Planning for Process Industries) instruction sheet. Documents
are thus directly accessible from SAP PP-PI sheets.
SAP PP-PI modules control the manufacturing process in process industry environments. PP-PI
allows you to define hyperlinks to external applications, enabling you to retrieve documents (such as
recipes or SOPs) from a Documentum repository by using a configurable query together with specific
parameters. This mechanism is very flexible and is independent of the Documentum or ArchiveLink
system. Documents are linked to SAP PP-PI with a query stored in Documentum.
This information in this chapter assumes that the Content Services View is installed on at least one PC
and that the Documentum repository is configured according to your business needs.
You must customize the SAP server before you can use hyperlinks from a PP-PI sheet. This section
explains how to create and configure the mandatory new process instruction categories. These
concepts are described in the following sections:
• Configuring the Process Instruction category, page 71
• Defining Process Instruction category DCTM, page 72
• Configuring the Characteristics/Process Instruction category, page 72
The default location of the Content Services View executable is the SAPGUI
installation directory. This is a system-wide setting.
The maximum numbers of characters is 30.
6. 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. You
may either leave this field blank for now, or enter the repository name and the query
name. The command line has some constraints:
• The maximum string length is 30 characters.
• All letters are capitalized.
8. Enter the value for the characteristics described below.
/ Comments
PPPI_FUNCTION_NAME WS_EXECUTE
PPPI_BUTTON_TEXT Show Related Documents
/ Comments
PPPI_EXPORT_PARAMETER COMMANDLINE
PPPI_STRING_CONSTANT The value of this field is the command line
passed to Content Services View. You may
either leave this field blank for now, or enter
the repository name and the query name. The
command line has some constraints:
A number ranges, 21
Administrative Console, 15 optical archive as output device, 22
Agent services, 15 content repositories, 33
ALF, 38, 40 Content Services, see Content Services for
ALF class, 16 SAP
ALF format, 16 Content Services for SAP, 7
Anonymous Login defined, 13
protocol, 29 Content Services for SAP administrator, 7
archived and deleting documents, Content Services server, 38
deleting, 42 creating
archived data, 16 queues, 21
archived Print List creating links, 7
displaying in SAPGUI, 41 CS for SAP, see Content Services for SAP
ArchiveLink Monitor window, 41
archiving D
Print List, 40
DB2, 7
archiving reports
defining
testing, 40
document types, 38
Archiving request window, 41
links, 39
Archiving Server, 14
logical ArchiveID, 20
asynchronous queue, 21
deleting
archived and linked documents, 42
B displaying
bar codes, 44 archived Print List in SAPGUI, 41
basic settings, configuring, 20 dmview.exe, 65 to 67
document
incoming, 16
C outgoing, 16
CAD field sets, 70 scanned, 16
CAD Integration, configuring, 67 supported formats in SAP, 16
capture operator, 7 document controller, 7
class document formats, supported in SAP, 16
ALF, 16 Document Management General Data, 64
FAX, 16 to 66, 69
OTF, 16 document types
REO, 16 ALF, 38
configuration procedures, 36, 67 defining, 38
configuring FAX, 38
basic settings, 20 OTF, 38
Manage, 53 REO, 38
I P
Inline Print List Viewer PDF format, 16
prerequisites
protocol, 30
system administrator, 7
intended audience, 7
Print List, 40
archived, displaying in SAPGUI, 41
J archiving, 40
jobs, scheduling, 22 Print Lists, 16
ALF class, 16
ALF format, 16
L protocol
linking, 42 Anonymous Login, 29
links Inline Print List Viewer, 30
defining, 39 purpose of the guide, 7
logical ArchiveID
defining, 20
Q
queues, creating, 21
M
maintaining links, 7
Manage, 53 to 55 R
releasing documents to SAP, 7
REO, 38
N REO class, 16
number ranges, configuring, 21 REO format, 16
Reports, see Print Lists
O RFC destination archive, 36
oaa4, 27
oaat, 22 S
oac0, 20, 33 SAP
OAC0, 34 print spooler, 24