Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
Preface
Chapter 1
Chapter 2
Chapter 3
...........................................................................................................................
...................................................
Overview ...................................................................................................
Understanding the Content Services for SAP architecture .............................
Supported SAP document formats ...............................................................
Understanding SAP and Content Services for SAP terms ..............................
13
14
16
16
19
19
20
20
21
21
22
22
24
25
26
29
29
30
31
33
33
36
37
38
39
40
40
42
42
42
43
44
44
13
Table of Contents
......................................................................... 49
Chapter 4
Chapter 5
53
53
53
54
55
56
56
59
60
61
61
62
63
64
65
67
67
69
69
70
70
71
71
72
72
Chapter 6
Table of Contents
List of Figures
Figure 11.
14
Table of Contents
List of Tables
Table 11.
Table 21.
Table 22.
16
23
24
Table 23.
Table 24.
Table 25.
Table 26.
Table 27.
Table 28.
Table 29.
25
26
27
28
29
30
32
Table 31.
34
Table 32.
Table 51.
Table 52.
Table 53.
Table 54.
39
56
57
59
59
Table 55.
Table 56.
Table 57.
Table 61.
60
69
70
73
Preface
Purpose of this guide
This guide explains how to congure SAP to use Content Services for SAP 5.3 SP1 (CS
for SAP 5.3 SP1 or Content Services 5.3 SP1). It provides task-based instructions for
conguring SAP, so that it works together with Content Services.
Intended audience
In order to address the manuals to the correct audience, the roles of the users of the
manuals have been dened as follows:
System Administrator - This role covers users who install and congure 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.
Preface
Revision history
This section contains a description of this documents revision history.
Revision history
Revision Date
Description
January 2004
March 2004
January 2005
June 2005
October 2005
Chapter
Contents
Preface
Chapter
Contents
Typographic conventions
This guide uses the following text conventions:
Typographic conventions used in this guide
Convention
Description
>
[] square brackets
{} curly brackets
Related documentation
This manual forms part of a documentation suite designed to support those who install,
congure, and use Content Services for SAP. The product and documentation suite can
be found on Documentums 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 rst applied for access.
Note: Your login ID, by default, is your email address. If you cannot locate your
password, use the password nder at the bottom of the login page.
Preface
If youre accessing Subscribenet for the rst time, you will need to apply for access and
obtain a user name and password. Refer to Applying for access.
Content Services for SAP documentation suite
Title
Description
Target role
Provides an overview
of new and amended
features, known bugs,
limitations, miscellaneous
technical notes, and
documentation correctness
and clarications.
System Administrator
System Administrator
(SAP)
Content Services
Administrator
Standard User
Note: Content Services extensively uses SAPs ArchiveLink component. Please refer to
SAP ArchiveLinks documentation for information on how you can perform advanced
tasks.
1.
2.
3.
4.
10
Preface
1.
2.
3.
4.
5.
6.
Click List.
7.
11
Preface
12
Chapter 1
Introducing Content Services for SAP
Overview
The Content Services for SAP application integrates the Documentum content
management system with the SAP R/3 system. It is an interface to the SAP R/3 system
based on SAPs standard DMS and ArchiveLink interfaces.
Content Services for SAP provides the following functionalities:
13
for SAP
14
Agent services
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 Documentums 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 lters that provide the following renditions::
PDF rendition
ASCII text rendition
HTML rendition
When one of these built-in lters 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, congure, and manage archives
Manage certicates for the archive
Create repository connections for Content Services
Congure document archival for Content Services
15
Note: Please refer to the Content Services for SAP Release Notes for detailed information
about specic OS versions and supported software environments.
for
This section presents some terms and their denitions, as used in this guide.
Table 1-1. Terms and denitions
16
Term
Denition
Archiving Server
ArchiveLink
Term
Denition
WebAdmin
Capture
Capture Import
SAP DMS
SAP PLM
SAPGUI
17
Term
Denition
Original Document
18
Chapter 2
Conguring the ArchiveLink Interface
for Content Services for SAP
Overview
The Archiving Server component is the part of the Content 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.
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, the SAP R/3 system must also be congured. This
chapter describes how to congure your R/3 ArchiveLink and other related transactions
through SAPGUI and the R/3 system.
Note: The conguration steps often reference direct transaction codes. These codes
allow you to navigate directly to the correct conguration screen. Most of the system
conguration 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 conguring Archive Services, you can congure either an HTTP-based Archive
Server or an RFC (Remote Function Call) Archive Server.
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.
The conguration steps are different for RFC and HTTP based archiving. Conguration
steps have been marked as being relevant only to RFC- or HTTP-based archiving.
The various conguration tasks that you have to perform are described in the following
sections:
19
1.
2.
3.
In the Display Content Repositories: Detail page, click the Display/Change icon
The Copy as ... button is now enabled.
4.
5.
Edit the Content Rep. eld so that its the same as ArchiveID created using
WebAdmin (refer to the Conguring, Viewing, and Editing Archives section of the
Content Services for SAP Administration Guide).
6.
In the Transfer drctry eld, enter the directory path where SAP can write the Print
List till it is in the Storage Queue.
7.
8.
9.
20
1.
2.
Ensure that the Deactivate Print List Management in DMS box is checked.
3.
1.
2.
To edit the conguration, click on the Intervals button (marked with a pencil).
The Display Number Range Intervals window opens.
3.
4.
1.
2.
3.
4.
Choose Program>Execute.
5.
21
1.
2.
3.
4.
5.
6.
7.
8.
9.
Frequency of archival
Time taken to archive your largest document; for example, your largest Print List
1.
22
2.
Execute the following transaction in the in the transaction code eld: spad.
3.
4.
5.
In case ARCH already exists, select device ARCH and click the Delete button.
6.
7.
Field name
Value
Output Device
ARCHIVE
Short Name
ARCH
Device Type
ARCHLINK
Spool Server
Location Fill
Archive
Message Fill
ArchiveLink Device
8.
9.
10. Execute the following transaction in the in the transaction code eld: 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 eld.
23
1.
Execute the following transaction in the in the transaction code eld: spad.
2.
3.
4.
In case ARCH already exists, select device ARCH and click the Delete button.
5.
6.
Field name
Value
Host Printer
Device Class
Spool Server
7.
8.
1.
24
2.
1.
Start SAPGUI.
2.
3.
To congure 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.
Field name
Value
OLE Application
DOCLINKSCAN.DOCUMENT
CLSID
{135C6154-BFC0-11D0-B56900C04FD88E1E}
NO_TYPELIB
Language
EN [English]
Text
7.
8.
9.
10. Click New Entries to create a new entry for a supported OLE application.
25
11. Click Enter, then double-click the selected entry (highlighted in red).
The Details screen opens.
12. Fill in the following conguration information:
Table 2-4. Field descriptions
Field name
Value
OLE Application
DMVIEW.DOCUMENT
CLSID
{B8192AB0-DB3A-11D0-97410060974A8A8D}
NO_TYPELIB
Language
EN [English]
Text
Enter the above information exactly as it is displayed. All other elds should be
left blank.
13. Save your changes.
14. Execute the following transaction in the transaction code eld: soli.
The Type Info Loaded screen opens. Both the OLE applications you congured
in the previous steps should be listed.
15. To load the conguration, double-click each new entry DMVIEW.DOCUMENT and
DOCLINKSCAN.DOCUMENT (or in SAP 3.x, click Load TypeInfo).
16. Check to see if you congured these items correctly.
a.
b. If nothing opens:
Click the Change Language button (either on a menu or right click the item)
26
congured 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 congured
to use a certain protocol. From the protocol the SAPGUI determines how documents
are to be scanned and viewed via OLE.
To congure applications maintenance and the communications protocol to associate the
correct OLE 2 method to an SAP archive for 4.x:
1.
2.
3.
window.
4.
5.
6.
Application: DMVIEW.DOCUMENT
Radio button
Command
DOCBASE=<Your_Repository_Name>
Display @DID
@EID=ERRORCODE
@ETX=ERRORTEXT
7.
Ensure that the Release generated object after call box is checked.
8.
Go back to the previous window and select Archive From Frontend (usually by
double-clicking).
9.
Application: DOCLINKSCAN.DOCUMENT
27
Radio button
Command
Scan
@EID=ERRORCODE
@ETX=ERRORTEXT
@DID=DOCID
10. Ensure that the Release generated object after call box is checked.
11. Return to the previous screen and save your conguration.
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 dene 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-dened 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 eld 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 eld, and click Continue.
23. Save your changes.
You are returned to the Overview of a Protocol window.
28
Note: This Protocol denes what method SAP will use to display an object. The
DCTM application requires Content Services View to be installed on all PCs that
want to display Print lists (for other options look under SPECIAL PROTOCOLS). In
this case the Web Admin Client has to be congured 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 eld.
27. Press the [Enter] key.
28. Type DCTM in the Application eld, 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 congured 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.
1.
Application: DMVIEW.DOCUMENT
Radio button
Command
USER=<username>
PASSWORD=<password>
29
Radio button
Command
Display @DID
@EID=ERRORCODE
@ETX=ERRORTEXT
2.
Ensure that the Release generated object after call checkbox is selected. Then
continue with the remaining steps.
1.
Application: DOCLINKSCAN.DOCUMENT
Radio button
Command
DOCBASE=<repository>
USER=<username>
PASSWORD=<password>
DOMAIN=<domain>
CLIENT=<client>
SYSTEM=<system>
Scan
@EID=ERRORCODE
@ETX=ERRORTEXT
@DID=DOCID
2.
Click Continue.
3.
Ensure that the Release generated object after call checkbox is selected. Then
continue with the remaining steps.
30
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 dene 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.
4.
5.
6.
7.
8.
9.
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 eld 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.
1.
31
Application: DMVIEW.DOCUMENT
32
Radio button
Command
DOCBASE=<Your_Repository_Name>
Display @DID
@EID=ERRORCODE
@ETX=ERRORTEXT
Chapter 3
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:
ALF
FAX
OTF
REO
OAC0
OAC2
OAC3
plus any specic customizations. These customizations are described in the following sections:
33
1.
2.
oac0
spro
3.
4.
5.
6.
7.
34
Field name
Value
Content rep
Description
Storage Type
Protocol
Field name
Value
Version No.
Output Device
ARCHIVE
8.
The next few elds are congured 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.
35
1.
2.
3.
4.
Click Create.
5.
6.
7.
8.
9.
Press [Enter].
36
1.
Switch on debugging before processes or services are started the rst time by setting
the debug level:
2.
3.
4.
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.
37
A message appears on the status bar, stating that the connection is OK. A new
window opens, displaying some performance gures (similar to ping).
8.
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 conguration 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 le.
FAX documents are documents that will be scanned and linked to SAP.
OTF are outgoing SAPSCRIPT documents produced and linked from SAP.
REO documents are data archive les which are compressed by the SAP ADK and
stored externally in that format.
1.
2.
3.
38
If you are modifying an existing document type, use Change and Details.
4.
Enter information in the Description and Doc. class elds as appropriate for your
conguration.
5.
When you have nished selecting document types, save your changes.
1.
2.
3.
Field name
Value
Object Type
Document Type
S (Status)
Arch. ID
Link
Ret Prd.
4.
39
1.
2.
3.
In the List of Customer Open Items page that appears, select List>Print.
The Print Screen List dialog box appears.
4.
5.
6.
7.
Verify that the Object Type and Document Type elds contain the correct values, as
congured in the New Entries table (refer to oac3 - Dening links, page 39). Pick
the following values for example: SOOD GENPRILIS.
If your Document Type is incorrectly congured, refer to the following procedures
for conguring document types in SAP archives:oac2 - Dening document types,
page 38 and oac3 - Dening links, page 39.
8.
40
This label may be anything you wish; for example, your initials.
9.
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 eld: 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 conguring 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 conrmation 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.
2.
3.
4.
41
Then you can make specic customizations using the following procedures:
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:
For storing for subsequent entry which uses SAP workow to move the image to the SAP
inbox, you can specify what organizational object will be used for routing (like User) and
then what specic organizational object to route to (like the SAP User ID).
To display/change SAP settings for document types for 4.X:
1.
42
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 specied 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 eld.
This enables you to send scanned documents to your SAP workow inbox (You may
want to integrate these entries with the SAP organizational roles, see your workow
consultant for details).
6.
7.
Make sure to note the values of document type and object type elds.
You will need these values to complete later conguration steps. For example,
Incoming Invoice Preliminary Posting has an object type BKPF and object type
FIIINPREL.
43
To congure all SAP object type/document type/User ID combinations you want to use
with bar codes for 4.x.
1.
2.
Click Edit.
3.
4.
Enter any SAP object types for which you want a bar code dialog to open upon
saving of that object.
5.
Enter any SAP document types for which you want a bar code dialog to open upon
saving of that document.
6.
Enter any User IDs for which you want a bar code dialog to open upon saving under
that user ID.
7.
8.
Enter your object, document, and user ID to test your bar code.
1.
44
2.
3.
In Content Services Capture, scan or import a few pages and ll in the default
attributes.
4.
From the Document Type drop-down list, select Sap_invoice (or other valid
Documentum document type).
5.
6.
7.
8.
9.
While the image displays in Content Services Image Viewer, ll in the attributes.
10. Click the Add to Queue button from Content Services Capture and the image should
disappear from the Viewer.
11. Minimize Content Services Capture.
12. In SAP, use transactions OAC2, SOA0, OACA, OAC3, OAC0 and OAWS to review
the settings for the doc type you are planning to use. For example, FIIINPREL.
13. In WebAdmin, make sure you have set up an Archive for incoming fax which
matches the Archive ID information found via OAC3 and OAC0.
You can copy and modify an existing incoming document archive.
14. On your Content Services Server, make sure that the Archive Services are started
with the correct:
RFC Destination
Share user ID
and that you IIS is up and running with HTTP, and certicates have been installed
15. To link the document with SAP workow and remove it from the queue.
16. Maximize Content Services Capture.
17. Capture and select the document in the linking queue.
18. Start SAPGUI and select Ofce>Business Documents>Documents>Move> <your
OAWS setting>.
Size the windows so that you can see both SAP and Capture.
19. Select the SAP document type which points to your user ID.
20. Click the Store For Subsequent Entry icon.
21. Replace the existing text with meaningful text so you will be able to recognize the
le in a later step.
22. Select Continue (Check).
45
Currency/date: USD
Doc type: KR
46
47
48
Chapter 4
Creating Custom BAPIs
Content Services for SAP enables you to create and install custom conguration objects known as
BAPIs for linking and querying SAP data.
To create a custom BAPI you must modify the custom.xml le that is included with the Content
Services for SAP installation les. The installation les are available for downloading from
subscribenet.com (see the Installation Guide for more details on downloading the release). After
modifying the custom.xml le 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.
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 le named custom.xml in the Server folder of the installation les.
3.
4.
Add the following sample XML code to the custom.xml le. 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 le:
<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>
49
</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>
Repeat these steps to create as many custom BAPIs as you need, creating separate
XML elements in the custom.xml le for each custom BAPI.
6.
To install the custom BAPIs into your repository, run the Content Services for SAP
Server setup.exe le, choose Docbase Conguration, 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 eld 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>
50
51
52
Chapter 5
Conguring the DMS Interface for the
Manage and View Components
The procedures in this chapter assume that the software is installed on at least one PC and that the
Documentum repository is congured 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 nd 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
congure the CAD Interface to your needs. Additionally, you must verify a number of parameters
and certify that everything is congured properly. This chapter discusses the following topics:
1.
53
Conguring the DMS Interface for the Manage and View Components
2.
3.
Click Enter.
4.
Click the Enterprise IMG button, F5 or click on the button for your specic project if
you congure your system on a project basis.
The Implementation Guide for R/3 Customizing screen appears:
5.
1.
2.
3.
Click Enter.
4.
Select Implement Projects>SAP Reference IMG (or click on the button for your
specic project if you congure your system on a project basis).
The Implementation Guide for R/3 Customizing screen appears:
5.
1.
2.
Click Enter.
3.
Click the Enterprise IMG button, F5 (or click on the button for your specic project if
you congure your system on a project basis).
The Implementation Guide for R/3 Customizingscreen appears:
4.
54
Conguring the DMS Interface for the Manage and View Components
1.
2.
Select SAP Reference IMG (or click on the button for your specic project if you
congure your system on a project basis).
The Implementation Guide for R/3 Customizing window appears:
3.
1.
2.
3.
Click on each item (marked with a green tick and a clock) to congure it.
The following sections explain how to do this.
You must verify several parameters in Document Management Control data for 4.0.
1.
2.
Click on each item (marked with a green tick and a clock) to congure it.
The following sections explain how to do this.
55
Conguring the DMS Interface for the Manage and View Components
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.
3.
Click on each item (marked with a green tick and a clock) to congure it.
The following sections explain how to do this.
1.
To edit the conguration, click on the Intervals button (marked with a red pen).
The Display Number Range Intervals window appears:
2.
No.
From number
To number
Ext.
01
00000000000000000001
00000000000000999999
Checked
02
00000000010000000000
00000009999999999999
Unchecked
03
00000010000000000000
99999999999999999999
Checked
04
00000000000001000000
00000000009999999999
Checked
3.
4.
Click the Back button twice. This returns you to the Document Management Control
Data window.
1.
56
Conguring the DMS Interface for the Manage and View Components
3.
Click Enter.
4.
5.
Starting with the document type DRW, dene the parameters for each document
type.
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 eld 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-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.
7.
Parameter
Setting
Engin/Des. Drawing
Version Assign.
Checked
Checked
Archiving authorization
Checked
Change docs
Checked
02
01
57
Conguring the DMS Interface for the Manage and View Components
Parameter
Setting
Number exit
MCDOKZNR
File size
8.
9.
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.
3.
Starting with the document type DRW, dene 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 eld 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.
5.
58
Conguring the DMS Interface for the Manage and View Components
Parameter
Setting
Engin/Des. Drawing
Version Assign.
Checked (optional)
Checked (optional)
Archiving authorization
Checked
Change docs
Checked (optional)
02
01
Number exit
MCDOKZNR
File size
6.
7.
1.
Verify that the following three items are congured and the names are spelled
exactly as follows:
Lang.
Object
Name
EQUI
Equipment master
IFLOT
Functional location
MARA
Material master
2.
Click Back.
This returns you to the Document Management Control Data screen.
To dene and maintain object link descriptions for 4.0 and 4.x:
1.
59
Conguring the DMS Interface for the Manage and View Components
2.
3.
Verify that the following three items are congured and the names are spelled
exactly as follows:
Lang.
Object
Name
EN
EQUI
Equipment master
EN
IFLOT
Functional location
EN
MARA
Material master
4.
1.
2.
3.
Click Enter.
4.
5.
Close the Document Management Control Data screen and navigate to the General
Data level.
The following items are listed:
6.
60
Click on each item (marked with a green tick and a clock) to congure it.
Conguring the DMS Interface for the Manage and View Components
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.
3.
Click on each item (marked with a green tick and a clock) to congure it.
The following sections explain how to do this.
1.
2.
3.
TY = EX
Description = Documentum
Save the new entry. You should then go on to dene the data carrier type server,
front end.
61
Conguring the DMS Interface for the Manage and View Components
1.
2.
3.
TY = EX
Description = Documentum
4.
5.
6.
Save the new entry. You should then go on to dene the data carrier type server,
front end.
1.
2.
If the type PC does not exist, click the New Entries button and set the parameters
as listed in step 2.
Online = checked
Printer = unchecked
Vault = unchecked
Ex = checked
3.
4.
5.
Click Back.
You should then go on to dene the data carrier
Use the following procedure to congure a new carrier type for 4.0 and 4.x
1.
62
Conguring the DMS Interface for the Manage and View Components
2.
If the type PC does not exist, click the New Entries button and set the parameters
as listed in step 2.
Type = PC
Description = Windows PC
Online = Checked
3.
4.
5.
Click Back.
You should then go on to dene the data carrier.
1.
2.
DataCar = DEFAULT
Ty = PC
3.
4.
5.
Click Back.
You should then go on to dene the workstation applications.
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 Dene data carrier type server, front end option and select the
type PC.
2.
3.
FrontendComputer. = DEFAULT
63
Conguring the DMS Interface for the Manage and View Components
4.
5.
6.
Click Back.
You should then go on to dene the workstation applications.
1.
2.
WS application = DCM
StartAut = checked
3.
4.
5.
Click Back.
You should then proceed to dene the Workstation Applications in a Network.
64
1.
2.
Conguring the DMS Interface for the Manage and View Components
3.
WS application = DCM
4.
5.
1.
DataCar type = PC
Applic. = DCM
ApplTyp = 1 (Display)
You can congure Content Services to provide a print button in addition to a view
one. This option is not available under WebView. To congure printing, add an
identical entry which has the ApplTyp = 3 (Print) and dene the program as
dmview.exe /print %f
Program = dmview.exe
If you have installed the View component somewhere other than the default SAP
main program directory, you must dene the path.
If you installed WebView for viewing documents, you should dene the Program as:
dmwebview.exe %f host/rs-bin/RightSite.dll
StartAuth = Yes
2.
3.
4.
Click Back.
This is the nal task for document management customization.
65
Conguring the DMS Interface for the Manage and View Components
1.
2.
Select the DCM entry and navigate to Dene workstation applications in network.
3.
You can congure Content Services to provide a print button in addition to a view
one. This option is not available under WebView. To congure printing, add an
identical entry which has the Application Type = 3 (Print) and dene the program as
dmview.exe /print %f
If you have installed the View component somewhere other than the default SAP
main program directory, you must dene the path.
If you installed WebView for viewing documents, you should dene the Program as:
dmwebview.exe %f host/rs-bin/RightSite.dll
4.
5.
6.
Click Back.
1.
2.
Select the DCM entry and navigate to Dene workstation applications in network.
3.
4.
66
Conguring the DMS Interface for the Manage and View Components
If you have installed the View component somewhere other than the default SAP
main program directory, you must dene the path.
If you have installed WebView for viewing documents, you must dene the program
as dmwebview.exe. (The previous note about passing program arguments applies
also to dmview.exe. For example, If webview.exe is called without command line
parameters, the user is prompted to ll in the host name under which the Web
application runs. To get around this problem, see OSS notes: 0135155 and 0105208.)
This conguration may look different for a UNIX Web server.
5.
6.
7.
Click Back.
1.
2.
3.
Description = Documentum.
4.
5.
67
Conguring the DMS Interface for the Manage and View Components
To congure and verify the control parameters for 3.x and 4.0:
1.
2.
3.
Click Enter.
4.
5.
The remaining parameters on this screen are not relevant and do not need to be
edited.
6.
7.
1.
2.
The remaining parameters on this window are not relevant and do not need to be
edited.
3.
4.
68
Conguring the DMS Interface for the Manage and View Components
You may receive an error message here stating that control parameters are not
dened for the current client. If this happens, save the settings even if you have
not modied anything.
Dening functions
Use the Position button to verify that the following items in the table are dened. This
table must contain about 180 entries:.
Table 5-6. Function values
Proc. Code
Sub-process code
DOCCH
DO
DOCCR
MR
DOCRQ
CL
EQUIRQ
MR
MATRQ
MR
69
Conguring the DMS Interface for the Manage and View Components
Direction = U
70
Field set
Field name
DCCRDAT
DOC_NUMBER
DCCRDAT
DOC_TYPE
DCCRDAT
DOC_PART
DCCRDAT
DOC_VERS
DCCRDAT
DESCRIPT_D
DCCRDAT
DISP_APPL
DCCRDAT
DATA_CARR
DCCRDAT
ORIGINAL
DCCRDAT
PROTOCOL
Chapter 6
Conguring SAP for PP-PI
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 dene hyperlinks to external applications, enabling you to retrieve documents (such as
recipes or SOPs) from a Documentum repository by using a congurable query together with specic
parameters. This mechanism is very exible 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 congured 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 congure the mandatory new process instruction categories. These
concepts are described in the following sections:
1.
2.
To invoke the SAP conguration tool, type /nspro into the command eld.
A dialog box appears.
3.
4.
Click the Enterprise IMG button (or click your specic project if you congure your
system on a project base).
71
6.
1.
2.
3.
4.
You must have a screen resolution of at least 600x800 to be able to enter characteristics
of the new process instruction category.
1.
2.
3.
4.
5.
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.
7.
8.
Characteristic
PPPI_FUNCTION_NAME
WS_EXECUTE
PPPI_BUTTON_TEXT
PPPI_EXPORT_PARAMETER
PROGRAM
PPPI_STRING_CONSTANT
73
Characteristic
PPPI_EXPORT_PARAMETER
COMMANDLINE
PPPI_STRING_CONSTANT
9.
74
Index
A
Administrative Console, 15
Agent services, 15
ALF, 38, 40
ALF class, 16
ALF format, 16
Anonymous Login
protocol, 29
archived and deleting documents,
deleting, 42
archived data, 16
archived Print List
displaying in SAPGUI, 41
ArchiveLink Monitor window, 41
archiving
Print List, 40
archiving reports
testing, 40
Archiving request window, 41
Archiving Server, 14
asynchronous queue, 21
number ranges, 21
optical archive as output device, 22
content repositories, 33
Content Services, see Content Services for
SAP
Content Services for SAP, 7
dened, 13
Content Services for SAP administrator, 7
Content Services server, 38
creating
queues, 21
creating links, 7
CS for SAP, see Content Services for SAP
DB2, 7
dening
document types, 38
links, 39
logical ArchiveID, 20
deleting
archived and linked documents, 42
displaying
archived Print List in SAPGUI, 41
dmview.exe, 65 to 67
document
incoming, 16
outgoing, 16
scanned, 16
supported formats in SAP, 16
document controller, 7
document formats, supported in SAP, 16
Document Management General Data, 64
to 66, 69
document types
ALF, 38
dening, 38
FAX, 38
OTF, 38
REO, 38
75
B
bar codes, 44
basic settings, conguring, 20
Index
documents, 42, 55
F
f.21, 40
FAX, 38, 42
FAX class, 16
eld sets, allocating, 70
format
ALF, 16
PDF, 16
REO, 16
Tiff, 16
frequency of archival, 22
G
General Data, 69 to 70
PDF format, 16
prerequisites
system administrator, 7
Print List, 40
archived, displaying in SAPGUI, 41
archiving, 40
Print Lists, 16
ALF class, 16
ALF format, 16
protocol
Anonymous Login, 29
Inline Print List Viewer, 30
purpose of the guide, 7
J
jobs, scheduling, 22
L
linking, 42
links
dening, 39
logical ArchiveID
dening, 20
queues, creating, 21
maintaining links, 7
Manage, 53 to 55
N
number ranges, conguring, 21
O
oaa4, 27
oaat, 22
oac0, 20, 33
OAC0, 34
76
oac2, 38
oac3, 39
oadr, 41
oag1, 20
oam1, 21
oanr, 21
oaq1, 21
oaqi, 21
OAWS, 42
OLE, application, 25
optical archive, conguring as output
device, 22
Oracle, 7
OTF, 38
OTF class, 16
output device
conguring logical archive as, 22
S
SAP
print spooler, 24
Index
ALF format, 16
FAX class, 16
OTF class, 16
PDF format, 16
REO class, 16
REO format, 16
Tiff format, 16
Sybase, 7
system administrator, 7
prerequisites, 7
T
test scanning, 44
testing the connection, 37
Tiff format, 16
transaction code
f.21, 40
oaat, 22
oac0, 20, 33
oac2, 38
oac3, 39
oadr, 41
oag1, 20
oam1, 21
oanr, 21
oaq1, 21
oaqi, 21
sm50, 24
spad, 22
spro, 19
Transfer drctry eld, 20
U
ueue Administrator eld, 21
user roles, 7
V
verifying, spool processes, 24
View, 53 to 55
W
WebAdmin, 15
77