• No results found

223 BB ConfigGuide en US Configuration and Setup of Easy Document Management System

N/A
N/A
Protected

Academic year: 2021

Share "223 BB ConfigGuide en US Configuration and Setup of Easy Document Management System"

Copied!
19
0
0

Loading.... (view fulltext now)

Full text

(1)

English

Configuration and Setup

of Easy Document

Management System

(EasyDM) (223)

SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf Germany

(2)

Copyright

©© 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook,and PowerPointare registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(3)

Icons

Icon Meaning Caution Example Note or Tip Recommendation Syntax

Typographic Conventions

Type Style Description

Example

text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example

text Emphasized words or phrases in body text, titles of graphics and tables. EXAMPLE

TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a

programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example

text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example

text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example

(4)

Contents

1 Purpose... 5

2 Preparation... 5

2.1 Prerequisites... 5

3 Configuration... 6

3.1 Settings for Document Management...6

3.1.1 Define Document Types...6

3.1.2 Define Data Carrier...11

3.1.3 Defining Workstation Application...13

3.2 Download and Installation of Easy Document Management...16

3.2.1 Download of Easy Document Management (Manual Step)...16

3.2.2 Installation of Easy Document Management (Manual Step)...17

3.3 Trouble Shooting... 19

(5)

Configuration of Easy Document Management

(EasyDM)

1 Purpose

SAP Document Management allows managing and storing documents within SAP. Documents This configuration guide provides you with the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the SAP Best Practices Quick Guide, located on the SAP Note.

2 Preparation

2.1 Prerequisites

Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisite Matrix for Baseline. The matrix (an Excel file) is linked on the solution's DVD/website in one of the following two locations:

 Content Library  Site Map

(6)

3 Configuration

3.1 Settings for Document Management

3.1.1

Define Document Types

Use

The purpose of this activity is to define the document type YBO for office documents.

Prerequisites

A number range must be defined already.

Recommendation:

SAP Document Management stores the document info records, that is, the meta data, inside the SAP system. The document info records contain links to the actual original files. These originals should typically be stored in a SAP Content Server, that is, on a separate server.

If an SAP Content Server is not available, the storage category DMS_C1_ST can be used. Using this category will save the originals in the SAP database. This is useful for testing but not recommended for a productive environment.

Procedure

1. Access the activity using one of the following navigation options:

IMG Menu Cross-Application Components  Document Management System  Control Data  Define document types Transaction Code SPRO

2. On the Change View ”Define Document Types”: Overview screen, choose New entries. 3. On the New Entries: Details of Added Entries screen, enter the following values:

Field name Description User action andvalues Note

Document Type YBO

Document Type

description Office-Documents

Use KPro Select by ticking

Version

Assignment Select by ticking

(7)

Field name Description User action andvalues Note

Internal Number

Range 02

Click on the Number Ranges button in order to define your own number ranges

External number

range 01

Number exit MCDOKZNR Click on the Default button to generate this entry

Vers. No. Incr. 2 Choose "1" if you want versions to start with "00" instead of "01" Hierarchy indicator -Document Status + Document Description + Authorization

Group - Depending on your requirements choose ”.” instead of ”-” here. Lab./Office - Depending on your requirements choose ”.” instead of ”-” here.

Change Number . Allows optional entry of change number

CAD Indicator

-Superior

Document

-WS Application 2

-CM Relevance

-4. Save your settings and choose Back (F3) to return to the Change View ”Define Document Types”: Overview screen.

5. On the Change View ”Define Document Types”: Overview screen, select the document type YBO. Go into the Define document status folder.

6. On the Change View "Define document status": Overview screen, choose New Entries. 7. Add the new entries as follows:

Field name Description User action and values Note

Document Status FR Press Enter

Object Check Select by ticking

Complete for ECM Select by ticking

Release Flag Select by ticking

Check-In Required Select by ticking

(8)

Field name Description User action and values Note

Status type S Locked Status

8. Choose Next Entry (F8) and add the new entries as follows:

Field name Description User action and values Note

Document Status IA Press Enter

Object Check Select by ticking

Check in Select by ticking

Status type I Initial Status

9. Save your settings and return to the "Define document status": Overview screen (you may need to choose Back (F3) twice).

10. Choose Select All (F7) in order to select both newly created statuses, and then choose Details (Ctrl-Shift-F2) in order to change the statuses.

11. For Document Status FR enter IA into field Prev. 1, and then choose Next Entry (F8) .

12. For Document Status IA, enter FR into field Prev. 1.

This will allow you to switch back from status FR (released) to status IA (in work). You may omit this step if you prefer to not allow changes to released documents. In that case users will have to create a new version whenever they need to make changes to a document that has already been released.

13. Save your settings and return to the Change View ”Define Document Types”: Overview screen (you may need to choose Back (F3) twice). You have created the status network for the document type.

14. On the Change View ”Define Document Types”: Overview screen, select the document type YBO. Go into the Define object links folder.

15. Choose "New Entries" and add the new entries as follows:

Field name Description User action and values Note

Document Type YBO

Object MARA Press Enter

When New Version 1

Create Document 2

Document Version 1

(9)

Field name Description User action and values Note

Document Type YBO

Object EQUI Press Enter

When New Version 1

Create Document 2

Document Version 1

17. Choose Next Entry (F8) and add the new entries as follows:

Field name Description User action and values Note

Document Type YBO

Object EKPO Press Enter

When New Version 1

Create Document 2

Document Version 1

18. Choose Next Entry (F8) and add the new entries as follows:

Field name Description User action and values Note

Document Type YBO

Object PRPS Press Enter

When New Version 1

Create Document 2

Document Version 1

19. Choose Next Entry (F8) and add the new entries as follows:

Field name Description User action and values Note

Document Type YBO

Object VBAP Press Enter

When New Version 1

Create Document 2

Document Version 1

20. Save your settings and return to the Change View ”Define Document Types”: Overview screen (you may need to choose Back (F3) twice). You have set up four possible object links for document type YBO.

21. On the Change View ”Define Document Types”: Overview screen, select the document type FOL. Go into the Define document status folder.

22. On the Change View "Define document status": Overview screen, choose New Entries. 23. Add the new entries as follows:

(10)

Field name Description User action and values Note

Document Status FR Press Enter

Object Check Select by ticking

Complete for ECM Select by ticking

Release Flag Select by ticking

Check-In Required Select by ticking

Check in Select by ticking

Status type I Initial Status

24. Save your settings and leave the transaction (you will need to choose Back (F3) several times). You have created object links to Material Master, Equipment Master, Purchase Order Item and WBS element.

Result

The document type used (YBO = Office Documents) has been defined, a basic status network and some object links were set up. For document type FOL (folder) a status has been defined.

(11)

3.1.2

Define Data Carrier

Use

The purpose of this activity is to define the settings for data carrier type PC.

Procedure

1. Access the next activity using the following navigation options:

IMG Menu IMG Cross-Application Components Document Management  General Data  Define Data Carrier

Transaction Code SPRO

1. Confirm the information message: Caution: The table is cross-client with Enter.

2. On the Change View ”Define data carrier type ”archive””: Overview screen, double-click the folder Define data carrier type ”server, front end” and choose New Entries.

3. Make the following entries:

Field

Name Description User Action and Values Note

Type Data carrier

type PC Description PC with MS Windows Operating System

Path If left empty, temporary files will be placed

into the standard Windows-folder for temporary files (Local Settings\Temp) or the path entered in WinGUI – Options – Local Data is used. Alternatively you may enter any path here, For Example, c:\temp or a

network drive.

Online  Set

indicator

4. Select your entry and choose Define servers and files or folders. Choose New entries to create a new entry with the following values:

Field Name Description User Action and Values Note

Data Carr. PC

Type Data carrier type Default

Description Personal Computer

5. Select the entry Identify frontend computers in the dialog structure. Choose Default entry to create a new entry with the following values:

(12)

DataCar. Default

Type Data carrier type PC

Netw. Address DEFAULT

Description Default for local PC

6. Double-click on the entry Define mount points / logical drive in the dialog structure. Choose New entries to create a new entry with the following values:

Field Name Description User Action and Values Note

Data Carr. PC

Data carr. type PC

Prefix for access path C:\SAP BP

7. Save your entries.

Result

(13)

3.1.3

Defining Workstation Application

Use

The purpose of this activity is to define the settings for workstation applications

Procedure

1. Access the activity using the following navigation options:

IMG Menu IMG Cross-Application Components Document

Management  General Data  Define Workstation Application

Transaction Code SPRO

2. On the Change View ”Define Workstation Application”: Overview screen, choose New Entries.

3. Make the following entries:

Field Name Description User Action and

Values Note

WS application Key field DOC

Description Document

Archive

identificatio *

File suffix for

appl. File format for a temporary file doc

File format File format for selection via the file manager

*.doc,*.*

MIME type application/msword

Appl. Icon @J7@

Start

authorization Application can be started immediately Indicator set

4. Save your entries and go back to the Change View ”Define workstation application”: Overview screen.

5. On the Change View ”Define workstation application”: Overview screen, select the workstation application DOC and choose Define workstation application in network. 6. Choose New Entries (F5) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application DOC Is already filled

Data carr. Type PC

Application type 1

Path with prog. Name

(14)

7. Choose Next Entry (F8) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application DOC Is already filled

Data carr. Type PC

Application type 2

Path with prog. Name

%SAP-OFFICE-INTEGRATION.OUTPLACE%

8. Choose Next Entry (F8) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application DOC Is already filled

Data carr. Type PC

Application type 3

Path with prog.

Name %SAP-OFFICE-INTEGRATION.OUTPLACE%

9. Save your entries and go back to the Change View ”Define workstation application”: Overview screen.

10. On the Change View ”Define workstation application”: Overview screen, select the workstation application XLS and choose Define workstation application in network. 11. Choose New Entries (F5) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application XLS Is already filled

Data carr. Type PC

Application type 1

Path with prog. Name

%SAP-OFFICE-INTEGRATION.OUTPLACE%

12. Choose Next Entry (F8) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application XLS Is already filled

Data carr. Type PC

Application type 2

Path with prog.

(15)

13. Choose Next Entry (F8) and make the following entries:

Field Name Description User Action and Values Note

Workstation

Application XLS Is already filled

Data carr. Type PC

Application type 3

Path with prog. Name

%SAP-OFFICE-INTEGRATION.OUTPLACE%

14. Save your entries and go back to the Change View ”Define workstation application”: Overview screen.

15. On the Change View ”Define workstation application”: Overview screen, select the entries for BVO, BVV, LIM, OHD, SIM, WRD and WWI and choose Delete (Shift+F2).

16. In the Specify objects to be deleted dialog box, choose all entries.

If the deletion reports an error similar to: You cannot use data carrier type 01, then you must enter the Define workstation application in network step for this workstation application first, and then delete the problematic subentries there. Next, repeat the previous step.

17. Save your changes.

Result

(16)

3.2 Download and Installation of Easy Document

Management

3.2.1

Download of Easy Document Management (Manual

Step)

Use

The purpose of this activity is to download the front-end installation for Easy Document Management.

Prerequisites

You will need internet access and a user (For Example, S-user) to log on to the SAP service market place.

Procedure

Please follow the following steps to download the Easy Document Management Interface (version 6.0).

Go to SAP service market place (http://www.service.sap.com).Click on Software Download available under the SAP Support Portal Group.

On the left hand menu, click on Download and navigate to Support Packages and Patches -> Entry by Application Group.

On the right hand frame, navigate to Supplementary Components for Cross Industry Solutions -> Life-Cycle Data Management -> SAP EASY DOCUMENT MANAGEMENT -> SAP EASY

DOCUMENT MGMT 6.00.

There you will find the link to download the installation files under EASY DOCUMENT MGMT 6.00 -> Win32. You may choose the newest version of SAP Easy Document Management 6.00. The installation was tested with SP08 (”EasyDMS60USP08_0-20001190.ZIP”).

(17)

3.2.2

Installation of Easy Document Management (Manual

Step)

Use

The purpose of this activity is to install the Easy Document Management on the local PC.

Prerequisites

Administrator rights in MS Windows are advisable but not necessary.

A prior installation of SAP Logon (WinGUI) is advisable. The list of available systems in EasyDM is taken from the SAP-Logon-installation. If no SAP Logon is installed, the system needs to be added manually to the list of systems in EasyDM.

System requirements are with regard to the local PC on which SAP Easy Document Management is installed:

Requirement Type Requirement

Hardware requirementsFree disk space: 20 MB in the standard program folder, for example C:\Program Files RAM: 128MB

Screen resolution: at least 1024x768 pixels Software requirements Microsoft Windows 2000 with SP 3 or higher

or

Microsoft Windows XP with SP1 or higher and

Microsoft Internet Explorer 5.0 or higher

Microsoft Office is supported as of version 2000, but this is not a prerequisite for installation

Procedure

1. Unzip the zip file in any folder and then run the setup.exe by double-clicking on it. This installs the EasyDM Interface on your system. (Administrator privileges for the Windows Operating System are not necessary for a single user installation.)

For more information please see the file SAP_Easy_Doc_Mgmt_Installation.pdf. This file is located in the folder data of the unzipped files, or, after installation, in C:\Program Files\SAP AG\EasyDmsInterface.

2. Click OK to finish the installation.

3. Start SAP Easy Document Management using one of the following options: Windows Desktop Double-click the new icon

SAP Easy Doc Mgmt on your desktop

Windows Explorer Click on the folder SAP Easy Doc Mgmt located in your desktop-folder.

(18)

4. Log on to the SAP system in which you want to work. 5. You will need the following information:

 System name  Client

 User  Password  Language

You must enter the language, For Example, EN for English.

6. Upon first start, the following message will be displayed: ”No public root folder found. Do you want to create one?” (If this message does not appear, continue with step 10.)

7. Choose Yes.

8. On the next screen, change the following entry:

Field name Description User action and values Note

Document

Type Choose Folder (FOL) from the dropdown-list

Leave the rest unchanged

9. Choose OK.

10. The message ”No private root folder found. Do you want to create one?” will be displayed. (If this message does not appear, continue with step 12.)

11. Repeat the instructions from step 7, 8 and above.

12. A Windows Explorer window will show the following three entries:  Private Root Folder

 Public Root Folder  Search Result

Result

(19)

3.3 Trouble Shooting

3.3.1

Referred SAP Notes

Please refer to the following SAP Notes:

SAP Note 929084: Easy DMS 6.0 SP02 Release Note SAP Note 903827: FAQ for Easy DMS 6.0

SAP Note 885058: Easy Doc. Mgmt.: Unicode versions are required

(Error message is: "I::001 Only available with the RFC library from 4.0C onwards.")

References

Related documents

Therefore fault management tools for home networks must be easy to use and easy to understand: rather than just presenting networking information, tools must be able to analyse the

Operator Workstation Application Workstation Master 10.4.128.1 Backup 10.8.128.2 Primary ACN Secondary ACN ProPlus Workstation Primary Remote Network Remote Workstation

Nipper Studio is typically installed and run from a workstation and most customers choose to manually retrieve their device configuration files, but there is support for network

From the SG menu, choose Configure &gt; Options &gt; Registration &gt; Local Workstation (or “next” if using the Wizard). In the Workstation Registration screen: the Software

If a claim is submitted as a Fair PharmaCare claim and the patient is covered under Plan C (or vice-versa), PharmaCare will return the claim form to you for resubmission through the

[r]

With a passionate team we aim to bring your brand to the next level, we want to understand what your company values are, what your brand story is and what the next steps should be

2.1 Lower extremity arterial evaluation (segmental pressures and/or Doppler velocity waveform analysis) is normal at rest but the patient has history of claudication, i.e., leg