Utilities_Building_Blocks_China_Document Management _692_BB_ConfigGuide.doc

EHP3 for SAP ERP 6.0

December 2009

English

Document Management for Utilities (692)

SAP AGDietmar-Hopp-Allee 1669190 Walldorf

Building Block Configuration Guide

SAP Best Practices Organization Change (687): Configuration Guide

Germany

SAP Best Practices Document Management for Utilities (692): Configuration Guide

Copyright

© Copyright 2009 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 PowerPoint are 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 MultiWin are 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, SAP Business ByDesign, 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 Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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.

© SAP AG of 9


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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 text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 9


Contents

Document Management for Utilities: Configuration Guide........................................................5

1 Purpose............................................................................................................................. 5

2 Preparation........................................................................................................................ 5

2.1 Prerequisites............................................................................................................5

2.1.1 Building Blocks....................................................................................................5

3 Configuration.....................................................................................................................5

3.1 Defining Document Type/Document Status.............................................................5

3.2 Defining data carrier................................................................................................7

3.3 Defining Workstation Application.............................................................................7

3.4 Defining Content Repositories.................................................................................7

© SAP AG of 9


Document Management for Utilities: Configuration Guide

1 PurposeThis configuration guide provides 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 eCATTs and BC Sets, use the Building Block Installation Assistant.

2 Preparation

2.1 Prerequisites2.1.1 Building BlocksBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_ZH.xls; the placeholder [xx] depends on the SAP Best Practices version you use, e.g. UTL refers to the SAP Best Practices Utilities Package: Prerequisites_Matrix_UTL_EN_ZH.xls). This document can be found on the SAP Best Practices documentation DVD in the folder ..\BBLibrary\General\

3 Configuration

3.1 Defining Document Type/Document Status

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

Transaction code SPRO

IMG menu Cross-Application Component Document Management Control Data Define Document Types

2. On the Change View Define document types: Overview screen , check the following entries exist or not:

Field name Document type Description(EN)

Entry 1 YU1 Cfolder Document

Entry 2 YU2 Work clean Document

3. If the entries does not exist, choose New Entries to make the entries according to following table:

Field name

Doc. type

Description(EN)

Version assign.

Archiv. Auth.

Chang. Docs

Int. number range

Ext. number range

Vers. No. Incr.

Number Exit

File Size

© SAP AG of 9


1st Entry

YU1

Cfolder Document

selected selected

selected

02 01 1 MCDOKZNR

3000000

2nd Entry

YU2

Work clean Document

selected selected

selected

02 01 2 MCDOKZNR

9999999

4. Choose Save.

5. On the Change View Define document types: Overview screen, select document type YU1 by highlighting the row, double click Define language-dependent descriptions , a screen appears on the right , make the following entry:

Field name Description User action and values Comment

Language ZH

Doc. type YU1

Doc. Type desc

Cfolder 示范文档6. Double-click Define document status in the Dialog Structure window, choose New Entries

to maintain entries according to the following table:

Field name Doc. type Doc. Status Status text Abbrev.

Entry 2 YU1 Y2

Entry 1 YU1 YC Export Cfolder YC

Need to choose New Status to create a new document type.

7. Repeat step 5 to 6 for the document type YU2, make entries according to the following tables:

Define language-dependent descriptions


Language ZH

Doc. type YU2

Doc. Type desc

工作清场文档 Define document status

Field name Doc. type Doc. Status Status text Abbrev.

Entry 1 YU2 AA Work request WR

Entry 2 YU2 FR Released RE

8. Choose Define Object Links , make entries according to the followinig tables:


Document Type

YU2

Object WCAHE

Screen no. 500

Additional Functions

X

© SAP AG of 9


9. Choose Save.

10. Choose Exit.

3.2 Defining data carrier



IMG menu Cross-Application Component Document Management General Data Define Data Carrier

2. Choose Enter to confirm the Information dialog box with Caution: The table is cross-client

3. On the Change View Define data carrier type “archive: Overview screen , double-click Define data carrier type “archive” in the browse window Dialog Structure , choose New Entries , make the following entry:


Type Y1

Description Local PC

Online Selected

4. Choose Save.

5. Choose Exit.

3.3 Defining Workstation Application



IMG menu Cross-Application Component Document Management General data Define Workstation Application

2. On the Change View Define workstation application: Overview screen , check the following entry exist or not :

Application Description Suffix ArchID StartAuth NotRename File format

GIF GIF Anzeige jpg A2 selected selected *,jpg,*.gif

3. If the entry does not exist, choose New Entries to maintain it,

4. If the entry exist and the data does not match the above table, just modify the record according to the table

5. Choose Save.

6. Choose Exit return to SAP Easy Access.

3.4 Defining Content Repositories

Use

© SAP AG of 9


If you want to store document physically on a HTTP server, you must create a content repository which link to a physical HTTP address and storage menu path.


Transaction code OAC0

IMG menu SAP Netweaver Application Server Basis Services ArchiveLink Basic Customizing Define Content Repositories

2. On the Display Content Repositories: Overview screen , choose Display/Change to switch to change mode

3. Choose Create , go to Change Content Repositories: Detail screen, make the following entries:


Content Rep. Content repositories

A2

Description Optional Archive

Storage type 04 HTTP content server The value is defaulted by system

Version no. 0045

HTTP server hs2086.wdf.sap.corp The value described here is only for example, in each installation, you need to contact your system administrator to set up archive link and get the HTTP server IP address and port number

Port number 1080 Same as above, the real port number comes from your system administrator

HTTP Script Archive

4. Choose Save

5. Choose Exit.

© SAP AG of 9

Utilities_Building_Blocks_China_Document Management _692_BB_ConfigGuide.doc

Documents

Transcript of Utilities_Building_Blocks_China_Document Management _692_BB_ConfigGuide.doc