cg_cfo310_04_11_18_en

Business Scenario Configuration GuideBusiness Scenario Configuration GuideBusiness Scenario Configuration GuideBusiness Scenario Configuration Guide

Collaboration Collaboration Collaboration Collaboration Folders (cFolders) Folders (cFolders) Folders (cFolders) Folders (cFolders) 3.103.103.103.10

Document Version 1.1 - November 18, 2004

© Copyright 2004 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/instguides

SAP AGSAP AGSAP AGSAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.comwww.sap.comwww.sap.comwww.sap.com

Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply.

For the HTTPClientStack library, the following conditions apply:

HTTPClientStack - a library to enable an easy programmatic access to the

HTTP protocol stack

Copyright © 2001 Ronald Tschalär

This library is free software; you can redistribute it and/or modify it under the

terms of the GNU Lesser General Public License as published by the Free

Software Foundation; either version 2 of the License, or (at your option) any

later version.

This library is distributed by in the hope that it will be useful, but WITHOUT

ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See

the GNU Lesser General Public License for more details.

SAP’s warranty and liability is subject to your end user license with SAP.

These warranties and liabilities are only on SAP’s behalf and not on behalf of

any other contributors. On behalf of all Contributors all liability for damages,

including direct, indirect, special, incidental and consequential damages, such

as lost profits is expressly excluded.

You should have received a copy of the GNU Lesser General Public License

along with this library; if not, write to the Free Software Foundation, Inc., 59

Temple Place, Suite 330, Boston, MA 02111-1307 USA

Ronald Tschalär

[email protected]

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a "copyright disclaimer" for the library, if necessary.

Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a

library for tweaking knobs) written by James Random Hacker.

<signature of Ty Coon>, 1 April 1990

Ty Coon, President of Vice

For the Jakarta Apache tool, the following conditions apply:

This product includes software developed by the Apache Software Foundation

(http://www.apache.org/).

The Apache Software License, Version 1.1

Copyright © 2000 The Apache Software Foundation. All rights reserved.

Redistribution and use in source and binary forms, with or without

modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this

list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,

this list of conditions and the following disclaimer in the documentation

and/or other materials provided with the distribution.

3. The end-user documentation included with the redistribution, if any, must

include the following acknowledgment:

"This product includes software developed by the Apache Software

Foundation (http://www.apache.org/)."

Alternately, this acknowledgment may appear in the software itself, if and

wherever such third-party acknowledgments normally appear.

4. The names "Apache" and "Apache Software Foundation", "Jakarta-Oro"

must not be used to endorse or promote products derived from this

software without prior written permission. For written permission, please

contact [email protected].

5. Products derived from this software may not be called "Apache" or

"Jakarta-Oro", nor may "Apache" or "Jakarta-Oro" appear in their name,

without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR

A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE

POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on

behalf of the Apache Software Foundation. For more information on the

Apache Software Foundation, please see http://www.apache.org/.

Portions of this software are based upon software originally written by Daniel

F. Savarese. We appreciate his contributions.

SAP and/or its distributors may offer, and charge a fee for, warranty, support,

indemnity or liability obligations to one or more recipients of the software.

However, SAP and/or its distributors may do so only on its/their own behalf,

and not on behalf of the Apache Software Foundation or its contributors.

For the JDom tool, the following conditions apply:

This product includes software developed by the JDOM Project

(http://www.jdom.org/)."

Copyright © 2000 Brett McLaughlin & Jason Hunter.

All rights reserved.




list of conditions, and the following disclaimer.


this list of conditions, and the disclaimer that follows these conditions in

the documentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products

derived from this software without prior written permission. For written

permission, please contact [email protected].

4. Products derived from this software may not be called "JDOM", nor may

"JDOM" appear in their name, without prior written permission from the

JDOM Project Management ([email protected]).

In addition, we request (but do not require) that you include in the end-user

documentation provided with the redistribution and/or in the software itself an

acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project

(http://www.jdom.org/)."

Alternatively, the acknowledgement may be graphical using the logos available

at http://www.jdom.org/images/logos.
















behalf of the JDOM Project and was originally created by Brett McLaughlin

([email protected]) and Jason Hunter ([email protected]). For more information

on the JDOM Project, please see http://www.jdom.org/.

For the Jython tool, the following conditions apply:

HISTORY OF THE SOFTWARE

JPython was created in late 1997 by Jim Hugunin. Jim was also the primary

developer while he was at CNRI. In February 1999 Barry Warsaw took over as

primary developer and released JPython version 1.1.

In October 2000 Barry helped move the software to SourceForge where it was

renamed to Jython. Jython 2.0 is developed by a group of volunteers.

The standard library is covered by the BeOpen / CNRI license. See the

Lib/LICENSE file for details.

The oro regular expresion matcher is covered by the apache license. See the

org/apache/LICENSE file for details.

JYTHON CHANGES SOFTWARE LICENSE

Copyright © 2000, Jython Developers

All rights reserved.



- Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright

notice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.

- Neither the name of the Jython Developers nor the names of its

contributors may be used to endorse or promote products derived from

this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND

CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE

OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.

JPYTHON SOFTWARE LICENSE.

IMPORTANT: PLEASE READ THE FOLLOWING AGREEMENT

CAREFULLY.

BY CLICKING ON THE "ACCEPT" BUTTON WHERE INDICATED, OR

BY INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE,

YOU ARE DEEMED TO HAVE AGREED TO THE TERMS AND

CONDITIONS OF THIS AGREEMENT.

JPython version 1.1.x

1. This LICENSE AGREEMENT is between the Corporation for National

Research Initiatives, having an office at 1895 Preston White Drive,

Reston, VA 20191 ("CNRI"), and the Individual or Organization

("Licensee") accessing and using JPython version 1.1.x in source or

binary form and its associated documentation as provided herein

("Software").

2. Subject to the terms and conditions of this License Agreement, CNRI

hereby grants Licensee a non-exclusive, non-transferable, royalty-free,

world-wide license to reproduce, analyze, test, perform and/or display

publicly, prepare derivative works, distribute, and otherwise use the

Software alone or in any derivative version, provided, however, that

CNRI's License Agreement and CNRI's notice of copyright, i.e.,

"Copyright ©1996-1999 Corporation for National Research Initiatives;

All Rights Reserved" are both retained in the Software, alone or in any

derivative version prepared by Licensee.

3. Alternatively, in lieu of CNRI's License Agreement, Licensee may

substitute the following text (omitting the quotes), provided, however,

that such text is displayed prominently in the Software alone or in any

derivative version prepared by Licensee: "JPython (Version 1.1.x) is

made available subject to the terms and conditions in CNRI's License

Agreement. This Agreement may be located on the Internet using the

following unique, persistent identifier (known as a handle): 1895.22/1006.

The License may also be obtained from a proxy server on the Web using

the following URL: http://hdl.handle.net/1895.22/1006."

In the event Licensee prepares a derivative work that is based on or

incorporates the Software or any part thereof, and wants to make the

derivative work available to the public as provided herein, then Licensee

hereby agrees to indicate in any such work, in a prominently visible way,

the nature of the modifications made to CNRI's Software.

4. Licensee may not use CNRI trademarks or trade name, including JPython

or CNRI, in a trademark sense to endorse or promote products or services

of Licensee, or any third party. Licensee may use the mark JPython in

connection with Licensee's derivative versions that are based on or

incorporate the Software, but only in the form "JPython-based

___________________," or equivalent.

5. CNRI is making the Software available to Licensee on an "AS IS" basis.

CNRI MAKES NO REPRESENTATIONS OR WARRANTIES,

EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT

LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY

REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR

FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE

OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY

RIGHTS.

6. CNRI SHALL NOT BE LIABLE TO LICENSEE OR OTHER USERS

OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL OR

CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING,

MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY

DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY

THEREOF. SOME STATES DO NOT ALLOW THE LIMITATION OR

EXCLUSION OF LIABILITY SO THE ABOVE DISCLAIMER MAY

NOT APPLY TO LICENSEE.

7. This License Agreement may be terminated by CNRI (i) immediately

upon written notice from CNRI of any material breach by the Licensee, if

the nature of the breach is such that it cannot be promptly remedied; or

(ii) sixty (60) days following notice from CNRI to Licensee of a material

remediable breach, if Licensee has not remedied such breach within that

sixty-day period.

8. This License Agreement shall be governed by and interpreted in all

respects by the law of the State of Virginia, excluding conflict of law

provisions. Nothing in this Agreement shall be deemed to create any

relationship of agency, partnership, or joint venture between CNRI and

Licensee.

9. By clicking on the "ACCEPT" button where indicated, or by installing,

copying or otherwise using the Software, Licensee agrees to be bound by

the terms and conditions of this License Agreement.

For the RegEX Apache tool, the following conditions apply:


(http://www.apache.org/)."


Copyright © 1999 The Apache Software Foundation. All rights

reserved.









include the following acknowlegement:



Alternately, this acknowlegement may appear in the software itself, if and

wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Jakarta-Regexp", and "Apache

Software Foundation" must not be used to endorse or promote products

derived from this software without prior written permission. For written


5. Products derived from this software may not be called "Apache" nor may

"Apache" appear in their names without prior written permission of the

Apache Group.













OUT

OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE









For SAX, the following conditions apply:

SAX 2.0

I hereby abandon any property rights to SAX 2.0 (the Simple API for XML),

and release all of the SAX 2.0 source code, compiled code, and documentation

contained in this distribution into the Public Domain. SAX comes with NO

WARRANTY or guarantee of fitness for any purpose.

David Megginson, [email protected]

2000-05-05

For the Struts Apache tool, the following conditions apply:


(http://www.apache.org/).


Copyright © 1999-2001 The Apache Software Foundation. All rights reserved.









include the following acknowlegement:



Alternately, this acknowlegement may appear in the software itself, if and

wherever such third-party acknowlegements normally appear.

4. The names "The Jakarta Project", "Struts", and "Apache Software

Foundation" must not be used to endorse or promote products derived

from this software without prior written permission. For written


5. Products derived from this software may not be called "Apache" nor may

"Apache" appear in their names without prior written permission of the

Apache Group.






















Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

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

<Exampletext>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Collaboration Folders (cFolders): Configuration Guide

10 July 26, 2004


July 26, 2004 11

Contents Collaboration Folders (cFolders): Configuration Guide............. 13

Version Overview ................................................................................ 15 1 Documentation Landscape for SAP Solutions and Business Scenarios ............................................................................................. 16 2 Upgrading cFolders 3.00 to 3.10 ..................................................... 18 3 SAP Notes ......................................................................................... 19 4 Overview of the BAdIs Available in cFolders ................................ 20 5 General Settings............................................................................... 21

5.1 Initial Information .................................................................................22 5.2 Setting Up Users for cFolders .............................................................23 5.3 Setting Up Administrators for cFolders..............................................26 5.4 Setting Up Additional Roles for Controlling Authorizations.............29 5.5 Network Configuration and Security ..................................................31

5.5.1 Security: Integration with mySAP SRM.......................................................................32 5.6 Configuring the Call Up of the Online Help (SAP Library) ................33 5.7 Defining Settings for the Search .........................................................35

6 System Connections........................................................................ 36 6.1 System Connection Settings in the cFolders WAS 6.40 ...................37

6.1.1 Setting Up the HTTP Server (Protocol and Port) ........................................................38 6.1.2 Creating the cFolders URL..........................................................................................40 6.1.3 Activating Services......................................................................................................42 6.1.4 Creating the Settings URL for WebDAV Access.........................................................43 6.1.5 Enabling E-Mails for cFolders .....................................................................................45

6.1.5.1 Setting Up the SMTP Service................................................................................46 6.1.5.2 Defining the Default Domain..................................................................................47 6.1.5.3 Configuring the SMTP Node..................................................................................48 6.1.5.4 Scheduling the Send Job.......................................................................................49 6.1.5.5 Sending E-Mails: Troubleshooting Guide..............................................................50

6.1.6 cFolders Back-End Integration....................................................................................52 6.2 System Connection Settings in the cFolders Application ................55

6.2.1 Network Settings .........................................................................................................56 7 Business Customizing..................................................................... 57

7.1 User Administration in cFolders .........................................................58 7.1.1 Processing Users in cFolders .....................................................................................59 7.1.2 System User................................................................................................................61

7.2 Central User Administration: Integration with SAP UME..................62 7.3 Distributed Content Server: Overview................................................66

7.3.1 Customizing for Content Servers ................................................................................70 7.3.1.1 Content Server Customizing in the cFolders WAS................................................71

7.3.1.1.1 Creating a Content Server Entry......................................................................73 7.3.1.1.2 Creating a Storage Category for a Repository.................................................74 7.3.1.1.3 Creating a Location..........................................................................................75


12 July 26, 2004

7.3.1.1.4 Linking Locations to Storage Categories .........................................................76 7.3.1.1.5 Naming the Server ...........................................................................................77 7.3.1.1.6 Defining the HTTP View for a Front-End Content Server................................78 7.3.1.1.7 Analyzing the Content Server Administration ..................................................79

7.3.1.2 Content Server Customizing in the cFolders Application ......................................80 7.3.2 Changing the Content Server Configuration ...............................................................81

7.4 Installing the FTP (File Transfer Protocol) Box..................................83 7.5 Configuring Integration with the Microsoft Windows File Explorer .85 7.6 Configuring the WebEx Meeting Service............................................86

7.6.1 WebEx Meeting Center: General Information .............................................................88 7.7 Archiving ...............................................................................................90 7.8 Processing Notifications......................................................................91 7.9 Integration with mySAP SRM ..............................................................93 7.10 Changing the Appearance of cFolders .............................................95

7.10.1 Creating Style Sheets ...............................................................................................96 7.10.2 Creating Logos..........................................................................................................97 7.10.3 Applying Style Sheets and Logos .............................................................................98

7.11 Changing cFolders Standard Settings Using WebDAV...................99 7.11.1 Adding New Languages and Vocabularies to cFolders ..........................................101 7.11.2 Changing User and System Settings ......................................................................103 7.11.3 Editing Attributes for Materials and Structures........................................................104

7.11.3.1 Information About the XSD for Materials and Structures ..................................105 7.11.3.2 XSD Description for Materials and Structures...................................................108

7.11.4 Creating Generic Object Types and Document Categories....................................110 7.11.4.1 Structural Elements of the Generic Object Type or Doc. Category...................112

7.11.4.1.1 Detailed Information About the XSD Description.........................................114 7.11.4.1.2 XSD for Generic Object Type and Document Category ..............................119

7.11.4.2 Example XML Files............................................................................................128 7.11.4.2.1 Example XML File for Document Structure (Gen. Object Type)..................129 7.11.4.2.2 Example XML File for CAD Document (Document Category).....................132 7.11.4.2.3 Example XML File for 8D Report (Generic Object Type) ............................133

7.11.5 Making WebDAV Settings for cFolders Integration with mySAP SRM...................154 7.11.5.1 Detailed Information About the XSD Description ..............................................155 7.11.5.2 XSD for the Integration with mySAP SRM ........................................................158 7.11.5.3 Example XML File for the Integration with mySAP SRM ..................................162

7.12 Installing the ECL Viewer.................................................................165 7.13 Importing External Class Systems for Data Sheets ......................166

Version Overview

July 26, 2004 13

Collaboration Folders (cFolders): Configuration Guide Use

Business Scenario This business scenario configuration guide applies to the cFolders business scenario with the corresponding releases of its mySAP.com application components.

Business Scenario and mySAP.com Application Components

Business Scenario mySAP.com application component with minimum release

Design Collaboration with cFolders

cProject Suite 3.10

For more information, refer to the Master Guide for mySAP PLM using SAP cProject Suite 3.10

Contents The business scenario configuration guide contains all steps required to implement cFolders. The guide specifies the sequence of the configuration activities, and their dependencies.

It includes information about the following topics:

• System connections

• Business customizing

For further information about cFolders, see service.sap.com/ibc → ….for mySAP PLM in the SAP Service Marketplace.

Target Group • Technical consultants

• Application consultants

• Project team members during the implementation of a mySAP.com solution

• SAP customer IT department

The System Connections section is aimed at technical consultants in particular, while the Business Customizing section is aimed at application consultants. The General Settings section is of equal interest to both groups of consultants. The importance of sections to the other target groups depends on their responsibilities.

Integration

mySAP.com Solution and Business Scenarios Documentation Landscape The system landscape has already been created, using the Master Guide and other documentation. What other documentation exists, and where you can find their latest versions, is under mySAP.com Solutions and Business Scenarios Documentation Landscape [Seite 15].

Business Scenario Configuration Guide Feedback

Version Overview

14 July 26, 2004

Your feedback can help us to continually improve the business scenario configuration guide. If you find errors in the configuration guide, please send a message in the SAP Service Marketplace under service.sap.com/message for component Product Lifecycle Management PLM.

Version Overview

July 26, 2004 15

Version Overview

Date of New Version Change Section 18.11.2004 New chapter added Defining Settings for the

Search [Page 35]

1 Documentation Landscape for SAP Solutions and Business Scenarios

16 July 26, 2004

1 Documentation Landscape for SAP Solutions and Business Scenarios Purpose This documentation gives you an overview of the major sources of information available to you on SAP solutions and business scenarios. Always use the current documents in your implementation.

Current documents

Document Quick Link on the SAP Service Marketplace (service.sap.com)

Master Guide, Installation and Upgrade Guides instguides

ibc

Business-Scenario Configuration Guide ibc

Implementation Guide (IMG) Note: This is in the SAP System, not in SAP Service Marketplace

Business Scenario Description ibc

SAP Library helpportal with all releases of a SAP component

Note: Available in the SAP System under Help → SAP Library

The following information supplements the individual documents:

Current supplementary information

Information Quick Link on the SAP Service Marketplace (service.sap.com)

SAP notes notes to the note search

instguides listed by installation and upgrade guide

Technical infrastructure (for example hardware sizing, platforms, network security)

ti

Features The following documents are available for a SAP solution.

Master Guide, Installation and Upgrade Guides These documents describe how you install or upgrade the system landscape required by a business scenario. The central initial access document for each SAP solution is the Master Guide. It lists the SAP application components and third-party applications required by each business scenario, and refers to their installation and upgrade guides. These are component installation guides, business scenario upgrade guides and component upgrade guides.

Business-Scenario Configuration Guide This document describes the settings you use to configure the SAP application components and third-party applications required for a business scenario. It contains information specific

1 Documentation Landscape for SAP Solutions and Business Scenarios

July 26, 2004 17

to business scenarios for the particular IMG activity. It does not reiterate the IMG documentation but makes reference to particular IMG texts.

Implementation Guide (IMG) This tool adjusts SAP systems to customer requirements. The IMG contains the IMG activities for all SAP components, and general documentation. The structure is component oriented, without reference to a business scenario. The Business-Scenario Configuration Guide establishes the link between the IMG and the various business scenarios.

Business Scenario Description This document describes how a business scenario runs once all components have been installed and configured. All the business processes of a business scenario are represented graphically in the component view, which illustrates the process steps of each SAP component.

SAP Library This contains the entire documentation of SAP components and business scenarios. The Business Scenario description is part of the SAP Library.

2 Upgrading cFolders 3.00 to 3.10

18 July 26, 2004

2 Upgrading cFolders 3.00 to 3.10 The following new configuration steps are available in cFolders 3.10:

1. BAdIs available in cFolders [Seite 20]

2. Call Up of the Online Help (SAP Library) [Seite 33]

3. Integration with Microsoft Windows File Explorer [Seite 85]

The content of the following sections has been changed or enhanced:

Section Type of Change

SAP Notes [Seite 19] Various SAP Notes added.

Setting Up Users for cFolders [Seite 23] Revision of and more information added to the section:

Information regarding users and administrators has been split into two sections.

Authorization object CFX_OBJ and various roles have been added.

Setting Up Administrators for cFolders [Seite 26]

Revision of and more information added to the section:

Information regarding users and administrators has been split into two sections.

Network Configuration and Security [Seite 31]

• Internet Gateway: Types and Set-Ups

• Installation Scenario A: No Content Server

• Installation Scenario B: One Hidden Content Server

• Installation Scenario C: One Public Content Server

• Installation Scenario D

• Additional Environment: FTP Server, Mail Gateway, WebEx Access

• cFolders Plug-In Security

• Integration with Back-End Systems

Revision of the section.

Content of subsections transferred to the SAP cProject Suite Security Guide on the SAP Service Marketplace. (See: service.sap.com/securityguide → SAP cProject Suite Security Guides → SAP cProject Suite 3.10 Security Guide)

Setting Up the HTTP Server (Protocol and Port) [Seite 38]

A second parameter has been added to step 7.

Creating the cFolders URL [Seite 40] URL in step 10 corrected.

cFolders Back-End Integration [Seite 52] Path for information on SAP Service Marketplace corrected.

Central User Administration: Integration with SAP UME [Seite 62]

Terminology corrections and SAP Notes added.

3 SAP Notes

July 26, 2004 19

3 SAP Notes Use Before you start to configure this business scenario, consult the following SAP notes. This summary only contains central SAP notes, to give you an initial overview.

Central SAP notes for the cFolders business scenario:

SAP note Title of SAP note

538324 Business Package cFolders – Installation

216419 Multi-Level Caching and Content Server Proxies

546617 EWB_CS_CL_S_BOM_CHANGE_COMPLETE (required for the cFolders back-end integration)

674653 Deactivation of Badi implementations cfx_ext_user*

550742 FAQ: General questions about Single Sign-On

138498 Single Sign-On Solutions

23611 Collective Note: Security in SAP Products

128447 Trusted/Trusting Systems

584394 ECL Viewer 4.0 Settings for cFolders

584372 ECL Viewer 4.0 Install (general information)

592085 Installing the HTTP Connect service

592115 Service HTTP Connect (for SAP only)

To get a comprehensive and up-to-date overview of the SAP notes about a business scenario and its mySAP.com application components, use the note search function under service.sap.com/notes in the SAP Service Marketplace.

4 Overview of the BAdIs Available in cFolders

20 July 26, 2004

4 Overview of the BAdIs Available in cFolders The following Business Add-Ins (BAdIs) are available for enhancement in Collaboration Folders (cFolders).

cFolders-BAdIs

Definition Name Title (Definition Short Text)

Associated Methods Description of Methods

CFX_GENERIC_OBJECT BAdI: Checks for Generic Objects and Object Categories

SUPPLEMENT_BEFORE_SAVE

CHECK_BEFORE_SAVE

Complete data before saving and before the check

Check data before saving

CFX_BUTTONS BAdI: User-Defined Pushbuttons

AFTER_BUTTON_PRESSED

BEFORE_BUTTON_DISPLAY

Is called when pushbutton is chosen

Change display properties of pushbutton

CFX_STATUS_TRANS BAdI: User-Defined Actions for Status Transitions

BEFORE_STATUS_CHANGE

AFTER_STATUS_CHANGE

Before status change

After status change

CFX_STATUS_TRANS_UI BAdI: User-Defined Actions for Status Transitions (UI)

BEFORE_STATUS_CHANGE_UI

AFTER_STATUS_CHANGE_UI

Before status change (UI)

After status change (UI)

CFX_SRM_SC BAdI: SRM Shopping Cart in cFolders

BEFORE_CREATE Directly before creating the shopping cart

CFX_THUMBNAIL BAdI: Thumbnails

SET_ON_CONTENT_CHANGE

BEFORE_THUMBNAIL_SAVE

Change the thumbnail when changing the object version

Save data directly before saving the thumbnail

For more information about the BAdIs listed above, see the documentation for the individual BAdIs.

5 General Settings

July 26, 2004 21

5 General Settings Purpose This section contains general information that you need to start the business scenario configuration.

Familiarize yourself with the documentation landscape for SAP solutions and business scenarios. For a description of the types of documentation provided by SAP and where to find the current versions, see Documentation Landscape for SAP Solutions and Business Scenarios [Seite 15].

Prerequisites • The system landscape is installed, using the SAP solution master guides, and the SAP

component and business scenario installation and upgrade guides.

• You are familiar with the relevant SAP notes about installation, configuration, and upgrade.

For more information, see SAP notes.

Procedure Perform the steps in these guidelines in the sequence in which they appear.

5 General Settings

22 July 26, 2004

5.1 Initial Information The online help documentation for cFolders can be called up in your Web browser from all pages of the cFolders application by choosing Help.

System Requirements: Client

cFolders ActiveX Component for Excel Data Sheet Comparison Data sheet comparison is a function in the cFolders application and is carried out by a cFolders ActiveX component. The component is installed the first time the comparison is started on the client machine.

Users must have:

• Access authorization to install components on the client

• Windows NT 4.0 or higher

• Microsoft Excel 2000 SR1

Feedback If you want to submit feedback about cFolders or any related issues, visit us at:

http://www.sap.com/cfolders

There you will find a feedback form that you can fill out and submit online.

5 General Settings

July 26, 2004 23

5.2 Setting Up Users for cFolders Use To ensure that users have the correct authorizations and access to the appropriate functions, every cFolders user must be assigned a cFolders role. You can create your own roles that you tailor to the conditions of your process.

Prerequisites

Roles Supplied by SAP with cFolders for Users • User

� Role name: SAP_CFX_USER

� Provides authorization to run cFolders in the Internet browser. It is sufficient to just assign this role to a user for working with the cFolders application.

If you use R3 back-end integration, an additional authorization object is required for the “trusted connection”. For more information, see SAP Note 128447.

Note that the following roles do not contain the authorization to use cFolders; therefore, the user will also need the role SAP_CFX_USER or a similar role:

• Collaboration creator

� Role name: SAP_CFX_COL_CREATOR

� Has authorization to create collaborations in the Collaborative Scenario.

• Collaboration deletor

� Role name: SAP_CFX_COL_DELETOR

� Has authorization to delete collaborations in the Collaborative Scenario.


� Role name: SAP_CFX_COMP_CREATOR

� Has authorization to create collaborations in the Competitive Scenario.


� Role name: SAP_CFX_COMP_DELETOR

� Has authorization to delete collaborations in the Competitive Scenario.


� Role name: SAP_CFX_STD_CREATOR

� Has authorization to create collaborations in the Standards.


� Role name: SAP_CFX_STD_DELETOR

� Has authorization to delete collaborations in Standards.

• User group creator

� Role name: SAP_CFX_USRGRP_CREATOR

5 General Settings

24 July 26, 2004

� Has authorization to create user groups.

• User group deletor

� Role name: SAP_CFX_USRGRP_DELETOR

� Has authorization to delete user groups.

• Status profile creator

� Role name: SAP_CFX_STATUS_PRF_CREATOR

� Has authorization to create status profiles.

• Status profile deletor

� Role name: SAP_CFX_STATUS_PRF_DELETOR

� Has authorization to delete status profiles.

Authorization Objects for Users Authorization objects that control authorizations and access to cFolders:

• CFX_USER: Authorization for access to cFolders. This authorization is needed by every user. Assign the value User to the user’s role.

• CFX_OBJ: Controls the authorization to create or delete cFolders objects. Possible values are:

� stat_prof: Authorization for creating or deleting status profiles

� usrgrp: Authorization for creating or deleting user groups

� col: Authorization for creating or deleting collaborations in the Collaborative Scenario

� comp: Authorization for creating or deleting collaborations in the Competitive Scenario

� stdpart: Authorization for creating or deleting collaborations in Standards

Other authorization objects not specific to cFolders

For all users of cFolders

• B_USERSTAT: Authorization object for status management. Make sure that your users have this authorization; otherwise, they cannot use status management in cFolders.

• S_RFC: Authorization for executing function modules via RFC. This is only necessary for external users who access cFolders (for example, via back-end integration, from a portal, or a 3rd party application). In such cases, you need authorization for the function groups CFX_ACO - CFX_ACO* ; CFX_API - CFX_API* ; CFX_MA_UI; CFX_UI_API; RFC1; SYST; SYSU; and SDIFRUNTIME. If you are using the SAP User Management Engine (UME), the replication user needs authorization for the function group SMUM.

• S_DATASET: Authorization for accessing files. Each cFolders user must be given read authorization in this object.

• S_USER_AGR: Authorization for retrieving roles. Each cFolders user must have authorization to display the role SAP_CFX_EMAIL_SYSTEM_USER. User administrators must have authorization to assign and change the roles that you want to use in cFolders.

• S_USER_GRP: cFolders users need authorization to display and change, user administrators need additional authorization to create, lock, delete, and assign.

For user administrators

5 General Settings

July 26, 2004 25

• S_USER_PRO: You need authorization to display and assign.

For network administrators

• S_ADMI_FCD: You need all values.

• S_BTCH_ADM: You need the value “Y”.

• S_BTCH_JOB: You need authorization to release a job and the value ‘ ‘ (that is: <apostrophe, space, apostrophe>).

• S_BTCH_NAM: You can assign user names to each user.

Procedure 1. From the cFolders Web Application Server 6.40 Menu, choose Tools → Administration

→ User Maintenance → Role Administration → Roles (transaction PFCG).

The Role Maintenance screen appears.

2. In the Role field, enter SAP_CFX_USER and choose Change Role.

3. Choose the Authorizations tab page.

4. Check the status in the Information about authorization profile group:

� If the status is Profile generated, you do not have to do anything else. If the other standard roles also have this status, move on to the next step in the Configuration Guide.

� If the status is Current version not generated, proceed as follows.

5. On the Authorizations tab page, choose Change Authorization Data.

The Change Role: Authorizations screen appears.

6. Expand the entire structure and check the authorizations (minimum authorizations for cFolders).

7. Choose Authorizations → Generate.

A dialog box appears.

8. Confirm the default values.

9. Choose Back to return to the screen for changing roles.

10. Check whether the status has changed to Profile generated.

11. If necessary, do the same for all other roles.

Result An authorization profile is defined for each cFolders role.

If the roles are not activated, that is, if you have not carried out the above procedure, an installation error occurs when you run cFolders.

Before cProject Suite 3.00, Support Package 5, this role setup was different, however, if you want to move to SP5, no reconfiguration is required.

5 General Settings

26 July 26, 2004

5.3 Setting Up Administrators for cFolders Use As a rule, a number of different people take on the various administrative tasks in cFolders.

At least one person in your organization has to administer the cFolders users, the network settings and several application settings.

Prerequisites

Roles Supplied by SAP with cFolders • User Administrator:

� Role name: SAP_CFX_USER_ADMINISTRATOR

� In addition to the user authorizations, the user administrator has authorization to create, change, and delete users. This includes assigning all SAP_CFX* roles.

• Network Administrator:

� Role name: SAP_CFX_NETWORK_ADMINISTRATOR

� In addition to the user authorizations, the network administrator has authorization to change all network settings and release batch jobs (for status and e-mail notifications).

� You can carry out the following activities with this role:

� Configure WebExTM meeting settings

� Activate the e-mail job

� Configure the cFolders server for HTTP Internet access (proxy server)

� Test the HTTP Internet access of the cFolders server

� Send test e-mails

� Specify the absolute URLs of the application and the documents (WebDAV)

• cFolders Administrator:

� Role name: SAP_CFX_CFOLDERS_ADMINISTRATOR

� In addition to the user authorizations, the cFolders administrator has authorization to maintain the features and the appearance of cFolders.

� You can carry out the following activities with this role:

� Switch on the diagnosis mode

� Reset system settings and languages

� Change the system-wide appearance of the cFolders application (logos and style sheet)

• Superuser:

� Role name: SAP_CFX_SUPER_USER_ADMIN

� In addition to the user authorizations, the superuser has authorization to manage all collaborations, status profiles, and user groups. However, this role does not allow you to create new cFolders objects. To create new objects in

5 General Settings

July 26, 2004 27

cFolders, you need other roles (for example, SAP_CFX_COL_CREATOR) or authorization to create documents in a specified folder.

Only assign this role to a small number of trustworthy users. With this role, you avoid the cFolders authorization concept that controls access to cFolders objects. This role can be used, if you do not need or want to split the roles up for different persons who are responsible for different administration tasks. The only difference is, that it does not contain the superuser role.

• Administrator (for users, network, and cFolders):

� Role name: SAP_CFX_ADMINISTRATOR

� Provides authorization to administer the cFolders application, including the authorizations of SAP_CFX_USER

• E-Mail System User:

� Role name: SAP_CFX_EMAIL_SYSTEM_USER

� Has authorization to start the jobs for summary e-mails and reminder notifications for status management and is assigned automatically in the background, when you create a system user. Do not assign this role to any user. It is only intended for the system user. For more information, see System User [Seite 61]. Do NOT copy this role into the customer namespace, please activate the original SAP Role regardless of the warning message you receive.

If you want to use the standard SAP roles, you must transport these roles into all SAP clients in which you want to use the cFolders application. Note that the SAP_CFX_EMAIL_SYSTEM_USER role must be active in the system in each case. To create the authorization profiles, each role has to be activated by the system administrator, as described below.

Authorization Objects Authorization objects that control authorizations and access to cFolders:

• CFX_APPL: Controls the individual administrative areas. Possible values are:

� Network_Definition: Setting up the network, for example, absolute URL or FTP server settings

� Content_Definition: Setting up cFolders content, for example, adding generic objects or selecting the scenarios that are used

� Layout_Definition: Setting up the appearance of cFolders, for example, choice of style sheet

• ACO_SUPER: Authorization for reading, writing, or managing specified object types. This authorization object is also used in Collaboration Projects (cProjects). Possible values for cFolders are:

� area: Authorization for all existing collaborations

� stat_prof: Authorization for all status profiles

� usrgrp: Authorization for all user groups

Other authorization objects not specific to cFolders:

For all users of cFolders

5 General Settings

28 July 26, 2004

• B_USERSTAT: Authorization object for status management. Make sure that your users have this authorization; otherwise, they cannot use status management in cFolders.

• S_RFC: Authorization for executing function modules via RFC. This is only necessary for external users who access cFolders (for example, via back-end integration, from a portal, or a 3rd party application). In such cases, you need authorization for the function groups CFX_ACO - CFX_ACO* ; CFX_API - CFX_API* ; CFX_MA_UI; CFX_UI_API; RFC1; SYST; SYSU; and SDIFRUNTIME. If you are using the SAP User Management Engine (UME), the replication user needs authorization for the function group SMUM.

• S_DATASET: Authorization for accessing files. Each cFolders user must be given read authorization in this object.

• S_USER_AGR: Authorization for retrieving roles. Each cFolders user must have authorization to display the role SAP_CFX_EMAIL_SYSTEM_USER. User administrators must have authorization to assign and change the roles that you want to use in cFolders.

• S_USER_GRP: cFolders users need authorization to display and change, user administrators need additional authorization to create, lock, delete, and assign.

For user administrators

• S_USER_PRO: You need authorization to display and assign.

For network administrators

• S_ADMI_FCD: You need all values.

• S_BTCH_ADM: You need the value “Y”.

• S_BTCH_JOB: You need authorization to release a job and the value ‘ ‘ (that is: <apostrophe, space, apostrophe>).

• S_BTCH_NAM: You can assign user names to each user.

Procedure To assign the SAP_CFX_USER_ADMINISTRATOR role or roles you have created yourself with the appropriate authorizations to at least one user, carry out the following steps:

1. From the cFolders WAS 6.40 Menu, choose Tools → Administration → User Maintenance → Users (transaction SU01).

The User Maintenance: Initial Screen appears.

2. Select the user who is to be the cFolders administrator and choose Change.

The Maintain User screen appears.

3. Select the Roles tab page and enter the SAP_CFX_USER_ADMINISTRATOR role or the name of the role you created yourself in the Role column.

The generated profile of the SAP_CFX_USER_ADMINISTRATOR role or the role you created is assigned to the user automatically.

4. Select the Address tab page and enter the address data of the administrator. Enter at least the user’s first and last names, and e-mail address.

5. Save your entries.

6. Use the cFolders interface to create more cFolders users and administrators.

Result At least one user can now administer cFolders users within the cFolders application.

5 General Settings

July 26, 2004 29

5.4 Setting Up Additional Roles for Controlling Authorizations Use In the cFolders application, users have the option of assigning authorizations to individual users, user groups, or roles.

While working on a collaboration, for example, you can assign the authorization to access a particular document to the Project Manager role. All users who have this role assigned to them then have authorization to access this document, as well as any other authorizations that this role may have.

Before roles can be used in this way in cFolders, however, you must activate them in cFolders WAS 6.40. You then have to use your own cFolders roles. You must:

• Create a role or select one from the available roles in the Authorization Management function

• Enter the role in authorization object S_USER_AGR in the authorizations for your roles. This ensures that all users can display the role in the cFolders application and assign it as required, even if they are not assigned to it themselves.

• Assign users to the role. These users then automatically have the authorizations that were assigned to the role in the cFolders application.

Prerequisites If you activate an existing role, you need to know the exact name of the role, for example, PROJECT_LEADER.

Procedure To activate an existing role, create a new role, and assign users to a role, choose Tools → Administration → User Maintenance → Role Administration → Roles (transaction PFCG) in the cFolders WAS 6.40 menu.

The Role Maintenance screen appears.

Activating an Existing Role ...

1. On the Role Maintenance screen, enter <your role> in the Role field and choose Change Role.

The Change Roles screen appears.

2. On the Authorizations tab page, choose Change Authorization Data.

The Change Role: Authorizations screen appears.

3. Select Basis – Administration and expand the structure.

4. Under Authorizations – Role Check, which is authorization object S_USER_AGR, choose next to Role Name.

A table appears that contains the three standard cFolders roles.

5. In this table, enter the existing role(s) that you want to use to control authorizations in cFolders, for example, the PROJECT_LEADER role.


5 General Settings

30 July 26, 2004

You have now entered the role in the authorization object S_USER_AGR in < your role > and thereby enabled all users in cFolders to display this role and assign it as required.

Now you have to assign users to the role using the cFolders interface.

Creating a New Role ... ... ...

1. On the Role Maintenance screen, enter a role name in the Role field and choose Create Role.

2. Enter the original language, for example, EN for English, and assign the role to a development package.

The Change Roles screen appears.

3. Enter a description and then save the role.

4. Exit the transaction.

Now assign this role to the authorization object S_USER_AGR in role <your role> as described above in Activating an Existing Role.

You must also assign users to this role, as described in Assigning Users to a Role.

Result The roles that you have activated can now be used in the cFolders application to control authorizations. All users assigned to the role, for example, PROJECT_LEADER, have the authorizations that were assigned to this role in the cFolders application.

5 General Settings

July 26, 2004 31

5.5 Network Configuration and Security cFolders defines an Internet-wide collaboration environment. In this area, security is extremely important. cFolders installations vary in complexity, but in general they consist of different servers according to the following list:

• Base server: a standard SAP Web Application Server (SAP Web AS)

• Optional content and cache servers for file storage: in actual installations at least one content server is installed.

• Optional: one FTP server.

• Additional technical components, for example, a mail gateway.

Users typically interact with cFolders using an Internet browser (Microsoft Internet Explorer 5.0 or higher). All operations, which consist of both file transfer and dialog processing, are communicated between the front end and the server(s) using the HTTP protocol. Files and data must be considered equally important.

Security in Typical cFolders Installation Scenarios There are four main types of cFolders installation scenarios (scenarios A – D). They get increasingly more complex, starting with the smallest “A” installation, up to an installation with several public content servers on more than one Internet gateway between a company’s intranet and the Internet. Scenario D can be divided into two major scenarios, depending on the number of gateways between the intranet and the extranet zone.

Although the complexity and the number of servers increases, the security for one particular server does not change. For example, the security conditions for the cFolders server (SAP Web AS) are always the same regardless of how many other servers surround it. The same applies to installations with public content servers. This allows the cFolders installation to be upgraded with minimal impact on the existing components in terms of security.

For more information about each scenario and the relation of the SAP Web AS to supplementary components in cFolders, for example, FTP server, mail gateway, and WebEx integration, see the SAP cProject Suite Security Guide on the SAP Service Marketplace under service.sap.com/securityguide → SAP cProject Suite Security Guides → SAP cProject Suite 3.10 Security Guide.

5 General Settings

32 July 26, 2004

5.5.1 Security: Integration with mySAP SRM For information on security questions concerning the integration of cFolders with mySAP Supplier Relationship Management (SRM), see Integration with mySAP SRM [Seite 93].

5 General Settings

July 26, 2004 33

5.6 Configuring the Call Up of the Online Help (SAP Library) Use cProject Suite (cProjects and cFolders) supports the following online help (SAP Library) variants:

• PlainHtmlHttp

The help files are installed on a Web server.

• PlainHtmlFile

The help files are installed in a directory on a file server, which facilitates general access.

• DynamicHelp

The files are accessed via the Knowledge Warehouse Server.

For more information about connecting the online help, see the readme.txt file on the cProject Suite 3.10 CD.

Procedure

Installation of the Online Help for the Variants PlainHtmlHttp and PlainHtmlFile ...

1. First, create a directory in the file system of your Web server or file server (for example, <Drive>:\SAPHelp\PlainHTML\helpdata). This directory will be the root directory of the help installation.

2. In this root directory, create an additional directory for every language version that you want to install and name these directories with the relevant language abbreviation, for example, DE for German and EN for English.

If you have already installed the online help for the WAS 6.40 in the PlainHtmlHttp or PlainHtmlFile variants, you do not have to create new directories on the Web server or file server. You can just use the existing directory structure of this previous installation. You can ignore any warning messages (that say that you could be overwriting existing files) that arise when you are later copying help files into the directory structure.

3. You can find the files you require on the cProject Suite 3.10 CD in the corresponding language directory in the plainhtml directory.

4. Copy the files to the corresponding language directory in the root directory of the help installation.

5. Create a virtual directory on your Web server or file server, or release a directory and link this directory with the root directory for the help installation in the file system. For more information, see the Help for your Web server or file server.

The root directory containing the help installation can now be viewed under the name that you assigned to the virtual directory or the released directory (for example, saphelp).

Installation of the Online Help for the DynamicHelp Variant

5 General Settings

34 July 26, 2004

The files to help you install the online help on a Knowledge Warehouse Server are located on the cProject Suite 3.10 help CD in the corresponding language directory in the htmlhelp directory. You can find information about the installation in the SAP Knowledge Warehouse Installation Guide in the section Importing SAP Knowledge Warehouse Contents. You can find the document on the SAP Service Marketplace under service.sap.com/instguides → Installation and Upgrade Guides → SAP Components → SAP Knowledge Warehouse → Release 6.0 → SAP Knowledge Warehouse 6.0 Installation Guide.

Configuration in the WAS 6.40 ...

Enter the following information in Customizing under General Settings → Setting Variants for Help (SAP Library) on the tab page of the documentation variant you want to install:

Column Entry

Variant You can choose a description, but it must be a unique description, for example, cProjects31_Docu_DE (for the German help) or cProjects31_Docu_EN (for the English help).

Platform NONE

Area IWBHELP (Documentation)

Server • For PlainHtmlHttp: Name of the Web server, if necessary include the domain and port of the server (this is only necessary if the port is not the default Http port 80).

• For PlainHtmlFile: Not relevant

• For DynamicHelp: Is copied from the configuration of the Knowledge Warehouse Server.

Path • For PlainHtmlHttp: Name of the virtual directory that is linked to the root directory of the help installation on the Web server (for example, saphelp).

• For PlainHtmlFile: Name of the released directory on the file server including the server name under which the root directory of the documentation installation on the Web server is visible (for example, <server>\saphelp).

• For DynamicHelp: Not relevant

Language Help language

Default Determines whether or not the language is the standard language.

For more information, see the documentation for this activity.

5 General Settings

July 26, 2004 35

5.7 Defining Settings for the Search Use cProject Suite provides a full-text search using the SAP search engine TREX. You use this search engine to find documents. To be able to use the search engine, you have to make the settings outlined below.

If you do not use TREX, you can continue to use the regular search function.

Prerequisites You have installed the TREX search engine.

Procedure ...

1. Make the following settings in Customizing for SAP NetWeaver or for the SAP Web Application Server under Basis Services → Knowledge Provider → Document Management Service:

a. In the Define Indexing Readiness activity, activate indexing for the CFF document area (Release Index indicator). A classification is not necessary (Classify indicator).

b. In the Schedule Asynchronous Indexing and De-indexing activity, schedule the indexing or de-indexing as a background process.

2. You can use the SKPR07 transaction to manage and monitor the indexed documents (document class CFF_VERS). You can also trigger the indexing process manually. The transaction enables you to:

� Determine marked documents � Determine problem cases in indexing � Index specific documents at a later date

� Index or de-index individual documents � Index specific languages � Index by class � Index by document area

� Determine relevant index categories For more information about this transaction, see Checking for Problems in IMS Monitoring [External].

5 General Settings

36 July 26, 2004

6 System Connections

Purpose This section contains information about connecting the systems in a SAP system landscape.

This involves, for example:

• Defining logical systems and assigning clients in the Online Transaction Processing System (OLTP)

• Determining the systems, servers, clients, distribution models and so on, in the system in which the SAP application component is installed

• Completing the configuration settings and performing other activities required for the interactions in a SAP system landscape


5 General Settings

July 26, 2004 37

6.1 System Connection Settings in the cFolders WAS 6.40 The settings described in this part of the Configuration Guide are carried out in the cFolders Web Application Server 6.40.

5 General Settings

38 July 26, 2004

6.1.1 Setting Up the HTTP Server (Protocol and Port) Use To allow the cFolders Web Application Server to communicate with your browser and display content, you must first set up a HTTP service.

For detailed information about the SAP Web Application Server, refer to the documentation in the SAP Library.

Procedure ...

1. From the cFolders WAS 6.40 Menu choose Tools → Administration → Monitor → System Monitoring → Internet Communication Manager (transaction SMICM).

The ICM Monitor screen appears.

2. Choose Goto → Services.

The ICM Monitor – Service Display screen appears.

reen appears.

3. Check the ICM monitor to see if a HTTP or HTTPS service is available and active.

� If this is the case, you do not need to carry out the rest of this procedure. Move onto the next step in the cFolders Configuration Guide.

� If this is not the case, continue with step 4 below.

A system administrator with experience of changing the instance profile should carry out the next steps.

4. Call up transaction RZ10.

The Edit Profiles screen appears.

5. Enter your profile in the Profile field.

6. If you do not have a profile, enter the file name of the profile and choose Profile → Import to import the profile from your hard drive.

� The file name of the profile usually consists of: <SID>_<instancename>_<machine name>

� The file is usually located in the directory: ...usr\sap\<SID>\sys\profile

7. Add the following new parameters.

� Parameter name: icm/server_port_<#>

'#' is a variable for a sequential number, for example, icm/server_port_3

Parameter value, for example:

� PROT=HTTP

� PORT=1080

� TIMEOUT=150

� Parameter name: icm/host_name_full

Parameter value: $(SAPLOCALHOST).<your company.com>

5 General Settings

July 26, 2004 39

8. Save your data.

9. To activate the HTTP service you have to restart your system.

Result A HTTP or HTTPS service that enables the cFolders WAS to communicate with your Web browser is now active.

After installing or reinstalling cFolders, you may have problems with time-out errors. If this occurs, log on again and the first page will recover. In addition, a new installation may cause all pages within cFolders to take longer to load. However, all subsequent sessions will have better access times.

5 General Settings

40 July 26, 2004

6.1.2 Creating the cFolders URL Use To access cFolders, you need a URL for your Internet browser.

In this procedure, you create an external alias for each client in the SAP System in which you want to run cFolders.

Procedure ...

1. From the cFolders WAS 6.40 Menu, choose Tools → Administration → Administration → Network → HTTP Service Hierarchy Maintenance (transaction SICF).

The Maintain Service screen appears.

2. In the Virt. Hosts / Services column, select the default_host text and then choose Goto → External aliases.

3. The Maintain external aliases screen appears.

4. Select the default_host text again and to create a new external alias, choose External alias → Create.

The Maintain external aliases dialog box appears.

5. Enter a name and a description for the external alias in the External alias and Description fields.

6. When you enter the external alias, use the following entry format:

"/<Alias Name>"

For example: "/engineering"

This entry is case sensitive, which is important when you enter an address in your browser address line.

7. On the Service data tab page, enter a client number.

8. In the same dialog box, choose the Trg Element tab page.

9. In the Virt. Hosts/Services column choose default_host → sap → bc → bsp → sap and double-click this folder.

The URL /default_host/sap/bc/bsp/sap appears under the “Trg Element:“ entry.

10. Optional: If you want to forbid, that users can logon with their initial password (without changing it), perform the following step:

Choose the Error Pages tab → Choose the Logon Error tab → Under Redirect to URL enter the following URL:

/sap/public/bsp/sap/system/login.htm?sap-url=<%=PATHTRANS%>&bspclient=<%=SYMANDT%>

11. Choose Store to save your entries.

12. Choose Cancel to close the dialog box.

Result Once you have completed the remaining system connection steps in the cFolders WAS, you will be able to call up cFolders using the following URL:

5 General Settings

July 26, 2004 41

<Protocol>://<Server>:<Port>/<External aliascFolders>/cfx_rfc_ui/default.htmFor example: http://cfolders.my.company.com:1080/engineering/cfx_rfc_ui/default.htm

You must repeat the above procedure for each SAP client in which you want to use cFolders.

The SAP Web Application Server only accepts fully-qualified server names. For example <Server> = cfolders.my.company.com You can also use the IP address of the server.

5 General Settings

42 July 26, 2004

6.1.3 Activating Services ...

1. From the cFolders WAS 6.40 Menu, choose Tools → Administration → Administration → Network → HTTP Service Hierarchy Maintenance (transaction SICF).


2. In the Virt. Hosts / Services column, go to default_host → sap → bc → bsp → sap → cfx_rfc_ui

3. Open the context menu by right-clicking on cfx_rfc_ui and choose Activate Service.

4. In the Virt. Hosts / Services column, go to default_host → sap → bc → kw → cfs.

5. Open the context menu by right-clicking on cfx_rfc_ui and choose Activate Service.

5 General Settings

July 26, 2004 43

6.1.4 Creating the Settings URL for WebDAV Access Use To be able to change various cFolders settings, for example, user settings and languages, you must access the corresponding xml files using an alias via the WebDAV client [Seite 99] (Web-based Distributed Authoring and Versioning).

WebDAV is an XML-based enhancement of the HTTP/1.1 protocol for asynchronous document management, which is the standard for accessing documents by using a Web browser application.

First, you must create an external alias for each client, as described below.

You only need to carry out this procedure if you want to execute the following steps in the Business Customizing section of the Configuration Guide:

Changing the Appearance of cFolders [Seite 95]

Changing cFolders Standard Settings Using WebDAV [Seite 99]

Editing Attributes for Materials and Structures [Seite 104]

Creating Generic Object Types and Document Categories [Seite 110]

Integration with mySAP SRM [Seite 93]

Procedure ...

1. From the cFolders WAS 6.40 Menu choose Tools → Administration → Administration → Network HTTP Service Hierarchy Maintenance (transaction SICF).


2. In the Virt.Hosts/Services column, select the default-host text and then choose Goto → External aliases.

The Maintain external aliases screen appears.

3. Select the default-host text in the Virt. Hosts/Services column and to create a new external alias, choose External alias → Create.

The Maintain external aliases dialog box appears.

4. Enter a name and a description for the external alias in the External alias and Description fields.

When you enter the external alias, use the following entry format: "/<Alias Name>". For example, "/cfolders-settings”

5. On the Service data tab page, enter a client number.

6. In the same dialog box, choose the Trg Element tab page.

7. In the Virt. Hosts/Services column, choose: default_host → sap → bc → kw → cfs and double-click this folder.

The URL /default_host/sap/bc/kw/cfs appears under the “Trg Element:“ entry.


9. Choose Enter to close the dialog box.

5 General Settings

44 July 26, 2004

Result You can now access the cFolders settings through a WebDAV client using the following URL:

<Protocol>://<Server>:<Port>/<External alias settings>

5 General Settings

July 26, 2004 45

6.1.5 Enabling E-Mails for cFolders Use The following configuration is required for sending e-mails in the cFolders application. For example, notifications and meeting invitations can be sent by e-mail.

Prerequisites The cFolders URL is set up correctly, as described in Creating the cFolders URL [Seite 40].

Procedure ...

1. Setting Up the SMTP Service [Seite 46]

2. Defining the Default Domain [Seite 47]

3. Configuring the SMTP Node [Seite 48]

4. Scheduling the Send Job [Seite 49]

See also: Sending E-Mails: Troubleshooting Guide [Seite 50]

5 General Settings

46 July 26, 2004

6.1.5.1 Setting Up the SMTP Service ...

1. From the cFolders WAS 6.40 Menu choose Tools → Administration → Monitor → System Monitoring → Internet Communication Manager (transaction SMICM).

The ICM Monitor screen appears.

2. Choose Goto → Services.

The ICM Monitor – Service Display screen appears.

3. Check the ICM monitor to see if a SMTP service is available and active.

� If this is the case, you do not need to carry out the rest of this procedure for the SMTP service. Move onto the next procedure described below (Default Domain).

� If this is not the case, continue with step 4 below.

Only a system administrator with experience in changing the instance profile should carry out the next steps.

4. Call up transaction RZ10.

The Edit Profiles screen appears.

5. Enter your profile in the Profile field.

6. If you do not have a profile, enter the file name of the profile and choose Profile → Import to import the profile from your hard drive.

� The file name of the profile usually consists of: <SID>_<instancename>_<machine name>

� The file is usually located in the directory: ...usr\sap\<SID>\sys\profile

is is a dynamic library which implements the SMTP protocol. <prog> specifies the file name of the SMTP Plug-In. The program is located in the execution directory of the SAP Web Application Server instance. It has the name "smtpplugin" and the usual extension for your operating system (".so",".dll", etc.).

7. Add another new parameter.

Parameter name: icm/server_port_<#>

Parameter value: PROT=SMTP,PORT=<port>

You are recommend to use a port of the form 250xx, where xx stands for the system number.

(If you only use the Web Application Server for sending e-mails and not for receiving them, you can also use port 0.)

8. Save your data.

9. To activate the SMTP service you have to restart your system.

For further details about the SMTP service, see note 455140.

5 General Settings

July 26, 2004 47

6.1.5.2 Defining the Default Domain This is a client-specific setting. SAP recommends that you make this setting in client 000 first and then in all other clients that you want to use. ...

1. From the cFolders WAS 6.40 menu, choose Tools → Business Communication → Communication → SAPconnect (transaction SCOT).

The SAPconnect: Administration screen appears.

2. Choose Settings → Default Domain to enter a valid Internet mail domain, for example, sap.com. This Internet mail domain is used for the following:

� In cFolders, a special system user is used for sending certain e-mails, such as summary e-mails or reminder notifications. For more information, see System User. The system user’s proposed Internet e-mail address is generated from the user name and the default domain. For example, if you set the default domain sap.com, then the system user’s proposed Internet e-mail address is [email protected].

� The default domain is used for different issues in standard SAPConnect functionality and not just for cFolders, for example:

� If you link the local document identification and the default domain, for example [email protected], the message ID of any outbound mail is generated.

� If there is no Internet e-mail address in the sender’s master record in SAP, an automatic From: address is generated by linking the sender’s SAP user name and the default domain, for example, [email protected].

5 General Settings

48 July 26, 2004

6.1.5.3 Configuring the SMTP Node In SAPconnect there are two types of nodes: "old" RFC nodes (used for connecting legacy gateways) and "new" SMTP nodes (representing the SAP Web Application Server's intrinsic SMTP module). There can only be one SMTP node in each client of the cFolders WAS and it must not be deleted. It is automatically generated the first time you call transaction SCOT, so you only need to configure it.

This is a client-specific setting. You are recommended to carry it out in client 000 first and then in all other clients that you want to use.

...

...

1. From the cFolders WAS 6.40 Menu, choose Tools → Business Communication → Communication → SAPconnect (transaction SCOT).


2. Select and double-click the existing SMTP node.

The SAPconnect: General node data dialog box appears.

3. Set the Node in Use flag.

4. Enter the mail host (for example, mail.sap.com) and the mail port (normally 25) of your mail server.

5. If you have a system with multiple code pages, select the code page 4110 Unicode UTF-8 in the Code Page dropdown list.

6. Under Supported address types, choose Set for Internet.

7. Enter an address area (use * if all e-mails are to be sent via the SMTP plug-in).

8. Enter the mail host (for example, mail.sap.com) and the mail port (normally 25) of your mail server.

9. Define the document formats to which you want outgoing SAP-specific objects to be converted. Recommended:

� SAPscript/SmartForms PDF

� ABAP Lists HTM

� Objects/Links HTM

� RAW text TXT

5 General Settings

July 26, 2004 49

6.1.5.4 Scheduling the Send Job Mails sent by an application are queued only first. A service is required in the background that processes this queue and then actually sends out the messages over the Internet. This service is provided by the SAPconnect send job and is an ABAP program that must run periodically. You can schedule this job from within the SAPconnect: Administration screen.

This is a client-specific setting. You are recommended to carry it out in client 000 first and then in all other clients that you want to use.

...

...


The SAPconnect: Administration screen appears

2. Choose View → Jobs and check if a job is already scheduled (it is displayed with a calendar icon). If not, choose Create to schedule a new one.

3. In the Schedule send process dialog box, enter a job name (for example: SAPconnect).

4. In the SAPconnect send process: Variants screen select your variant in the Variant column and choose Schedule job to check the execution date and time, that is the time at which the job is to be started for the first time.

5. Choose Schedule periodically.

6. In the Period Duration dialog box, select a time period (for example 5 or 10 minutes) and then choose Create.

Regular, automatic e-mails that contain a summary of received notifications still cannot be sent. For information on how to activate this function, refer to Notifications [Seite 91].

5 General Settings

50 July 26, 2004

6.1.5.5 Sending E-Mails: Troubleshooting Guide Sending Test E-Mails If you want to test sending e-mails in the cFolders WAS, independently of the cFolders application, proceed as follows: ...

1. From the cFolders WAS 6.40 Menu, choose Office → Workplace (transaction SBWP) to enter the Business Workplace.

2. Choose New Message.

The Create Document and Send screen appears.

3. Enter a Title and the Document contents.

4. In the Recipient column, insert an e-mail address and in the Recip. type column, select Internet address.

5. Choose Send (in the top left-hand corner).

The e-mail is physically sent when the periodical send job is run (see the Send Job section of Enabling E-Mails for cFolders [Seite 45]).

If you do not want to wait until the next time the job is run, you can start the job immediately in transaction SCOT, by choosing View → Jobs and then Start send process.

For information on how to send test e-mails in the cFolders application, see Network Settings [Seite 56].

Problems Scheduling the Send Job If you have problems scheduling the send job as described in Enabling E-Mails for cFolders [Seite 45], because you cannot find a variant, proceed as follows: ...

1. From the cFolders WAS 6.40 Menu, choose Tools → CCMS → Jobs → Definition (transaction SM36) to schedule the job.

2. In the screen Define Background Job specify a job name.

3. Choose Step and then ABAP program. Under ABAP program specify the name RSCONN01 and the variant SAP&CONNECTALL.

4. Save your settings.

5. Choose Start Condition and then Immediate and select Periodic job.

6. Choose Periodic values, then Other period and specify a time period of, for example, 5 to 10 minutes.

7. Save the settings on all screens that are still open.

Overview of Send Requests To get an overview of the send requests, proceed as follows: ...



2. Choose Utilities → Overview of send orders.

The Administration of External Send Operations appears.

5 General Settings

July 26, 2004 51

Here you can see which e-mails have been sent successfully and where there has been a send error. There is also a list of the send requests that are still waiting to be sent by the send job.

Missing or Wrong cFolders URL in Notification E-mails A missing URL in a notification e-mail could be caused by a missing cFolders absolute URL (see Configuring the Absolute URL of the cFolders Application in Network Settings in the cFolders Application [Seite 56]). If this URL is wrong an error might occur in cFolders immediately after logging on.

5 General Settings

52 July 26, 2004

6.1.6 cFolders Back-End Integration Purpose You can use the back-end integration for cFolders to exchange documents, bills of material, and materials between cFolders and an SAP R/3 back-end system.

Prerequisites

System requirements (transactions CFI01 and CFE01 for documents only)

• SAP R/3 Release 4.6B or higher (back-end system)

• SAP R/3 Plug-In 2001.2 with support package 2 or higher

System requirements (transactions CFI02 and CFE02 for documents, materials, and bills of material)

• SAP R/3 Release 4.6C, SP33 or higher (back-end system) and SAP note 546617

• SAP R/3 Plug-In 2002.2 or higher

Only use transactions CFI01 and CFE01 if your system does not fulfill the requirements for transactions CFI02 and CFE02.

For more information on system requirements, see also the Master Guide mySAP PLM using SAP cProject Suite 3.10 on the SAP Service Marketplace under service.sap.com/instguides → Installation & Upgrade Guides → mySAP Business Suite Solutions → mySAP PLM → using cProject Suite 3.10.

Process Flow You must carry out the installation in the back-end system. Ensure that the system requirements are fulfilled and proceed as follows:

1. Create an RFC connection to the cFolders system using transaction SM59. For detailed information on how to create an RFC connection, choose Help → Application help in transaction SM59. Test the connection. If you do not want the user of the back-end integration to have to explicitly log onto the cFolders system, you can set up a "Trusted System" connection. Refer to SAP note 128447 and to Integration with Back-End Systems [Extern].

2. In Customizing for the cFolders back-end integration, make the required settings using transaction CFC01. You can make settings about the following topics:

a. cFolders system data

Here you need, in particular, the name of the RFC connection that you created in the first step.

b. Document-type dependent data

Here you can assign, according to the document type, a particular document status for the export to cFolders. When a document of this type is exported as changeable to cFolders and the status change is allowed, the system will assign this status to the document. The document only has this status in the back-end system, it does not apply in cFolders. (However, if the document is assigned to a status profile in cFolders, it can have a cFolders-specific status.)

5 General Settings

July 26, 2004 53

This function can be used for the following: In principle, a document can be changed in the back-end system after it has been exported to cFolders, including changes to its status, for example. You can prevent this, however, in Customizing for the Document Management System, where you can define and assign a status such as “Exported to cFolders” for the document types to be exported. You can then assign the document status type S (= Locked status) to your status “Exported to cFolders” so that the documents are protected against changes.

If you re-import a document that was edited in the meantime in cFolders, a new version of the document is created in the back-end system.

In this case also, the status that the document had in cFolders does not apply in the back-end system.

To find out more about the meaning of the individual fields, refer to the F1 Help.

Business Add-Ins If the standard implementation of the cFolders back-end integration fulfills your requirements, you do not need to implement the following Business Add-In (BAdI). Otherwise, you can implement the Business Add-In by choosing Tools � ABAP Workbench � Utilities � Business Add-Ins � Implementation (transaction SE19). Name Function

CFOLDERS_BI_MAIN01 Business Add-In “CFOLDERS_BI_MAIN01” contains the interface “IF_EX_CFOLDERS_BI_MAIN01” . By implementing the methods of this interface, additional attributes for materials, bills of material, and bill of material items can be integrated in the backend integration for cFolders. The documentation of the individual parameters can be accessed in the back-end system.

CHANGE_IMPORT_MAT_ATTRIBUTES Processes the material attributes from cFolders before they are imported to the back-end system.

CHANGE_EXPORT_MAT_ATTRIBUTES Processes the table of attributes that is exported from a back-end material into a cFolders material.

CHANGE_IMPORT_BOM_ATTRIBUTES Processes the bill of material attributes from cFolders before they are imported to the back-end system.

CHANGE_EXPORT_BOM_ATTRIBUTES Processes the table of attributes that are exported from a back-end bill of material to a cFolders bill of material.

CHANGE_IMPORT_ITEM_ATTRIBUTES Processes the attributes of a bill of material item before they are imported to the back-end system.

5 General Settings

54 July 26, 2004

CHANGE_EXPORT_ITEM_ATTRIBUTES Processes the table of attributes that are exported from a back-end bill of material item to an item in a cFolders bill of material.

5 General Settings

July 26, 2004 55

6.2 System Connection Settings in the cFolders Application The settings described in this part of the Configuration Guide are carried out in the cFolders application in the Web browser.

5 General Settings

56 July 26, 2004

6.2.1 Network Settings Use You have to make certain network settings in the cFolders application in your Web browser.

Procedure ...

1. Start cFolders by entering the following URL in the address line of your browser:

<Protocol>://<Server>:<Port>/< External aliascFolders>/cfx_rfc_ui/default.htm

The external alias name is case-sensitive.

2. Choose Administration in the cFolders menu and carry out the following settings on the Network tab page.

Configuring the Absolute URL of the cFolders Application The cFolders application needs to know its own absolute URL to generate links to e-mails or to create redirection requests. This URL cannot be determined automatically because of the network configuration where the server is located. If the absolute URL is not specified, the cFolders application issues installation error messages. To determine the valid URL: ...

1. Choose Determine Application URL on the Network tab page.

The default URL displayed here is the current URL in the Internet browser. The absolute URL now appears in the Absolute URL of the Application field. This field must contain a valid URL to the cFolders application in this form:

<Protocol>://<Server>:<Port>/<External aliascFolders>/cfx_rfc_ui

2. If you set up a different server name from a reverse proxy, for example, then change this URL to ensure that all users are able to access the application.

HTTP Server Connection To use the WebEx demo site, you have to allow the cFolders server to connect to the Internet to create users on the demo site. ...

1. Specify the proxy server and the port number that is used by the Web Application Server (not the client - Internet Browser) for the outgoing connection.

2. Choose Test HTTP Connection to check whether or not the server is able to connect to the Internet.

Sending Test E-Mails Choose Send Test E-mail to send a test e-mail to a user who is currently logged on. Within a matter of minutes, the user should receive a test e-mail.

7 Business Customizing

July 26, 2004 57

7 Business Customizing Purpose This section contains information about the customizing settings in each system. Business customizing adjusts the company-neutral delivered functionality to the specific requirements of the company.

This involves, e.g.:

• Organizational Unit Customizing

• Master Data Customizing

• Process Customizing



58 July 26, 2004

7.1 User Administration in cFolders Use You use this local user administration to create, change, copy, and delete users in the cFolders application and change their passwords.

A wizard guides you through the different processes. While you are making the necessary entries, for example, for creating or changing a user, you have the option of navigating backwards and forwards between the individual steps before you save your entries.

Prerequisites • You have authorization for user administration in cFolders (cFolders administrator)

• The Activate Central User Administration indicator has not been set in the Central User Administration group box on the User tab page in the collaboration overview screen under User Administration. (You can, however, use this function as an alternative to user administration in cFolders.)

See Also: Central User Administration: Integration with SAP UME [Seite 62]

Processing Users in cFolders [Seite 59]


July 26, 2004 59

7.1.1 Processing Users in cFolders Procedure To access the first four functions in the table, choose User Administration in the cFolders application to branch to the System Settings screen, select the User tab page and choose the appropriate function from the Functions from Local User Maintenance group box.

To access the last function in the table, choose Settings in the cFolders application to branch to the Settings screen, select the User tab page and choose Reset Password.

Function Follow-On Path What You Should Know

Creating users → Create. Enter the first and last names of the user (these are required entries), select a role, and choose Finish.

Default values are generated for the unique system ID and the e-mail address from the names entered. The password is generated for the new user in the background. An e-mail containing the user’s registration data is sent to the user automatically by e-mail.

Changing users → Change. Enter the name of the user and change the details as required.

Copying users → Copy. Enter the name of the user you want to use as a template and change the details if necessary.

Deleting users → Change. Enter the name of the user you want to delete and choose Delete.

Only system administrators have authorization to delete users and can see these functions in the cFolders application.

If a user is deleted, all their authorizations, favorites, and WebEx Meetings are also deleted.

Resetting passwords → Reset Password Only system administrators have authorization to reset passwords and can see these functions in the cFolders application.

If a password is reset, a new password is created automatically and is sent to the user by e-mail.

Changing passwords → Change Password. Enter the old password, the new password, repeat the latter


60 July 26, 2004

and save.


July 26, 2004 61

7.1.2 System User Definition A system user is a special user for sending different types of e-mail in the system.

Use The system user is used in the following situations:

• Always for summary e-mails

• Always for reminder notifications

• Sometimes for sending all e-mails in cFolders, if the network settings are appropriate

For more information about e-mails and notifications, see Processing Notifications [Seite 91].

When you start to create a system user, default values are proposed for the unique user ID, the user name, and e-mail address. You only have to save these proposed values. You can change the domain part of the e-mail address if you wish.

(The password for the system user is created automatically. However, because no user is actually supposed to log on with the system user, it is never accessible.)

In order to be compatible with cFolders 3.10, up to (and including) cFolders 3.00, Support Package 04, the system user was created for you automatically in the background. This system user can still be used for sending e-mails, but will not be displayed in the user screen of this new system. If summary e-mails or reminder notifications are activated in your system, the old system user already exists and there is no need to create any more users here.


62 July 26, 2004

7.2 Central User Administration: Integration with SAP UME Use You can link cFolders to the SAP User Management Engine (UME, Release 4.00 or higher) in the SAP Enterprise Portal. The UME is a central user administration tool that enables you to centrally manage the data of your users and distribute it in your systems. You can use central user administration instead of user administration in cFolders.

Note that you still need the system user when you use central user administration. For more information, see System User [Seite 61].

Integration The following UME Business Add-In definitions have been implemented in the cFolders system to optimize the synchronization of users for cFolders:

• SMUM_USER_CREATE

• SMUM_USER_DELETE

This took place with the help of the following implementations:

• CFX _EXT_USER_CREATE

• CFX_EXT_USR_DELETE

The implementations supplied are inactive in the system: You have to activate them before you can use them. To do this, start the transaction SE19 (SAP Easy Access → Tools → ABAP Workbench → Utilities → Business Add-Ins → Implementation) and enter the implementations named above. Click Activate. If it is not possible to activate the implementations, follow the instructions in the SAP note 674653.

All implementations have the filter definition BBP_SRM. You have to enter this in the UME configuration to be able to use the cFolders implementations.

Prerequisites • You have configured the UME in such a way that the users can be synchronized

together with the SAP roles the user needs in cFolders. For more information about configuring the UME, see the SAP Library under SAP NetWeaver → mySAP Enterprise Portal → SAP Enterprise Portal → Release EP 6.0 SP2 → SAP Enterprise Portal Documentation → Administration Guide → Portal Platform → System Administration → User Management Configuration.

• The user with which the UME logs on to the cFolders system has authorization for user administration in cFolders (cFolders user administrator).

• The defined user must be a cFolders user and must have, in addition to the RFC authorizations for normal portal users, the authorization to execute the function group SMUM using RFC.

• You have set the Activate Central User Administration indicator in cFolders and saved this setting. You do this in the collaboration overview screen on the User tab page in the Central User Administration group box.


July 26, 2004 63

� Set up an e-mail server so that you can send the data to the users. For more

information, see Enabling E-Mails for cFolders [Seite 45].

� Set up the absolute URL for your cFolders application so that the users receive a link to the cFolders application in your e-mail. For more information, see Creating the cFolders URL [Seite 40].

Features • CFX_EXT_USER_CREATE: The program creates a new user in the cFolders

system. The new user automatically receives an e-mail with his or her cFolders user data.

• CFX_EXT_USR_DELETE: The program deletes the user from the cFolders system. The user’s cFolders-specific settings are also deleted.

• You can also use the UME to change user data. This does not require you to make any cFolders-specific adjustments. Therefore, there is no individual cFolders implementation for the corresponding BAdI.

The system knows that you are using central user administration when you call the implementations. If you have not taken this into account under User Administration in cFolders, the system saves this information.

It is now no longer possible to create and delete users in cFolders. Furthermore, you can only change cFolders-specific user data (for example, the home page and the content server selection).

1. You use the CFX_EXT_USER_CREATE function to replicate a single user in the

cFolders system. The UME only assigns the intended roles to the users after you have done this, which means that at first, the users do not have any authorization to call the cFolders application.

2. Users that are created using the UME do not have a password in the cFolders system. In order for a user to be able to access cFolders, he or she needs a mySAP.com logon ticket for the UME. Set up your cFolders system so that it accepts the UME logon tickets. For more information on SSO (tickets), see SAP notes 550742, 138498, 23611, and 128447.

a. UME Standalone

You use the UME without the SAP Enterprise Portal. In your external alias, guide your logon error Redirect towards the logon servlet of the UME. Enter the absolute URL of the cFolders home page in the redirectURL parameters in the URL.

<Protocol>://<UME_Server>:<UME_Port>/logon/logonServlet?redirectURL=<absolute_cFoldersURL>/<External aliascFolders>/cfx_rfc_ui/default.htm

http://us7608.wdf.sap.corp:50000/logon/logonServlet?redirectURL=http://pwdf1028.wdf.sap.corp:50038/myalias/cfx_rfc_ui/default.htm

b. UME in the SAP Enterprise Portal

The user logs on to the portal. He or she can access cFolders from here. Import the Business Package for Collaboration by cFolders 2.0 to your portal.

64 July 26, 2004

User administrators in cFolders can generate a password for the user or assign one to him or her directly. The user can then log on to cFolders as normal with this password.

Configuration of the UME 4.00 Define the cFolders system as a UME client system.

Mapping SAP Roles Export the roles you want to assign to the cFolders users in the UME from the cFolders system as an XML file. Import this data to the UME. Then link these roles to your portal roles.

When you create a user in the portal and assign a portal role to him or her in this way, the user is automatically assigned the SAP roles that are part of the portal role when the user is replicated in the cFolders system.

UME Properties Examples of UME properties:

Secondary Storages (cFolders client system) ume.replication.adapters.index_1=xmladapter?adapterid=TPL

ume.r3.connection.TPL.poolmaxsize=10

ume.r3.connection.TPL.poolmaxwait=10000

ume.r3.connection.TPL.ashost=pwdf1028.wdf.sap.corp

ume.r3.connection.TPL.sysnr=38

ume.r3.connection.TPL.client=100

ume.r3.connection.TPL.lang=EN

ume.r3.connection.TPL.user=umeuser

ume.r3.connection.TPL.passwd= abcdef

ume.r3.connection.TPL.r3name=TPL

Role Mapping ume.roles.xml_files=UMErole.xml ...

Copy the ume.roles.xml_files to the UME-folder under the path <UME_J2EE/Systemnummer>/ume.

To activate the CFXrole.xml and therefore to make the UME roles available, start the J2EE Engine again.

Turn the role mapping into a comment again:

#ume.roles.xml_files=UMErole.xml

You can now assign these roles to the UME roles.

Content of the sample file CFXrole.xml for the SAP_CFX_USER and SAP_CFX_ADMINISTRATOR roles: <BUSINESSSERVICE NAME="CFX" DESCRIPTION_RESOURCE_BASE_NAME="cFoldersRole">



<ACTION NAME = "cFolders_User" ID = "SAP_CFX_USER" SCOPE="supplier" >

July 26, 2004 65

</ACTION >

<ACTION NAME = "cFolders_Administrator" ID = "SAP_CFX_ADMINISTRATOR" SCOPE="supplier" >

</ACTION >



<ROLE NAME="cFolders_User" SCOPE="supplier">

<ASSIGNEDACTION NAME="cFolders_User" />

</ROLE>

<ROLE NAME="cFolders_Administrator" SCOPE="supplier">

<ASSIGNEDACTION NAME="cFolders_Administrator" />

</ROLE>

</BUSINESSSERVICE>

See Also: User Administration in cFolders

[Seite 58]Processing Users in cFolders [Seite 59]


66 July 26, 2004

7.3 Distributed Content Server: Overview Use SAP provides content servers as a standard technology for storing files. The cFolders application can use content servers for two reasons: ...

• To avoid mass traffic and storage on the cFolders base server: Files are usually very big compared to HTML communication. This applies both to the mass transfer via HTTP for uploading or downloading and to the file storage itself, for which the content server is optimized. The Web Application Server (WAS) is not optimized for this.

• cFolders users might be in different geographic locations: For example, SAP has three main locations in Germany, America, and India. To optimize network traffic and speed, files can be stored on different content servers directly associated with the locations.

cFolders is shipped with a predefined set of content categories (CFFCONTENT and CFFURL, see transaction OACT) and associated storage repositories (CFF and CFFURL, see transaction OAC0). These basic settings should never be changed in any way. With this pair of settings, all internal XML files such as system settings, user settings and language settings are placed inside the cFolders WAS database, which is the correct storage location for these critical files. The cFolders document storage model, as defined in transaction DMWB (modelname = CFF), should also not be changed in any way, in particular, the content category definition for the PHIOs must point to the default category CFFCONTENT. Changing the basic default settings, for example, to another storage technique such as a content server is very dangerous, because a failure of the content server will result automatically in a complete and unrecoverable failure of the complete cFolders application itself, with the high probability of some data loss. In cFolders 1.1, the only way to change the repository is to make a change inside the DMWB, unfortunately accompanied by the dangers already mentioned. If you are upgrading a cFolders 1.1 system to a higher release, do not forget to reset the settings in DMWB, as described above. The following describes how to enable dedicated content server(s) for data files, which are all files that users upload/download/change inside cFolders, as opposed to the internal XML setting files.

Supported Scenarios for Distributed Content Servers The following four scenarios are available in conjunction with content servers (see below for diagrams of these four scenarios):

• Scenario A: File storage takes place in the database only (default configuration as-shipped; runs “out of the box”). This does not involve content servers at all.

• Scenario B: Exactly one content server that is not visible on the Internet. Files are stored on this content server; files are transferred over the cFolders WAS.

Advantage in comparison to scenario A: The WAS database is freed of the file storage workload.

• Scenario C: Exactly one content server that is visible on the Internet.

Advantage in comparison to scenario B: The cFolders WAS is additionally freed of the file transfer workload, as well as the file storage workload.


July 26, 2004 67

• Scenario D: Multiple content servers associated with different geographic locations that are all visible on the Internet. This is a direct extension of scenario C. Each cFolders user has the option of using different content servers.

Advantage in comparison to scenario C: File transfers/storage can be carried out by the nearest content server.

Scenario C and D partly rely on the cFolders plug-in technology for uploads. Without the plug-in, scenarios C and D default to scenario B for uploading. The plug-in is not required for accessing files for downloading (read/view). The content servers are only used for the “file-based” documents; all other files used are stored in the database.

The plug-in for cFolders can be activated in the cFolders application by choosing Administration → General (tab page) → Activate Plug-In (indicator)

Diagrams of the Supported Scenarios

Scenario A: File storage only in the database

Files are transported between theuser‘s browser and the cFoldersWeb Application Server. Filestorage is done in the WASdatabase.

DB

Files +Metadata

cFolders


68 July 26, 2004

Scenario B: Exactly one content server that is not visible on the Internet.

Files are transported between theuser‘s browser and the cFoldersWeb Application Server. Filestorage is done in the defaultcontent server.

Content Server: accessed throughStorage Category named CFFMAINor ZCFFMAIN

Files +Metadata

cFolders

Scenario C: Exactly one content server that is visible on the Internet

Files are transported between theuser‘s browser and the defaultcontent server. Only metadata isexchanged between browser andWAS

Content Server: Storage Categorynamed CFFMAIN or ZCFFMAIN,directly accessed by choosing thelocation associated with this server.

Metadata Files

cFolders


July 26, 2004 69

Scenario D: Multiple content servers associated with different geographic locations

Metadata

Files Files

Metadata

Location1

Content Server 1 foundthrough storagecategory associatedwith location1

Content Server 2 foundthrough storagecategory associatedwith location2

cFolders

Location2


70 July 26, 2004

7.3.1 Customizing for Content Servers Purpose The installation of a content server on a particular server is described in the SAP Content Server Installation Guide.

If content servers are to be set up for cFolders, there are certain special requirements:

• There must be exactly one “main” content server that should be located “near” the cFolders WAS server. (“Near” means that a good network connection between the WAS and the content server must exist). The associated storage category must be named “CFFMAIN” or “ZCFFMAIN” (the Z denotes the customer namespace).

• For direct access to a particular content server, it must be associated with a location. This means a content server is identified by its location parameter.

Process Flow The customizing for content servers must be carried out partly in the cFolders WAS 6.40 in the Implementation Guide (IMG) (transaction SPRO), and partly in the cFolders application in the Web Browser. The recommended sequence of installation steps is as follows: ... ...

1. Decide which scenario is to be used (this is an organizational decision). Also decide how many and which locations are to be used depending on the scenario.

2. Hardware installation of content servers at each location.

3. cFolders WAS 6.40 Customizing.

4. Settings in the cFolders application.

For information on how to carry out the required Customizing steps, refer to the next two steps in the Configuration Guide.

Content Server Customizing in the cFolders WAS [Seite 71]

Content Server Customizing in the cFolders Application [Seite 80]

See also: Network Configuration and Security [Seite 31]


July 26, 2004 71

7.3.1.1 Content Server Customizing in the cFolders WAS Use To customize your distributed content servers for cFolders, you must first carry out certain steps in the cFolders WAS 6.40 in Customizing for the SAP Web Application Server, depending on your chosen scenario.

Prerequisite The hardware and basic content server software has been installed as described in the SAP Content Server Installation Guide.

Procedure The steps involved are: ...

1. Creating a Content Server Entry [Seite 73]

2. Creating a Storage Category for a Repository [Seite 74]

3. Creating a Location [Seite 75]

4. Linking Locations to Storage Categories [Seite 76]

5. Naming the Server [Seite 77]

6. Defining the HTTP View for a Front-End Content Server [Seite 78]

For the four available scenarios, you must customize the following:

Scenario A File storage only in the database (default configuration as-shipped; runs “out of the box”):

• No customizing required.

Scenario B Exactly one content server that is not visible on the Internet: ...

1. Install one content server.

2. Create a storage category that is called CFFMAIN or ZCFFMAIN.

No locations required.

Scenario C Exactly one content server that is visible on the Internet: ... ...

1. Define one content repository.

2. Create a storage category that is called CFFMAIN or ZCFFMAIN.

3. Define one location.

4. Link the location to a storage category.

In this configuration the location is usually not the synonym for a geographic location, so you may name the location “MAIN_FILES”, “DIRECTFILE”, or similar.


72 July 26, 2004

Scenario D Multiple content servers associated with different geographic locations; all visible on the Internet: ... ...

1. Define one content repository for each location that you want to support.

2. Create storage categories for each content server.

3. Define the locations.

4. Then link the locations to storage categories. To set a default storage category, call it CFFMAIN or ZCFFMAIN.

5. Define the URLs that are valid at each location for one server (steps 5 and 6)

See also: Analyzing the Content Server Administration [Seite 79]


July 26, 2004 73

7.3.1.1.1 Creating a Content Server Entry ...

1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Define Content Repositories

2. Choose Content Repository → Display/Change.

3. Choose Content Repository → Create.

4. Enter a name and a description for the content server.

5. Enter CFF in the Document Area field and HTTP in the Storage type field.

All other settings are described in the standard SAP Content Server Installation Guide.

Note that the server address (HTTP address of the server) is needed later (see Naming the Server [Seite 77]).


74 July 26, 2004

7.3.1.1.2 Creating a Storage Category for a Repository 1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP

Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Define Content Categories.

2. Choose New entries.

3. Enter a name, a description, and in the Document Area field enter CFF.

4. In the Content Rep. field enter the name of the newly-created content repository (see Creating a Content Server Entry [Seite 73]).

If this storage category is meant to be the standard category for files, than the name must be “CFFMAIN” or “ZCFFMAIN”.

For the extended scenario D you create more categories. These other categories can have arbitrary names, but you must continue to define associated locations in the third Customizing step (Creating a Location). You are recommended to name them after the location (for example, if the location is LONDON, then name the storage category LONDON as well).


July 26, 2004 75

7.3.1.1.3 Creating a Location You only need to carry out this step if you want the associated content server to be publicly accessible. ...

1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Distribution → Define locations.

2. Choose New Entries to define locations that are available later in the cFolders application. Each user can choose his/her location from this list. This means, the name and description of the location should be meaningful to the users.

If you define at least one location in this step, the cFolders system automatically generates an additional entry in the list called “Default server”. If the user chooses this, the file transfers are done via the cFolders WAS server itself and not to a content server (the file storage, however, is done on the main content server).


76 July 26, 2004

7.3.1.1.4 Linking Locations to Storage Categories Use This step is only required for scenario C and D. You only need to carry out this step if you want the associated content server to be publicly accessible.

Procedure ...

1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Distribution → Define distribution of categories

2. Choose New entries.

3. Enter the name of a location as defined in the previous step (Create a Location).

4. In the second column, always enter CFFCONTENT.

5. In the third column, enter the storage category that you created in step 2 (Create a Storage Category), which points to the content server that should be used at this location.

You must associate each location with one storage category.


July 26, 2004 77

7.3.1.1.5 Naming the Server Use This step is only required for scenarios C and D. You only need to carry out this step if you want the associated content server to be publicly accessible. ...

1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Define Host and Properties.

2. Choose New Entries.

3. In the Host name field, enter the server address as defined in Creating a Content Server Entry [Seite 73] and its location.


78 July 26, 2004

7.3.1.1.6 Defining the HTTP View for a Front-End Content Server Use This step is only required for scenarios C and D. You only need to carry out this step if you want the associated content server to be publicly accessible.

Here, you define that if a URL is to be created for direct access to the content server, it must be created with dependency on the location. The URL depends on the network configuration, and this means that the URL to one particular server might be different at each location. The settings made in Naming the Server [Seite 77] and in this step allow you to define these URLs.

Procedure ...

1. From the cFolders WAS 6.40 Menu, call up transaction SPRO and choose SAP Reference IMG → SAP Web Application Server → Basis Services → Knowledge Provider → Content Management Service → Distribution → Define Content Server Alias.

2. Choose New Entries

3. Enter the alias address, ports, and HTTP script (usually ContentServer/ContentServer.dll) in the Content Server Alias section. In the For Content Server section, enter the real HTTP address, ports and script.


July 26, 2004 79

7.3.1.1.7 Analyzing the Content Server Administration For an analysis of the content server administration as seen by the cFolders package use the report “CFX_CHECK_LOCATIONS” in transaction SE38 in the cFolders WAS (this is recommended).

It lists all available locations, checks if they are properly connected to storage categories and therefore to content repositories, and reports the URL which would be used by the Internet browser at a particular location. Check that this URL is correct.

It gives you an output similar to the following:

Program CFX_CHECK_LOCATIONS

a) List of found locations:

============================================

Location: COPENHAGEN Server in Copenhagen

Location: LONDON (Default) British server

b) View of URL's on each location (Browser view):

============================================

Location: COPENHAGEN Server in Copenhagen

> Found Storage Category: CFFCONT3

> Found Content Repository: CFF3

> URL: http://p46623.wdf.sap-ag.de:1090/ContentServer/ContentServer.dll?create&pVersion…

Location: LONDON (Default) British server

> Found Storage Category: CFFMAIN

> Found Content Repository: CFF2

> URL: http://P46623:1090/ContentServer/ContentServer.dll?create&pVersion=0046&contRep=…

Here, you see that there are two locations COPENHAGEN and LONDON, and that the London server is the default server. Note that the URLs are normally much longer, but they are truncated at 80 characters, which is enough for the server name and port verification.


80 July 26, 2004

7.3.1.2 Content Server Customizing in the cFolders Application Use The cFolders application determines at runtime which settings are available to the network administrator and the end users. Most Customizing is carried out in the cFolders WAS 6.40, which is why the settings carried out in the cFolders application itself are very simple.

Prerequisites All the Customizing steps described in Content Server Customizing in the cFolders WAS [Seite 71] have been carried out.

Procedure

Administrator Settings ... ...

1. In the cFolders application, choose Network Administration from the menu.

The System Settings screen appears.

2. Choose the Network tab page.

If more than one storage category is available in the system, the you can enable direct access to the content server(s) by activating the Internet Access Allowed indicator.

If you do this, users can choose their location, that is, their preferred content server.

By default, the indicator is not activated. If you want to use scenarios C or D, you must activate the indicator.

User Settings If there are different locations available in the cFolders application, and the network administrator has allowed direct content server access, then each user can choose their location: ... ...

1. The user chooses Settings (My Settings .... ....) from the top right-hand corner of the cFolders screen.

The User Settings screen appears.

2. On the General tab page, the user chooses one of the entries in the File Server field.

� If the user chooses the default setting, which is the automatically generated “Standard server” setting, then the cFolders application transfers files via the base WAS server. For all other settings, the system optimizes the HTTP transfer for the selected location.

� If the user chooses one of the other options, then a storage category is derived from this location.


July 26, 2004 81

7.3.2 Changing the Content Server Configuration Use During the lifetime of your cFolders system you may need to change the content server configuration. This is usually not a problem, as long as you observe the following.

Procedure

Changing Scenarios

Typical “Upward” Scenario Change ...

1. From A to B, C, or D (switching from the default minimal configuration to a productive environment): Simply configure the content servers as described previously. The old documents that have been stored in the WAS database are still valid, however, they are not automatically transferred to the next content server.

2. From B to C or D (open the content server to direct Internet access): Add as many content servers as you want and associate locations with them (make sure you do not forget the first one, which did not need a location for scenario B).

The cFolders network administrator must explicitly allow direct content server access by activating the Internet Access Allowed indicator in the cFolders system on the Network tab page of the Administration service.

3. From C to D (add new locations): Configure new content servers and associate locations.

Typical “Downward” Scenario Change ...

1. From C or D to B (close the single content server to Internet access): The cFolders network administrator must disallow direct content server access by deactivating the Internet Access Allowed indicator in the cFolders application.

The content server(s) must continue to run, because the files are still located on them. Only the access type is changed here.

2. From D, C, or B to A: Not possible.

Upgrading to a New Content Server When an upgrade is carried out, for example, because a certain content server is full, no data is lost.

Proceed as follows: ...

1. Keep the old content server running, and also leave its storage category and content repository settings.

2. Add a new storage category and content repository for the new content server.

3. If the old server was directly accessible from the Internet, change the location link to the new storage category. This way all new files are created on the new content server, and the old ones can still be found on the old one.


82 July 26, 2004

Shutting Down a Content Server The files stored on this content server are no longer available; however, the collaborations, areas and folders that use some of these files are still valid. The missing files will cause all operations that access one of the files to fail : Read/view/edit files, copy files, create files, copy collaborations (which also copies the files).

When copying a document, only the file of the current document version is copied and therefore should be valid.

In addition, keep the cFolders WAS 6.40 customizing consistent by deleting the associated location of the old content server, its storage category, and content repository in customizing.

Users who still have this location as their chosen location in their user settings are automatically defaulted back to the Standard Server setting.


July 26, 2004 83

7.4 Installing the FTP (File Transfer Protocol) Box Use The FTP box allows files to be transferred between the cFolders application and a user-specific branch on an FTP server. The FTP box is an optional component within the cFolders landscape.

File storage on the FTP server is carried out as follows: ...

• Each user has a directory branch inside the base path, as defined by the network administrator. This branch name is made up of: SAP R/3 name+client+_+userid (example: APL200_kirsch).

The first part identifies the cFolders WAS and the SAP R/3 client, and the second part is the user ID, which is unique within the client. All read and write operations are performed only inside the user-specific directory and below. This ensures that no user can read or write in branches belonging to other users.

• Each user has an incoming and an outgoing directory. He or she can import cFolders files from the incoming directory and write files to the outgoing directory.

Procedure 1. Install an FTP server that is accessible from the cFolders WAS.

This means that there must be an open network connection between the WAS and FTP server for the FTP protocol. Additionally, the file listing on the FTP server must be in UNIX format.

You can verify access to the FTP server and the listing format by using the program “sapftp.exe”, which is installed with each SAP WAS set-up. Call “sapftp.exe” and use the ”open (FTP-SERVER)” command to log onto the server. Then type “dir”. The output must look similar to: ftp> dir200 PORT command successful.150 Opening ASCII mode data connection for/path/APL200_krisch/incoming.total 7-rwxr-xr-x 2 3 96 Jan 10 2001 test.gif-rwxr-xr-x 2 3 1024 Dec 20 2001 demo.jpg-rwxr-xr-x 5 3 96 Jul 11 2001 readme.txt-rw-r--r-- 1 sap 892 Jul 14 2000 readme-old-rwxrwx--- 2 sap 1024 Jul 16 10:51 template.asd-rwxr-xr-x 6 3 96 Dec 20 2001 readme.first226 Transfer complete. Note that the Microsoft Internet Information Server IIS has an FTP module that can be used for the FTP box. It has a setting inside the MMC (Microsoft Management Console) that allows the UNIX listing style to be set (default is DOS format, which cannot be used).

2. Settings on the FTP server:

The system administrator must create a base directory inside which the user-specific subdirectories are created. In the directory tree example below, the base directory is


84 July 26, 2004

described as (BASEPATH). A good choice for the directory name might be “/box”. If the server name is “p46623”, for example, this results in the path ftp://p46623/box.

3. Settings made by the cFolders network administrator:

a. On the Network Administration page, choose the File Storage tab page.

b. Set the Activate File Storage indicator to enable the FTP box functionality and enter the FTP server address and base path.

You can also enter a description in the External Tool field, which allows the user to identify the file storage more easily (for example, “FTP”). You can also enter a system-wide user + password combination. The system user + password are used if a user does not use their own password (see next step). The predefined values are user=ftp, password=ftp, which is commonly used for “anonymous ftp”.

4. Settings made by the cFolders user:

If the FTP box on the administrator settings page is activated, each user has a new tab page under their user settings. Under File Storage they can switch the FTP box on and off themselves (default = off). They can also set up a personalized user + password combination for accessing their personal branch on the FTP server directory tree. Personalized passwords on FTP directories are supported by some FTP servers, and must be set up by the FTP server administrator.

Example Using the following example data:

cFolders SAP R/3 name = APL

Client = 200

Three users: Krisch, Frank, Charly

the overall directory tree on the FTP server would look like this:

(FTP-SERVER)

(BASEPATH)

APL200_krisch

incoming

(File 0..n)

outgoing

(File 0..n)

APL200_frank

incoming

(File 0..n)

outgoing

(File 0..n)

APL200_charly

incoming

(File 0..n)

outgoing

(File 0..n)


July 26, 2004 85

7.5 Configuring Integration with the Microsoft Windows File Explorer Use The integration with Microsoft® Windows File Explorer enables users to work as comfortably with documents as with files saved locally in the file system. This function complements the normal document management function in cFolders and cProjects; it does not replace the normal online processing options. It is up to the individual users to decide whether they want to use this integration.

Prerequisites To install the software for the integration, you need administrator rights on the relevant PC.

Procedure To use File Explorer Integration, you must have made the following settings: ...

1. Activate the SOAP handler in the SAP Web Application Server, by activating the /sap/bc/soap/rfc node in transaction SICF.

2. Execute the Specify URLs for Windows File Explorer Integration activity in Customizing for Collaboration Projects.

The activity is also relevant to cFolders.

3. Assign the users who are to work with the Windows File Explorer the appropriate RFC authorization in the user profile.

� Function group CPRO_API

� Authorization object S_RFC

4. Activate the function in your personal settings as the user and execute the installation file:

� In cFolders you can find the installation file under Settings.

� In cProjects you can find the installation file under Settings → Technical Settings.

Note the prerequisites for installation that are mentioned there.


86 July 26, 2004

7.6 Configuring the WebEx Meeting Service Use The WebEx settings for cFolders apply to all components of the application. You can change these settings directly in the cFolders application.

WebEX Meeting Center: Terms of Use Agreement You agree that you are solely responsible for the content of all visual, written or audible communications sent by you. You further agree not to use the Services to communicate any message or material that is harassing, libelous, threatening, obscene, indecent, would violate the intellectual property rights of any party or is otherwise unlawful, that would give rise to civil liability, or that constitutes or encourages conduct that could constitute a criminal offense, under any applicable law or regulation. Although SAP is not responsible for any such communications, SAP may delete any such communications of which SAP becomes aware, at any time without notice. SAP may at any time and in its sole discretion, terminate the operation of the Website.

Procedure Select Administration in the cFolders menu to branch to the System Settings screen and choose the Meetings tab page.

Function Follow-On Path What You Should Know

Using the WebEx meeting service (default)

Select the Activate Meetings indicator

If the indicator is not activated, no users have the Meetings function or are able to see the Create Meeting pushbutton.

Sending e-mail invitations

Select the Activate E-Mail Invitations indicator

If this function is enabled, invitation e-mails are sent to all participants including the host.

Using the cFolders demo site

The WebEx integration with cFolders includes access to the SAP cFolders demo WebEx site. The demo site can be activated for testing purposes.

Select the Use cFolders Demo Site indicator

If this indicator is activated, cFolders creates WebEx demo users automatically in the background when accessing the demo site.

The demo site is limited to four participants per meeting at any one time. Additionally, each meeting is limited to a period of fifteen minutes.

For important information about restrictions related to the demo site, see WebEx Meeting Center: General Information [Seite 88].

Using your company’s own WebEx site

Enter the meeting site in the Meeting Site field.

The Use cFolders Demo Site indicator must remain deselected. Usually, you specify the site as follows:

<Protocol>://<companyname>.webex.com/

Note that the effective URL will be named as


July 26, 2004 87

negociated with WebEx.

Setting the maximum meeting duration in minutes

Maximum meeting duration

The default duration is 15 minutes.

Setting the update interval for the meeting assistant.

Update Interval The meeting assistant automatically updates the meeting overview. To limit the workload of the server, the network administrator can specify the update interval in seconds. The default is 60 seconds.

Note that the meetings are stored as XML files and can be accessed using WebDav [Seite 99]. The folder where the meetings are stored can be changed. The default is WebEx-meetings.


88 July 26, 2004

7.6.1 WebEx Meeting Center: General Information cFolders Demo WebEx Site https://sap-cfolders.webex.com/sap-cfolders

The WebEx integration in cFolders includes a demo version for using WebEx. The services provided through this Micro Site are limited, as follows:

• No more than four users may participate in a meeting at any one time. Additionally, each meeting is limited to a period of fifteen minutes.

• To be able to use the full range of functions in WebEx, customers have to contract with WebEx directly.

• Sales contact for WebEx within cFolders: Nick Goddard Channel Sales Manager Office: 408-944-4559 Mobile: 408-888-4217 [email protected]

Note that the automatic creation of WebEx demo users requires that your cFolders WAS must be accessible from the WebEx demo site. This means that your cFolders installation must have an open network connection for incoming calls from WebEx. If this connection is not available, it cannot be guaranteed that the WebEx demo site works correctly. In this case, contact WebEx at the address above and they will provide you with a company-specific demo site, which you can use for a limited period of time.

Customer with an Existing WebEx Meeting Center If you already have a WebEx Meeting Center you must verify the following settings to ensure flawless performance within cFolders.

Administrative Settings ...

1. Ensure that the Web site is API-enabled. Contact your representative at WebEx.

2. If you have an administrative account at your WebEx Meeting Center, you can log on and modify the settings at: http://<customer>.webex.com/webex/admin.

3. As a cFolders network administrator, you can configure WebEx as described in Configuring the WebEx Meeting Service [Seite 86].

User-Specific Settings To use WebEx Meetings users must carry out the following:

• Ensure that an administrator has created a user for you at WebEx and ask for your ID, password and e-mail that you use to sign in at the WebEx system.

• Ensure that an administrator has entered the same time zone for you in the WebEx system as the one you have in cFolders.

• Choose Settings from the top right-hand corner of the cFolders screen. On the Meetings tab page, enter the WebEx-ID in the Meeting User field, enter the WebEx-password in the Meeting Password field and confirm it in the Repeat Password field. Note that these entries are case-sensitive.

• On the User tab page ensure that there is an entry in the E-mail field. We recommend that you use the WebEx e-mail. Although you can use other e-mail addresses we


July 26, 2004 89

strongly suggest that the one from WebEx is retained, since the value given in cFolders overwrites the one in the WebEx Meeting Center.

Note that the entries User, Password and Repeat Password on the User tab page is data related to the cFolders user and not the WebEx user.

Confirm all these changes by choosing Save. After changing the data for the WebEx user, close the cFolders session, close the browser and restart the browser.

Troubleshooting Hints An error in the user settings may cause an error-message from WebEx to appear, which displays the text:

BadWebExIDOrPassword

If this occurs, it is because one of the entries described above is incorrect.


90 July 26, 2004

7.7 Archiving Use Collaborations can be archived from the collaboration overview in cFolders. They are archived using SAP Data Archiving and the archiving object "CFX_ARCH".

Activities To enable a collaboration to be archived, you must make certain settings in SAP Data Archiving using the archiving transaction SARA. For more information about which settings are necessary and how to carry them out, see SAP Library → SAP R/3 Enterprise Application Components → Cross-Application Components → Archiving Application Data (CA-ARC).


July 26, 2004 91

7.8 Processing Notifications Use There are two types of notifications that are sent via a job in the cFolders application:

• Summary e-mails contain a summary of received notifications and are sent automatically on a regular basis

• Reminder notifications are sent when a deadline has passed or processing time elapses

Prerequisites The cFolders system user has to exist. The system user can be created or changed under User Administration. For more information, see System User [Seite 61].

Procedure To access the individual functions, choose Network Administration from the cFolders Functions to branch to the System Settings screen.

Function Follow-On Menu Path What You Should Know

Activate the function for regularly sending summary e-mails

→ Notifications tab page. Choose Activate Summary E-Mails.

See below: Technical Information for Summary E-mails

Setting: Send all e-mails in cFolders with the system user as the sender

→ Notifications tab page

Set the Use System User as E-Mail Sender indicator.

If this indicator has been set, all e-mails that are sent from cFolders have the system user as the technical sender.

However, the content of the e-mail contains the name of the actual sender and the recipient of the answer to the e-mail (Reply to field) is also the actual sender.

This setting is useful, for example, if the network settings of the mail server in the enterprise do not allow e-mails to be sent that have a number of different sender domains.

Activate the status management function for sending reminder notifications

→ Status tab page. Choose Activate Reminder Notifications.

See below: Technical Information for Reminder Notifications.

Technical Information for Summary E-Mails The summary e-mails are sent by the SAP_CFX_NOTIFICATIONREPORTEMAIL job, which is scheduled periodically every few minutes. The job runs the CFX_SEND_REPORT_EMAIL


92 July 26, 2004

report. The job user is a special system user that has to be created under User Administration. For more information, see System User [Seite 61].

If the job or the job user is deleted for some reason, you can create them again by repeating the above procedure, that is, by choosing Activate Summary E-Mails.

If you have activated the Status Reminder Notifications (described below), this job may also run the CFX_SEND_REMINDER report. Therefore, if you delete this job, neither function will work.

Technical Information for Reminder Notifications The reminder notifications are sent by the SAP_CFX_NOTIFICATIONREPORTEMAIL job, which is scheduled periodically every few minutes. The job runs the CFX_SEND_REMINDER report. The job user is a special system user that has to be created under User Administration. For more information, see System User [Seite 61].

If the job or the job user is deleted for some reason, you can create them again by repeating the above procedure, that is, by choosing Activate Reminder Notifications.

If you have activated the Summary E-Mails (described above), the same job may also run the CFX_SEND_REPORT_EMAIL report. Therefore, if you delete this job neither function will work.


July 26, 2004 93

7.9 Integration with mySAP SRM Purpose cFolders supports the integration with the SAP Enterprise Buyer of mySAP Supplier Relationship Management (SRM). You can use the integration of cFolders with mySAP SRM to order a shopping cart in a connected SRM system (which triggers a follow-up process, in which a bid invitation, a purchase order, or a strategic contract will be created). An External Reference to the shopping cart in mySAP SRM is automatically created in the cFolders collaboration from which the shopping cart has been ordered,. Inside mySAP SRM, the follow-up objects created during the triggered workflow also contain a reference to the cFolders collaboration concerned.

Prerequisites mySAP SRM 3.00, SP 03 or higher

Process flow 1. Create an RFC connection from the cFolders system to the SRM system using

transaction SM59. For more information on how to create an RFC connection, choose Help → Application Help in transaction SM59. Test the connection. This connection requires a particular dummy user. This dummy user needs certain authorizations and SAP roles within the SRM system. For more information on authorizations and SAP roles, see SAP Library → SAP Cross-Industry Solutions → mySAP Supplier Relationship Management → Enterprise Buyer Professional Edition → Integration → Integration of Applications → Procurement of External Requirements and Prerequisites for External Requirements.

2. Create an RFC connection from the SRM system to the cFolders system using transaction SM59. Test the connection. You must use the same dummy user in both RFC connections. This dummy user needs the SAP role SAP_CFX_USER and the authorization to create collaborations. When a shopping cart has been created from cFolders, this particular dummy user will automatically receive administration authorization for the corresponding collaboration. For the follow-up process, SRM users (for example, purchasers or suppliers) will need to obtain access to the collaboration. The above mentioned dummy user for the RFC connections will automatically assign the relevant authorization to these SRM users.

3. Edit the settings for the integration with mySAP SRM in accordance with Making WebDAV Settings for cFolders Integration with mySAP SRM [Seite 154].

SAP recommends that you use Single Sign-On to switch more easily between the systems.

Restrictions • Both mySAP SRM and cFolders structure information. However, it is not possible to

transfer one system structure to the other automatically.

• Master data such as materials will not be integrated. Therefore, no help will be available. Instead free text will be used.

• After having created a shopping cart from cFolders, the corresponding data can only be viewed in mySAP SRM. cFolders only contains the link to this data in mySAP SRM.

• Creating a shopping cart is only possible in the cFolders competitive scenario.


94 July 26, 2004

• Shopping carts and the follow-up objects created during the triggered workflow can only be created locally in the SRM system. They are not sent to any back-end system.

Security Note that you have to set up an RFC connection to an SRM system, which is may be behind your company firewalls, while cFolders is usually located in your demilitarized zone (DMZ). This is a potential security risk, because it opens a system connection from the outside (DMZ) to the intranet. However, this connection can be additionally protected by placing a SAProuter between the systems to cross the intranet border in a controlled manner. The system connection will be used exclusively for the RFC protocol. HTTP is not necessary.


July 26, 2004 95

7.10 Changing the Appearance of cFolders Use You can change the appearance of cFolders by replacing the standard style sheet and logos with your own company-specific style sheets and logos. There are two ways of doing this:

• Change the mime objects in the mime repository in the cFolders WAS 6.40. This is a program modification. Or you can add the mime objects with different names to the mime repository.

• Override the default style sheets and logos with system and/or user settings in the cFolders application. For this you need an additional Web server where you can store the mime objects.

Procedure Creating Style Sheets [Seite 96]

Creating Logos [Seite 97]

Applying Style Sheets and Logos [Seite 98]


96 July 26, 2004

7.10.1 Creating Style Sheets Use Two different style sheets are provided as examples and are stored in the mime repository in the cFolders WAS:

• css/green.css

• css/yellow.css

cFolders uses special style classes, therefore, you probably cannot use an existing company style sheet. The cFolders style classes may change from one cFolders release to another.

Prerequisites A style sheet has to be in the css style sheet format: (*.css).

We strongly recommend that you have prior knowledge of CSS style sheets. SAP does not provide application support for any errors that occur because of changed template style sheets or incorrect style sheets.

Procedure ...

1. Create a copy of the cFolders template style sheet.

Location for example: <cFolders url>/css/purple.css

2. Change this template style sheet, for example colors, fonts and so on.

3. Store the changed style sheet on a Web server, where it is accessible to all cFolders users.


July 26, 2004 97

7.10.2 Creating Logos Use The logo line at the top of every cFolders page consists of three different images: left, middle, and right. The height of the logo line is 50 pixels and the width depends on the page content, but is a minimum of 990 pixels. So that the logo can be stretched, the middle part of the logo should be scaleable. The easiest way to achieve this is by using an image with only one color, or maybe a color scheme that scales well.

Since the height is fixed at 50 pixels, the requirements for the width of the three images (left, middle, and right) is that the sum of the width is <= 990 pixels. Then if the page needs a wider logo line, the middle part is stretched.

SAP does not provide application support for changing logos or for any errors that occur because of incorrect logos.

Prerequisites The logos have to be in bitmap format: (*.bmp,*.gif,*.jpeg,*.jgp). You are recommended to use the GIF and/or JPG format (the original SAP logos are in JPG format).

Procedure ...

1. Create a bitmap with n x 50 pixels for the logo on the left-hand side of the upper frame.

2. Create a bitmap with m x 50 pixels for the logo on the right-hand side of the upper frame.

3. Create a bitmap that can be stretched with (990 – n – m) x 50 pixels for the middle part.

4. Store the logos on a Web server, where they are accessible to all cFolders users.


98 July 26, 2004

7.10.3 Applying Style Sheets and Logos Web Server Method For the style sheet or logos to have an affect on the appearance of the cFolders application, you can enter the URL of the style sheet in the cFolders settings. If you want the style sheet to appear for all cFolders users, you do this in the system settings under Administration. If it is just for one specific user, you do this in the user settings under Settings. To access the new or changed mime files, you need an additional Web Server. ...

1. In the cFolders application, choose Administration from the menu, or Settings from the top-right hand corner of the screen.

2. Select the Layout tab page.

3. Specify the URLs of your own logos and style sheets:

� Banner left

� Banner middle

� Banner right

� Style sheet

You can also hide the banner by deactivating the Activate Banner indicator. This is useful if you embed the cFolders application into a HTML frame inside a company portal. If this indicator is set in the system administration settings, each user can still override it in their user settings.

Users can also display a photo of themselves in the cFolders system, by entering the URL of a photo on the Layout tab page in their user settings (My Photo URL). The image is scaled to 130 x 100 pixels. This is only available in the user settings.

Mime Repository Method Instead of storing your style sheet or logos on a separate Web server and changing the user or system settings, you can replace the original SAP style sheet mime objects: ... ...

1. In the cFolders WAS 6.40, call up transaction SE80.

2. Choose Mime Repository

3. In the BSP application field, enter CFX_RFC_UI.

The name of the original style sheet(s) are “css/bspie5.css” and “css/cfxie5.css”. Note that the alternative style sheets green.css and yellow.css contain all CSS classes in one single file.

The name of the original logo files are: logo_left.jpg, logo_middle.jpg, and logo_right.jpg.

Note that if you change the original SAP mimes, this is a program modification. You need developer authorization for this.


July 26, 2004 99

7.11 Changing cFolders Standard Settings Using WebDAV Use You can run cFolders without having to change any standard settings in the cFolders application. However, if you want to change certain settings, you can do this using a WebDAV client (for example, Microsoft Web Folders or Microsoft Word 2000).

WebDAV allows you to save user and/or system settings in cFolders as XML files on a cFolders Web file system, which can be accessed through the WebDAV protocol. Using this procedure you can, for example, add an additional language or a specific vocabulary to be used in cFolders.

Prerequisites You have created the settings URL for WebDAV access as described in Creating the Settings URL for WebDAV Access [Seite 43].

Procedure To set up Microsoft Windows WebFolders as a WebDAV Client, proceed as follows. (As an example, the use of Microsoft Windows 2000 is described here): ...

1. In your Microsoft Windows 2000 Explorer choose My Network Places → Add Network Place.

The Add Network Place Wizard appears.

2. In the entry field Type the location of the Network Place enter the specified URL in the following format: <Protocol>://<Server>:<Port>/<External aliassettings>.

3. Choose Next.

The popup Enter Network Password appears.

4. Enter your user name and password.

5. Choose OK.

The Add Network Place Wizard reappears.

6. In the entry field Enter a name for this Network Place enter a name for the folder as you want it to be displayed in your file explorer.

7. Choose Finish.

Your newly created Web folder with all its content is opened in a separate file explorer window.

The system creates the content for the Web folder dynamically when a user logs on to cFolders.

Troubleshooting Hints To change the settings, you can add files to specified folders of the WebDAV directory. These folders might not exist yet. Some folders are created automatically, others must be created manually:

1. The Attributes folder used for the definitions of materials and bills of material and the GenericObjects folder used for the definitions of Generic Objects are created


100 July 26, 2004

automatically as soon as you try to create an object in a folder for the very first time in the cFolders application.

2. The ObjectCategories folder is created automatically, as soon as you try to create a document in a folder for the very first time in the cFolders application.

3. The Icons folder must be created manually in the WebDAV directory.

You can also create the folders mentioned under 1. and 2. manually in the WebDAV directory.

If you use the Microsoft Windows File Explorer for WebDAV administration, you first have to create the required folders locally on your hard disk. Then you can drag and drop them into the WebDAV directory.

See also: Adding New Languages and Vocabularies to cFolders [Seite 101]

Changing User and System Settings [Seite 103]

Editing Attributes for Materials and Structures [Seite 104]

Creating Generic Object Types and Document Categories [Seite 110]

Integration with mySAP SRM [Seite 93]


July 26, 2004 101

7.11.1 Adding New Languages and Vocabularies to cFolders New languages and new vocabularies can be applied to cFolders using WebDAV.

The language setting for cFolders applies to all components of the application. The language directory contains XML files that contain language-dependent texts. The directory contains a single file for each language. You can translate text entries (concepts) directly within these files using any XML editor.

To view the concept IDs within cFolders, choose Settings (top right-hand menu in cFolders) and on the Diagnosis tab page, activate the Show Text IDs indicator.

You can create new languages or vocabularies for cFolders by copying and changing the name of a file and then changing the contents of the file. When you create a new file, you are free to use any naming convention. Refer to the example below for creating a new vocabulary.

Example If some of the terminology in the standard cFolders translation is not suitable, you can selectively replace individual terms. To do this, you must define your own specific vocabulary by copying the original file under a new name. In the new file (which is an XML file), within the package tag you can specify the attribute vocabulary to identify your specific vocabulary (for example, "Engineering").

• Standard vocabulary:

<package name="CFX_UI" vocabulary="SAP" language="EN">

• Sample customer vocabulary “Engineering”:

<package name="CFX_UI" vocabulary="Engineering" language="EN">

The new vocabulary file must only contain terms (concepts) that are different from those in the standard vocabulary. In the example below, only the concept “INITIATOR” has been replaced in the "Engineering" vocabulary:

• Content of the standard cFolders file (English version):

<package name="CFX_UI" vocabulary="SAP" language="EN">

...

<concept id="INITIATOR">

<text>Manager</text>

</concept>

...

</package>

• Content of the new vocabulary file:

<package name="CFX_UI" vocabulary="Engineering" language="EN">

<concept id="INITIATOR">

<text>Purchaser</text>

</concept>

</package>


102 July 26, 2004

You have to ensure that the new file is still syntactically a valid XML document.

You can assign the new vocabulary in cFolders under the user settings, on the General tab page.

If you want to restore the standard settings, simply delete the entire language directory. When you restart cFolders, the standard files are automatically restored by the system.


July 26, 2004 103

7.11.2 Changing User and System Settings System Settings The system settings for cFolders apply to all components of the application. You can change these settings directly in the cFolders application by choosing User Administration in the cFolders menu. Changing these settings with the WebDAV client is not recommended.

User Settings The user settings for each user are stored in a separate XML file. The file name for a user consists of the SAP user name with an XML extension (for example, smith.xml). Each user can change his own settings directly in cFolders by choosing Settings (in the top right-hand corner of cFolders). A user administrator can also change individual settings using the WebDAV client.

You can also use the settings of a specific user to create new user groups with the same settings. To do this, you simply copy a user's file with the desired settings to a new target file.

You want to provide a group of users with the same company logo or style sheet. Change the user settings for a specific user (for example, “brown”) as required. You can then use brown's settings as a template for creating a group. Simply copy the file "brown.xml" under a new name (for example, "smith.xml").


104 July 26, 2004

7.11.3 Editing Attributes for Materials and Structures Use If you create a bill of material, bill of material item, or material in cFolders, you see a list of attributes such as size, base unit of measure, item category and so on. Some of the fields are read only, some have a dropdown list from which you have to choose a value.

These lists of attributes for BOM, BOM item, and material are each stored in a separate XML file that you can change using the WebDAV client.

The XML files must adhere to this XSD Description [Seite 108]. It is important that you adhere to the entry conventions described below. SAP cannot provide support for any problems that arise due to not adhering to these conventions.

Procedure ...

1. To change one of the XML files for cFolders attributes, go to the WebDAV Settings folder where the Attributes subfolder is located. This contains the following XML files:

� For bill of material attributes: structure_Attributes.xml

� For bill of material item attributes: s_item_Attributes.xml

� For material attributes: mat_Attributes.xml

2. Open the file you want to change in an editor of your choice.

3. Open an attribute tag in the XML file.

A cFolders attribute, for example, base unit of measure, is represented by an attribute tag in the XML file. You can edit and delete existing tags, and add new tags. The sequence of attributes displayed in cFolders mirrors the sequence of attributes in the XML file.

The recommended procedure for creating new cFolders attributes is to copy and paste an existing attribute in the XML file and then to change its values.

4. Save your modified XML file in the WebDAV folder.

If you delete one of the attribute files from the WebDAV folder, the attribute file provided by SAP is copied into the WebDAV folder next time you start cFolders.


July 26, 2004 105

7.11.3.1 Information About the XSD for Materials and Structures Attribute Tag The attribute tag consists of the following:

• namespace: You can enter your own namespace to identify your attributes.

Do not use a blank for your namespace because this is reserved for SAP.

• ID: You can enter any character string. This uniquely identifies the attribute in the file. You are recommended to use your own namespace and then a different ID for each attribute. An attribute is uniquely identified by the parameters ID and namespace.

• EntryRequired: This must contain either the value true or false. It defines whether a value must be entered (= true) or not (= false) for the attribute that is displayed in cFolders. Do not leave the EntryRequired attribute blank.

• ReadOnly: This must also contain either the value true or false. It defines whether the cFolders attribute can be changed (= false ) or not (= true).

Exception: When you create a material, bill of material, or bill of material item, values can be entered into read-only fields. On saving, these fields then become read-only and cannot be changed.

Subnodes of the Attribute Tag

Label The Label subnode defines the label for the cFolders attribute that is displayed on the cFolders interface. The label subnode contains the attributes Alias and Default. One of these attributes must be filled.

• Alias: This refers to a text alias that is stored in the text repository. If this attribute is filled, the corresponding text in the repository is always displayed in cFolders (the texts in the text repository are stored in XML files, for more information see Adding New Languages and Vocabularies to cFolders [Seite 101]).

• Default: This is the text that you can enter if you do not want to use the text repository. You can enter anything here.

If both alias and default contain an entry, then the system always uses the alias entry.

AllowedValues The optional AllowedValues subnode contains all the values that are allowed for the cFolders attribute. For example, for the base unit of measure in cFolders, the allowed values include centimeter, millimeter, ton, and so on, which are displayed as a drop-down list.

You do not have to enter anything here if you do not want to have a list of allowed values for a cFolders attribute.

The AllowedValues subnode contains a list of AllowedValue subnodes.

• The AllowedValue subnode has the attributes ID, Alias and Default.


106 July 26, 2004

� ID is the value that is stored internally in the XML file.

� Alias is the text alias that is displayed on the cFolders interface in the dropdown menu.

� Default is the text that you can enter if you do not want to use the text repository. You can enter anything here.

• If there are exactly two AllowedValue subnodes that have an ID which is “true” or “false”, the attribute is displayed as a checkbox in cFolders.

Types The optional Types subnode contains a list of Type subnodes. It is used for structure items only. If the Types subnode is specified, this cFolders attribute is only shown for the item types specified in the Type subnodes. See below, Attributes with Special Names.

Once you have created an XML file containing attributes of your choice, and a material, bill of material, or BOM item, has been created in the cFolders system using these attributes, it is not recommended to change any of the attributes in the XML file. For example, changing an attribute from a required entry field to read only and so on. SAP does not provide support for problems arising from attributes being changed after they have already been used in the cFolders application.

Back-End Integration The default XML file supplied with cFolders contains all the attributes that are relevant for back-end integration, that is, they can be imported and exported between the cFolders system and the back-end system. However, only the most important attributes are actually displayed, all other attributes are hidden using comment tags. This is because there are so many existing attributes that the user interface would become unmanageable if they were all displayed. If you would like to use any of the hidden attributes, remove the comment tags, or add comment tags to an attribute to hide it.

The ID must remain as it is in the default XML file for the back-end integration to function properly.

Any attributes that are not contained in the default XML are not supported for back-end integration.

Attributes with Special Names

Material Names Two attributes make up the name for a material:

• The attribute for the material description (Namespace=” ”, ID = "MaterialDescription")

• The material number (Namespace=" " ID="MaterialNumber").

The first 21 letters of the material description attribute, a blank, and the material number attribute are concatenated to get the material name.

To be able to work with materials, you need at least one of these two attributes. You are free to change the Label and AllowedValue subnodes, but do not change the Namespace and the ID of material description and material number.

BOM Item Number Attribute


July 26, 2004 107

The bill of material item attribute (Namespace=" " ID="Number") appears in particular places in the cFolders application, for example, as part of the title of a bill of material item, in the navigation path, and in the item overview.

This attribute should not be deleted.

BOM Item Type Attribute This attribute (Namespace=" " ID="Type") controls whether or not other attributes are displayed in certain situations.

For example, if you create a BOM item, you must enter an item type. The attributes that are then displayed on the cFolders interface, after saving or updating the screen, are defined by the particular item type that is chosen. This can be controlled using the “Type” attribute.

108 July 26, 2004

7.11.3.2 XSD Description for Materials and Structures <?xml version="1.0" encoding="UTF-8" ?>



- <xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.sap.com/2002/abap/cfx_folders/customizing/attributes" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="" elementFormDefault="qualified">

- <xsd:element name="Attribute">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element ref="Label" />

<xsd:element ref="AllowedValues" minOccurs="0" />

<xsd:element ref="Types" minOccurs="0" />

</xsd:sequence>

<xsd:attribute name="Namespace" use="required" type="xsd:string" />

<xsd:attribute name="ID" use="required" type="xsd:string" />

<xsd:attribute name="EntryRequired" type="xsd:boolean" />

<xsd:attribute name="ReadOnly" use="optional" type="xsd:boolean" />

</xsd:complexType>

</xsd:element>

- <xsd:element name="Attributes">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element ref="Attribute" minOccurs="0" maxOccurs="unbounded" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

- <xsd:element name="Types">

- <xsd:complexType>

- <xsd:sequence>

<xsd:element ref="Type" minOccurs="0" maxOccurs="unbounded" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="Type" type="xsd:string" />

- <xsd:element name="AllowedValues">


July 26, 2004 109

- <xsd:complexType>

- <xsd:sequence>

<xsd:element ref="AllowedValue" minOccurs="0" maxOccurs="unbounded" />

</xsd:sequence>

</xsd:complexType>

</xsd:element>

- <xsd:element name="AllowedValue">

- <xsd:complexType>

- <xsd:complexContent>

- <xsd:extension base="TextType">

<xsd:attribute name="ID" use="required" type="xsd:string" />

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

</xsd:element>

<xsd:element name="Label" type="TextType" />

- <xsd:complexType name="TextType">

<xsd:attribute name="Alias" use="optional" type="xsd:string" />

<xsd:attribute name="Default" use="optional" type="xsd:string" />

</xsd:complexType>

</xsd:schema>


110 July 26, 2004

7.11.4 Creating Generic Object Types and Document Categories Use SAP supplies certain objects in the cFolders system such as material, document, and folder. You also have the option of creating your own objects types using the generic object type, for example, 8D report or functional location, and your own document categories, for example, certificate or CAD drawing.

You create generic object types and document categories in the XML format, adhering to a predefined XSD description and store them with all other cFolders system settings in the WebDAV directory [Seite 99].

When you create a generic object type and document category, you can define, for example:

• The icon and name used to display the object or category in the cFolders system

• The data fields for the object or category, and their type (for example, string, date, and so on)

• Whether data fields in a document category are relevant to authorization

• Whether data fields in a generic object type are relevant to authorization and status

Prerequisites You have set up a WebDAV [Seite 99] client for cFolders.

Procedure What How More Information

Generic Object Type Create XML file, adhering to XSD description.

Store XML file in GenericObjects folder in the WebDAV directory under cFolders settings.

To simplify the creation process, you can copy the example of a generic object type provided.

Document Category Create XML file, adhering to XSD description. Ensure that the CategoryForRefs tag contains the word “document“.

Store XML file in the ObjectCategories folder in the WebDAV directory under cFolders settings.

To simplify the creation process, you can copy the example of a document category provided.


July 26, 2004 111

Each generic object type and document category must have a separate XML file.

Result Once you have created the generic object type or document category, users can create and edit objects of this new type or documents of this new category in the cFolders system:

• The generic object type appears in the list of cFolders objects that you can create for a collaboration, along with the supplied object types such as data sheet, material, and so on.

• The document category appears in a dropdown list on the initial screen when you create a document.


112 July 26, 2004

7.11.4.1 Structural Elements of the Generic Object Type or Doc. Category When you create a generic object type or document category in the XML file format, you can define the fields, link lists, field groups, items, and also the attributes and contents of these, according to the rules laid down in the XSD description.

Fields A field can be a checkbox, dropdown list box, a reference, or an input field.

An input field can have a data type and a length (for example, integer 5 for a German zip code field). It can be a required-entry field and have a default value. This default value can be defined as a constant so that it cannot be changed in the generic object itself.

There is no “read-only” concept as for materials and bills of material. You can use status profiles to make a field read-only for particular statuses.

Items Items are used to structure the fields and link lists, and thereby the user interface.

In the generic object or document category, all items are displayed in an overview table, and each item has its own page where the user can edit it. The cFolders administrator defines all the fields and link lists for an item.

If a user has no authorization for any field or link list in an item, the user cannot see this item.

The cFolders administrator defines which fields belong to the items and which of them are displayed in the overview table. The item field in the first column of the overview table is used to navigate to the detail screen for that item. This field cannot be a link and must always have a value. As a consequence, items that you define in the XML must have a default value for this first field.

Link Lists A link can be to an object of a predefined object type that is located in the same collaboration area as the generic object type.

You can have several link lists, but you cannot have several object types in one list. In other words, one link list can link to documents, another can link to materials, but you cannot have a list that links to both materials and documents.

Field Groups Field groups are a means of grouping together fields and link lists that belong together thematically or according to how they are processed, regardless of their location on the interface, so that authorizations and status can be applied to them and used to control them.

You can assign a field or link list to multiple field groups. Note, however, that each field can only be assigned to one field group that is relevant for authorization.

Status and Authorization In the XML file, you can define that a field group is relevant for authorization (generic object type and document category) and status (generic object type only):

• Status: If a status profile is restricted to a generic object type, users with create authorization for the status profile can define whether the field groups are to be protected in each status.


July 26, 2004 113

• Authorization: If a user has administration authorization for a field group in a generic object or document category, they can decide who has authorization for the field group.

Allowing Users to Add Fields and Items You can define that users with write authorization can add their own fields and/or items to generic objects or document categories. They do not touch the actual definition in the XML file, just their generic object or document category that they have created or changed in a collaboration. In the XML file, you define the properties of the fields and items that they add.

Ranking You can also rank a generic object type, that is, define where it is displayed in the list of object types on particular screens using the “IsStandardObjectType” attribute (see the XSD Description [Seite 108] and XSD for Generic Object Type and Document Category [Seite 119]). This is useful if you have 20 or more generic object types in the cFolders system. Note that this attribute does not apply to document categories.


114 July 26, 2004

7.11.4.1.1 Detailed Information About the XSD Description The following provides you with additional information about the XSD [Seite 119] description for the generic object type and document category.

Information contained in the XSD itself, for example, which attributes are required, data types, and so on, is not repeated here. The name of the XSD is „GenericObjectType“, however, it also applies to the document category.

ID and Namespace This pair is used to uniquely identify objects. Ensure that each of these pairs is used only once within its validity space. The validity space of the GenericObjectType node is one cFolders client. The validity space for all other nodes is the generic object type or category definition in which they are defined.

The objects provided by SAP have an empty string or ‘SAP’ for the namespace. For the namespace of objects that you create, choose “www.<your_company>.com/<your_department>/<your group>“ for example. Make sure that you are the only one using this namespace. Use the same namespace for all your objects so that it is possible to differentiate between objects that are created by different groups, even if their IDs happen to be the same.

The ID and the namespace can have a maximum of 255 characters each. This restriction applies to all other strings and is especially important if the data is access via the API.

TextType (Alias, Default) Elements that contain texts displayed on the user interface have this type. If you do not need language-dependent texts, you must use the “default” attribute and leave out the “alias” attribute. For example, “default=’worker’ ”. If you need language-dependent texts, you must create an alias for each text in the cFolders text management system and use the alias in the “alias” attribute. For example, “alias=’CFX_UI/STUDENT’”. In this case, you leave out the “default” attribute. If you use both attributes, (alias and default), system behavior is not defined.

For more information about the cFolders text management system, see Changing cFolders Standard Settings Using WebDAV [Seite 99].

Individual Elements of the GenericObjectType.xsd • GenericObjectType: Generic object type / document category

� Attributes:

� Namespace, ID: Uniquely identifies the generic object type or document category.

� IsStandardObjectType: “true“ or “false“. Select “true“ for the object types used the most. There should be no more than 5 – 10 standard object types in the system so that the user interface does not become unmanageable. This attribute does not apply to document categories.

� Nodes:


July 26, 2004 115

� CategoryForRefs: Only used to define a category. Here you specify for which object types this category can be used. At the moment, only documents are supported (ID =”doc”, Namespace =““).

� Name: The name of the generic object type/document category displayed on the user interface.

� Description: Description of the generic object type/document category.

� Icon: Name of the graphic file for the icon. The file must be located in the “Icons“ folder with the cFolders settings in the WebDAV directory.

� FieldGroups: List of field groups.

� DataTypes: Lists with data types.

� NonStructuredElements: Fields and links that are not structured in items.

� StructuredElements: List with items

• FieldGroup: Field group

� Attributes:

� Namespace, ID: Uniquely identifies the field group.

� IsForAuthorization: Can the field group be used for authorizations? Note: each field can only be assigned to one field group that can be used for authorizations.

� IsForStatus: Can the field group be used for status properties?

� Nodes:

� Name: Name of the field group that is displayed on the user interface.

• DataType: Data type

� Attributes:

� Namespace, ID: Uniquely identifies the data type.

� Type: Data type. The options and the internal format for storing the data in cFolders is as follows:

• string: Any character string (text)

• integer: Number without decimal places (also negative). The range is –2^31 to 2^31 – 1.

• date: Date. The internal format is‘YYYYMMDD’, where YYYY is the year, MM, the month and DD the day.

• boolean: Only ‘true’ or ‘false’

• enumeration: Selection list. The options must be maintained for “AllowedValues“ (see below). The internal format is the value of the ‘Value’ attribute of the ‘AllowedValue’ node.

• IDREF: Link to cFolders object. ”AllowedObjectTypeRefs” must be specified (see below). The internal format is the internal cFolders ID of the object

� Length: Only for “type” = “string” or “integer”: Maximum length (number of characters).


116 July 26, 2004

� Nodes:

� AllowedValues: Only for “Type” = “enumeration”. Selection list.

� AllowedObjectTypeRefs: Only for “type” = “IDREF”. Specifies to which object type the link points.

• AllowedValue: Option for enumeration.

� Attributes:

� Alias, Default: The text displayed to the user.

� Value: Key of the option. It is used and saved internally. Must be specified.

• AllowedObjectTypeRef: Specifies to which object type the link points. In addition to the generic object types, you can also choose standard object types, users, and user groups.

� Attributes:

� Namespace, ID: If you want to link to generic object types, you must specify their ID and namespace. For all other object types, you must leave out the namespace, and specify the ID:

• doc: Document

• hyp: Bookmark

• mat: Material

• structure: Bill of material

• ds: Datasheet

• dis: Discussion

• txt: Text

• usr: User (not possible in LinkList node, see below )

• usrgrp: User group (not possible in LinkList node, see below )

• PropertyList: List of properties that are displayed one below the other on the interface.

� Nodes:

� Heading: Title. It is displayed on the user interface above the properties.

� Properties: Properties with a predefined name that are common to all objects of this type. See also “Property”.

� TemplateProperties: Properties whose name (and meaning) can be specified for each individual object of this type. See also “TemplateProperty”.

• Property: Property that is displayed on the user interface as one or more fields next to each other, with a name to the left of the field or fields. For example: Name with a string – field or weight with a string (number) field for the value and an enumeration – field for unit.

� Nodes:

� Fields: List with (entry) fields


July 26, 2004 117

• TemplateProperty: Template property. Like property. The only difference being that the meaning and name for each object is defined when the object is edited. For every template property, you can define as many properties as required.

� Nodes:

� TemplateLabel: Field in which the label can be entered. Only simple data types are allowed for the field. Multiple values and links (“type” = “IDREF” in DataTypeRef) are not allowed.

� Fields: List with (entry) fields. The fields used here cannot have multiple values.

• Fields: (Entry) fields. Can contain one or two ‘Field’ nodes. Except if one field node is a link (“type” = “IDREF” in DataTypeRef ), in which case one field is allowed only.

� Nodes:

� Field: (Entry) field.

• Field: (Entry) field.

� Attributes:

� Namespace, ID: Uniquely identifies the field.

� DisplayLines: Only for strings and enumerations. The default is one. If you specify a larger value, a multi-line entry field can be generated for strings and a selection box instead of a dropdown list can be generated for enumerations.

� IsConstant: The value is the same for all objects of this type, cannot be changed, and is defined in this XML file.

� IsEntryRequired: Required field? If so, the field must have a value.

� HasMultipleValues: The field can have multiple values.

� Nodes:

� Label: The label of the first field of a property is displayed to the left of the property’s fields. The labels of the other fields are read out if the accessibility function is activated.

� DataTypeRef: Link to one of the data types specified above.

� DefaultValues: When the object is created, the field contains these default values.

� FieldGroupRefs: Link to the field groups defined above whose properties this field inherits.

• DefaultValue: When the generic object is created, the field contains this value.

� Attributes:

� Alias, Default: Only for strings. A language-dependent default can be defined for the text.

� Value: For all data types except for strings. The value in the internal cFolders format.

• LinkList: List with object links

� Attributes:

� Namespace, ID: Uniquely identifies the list.


118 July 26, 2004

� Nodes:

� Heading: Title.

� AllowedObjectTypeRefs: Type of the objects that can contain this list. As for “AllowedObjectTypeRef” (except users and user groups).

� FieldGroupRefs: Link to the field groups defined above whose properties this list inherits.

• ItemList: List with items.

� Attributes:

� IsNewItemAllowed: Can new items be created for each object? If not, there are only “DefaultItems“.

� Nodes:

� Heading: Title

� AllItems: Properties and link lists of all items, that is, those that are predefined and those created per object.

� FieldInOverviewRefs: References to fields defined in “AllItems”. These fields are displayed on the user interface in the overview list with all items of an object. The list is sorted according to the values of the first field named here.

� DefaultItems: Predefined items.

• DefaultItem: Predefined item

� Attributes:

� Namespace, ID: Uniquely identifies the predefined item.

� IsDeletable: Can this predefined item be deleted for each object?

� Nodes:

� Settings: Predefined values for all fields or lists with object links defined in “AllItems”.

� AdditionalElements: Properties and link lists of this item.

• Setting: Predefined values for fields or lists with object links defined in “AllItems”.

� Nodes:

� FieldOrLinkListRef: Reference to a field or a list with object links defined in “AllItems”.

� DefaultValues: Default values for the object specified with “FieldOrLinkListRef”.

� FieldGroupRefs: Link to the field groups defined above whose properties the object that is specified with ‘FieldOrLinkListRef’ inherits. If this node (“FieldGroupRefs”) is specified, the field groups that may have been specified directly for the object are replaced by those specified here.

July 26, 2004 119

7.11.4.1.2 XSD for Generic Object Type and Document Category <?xml version = "1.0" encoding = "UTF-8"?>



<xsd:schema xmlns = "http://www.sap.com/2002/abap/cfx_folders/customizing/GenericObjectType"

targetNamespace = "http://www.sap.com/2002/abap/cfx_folders/customizing/GenericObjectType"

xmlns:xsd = "http://www.w3.org/2001/XMLSchema"

version = "">

<xsd:element name = "GenericObjectType">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "CategoryForRefs" minOccurs = "0"/>

<xsd:element ref = "Name"/>

<xsd:element ref = "Description"/>

<xsd:element ref = "Icon" minOccurs = "0"/>

<xsd:element ref = "FieldGroups" minOccurs = "0"/>

<xsd:element ref = "DataTypes" minOccurs = "0"/>

<xsd:element ref = "NonStructuredElements" minOccurs = "0"/>

<xsd:element ref = "StructuredElements" minOccurs = "0"/>

</xsd:sequence>

<xsd:attribute name = "Namespace" use = "required" type = "xsd:anyURI"/>

<xsd:attribute name = "ID" use = "required" type = "xsd:token"/>

<xsd:attribute name = "IsStandardObjectType" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

</xsd:element>

<xsd:complexType name = "TextType">

<xsd:attribute name = "Alias" use = "optional" type = "xsd:token"/>

<xsd:attribute name = "Default" use = "optional" type = "xsd:string"/>

</xsd:complexType>

<xsd:complexType name = "PropertiesType">

<xsd:sequence>

<xsd:element ref = "Property" maxOccurs = "unbounded"/>

</xsd:sequence>


120 July 26, 2004

</xsd:complexType>

<xsd:complexType name = "TemplatePropertiesType">

<xsd:sequence>

<xsd:element ref = "TemplateProperty" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name = "LinkListsType">

<xsd:sequence>

<xsd:element ref = "LinkList" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name = "FieldType">

<xsd:sequence>

<xsd:element ref = "Label"/>

<xsd:element ref = "DataTypeRef"/>

<xsd:element ref = "DefaultValues" minOccurs = "0"/>

<xsd:element ref = "FieldGroupRefs" minOccurs = "0"/>

</xsd:sequence>



<xsd:attribute name = "DisplayLines" use = "optional" type = "xsd:nonNegativeInteger"/>

<xsd:attribute name = "IsConstant" use = "required" type = "xsd:boolean"/>

<xsd:attribute name = "IsEntryRequired" use = "required" type = "xsd:boolean"/>

<xsd:attribute name = "HasMultipleValues" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

<xsd:complexType name = "NonStructuredElementsType">

<xsd:sequence>

<xsd:element ref = "PropertyLists" minOccurs = "0"/>

<xsd:element ref = "LinkLists" minOccurs = "0"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name = "DataTypeType">

<xsd:sequence>

<xsd:element ref = "AllowedValues" minOccurs = "0"/>

<xsd:element ref = "AllowedObjectTypeRefs" minOccurs = "0"/>

</xsd:sequence>


July 26, 2004 121

<xsd:attribute name = "Length" use = "optional" type = "xsd:nonNegativeInteger"/>

<xsd:attribute name = "Type" use = "required">

<xsd:simpleType>

<xsd:restriction base = "xsd:token">

<xsd:enumeration value = "string"/>

<xsd:enumeration value = "integer"/>

<xsd:enumeration value = "IDREF"/>

<xsd:enumeration value = "date"/>

<xsd:enumeration value = "boolean"/>

<xsd:enumeration value = "enumeration"/>

</xsd:restriction>

</xsd:simpleType>

</xsd:attribute>



</xsd:complexType>

<xsd:complexType name = "ReferenceType">

<xsd:attribute name = "Namespace" use = "optional" type = "xsd:anyURI"/>


</xsd:complexType>

<xsd:complexType name = "ValueType">

<xsd:complexContent>

<xsd:extension base = "TextType">

<xsd:attribute name = "Value" use = "optional" type = "xsd:token"/>

</xsd:extension>


</xsd:complexType>

<xsd:element name = "Name" type = "TextType"/>

<xsd:element name = "Property">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Fields"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Field" type = "FieldType"/>


122 July 26, 2004

<xsd:element name = "Properties" type = "PropertiesType"/>

<xsd:element name = "AllowedValues">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "AllowedValue" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "AllowedValue" type = "ValueType"/>

<xsd:element name = "DefaultValue" type = "ValueType"/>

<xsd:element name = "DataType" type = "DataTypeType"/>

<xsd:element name = "AllItems" type = "NonStructuredElementsType"/>

<xsd:element name = "ItemList">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Heading"/>

<xsd:element ref = "AllItems"/>

<xsd:element ref = "FieldInOverviewRefs"/>

<xsd:element ref = "DefaultItems" minOccurs = "0"/>

</xsd:sequence>

<xsd:attribute name = "IsNewItemAllowed" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

</xsd:element>

<xsd:element name = "LinkList">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Heading"/>

<xsd:element ref = "AllowedObjectTypeRefs"/>


</xsd:sequence>



</xsd:complexType>

</xsd:element>

<xsd:element name = "AllowedObjectTypeRef" type = "ReferenceType"/>

<xsd:element name = "AllowedObjectTypeRefs">


July 26, 2004 123

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "AllowedObjectTypeRef"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "LinkLists" type = "LinkListsType"/>

<xsd:element name = "Heading" type = "TextType"/>

<xsd:element name = "FieldGroup">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Name"/>

</xsd:sequence>



<xsd:attribute name = "IsForAuthorization" use = "required" type = "xsd:boolean"/>

<xsd:attribute name = "IsForStatus" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

</xsd:element>

<xsd:element name = "FieldGroupRef" type = "ReferenceType"/>

<xsd:element name = "FieldGroupRefs">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "FieldGroupRef" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "FieldGroups">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "FieldGroup" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>


124 July 26, 2004

<xsd:element name = "Icon">

<xsd:complexType>

<xsd:attribute name = "Href" use = "required" type = "xsd:anyURI"/>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Label" type = "TextType"/>

<xsd:element name = "Description" type = "TextType"/>

<xsd:element name = "TemplateLabel" type = "FieldType"/>

<xsd:element name = "TemplateProperty">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "TemplateLabel"/>


</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "TemplateProperties" type = "TemplatePropertiesType"/>

<xsd:element name = "DefaultItem">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Settings" minOccurs = "0"/>

<xsd:element ref = "AdditionalElements" minOccurs = "0"/>

</xsd:sequence>



<xsd:attribute name = "IsDeletable" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

</xsd:element>

<xsd:element name = "DefaultItems">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "DefaultItem" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Setting">


July 26, 2004 125

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "FieldOrLinkListRef"/>

<xsd:element ref = "DefaultValues" minOccurs = "0"/>


</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Settings">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Setting" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "DataTypes">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "DataType" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "DataTypeRef" type = "ReferenceType"/>

<xsd:element name = "FieldOrLinkListRef" type = "ReferenceType"/>

<xsd:element name = "PropertyList">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Heading" minOccurs = "0"/>

<xsd:element ref = "Properties" minOccurs = "0"/>

<xsd:element ref = "TemplateProperties" minOccurs = "0"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "PropertyLists">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "PropertyList" maxOccurs = "unbounded"/>


126 July 26, 2004

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "NonStructuredElements" type = "NonStructuredElementsType"/>

<xsd:element name = "AdditionalElements" type = "NonStructuredElementsType"/>

<xsd:element name = "DefaultValues">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "DefaultValue" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "FieldInOverviewRef" type = "ReferenceType"/>

<xsd:element name = "FieldInOverviewRefs">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "FieldInOverviewRef" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Fields">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Field" maxOccurs = "2"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "CategoryForRef" type = "ReferenceType"/>

<xsd:element name = "CategoryForRefs">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "CategoryForRef" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>


July 26, 2004 127

<xsd:element name = "StructuredElements">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "ItemList"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:schema>


128 July 26, 2004

7.11.4.2 Example XML Files If required, you can copy the example XML files and modify them according to your requirements.

• Document structure [Seite 129]: This is an example of a generic object type. It is a bill of material with items that refer to documents. If a multi-level document structure is required, then you can use the document category CAD document [Seite 132], which has a link to a document structure as an additional property.

• 8D Report [Seite 133]: This example of a generic object type shows how processes can be represented in generic objecty using field groups with status properties. To make use of these status properties and thereby the full scope of this generic object type, you must create a status profile for it in the cFolders system and protect exactly one field group in each status. In the status Interim Containment Action, for example, you would protect the field group Protect at interim containment action.


July 26, 2004 129

7.11.4.2.1 Example XML File for Document Structure (Gen. Object Type) <?xml version="1.0" encoding="iso-8859-1"?>

<GenericObjectType ID="DocumentStructure" Namespace="SAP"

IsStandardObjectType="true"

xmlns="http://www.sap.com/2002/abap/cfx_folders/customizing/GenericObjectType">

<Name Alias="" Default="Document Structure"/>

<Description Alias="" Default="A document structure structures documents and represents a directory of all parts (items) that belong to a document."/>

<Icon Href="s_b_slis.gif"/>

<DataTypes>

<DataType ID="String" Namespace="SAP" Type="string" />

<DataType ID="Integer10" Namespace="SAP" Type="integer" Length="10"/>

<DataType ID="Unit" Namespace="SAP" Type="enumeration" >

<AllowedValues>

<AllowedValue Alias="" Default="Pieces" Value="piece"/>

<AllowedValue Alias="" Default="Meter" Value="m"/>

<AllowedValue Alias="" Default="Centimeter" Value="cm"/>

</AllowedValues>

</DataType>

<DataType ID="Document" Namespace="SAP" Type="IDREF">

<AllowedObjectTypeRefs>

<AllowedObjectTypeRef ID="doc" />

</AllowedObjectTypeRefs>

</DataType>

</DataTypes>

<NonStructuredElements>

<PropertyLists>

<PropertyList>

<Heading Alias="" Default=""/>

<Properties>

<Property>

<Fields>

<Field ID="CAD_Format" Namespace="SAP" DisplayLines="1" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="CAD Format"/>

<DataTypeRef ID="String" Namespace="SAP"/>


130 July 26, 2004

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>

</NonStructuredElements>

<StructuredElements>

<ItemList IsNewItemAllowed="true">

<Heading Alias="" Default="Documents" />

<AllItems>

<PropertyLists>

<PropertyList>

<Heading Alias="" Default="" />

<Properties>

<Property>

<Fields>

<Field ID="Item" Namespace="SAP" DisplayLines="1" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">

<Label Alias="" Default="Item" />

<DataTypeRef ID="Integer10" Namespace="SAP" />

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Description" Namespace="SAP" DisplayLines="5" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Description" />

<DataTypeRef ID="String" Namespace="SAP" />

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Document_REF" Namespace="SAP" DisplayLines="1" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Dokument" />

<DataTypeRef ID="Document" Namespace="SAP" />


July 26, 2004 131

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Quantity" Namespace="SAP" DisplayLines="1" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Quantity" />

<DataTypeRef ID="Integer10" Namespace="SAP" />

</Field>

<Field ID="QuantityUnit" Namespace="SAP" DisplayLines="1" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Quantity Unit" />

<DataTypeRef ID="Unit" Namespace="SAP" />

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>

</AllItems>

<FieldInOverviewRefs>

<FieldInOverviewRef ID="Item" Namespace="SAP" />

<FieldInOverviewRef ID="Document_REF" Namespace="SAP" />

</FieldInOverviewRefs>

</ItemList>

</StructuredElements>

</GenericObjectType>


132 July 26, 2004

7.11.4.2.2 Example XML File for CAD Document (Document Category) <?xml version="1.0" encoding="iso-8859-1"?>

<GenericObjectType ID="CAD_Document" Namespace="SAP"



<CategoryForRefs>

<CategoryForRef ID="doc" />

</CategoryForRefs>

<Name Alias="" Default="CAD Document"/>

<Description Alias="" Default="A CAD document can be used in document structures."/>

<DataTypes>

<DataType ID="DocumentStructure" Namespace="SAP" Type="IDREF">


<AllowedObjectTypeRef ID="DocumentStructure" Namespace="SAP"/>


</DataType>

</DataTypes>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="DocumetStructureRef" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Document Structure"/>

<DataTypeRef ID="DocumentStructure" Namespace="SAP"/>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>




July 26, 2004 133

7.11.4.2.3 Example XML File for 8D Report (Generic Object Type) <?xml version="1.0" encoding="iso-8859-1"?>

<GenericObjectType ID="8D-Report_EN" Namespace="SAP"



<Name Alias="" Default="8D-Report"/>

<Description Alias="" Default="Form for resolving complex problems consisting of 8 steps ( = disciplines )"/>

<Icon Href="s_b_prnt.gif"/>

<FieldGroups>

<FieldGroup IsForAuthorization="true" IsForStatus="false" ID="Customer" Namespace="SAP">

<Name Alias="" Default="Customer"/>

</FieldGroup>

<FieldGroup IsForAuthorization="true" IsForStatus="false" ID="Supplier" Namespace="SAP">

<Name Alias="" Default="Supplier"/>

</FieldGroup>

<FieldGroup IsForAuthorization="false" IsForStatus="true" ID="ProtectCustomer" Namespace="SAP">

<Name Alias="" Default="Protect at customer input"/>

</FieldGroup>

<FieldGroup IsForAuthorization="false" IsForStatus="true" ID="ProtectInterimContainmentAction" Namespace="SAP">

<Name Alias="" Default="Protect at interim containment action"/>

</FieldGroup>

<FieldGroup IsForAuthorization="false" IsForStatus="true" ID="ProtectPermanentContainmentAction" Namespace="SAP">

<Name Alias="" Default="Protect at permanent containment action"/>

</FieldGroup>

<FieldGroup IsForAuthorization="false" IsForStatus="true" ID="ProtectPreventRecurrence" Namespace="SAP">

<Name Alias="" Default="Protect at prevent recurrence"/>

</FieldGroup>

<FieldGroup IsForAuthorization="false" IsForStatus="true" ID="ProtectCongratulateTeam" Namespace="SAP">

<Name Alias="" Default="Protect at congratulate team"/>

</FieldGroup>

</FieldGroups>


134 July 26, 2004

<DataTypes>

<DataType ID="String" Namespace="SAP" Type="string" />

<DataType ID="String10" Namespace="SAP" Type="string" Length="10"/>

<DataType ID="Integer1" Namespace="SAP" Type="integer" Length="1"/>

<DataType ID="Date" Namespace="SAP" Type="date" />

<DataType ID="ImplementationIn" Namespace="SAP" Type="enumeration" >

<AllowedValues>

<AllowedValue Alias="" Default="Product FMEA" Value="ProductFMEA"/>

<AllowedValue Alias="" Default="Process FMEA" Value="ProcessFMEA"/>

<AllowedValue Alias="" Default="Control Plan" Value="ControlPlan"/>

<AllowedValue Alias="" Default="Procedure" Value="Procedure"/>

</AllowedValues>

</DataType>

<DataType ID="User" Namespace="SAP" Type="IDREF" >


<AllowedObjectTypeRef ID="usr" />


</DataType>

<DataType ID="UserGroup" Namespace="SAP" Type="IDREF" >


<AllowedObjectTypeRef ID="usrgrp" />


</DataType>

<DataType ID="Documents" Namespace="SAP" Type="IDREF" >


<AllowedObjectTypeRef ID="doc" />


</DataType>

</DataTypes>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ConcernTitle" Namespace="SAP" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">


July 26, 2004 135

<Label Alias="" Default="Concern Title"/>


<DefaultValues>

<DefaultValue Alias="" Default="New Concern Title" />

</DefaultValues>

<FieldGroupRefs>

<FieldGroupRef ID="Customer" Namespace="SAP"/>

<FieldGroupRef ID="ProtectInterimContainmentAction" Namespace="SAP"/>

<FieldGroupRef ID="ProtectPermanentContainmentAction" Namespace="SAP"/>

<FieldGroupRef ID="ProtectPreventRecurrence" Namespace="SAP"/>

<FieldGroupRef ID="ProtectCongratulateTeam" Namespace="SAP"/>

</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Ref.No." Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Ref.No."/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="StartDate" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Start Date"/>

<DataTypeRef ID="Date" Namespace="SAP"/>


136 July 26, 2004

<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="StatusDate" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Status Date"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="PartName" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Part Name"/>


<FieldGroupRefs>





July 26, 2004 137



</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Part Number/Index" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Part Number/Index"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


<StructuredElements>

<ItemList IsNewItemAllowed="false">

<Heading Alias="" Default="Disciplines"/>

<AllItems>

<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="DisciplineNumber" Namespace="SAP" IsConstant="true" IsEntryRequired="false" HasMultipleValues="false">


138 July 26, 2004

<Label Alias="" Default="Discipline"/>

<DataTypeRef ID="Integer1" Namespace="SAP"/>

</Field>

<Field ID="DisciplineText" Namespace="SAP" IsConstant="true" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Discipline Text"/>


</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>

</AllItems>

<FieldInOverviewRefs>

<FieldInOverviewRef ID="DisciplineNumber" Namespace="SAP"/>

<FieldInOverviewRef ID="DisciplineText" Namespace="SAP"/>

</FieldInOverviewRefs>

<DefaultItems>

<DefaultItem ID="D1" Namespace="SAP" IsDeletable="false">

<Settings>

<Setting>

<FieldOrLinkListRef ID="DisciplineNumber" Namespace="SAP"/>

<DefaultValues>

<DefaultValue Alias="" Default="1" Value=""/>

</DefaultValues>

</Setting>

<Setting>

<FieldOrLinkListRef ID="DisciplineText" Namespace="SAP"/>

<DefaultValues>

<DefaultValue Alias="" Default="Establish a team" Value=""/>

</DefaultValues>

</Setting>

</Settings>

<AdditionalElements>

<PropertyLists>

<PropertyList>



July 26, 2004 139

<Properties>

<Property>

<Fields>

<Field ID="TeamLeader" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Team Leader"/>

<DataTypeRef ID="User" Namespace="SAP"/>

<FieldGroupRefs>

<FieldGroupRef ID="Supplier" Namespace="SAP"/>

<FieldGroupRef ID="ProtectCustomer" Namespace="SAP"/>


</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="TeamMembersGroups" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="true">

<Label Alias="" Default="Team"/>

<DataTypeRef ID="UserGroup" Namespace="SAP"/>

<FieldGroupRefs>




</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>

</AdditionalElements>

</DefaultItem>


<Settings>

<Setting>


140 July 26, 2004


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>

<DefaultValue Alias="" Default="Describe the problem" Value=""/>

</DefaultValues>

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ProblemDescription" Namespace="SAP" DisplayLines="3" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Problem Description"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>


July 26, 2004 141

<Field ID="ProblemProfileData" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Problem Profile Data"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>

<DefaultValue Alias="" Default="Develop Interim Containment Action" Value=""/>

</DefaultValues>

</Setting>

</Settings>



142 July 26, 2004

<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ContainmentAction" Namespace="SAP" IsConstant="false" IsEntryRequired="true" HasMultipleValues="true">

<Label Alias="" Default="Containment Action(s)"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Effect" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Effect"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>


July 26, 2004 143

</Fields>

</Property>

<Property>

<Fields>

<Field ID="ImplementationDate" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Implementation Date"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>

<DefaultValue Alias="" Default="Define and Verify Root Cause" Value=""/>

</DefaultValues>


144 July 26, 2004

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="RootCause" Namespace="SAP" DisplayLines="4" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">

<Label Alias="" Default="Root Cause(s)"/>


<FieldGroupRefs>





</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Contribution" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Contribution"/>


<FieldGroupRefs>





</FieldGroupRefs>

</Field>

</Fields>


July 26, 2004 145

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>

<DefaultValue Alias="" Default="Choose and Verify Permanent Corrective Action" Value=""/>

</DefaultValues>

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ChoosePermanentCorrectiveAction" Namespace="SAP" DisplayLines="3" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">

<Label Alias="" Default="Choose Permanent Corrective Action(s)"/>


<FieldGroupRefs>





146 July 26, 2004


</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Verification" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Verification"/>


<FieldGroupRefs>





</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>


July 26, 2004 147

<DefaultValue Alias="" Default="Implement and Validate Permanent Corrective Action" Value=""/>

</DefaultValues>

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ImplementedPermanentCorrectiveAction" Namespace="SAP" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">

<Label Alias="" Default="Implemented Permanent Corrective Action(s)"/>


<FieldGroupRefs>





</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Controls" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Controls"/>


<FieldGroupRefs>





148 July 26, 2004


</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="ImplementationDate_2" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">



<FieldGroupRefs>





</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>


July 26, 2004 149

<DefaultValue Alias="" Default="Prevent Recurrence" Value=""/>

</DefaultValues>

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


<Properties>

<Property>

<Fields>

<Field ID="ActionsToPreventRecurrence" Namespace="SAP" DisplayLines="4" IsConstant="false" IsEntryRequired="false" HasMultipleValues="true">

<Label Alias="" Default="Action(s) To Prevent Recurrence"/>

<DataTypeRef ID="ImplementationIn" Namespace="SAP"/>

<FieldGroupRefs>




</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Responsible" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Responsible"/>

<DataTypeRef ID="User" Namespace="SAP"/>

<FieldGroupRefs>




</FieldGroupRefs>

</Field>

</Fields>

</Property>


150 July 26, 2004

<Property>

<Fields>

<Field ID="ImplementationDate_3" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">



<FieldGroupRefs>




</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>


<Settings>

<Setting>


<DefaultValues>


</DefaultValues>

</Setting>

<Setting>


<DefaultValues>

<DefaultValue Alias="" Default="Recognize Team and Individual Contributions" Value=""/>

</DefaultValues>

</Setting>

</Settings>


<PropertyLists>

<PropertyList>


July 26, 2004 151


<Properties>

<Property>

<Fields>

<Field ID="CongratulateYourTeam" Namespace="SAP" IsConstant="false" IsEntryRequired="true" HasMultipleValues="false">

<Label Alias="" Default="Congratulate your Team"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="CloseDate" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Close Date"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>


152 July 26, 2004

<Property>

<Fields>

<Field ID="Rep.by" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Rep. by"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Rep.byTel" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Rep. by Tel.:"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

<Property>

<Fields>


July 26, 2004 153

<Field ID="Rep.byFax" Namespace="SAP" IsConstant="false" IsEntryRequired="false" HasMultipleValues="false">

<Label Alias="" Default="Rep. by Fax:"/>


<FieldGroupRefs>






</FieldGroupRefs>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>


</DefaultItem>

</DefaultItems>

</ItemList>

</StructuredElements>



154 July 26, 2004

7.11.5 Making WebDAV Settings for cFolders Integration with mySAP SRM Use cFolders determines the RFC connection you created through a settings file located in the WebDAV directory [Seite 99].

Furthermore, you can tailor the appearance of the cFolders Create Shopping Cart screen to your personal needs by defining the fields you want to appears on it.

You edit the settings for the integration with mySAP Supplier Relationship Management (SRM) in XML format, adhering to a predefined XSD description and store the SRM settings with all other cFolders system settings in the WebDAV directory.

Prerequisites You have set up a WebDAV client [Seite 99] for cFolders.

Procedure 1. Create the new folder SRM in the WebDAV settings folder.

2. Edit an XML file according to the schema, which can be found under XSD for Integration with mySAP SRM [Seite 158].

3. Name this file SRM.xml and insert it into the new subfolder SRM of your WebDAV settings folder.

Result cFolders is ready to use the integration with mySAP SRM.

See also: Detailed Information About the XSD Description [Seite 155]

Example XML File for Integration with mySAP SRM [Seite 162]


July 26, 2004 155

7.11.5.1 Detailed Information About the XSD Description The following provides you with additional information about the XSD description for the integration with mySAP Supplier Relationship Management (SRM) [Seite 158].

Information contained in the XSD itself, for example, which attributes are required, data types, and so on, is not repeated here. The name of the XSD is SRM_integration.xsd.

ID and Namespace This pair is used to uniquely identify objects. Ensure that each of these pairs is used only once within its validity space. The validity space of the SRMType node is a cFolders client. The validity space for all other nodes is the SRM type definition in which they are defined.

The example provided by SAP has an empty string or ‘SAP’ for the namespace. For your namespace, choose “www.<your_company>.com/<your_department>/<your group>” for example. Make sure that you are the only one using this namespace.

The ID and the namespace can have a maximum of 255 characters each. This restriction applies to all other strings.

TextType (Alias, Default) Elements that contain texts displayed on the user interface have this type. If you do not need language-dependent texts, you must use the “default” attribute and leave out the “alias” attribute, for example, “default=’worker’ ”. If you need language-dependent texts, you must create an alias for each text in the cFolders text management system and use the alias in the “alias” attribute. For example, “alias=’CFX_UI/STUDENT’”. In this case, you leave out the “default” attribute. If you use both attributes, (alias and default), system behavior is not defined. For more information about the cFolders text management system, see Changing cFolders Standard Settings Using WebDAV [Seite 99].

Individual Elements of the SRMType.xsd • SRMType: Top Node

� Attributes:

� Namespace, ID: Uniquely identifies the SRM type.

� RFCDestination: Logical name of the RFC destination to the SRM system.

� cFoldersDestination: Logical name of the RFC destination to the cFolders system. This destination is maintained in the SRM system.

� Nodes:

� DataTypes: Lists with data types.

� PropertyLists: Lists of property lists.

• DataType: Data type

� Attributes:

� Namespace, ID: Uniquely identifies the data type.


156 July 26, 2004

� Type: Data type. The options and the internal format for storing the data in cFolders is as follows:

• string: Any character string (text)

• integer: Number without decimal places (also negative). The range is –2^31 to 2^31 – 1.

• date: Date. The internal format is‘YYYYMMDD’, where YYYY is the year, MM, the month and DD the day.

• boolean: Only ‘true’ or ‘false’.

• enumeration: Selection list. The options must be maintained for “AllowedValues” (see below). The internal format is the value of the ‘Value’ attribute of the ‘AllowedValue’ node.

� Length: Only for “type” = “string” or “integer”: Maximum length (number of characters).

� Nodes:

� AllowedValues: Only for “Type” = “enumeration”. Selection list.

• PropertyList: List of properties that are displayed one below the other on the interface.

� Nodes:

� Heading: Title. It is displayed on the user interface above the properties.

� Properties: Properties with a predefined name that are common to all objects of this type. See also “Property”.

• Property: Property that is displayed on the user interface as one or more fields next to each other, with a name to the left of the field or fields. For example: Name with a string – field or weight with a string (number) field for the value and an enumeration – field for unit.

� Nodes:

� Fields: List with (entry) fields.

• Fields: (Entry) fields. Can contain one or two ‘Field’ nodes.

� Nodes:

� Field: (Entry) field.

• Field: (Entry) field.

� Attributes:

� Namespace, ID: Uniquely identifies the field.

� DisplayLines: Only for strings and enumerations. The default is one. If you specify a larger value, a multi-line entry field can be generated for strings and a selection box instead of a dropdown list can be generated for enumerations.

� IsConstant: The value is the same for all objects of this type, cannot be changed, and is defined in this XML file.

� IsEntryRequired: Required field? If so, the field must have a value.

� Nodes:


July 26, 2004 157

� Label: The label of the first field of a property is displayed to the left of the property’s fields. The labels of the other fields are read out if the accessibility function is activated.

� DataTypeRef: Link to one of the data types specified above.

� ABAPField: DataType and Label will be taken from the ABAP dictionary field used as a reference. Use either DataTypeRef or ABAPField. If you use both Label and ABAPField, Label values will be displayed. The following references to ABAP dictionary fields will be used to fill the parameters of the function module ‘BBP_BC_EXTREQ_INB’ that creates a shopping cart in the SRM system. Note that these structures are not active in a cFolders system. Refer to an SRM system using the RFCDestination attribute.

• BBPS_EXTREQ_HEADER: Any fields referring to this structure will fill in the importing structure I_HEADER.

• BBPS_EXTREQ_ITEM: Any fields referring to this structure will fill in the first line of the table I_ITEMS.

• BAPI_ACC_C: Any fields referring to this structure will fill in the first line of the table I_ACC.

• BAPI_BUP_C: Any fields referring to this structure will fill in the first line of the table I_BUP.

• Any other reference will add lines to the table I_TEXTS.

� DefaultValue: When the object is created, the field contains this default value.

• ABAPField: Reference to a field in an ABAP dictionary table or structure. You can only refer to fields with internal type string C, I, or D.

� Attributes:

� TableName: Name of the table or structure referred to.

� FieldName: Name of the field referred to in <TableName>.

� RFCDestination: Logical name of the RFC destination to the system where this dictionary field exists.

� Nodes

� AllowedValues: Selection list.

• AllowedValue: Option for enumeration.

� Attributes:

� Alias, Default: The text displayed to the user.

� Value: Key of the option. It is used and saved internally and will be transferred. Must be specified. If used in an ABAPField, it must be valid for corresponding dictionary field.


158 July 26, 2004

7.11.5.2 XSD for the Integration with mySAP SRM Definition <?xml version = "1.0" encoding = "UTF-8"?>

<xsd:schema xmlns = "http://www.sap.com/2003/abap/cfx_integration/customizing/SRMType"

targetNamespace = "http://www.sap.com/2003/abap/cfx_integration/customizing/SRMType"

xmlns:xsd = "http://www.w3.org/2001/XMLSchema"

version = "">

<xsd:element name = "SRMType">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "DataTypes" minOccurs = "0"/>

<xsd:element ref = "PropertyLists"/>

</xsd:sequence>



<xsd:attribute name = "RFCDestination" use = "optional" type = "xsd:string"/>

<xsd:attribute name = "cFoldersDestination" use = "optional" type = "xsd:string"/>

</xsd:complexType>

</xsd:element>

<xsd:complexType name = "TextType">

<xsd:attribute name = "Alias" use = "optional" type = "xsd:token"/>

<xsd:attribute name = "Default" use = "optional" type = "xsd:string"/>

</xsd:complexType>

<xsd:complexType name = "PropertiesType">

<xsd:sequence>

<xsd:element ref = "Property" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name = "FieldType">

<xsd:sequence>

<xsd:element ref = "Label" minOccurs = "0"/>

<xsd:element ref = "DataTypeRef" minOccurs = "0"/>


July 26, 2004 159

<xsd:element ref = "ABAPField" minOccurs = "0"/>

<xsd:element ref = "DefaultValue"/>

</xsd:sequence>



<xsd:attribute name = "DisplayLines" use = "optional" type = "xsd:nonNegativeInteger"/>

<xsd:attribute name = "IsConstant" use = "required" type = "xsd:boolean"/>

<xsd:attribute name = "IsEntryRequired" use = "required" type = "xsd:boolean"/>

</xsd:complexType>

<xsd:complexType name = "DataTypeType">

<xsd:sequence>


</xsd:sequence>



<xsd:attribute name = "Length" use = "optional" type = "xsd:nonNegativeInteger"/>

<xsd:attribute name = "Type" use = "required">

<xsd:simpleType>

<xsd:restriction base = "xsd:token">

<xsd:enumeration value = "string"/>

<xsd:enumeration value = "integer"/>

<xsd:enumeration value = "IDREF"/>

<xsd:enumeration value = "date"/>

<xsd:enumeration value = "boolean"/>

<xsd:enumeration value = "enumeration"/>

</xsd:restriction>

</xsd:simpleType>

</xsd:attribute>

</xsd:complexType>

<xsd:complexType name = "ReferenceType">


<xsd:attribute name = "Namespace" use = "optional" type = "xsd:anyURI"/>

</xsd:complexType>

<xsd:complexType name = "ValueType">

<xsd:complexContent>

<xsd:extension base = "TextType">


160 July 26, 2004

<xsd:attribute name = "Value" use = "optional" type = "xsd:token"/>

</xsd:extension>


</xsd:complexType>

<xsd:element name = "Name" type = "TextType"/>

<xsd:element name = "Property">

<xsd:complexType>

<xsd:sequence>


</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Field" type = "FieldType"/>

<xsd:element name = "Properties" type = "PropertiesType"/>

<xsd:element name = "AllowedValues">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "AllowedValue" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "AllowedValue" type = "ValueType"/>

<xsd:element name = "DefaultValue" type = "ValueType"/>

<xsd:element name = "DataType" type = "DataTypeType"/>

<xsd:element name = "Heading" type = "TextType"/>

<xsd:element name = "Label" type = "TextType"/>

<xsd:element name = "Description" type = "TextType"/>

<xsd:element name = "DataTypes">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "DataType" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "DataTypeRef" type = "ReferenceType"/>

<xsd:element name = "PropertyList">


July 26, 2004 161

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Heading" minOccurs = "0"/>

<xsd:element ref = "Properties" minOccurs = "0"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "PropertyLists">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "PropertyList" maxOccurs = "unbounded"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "Fields">

<xsd:complexType>

<xsd:sequence>

<xsd:element ref = "Field" maxOccurs = "2"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name = "ABAPField">

<xsd:complexType>

<xsd:sequence>


</xsd:sequence>

<xsd:attribute name = "TableName" use = "required" type = "xsd:string"/>

<xsd:attribute name = "FieldName" use = "required" type = "xsd:string"/>

<xsd:attribute name = "RFCDestination" use = "optional" type = "xsd:string"/>

</xsd:complexType>

</xsd:element>

</xsd:schema>


162 July 26, 2004

7.11.5.3 Example XML File for the Integration with mySAP SRM SAP recommends that you use the current example XML file as a template. You only need to change the RFC destination attributes. This example XML file provides all fields that are necessary for ordering a shopping cart (except for the category ID, which is taken from the user settings). You can add further fields according to your needs.

<?xml version="1.0" encoding="UTF-8"?>

<SRMType ID="SRM" Namespace="" RFCDestination="Q4CCLNT300" cFoldersDestination="TPLCLNT100"

xmlns="http://www.sap.com/2003/abap/cfx_integration/customizing/SRMType">

<DataTypes>

<DataType ID="string" Namespace="" Type="string" Length=""/>

</DataTypes>

<PropertyLists>

<PropertyList>

<Heading Alias="CFX_UI/SRM_HEADER_DATA" Default=""/>

<Properties>

<Property>

<Fields>

<Field ID="Name" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="false" >

<Label Alias="" Default=""/>

<DataTypeRef ID="" Namespace=""/>

<ABAPField TableName="BBPS_EXTREQ_HEADER" FieldName="DESCRIPTION" RFCDestination="Q4CCLNT300"/>

<DefaultValue Value="">

</DefaultValue>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="PostingDate" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" Visibility="">



<ABAPField TableName="BBPS_EXTREQ_HEADER" FieldName="POSTING_DATE" RFCDestination="Q4CCLNT300"/>


July 26, 2004 163

<DefaultValue Value="">

</DefaultValue>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

<PropertyList>

<Heading Alias="CFX_UI/SRM_ITEM_DATA" Default=""/>

<Properties>

<Property>

<Fields>

<Field ID="Itemdesc" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" Visibility="" >



<ABAPField TableName="BBPS_EXTREQ_ITEM" FieldName="DESCRIPTION" RFCDestination="Q4CCLNT300"/>

<DefaultValue>

</DefaultValue>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="Itemdate" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true" >



<ABAPField TableName="BBPS_EXTREQ_ITEM" FieldName="DELIV_DATE" RFCDestination="Q4CCLNT300"/>

<DefaultValue>

</DefaultValue>

</Field>

</Fields>

</Property>

<Property>

<Fields>


164 July 26, 2004

<Field ID="CostCenter" Namespace="" DisplayLines="" IsConstant="false" IsEntryRequired="true">



<ABAPField TableName="BAPI_ACC_C" FieldName="COST_CTR" RFCDestination="Q4CCLNT300"/>

<DefaultValue>

</DefaultValue>

</Field>

</Fields>

</Property>

<Property>

<Fields>

<Field ID="InternalNote" Nameslpace="" DisplayLines="3" IsConstant="false" IsEntryRequired="false" Visibility="internal">

<Label Alias="CFX_UI/SRM_INT_NOTE" Default=""/>

<DataTypeRef ID="string" Namespace=""/>

<DefaultValue>

</DefaultValue>

</Field>

</Fields>

</Property>

</Properties>

</PropertyList>

</PropertyLists>

</SRMType>


July 26, 2004 165

7.12 Installing the ECL Viewer Use The ECL Viewer is a tool that allows you to use redlining functions. The viewer must be installed locally and separately for each user on their front-end system. You can download the ECL Viewer installation files (ECLViewer_4_0_3.zip) from the SAP Service Marketplace.

Prerequisites The user performing the installation must have administration privileges on the front-end system. Make sure all other applications are closed before installing the ECL Viewer.

For general information about the ECL Viewer installation refer to SAP note 584372. For specific information about using the ECL Viewer with cFolders, refer to SAP note 584394.

Procedure ...

1. On the SAP Service Marketplace go to: service.sap.com/plm →→→→ Life-Cycle Data Management → Integration → Visualization of Product Knowledge → Media Center.

2. Download the ECLViewer_4_0_3.zip file to your local hard drive.

3. Run the setup.exe file from the zip file to start the installation.

4. Restart your system once the installation has finished.

5. Carry out the settings for using the ECL Viewer with cFolders, as described in SAP note 584394.

Note that cFolders uses two applets: the redlining applet described here and the check-in/check-out applet called “plug-in”. Make sure that both applets work correctly on the local front-end environment.

Troubleshooting Hints To make sure your ECL Viewer installation was successful, check the Java class path settings after you have restarted your system. ...

1. Open a DOS dialog box (command prompt).

2. Enter SET CLASSPATH.

Your class path settings are displayed.

3. Make sure the following two JAR files are included: eaisupport.jar and VisWeb.jar.

4. If these entries are missing, find the JAR files on your disk (most likely under "C:\Program Files\EAI\ComDll\Jars\").

5. Add these settings to your system (Start → Settings → Control Panel → System → Environment).

6. Close the DOS dialog box and repeat steps 1 - 3.


166 July 26, 2004

7.13 Importing External Class Systems for Data Sheets Using the functions for datasheets in cFolders, you can create specifications consisting of classes and subordinate characteristics. If you want to use predefined classes and characteristics in external class systems, you can import such external class systems for use. For the import procedure, your external class system needs to be converted to the XML schema of the cFolders datasheet.

For more information about the import procedure, contact your consultant for mySAP Product Lifecycle Management.