plm512 en col62 fv part a4

5/21/2018 Plm512 en Col62 Fv Part a4

1/207

PLM512cFolders

mySAP Product Lifecycle Management

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2006 Q2Course Duration: 2 Day(s)

Material Number: 50080618

An SAP course - use it to learn, reference it for work


2/207

Copyright

Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout 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.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are

registered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX,

S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.

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

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks

of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World

Wide Web Consortium, Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com

are trademarks or registered trademarks of SAP AG in Germany and in several other countries

all over the world. All other products mentioned are trademarks or registered trademarks of

their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY

DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING

WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,

INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,

INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY

KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST

PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED

SOFTWARE COMPONENTS.


3/207

About This Handbook

This handbook is intended to complement the instructor-led presentation of this

course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following

typographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. These

include field names, screen titles, pushbuttons as well

as menu names, paths, and options.

Also used for cross-references to other documentation

both internal (in this documentation) and external (in

other locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles of

graphics, and tables

EXAMPLE TEXT Names of elements in the system. These include

report names, program names, transaction codes, tablenames, and individual key words of a programming

language, when surrounded by body text, for example

SELECT and INCLUDE.

Example text Screen output. This includes file and directory names

and their paths, messages, names of variables and

parameters, and passages of the source text of a

program.

Example text Exact user entry. These are words and characters that

you enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that you

replace these words and characters with appropriate

entries.

2006/Q2 2006 SAP AG. All rights reserved. iii


4/207

About This Handbook PLM512

Icons in Body Text

The following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor's

presentation.

iv 2006 SAP AG. All rights reserved. 2006/Q2


5/207

Contents

Course Overview ....... ....... ....... ....... ....... ...... ....... ....... .. vii

Course Goals ....... ........ ........ ........ ........ ....... ........ .....vii

Course Objectives ... .... ... .... .... .... .... .... .... ... .... ... .... .... .vii

Unit 1: Introduction to cFolders .. .. .. ... .. .. ... .. .. .. ... .. .. ... .. .. ... . 1

Introduction to cFolders ... .... .... .... .... .... .... ... .... .... .... .... ..2

System Settings.......................................................11

Unit 2: cFolders Scenarios ... ... .... ... .... ... .... ... .... ... .... ... ... 23Collaborative Scenarios..............................................24

Competitive Scenarios ...............................................32

Standard Scenarios...... ... .... .... .... .... .... .... ... .... .... .... ...42

Unit 3: Master Data ...................................................... 49

Material Masters ......................................................50

Bills of Material .... .... .... .... ... .... ... .... .... .... ... .... .... .... ...62

Unit 4: Document Management.......................................85

Documents.............................................................86

Unit 5: Other Objects................................................... 105

Structured Objects .... .... .... ... .... ... .... .... .... ... .... .... .... ..106Generic Objects......................................................125

Object Search ........................................................128

Unit 6: Back-End Integration ... .... ... .... ... .... ... .... ... .... ... ... 137

Back-End Integration .... ... .... .... .... .... .... .... ... .... ... .... ... 138

Data Transfer with the Back-End System.........................145

Unit 7: Administration ...... ... ... .... ... .... ... .... ... .... ... .... ... .. 155

Authorizations . .. . . . .. . . .. . . . .. . . . .. . .. . . . .. . . . . .. .. . . . . .. . . .. . . .. . . . .156

Status Profiles........................................................168

Unit 8: Integration....................................................... 177

Integration Scenarios.. ... .... .... .... ... .... ... .... ... .... ... .... ... 178

2006/Q2 2006 SAP AG. All rights reserved. v


6/207

Contents PLM512

Appendix 1: Appendix cFolders .... ... .... ... ... .... ... .... ... ... 193

Index ....................................................................... 197

vi 2006 SAP AG. All rights reserved. 2006/Q2


7/207

Course Overview

This course provides an overview of Collaboration Folders (cFolders). The main

focus of the course is on the use of cFolders. Some system settings, however,

are also explained.

Target Audience

This course is intended for the following audiences:

Project managers

Project team

Consultants

Decision makers

Course Prerequisites

Required Knowledge

Basic knowledge of master data management

Recommended Knowledge

PLM100 Overview of SAP Life-Cycle Data Management

Course Goals

This course will prepare you to:

Structure and use cFolders for product development projects that involve

external development partners or suppliers

Use cFolders in various collaborative and competitive scenarios

Course Objectives

After completing this course, you will be able to:

Describe the basic and advanced functions of cFolders

Prepare and use cFolders

Create collaborative and competitive scenarios

Define objects in the cFolders scenarios

Complete the back-end integration of an SAP ERP system

Create users, authorizations, and status profiles in the cFolders scenarios

Set up the integration to an SAP CAD desktop and to SAP iPPE

2006/Q2 2006 SAP AG. All rights reserved. vii


8/207

Course Overview PLM512

SAP Software Component Information

The information in this course pertains to the following SAP Software Componentsand releases:

viii 2006 SAP AG. All rights reserved. 2006/Q2


9/207

Unit 1Introduction to cFolders

Unit Overview

This unit provides an overview of the cProject Suite and its components.

Unit Objectives

After completing this unit, you will be able to:

Describe the basic concept of the cProject Suite

List the components of cFolders

Provide an overview of all the settings required for SAP Application Server

Make the user settings in the cFolders scenario

List the system requirements

Unit ContentsLesson: Introduction to cFolders.. .. ... ... .. ... .. ... ... .. ... .. ... .. ... .. ... ... .. .2

Lesson: System Settings ... .... .... .... ... .... ... .... .... .... ... .... .... .... ... 11Exercise 1: System Settings .. .. ... ... .. ... .. ... ... .. ... .. .. ... ... .. ... .. ..15

2006/Q2 2006 SAP AG. All rights reserved. 1


10/207

Unit 1: Introduction to cFolders PLM512

Lesson: Introduction to cFolders

Lesson Overview

This lesson provides an overview of SAP cProject Suite and various collaboration

scenarios within a business.

Lesson Objectives

After completing this lesson, you will be able to:



Business Example

The Precision Petrol Company consists of a number of independent business areas

across various locations worldwide. The engineering department is one business

area for which you are responsible and that functions independently of the other

engineering departments.

The engineering department currently processes a large amount of data; this data

is primarily SAP master data and external files. You use e-mail or fax to exchange

this data with external development partners who are involved at various stages of

product development.

You are now looking for an alternative scenario with which you can communicateusing an Internet platform, for example. You therefore want to evaluate SAP

cProject Suite.

Collaboration

Collaboration Collaboration is the backbone of teamwork: whether a project

team trying to coordinate employee activities at different locations, or an OEM

(original equipment manufacturer) aiming to accelerate and improve product

development in cooperation with partners in the supply chain. Seamless

collaboration between teams is essential for businesses, particularly in the area of

product development. Successful collaboration therefore requires an environment

in which information can be exchanged easily.

2 2006 SAP AG. All rights reserved. 2006/Q2


11/207

PLM512 Lesson: Introduction to cFolders

Figure 1: Collaboration with All Relevant Parties

Conversations in passing or regular meetings that were once adequate for

exchanging information no longer provide a sufficient environment for

information exchange. Teams are often distributed across various locations or

consist of resources from various internal or external partners. Furthermore,

information is more comprehensive than before: it can range from anything such

as simple memos right up to complex drawings. The range of communication

channels available has increased; current technologies include e-mail, telephone,

Web-based meetings, and so on. However, what we are still lacking is one central

environment that merges and provides these requirements.

cProject suite

To meet the high demands that complex development and consulting projects

place on a business, we require planning solutions that support progressive project

management methods and therefore have a positive impact on project duration

and quality. Also important are tools that are easy to use and implement and that

enable project participants to work together.



12/207


Figure 2: cProject Suite

SAP cProject Suite supports you in project management and collaborative

engineering by enabling you to exchange information such as project plans,

documents, and product structures between virtual project teams across the Web.

SAP cProject Suite consists of two components:

Collaboration Projects (cProjects)

Design Collaboration with cFolders (cFolders)SAP cProject Suite provides the environment required for successful cooperation

between teams today.

cFolders is a component of SAP cProject Suite and can be used either with

cProjects or as an independent application. Integration scenarios exist for both

applications. In cProjects, you can create collaborations for project definition,

phases, checklists, checklist items, and tasks. In cProjects 3.1 and higher, you

can use a template to create a collaboration in cFolders. Alternatively, you can

use an existing collaboration. Both scenarios (collaborative and competitive)

are supported.

cFolders is the Web-based SAP PLM collaboration platform that enables thoseinvolved in design and development projects to work in virtual teams, even across

company boundaries.



13/207


cProjects

Figure 3: cProjects

cProjects spans the whole range of project management activities, from planning

and execution to the final stages of the project. cProjects integrates cFolders for

exchanging documents with external partners.

Introduction to cFolders

Figure 4: Global Product Development



14/207


You are working with multiple suppliers and development partners. Until now,

all required data was exchanged by e-mail. You are looking for a method of

exchanging the required data by Internet. The data must be available on a secureserver from where you want to be able to retrieve and edit it.

You choose the cFolders solution from SAP and define a collaborative and a

competitive scenario.

Figure 5: Global Product Development with cFolders

cFolders

cFolders is the Web-based collaboration platform for the PLM area. The

application enables teams that work in product development in cross-enterprise

scenarios to communicate and cooperate with each other. cFolders enables

teams to exchange structured information as bills of material, data sheets, or

customer-defined structures, for example. This approach improves the consistency

of your data when communicating with external partners and suppliers, which in

turn reduces project duration.

Replaces classic communication using e-mail, telephone, fax, and employee

meetings Reduces misunderstandings and communication shortfalls and improves the

consistency of reliable data

Replaces unstructured communication with structured data (with redlining,

markups, data sheets, and secure storage areas)

Improves synchronous communication



15/207


Figure 6: cFolders: Functions

The cFolders solution is characterized by a hierarchy structure in the collaborative

and competitive area. This applies to folders, documents, material masters, bills

of material, data sheets, and other objects that can be included in the cFolders

scenarios.

If required, you can also implement the integrated Engineering Client Viewer(ECL viewer) for displaying, assessing, or redlining files.

The cFolders solution can be used in the area of SRM and PLM. If required, you

can also integrate a WebEx meeting.

You can search within individual objects in the cFolders scenario. Local and

global search options are provided to support this.

If required, you can also incorporate a TREX search engine for finding files.

If large external files are used in the cFolders scenario, you can also use an

external FTP server. This server enables you to exchange data faster.



16/207


Figure 7: cFolders Objects

The following objects can be used in a cFolders scenario:

Folder: Folders are used to structure a collaboration; they are the containers

in which objects are saved.

Document: Documents are SAP objects for any files. Storing multiple

versions of a document allows you to track changes.

Bookmark: Bookmarks are quick links to pages on the Internet, documents,or other collaborations.

Material: A material is an object (such as product or goods) that is produced,

used, traded, or consumed.

Bill of Material: A bill of material (BOM) structures materials and provides

an index for all the parts of a material.

Data Sheet: A data sheet structures specifications and classifies information.

Discussion: A discussion is a communication forum for a collaboration, a

folder, or an object. Once posted, entries cannot be deleted.

Note: Using notes, you can create descriptive texts of any length. Notescan have different versions.

iPPE Node: Technical basic component of iPPE that builds structures.

There are different types of nodes; each represent the various applications

and functions of the iPPE.

iPPE Variant: Possible types for an iPPE node

Manufacturer Part Number: Value under which a material is listed by

the manufacturer or supplier



17/207


You can apply an authorization concept to each object. You can define

authorizations for your employees either at folder level or at object level within

the folder.

You can also use generic objects to define additional SAP objects in the cFolders

application.



18/207


Lesson Summary

You should now be able to: Describe the basic concept of the cProject Suite


Related Information

For more information, see SAP Service Marketplace atservice.sap.com.

http://-/?-http://-/?-


19/207

PLM512 Lesson: System Settings

Lesson: System Settings

Lesson Overview

This lesson provides an overview of the required system settings for the cFolders

solution. You learn about the user-specific settings in the cFolders scenario and

the assigned SAP Application Server (SAP AS).

Lesson Objectives





Business Example

The cFolders scenario is an Internet-based scenario for SAP AS. You therefore

need to check the required settings in SAP AS and within the cFolders application

before you define the first scenario.

SAP Application Server Settings

In most cases, the cFolders solution is installed on an external system outside the

company firewall. This means that a cFolders user cannot access the productivesystem. The cFolders solution is installed on an SAP AS as part of SAP cProject

Suite. This requires SAP Web Application Server (SAP Web AS) 4.70 or higher.



20/207


Figure 8: Back-End Integration

In most cases, the cFolders system is installed on an external system outside the

company firewall. This means that a cFolders user cannot access the productive

system. External users can access the cFolders system by using the HTTPS

protocol. This is where external users find the data provided. This contains only

a selection of the data that is present in the SAP back-end system. From the

material master, for example, you can make only selected basic data available.

All other data, such as materials planning or costing, is not available to external

users. Internal users also access the data in the cFolders system by using HTTPS.

However, internal users may have the option of transferring data from the

back-end system to the cFolders system and back.

You install SAP cProject Suite on the SAP AS. In addition, you require the

following settings:

Standard Roles for cFolders

User: SAP_CFX_USER

Administrator: SAP_CFX_ADMINISTRATOR E-mail user: SAP_CFX_EMAIL_SYSTEM_USER

Additional roles for detailed tasks

Users of the cFolders solution can be given a user in the SAP AS and be assigned

the relevant roles. You can use the standard roles from SAP as a copy template

and copy it to your namespace and adjust as required. In addition to the three main

roles, there are further roles, for example, for creating or changing collaborative or

competitive scenarios.



21/207


Alternatively, you can create users within the cFolders application and then assign

them the relevant roles.

Establishing System Connections

HTTP server

BSP application or cFolders URL

Settings for e-mail connection in the SAP AS

Definition of content server

URL settings for World Wide Web Distributed Authoring and Versioning

(WebDAV) access

The SAP system on which you installed SAP cProject Suite needs to be

configured. This includes the required settings for Internet communication such asthe Internet Communication Manager or Internet services.

In addition, you can permit access either using a Business Server Page (BSP)

application or by directly specifying an Internet address. However, this depends

from which system, back end, or cFolders application server you are accessing

the application.

Within the cFolders application, you can send messages by e-mail. However, this

is only possible if SAPconnect was specified in the SAP AS. To do this, you

can use an SMTP server, for example.

As of Release 4.6, in the SAP system, you can use a content server that is

connected to the Knowledge Provider (KPro) in the SAP system. In Customizingfor the KPro, the content server must be defined and the cFolders application

must be assigned.

If you want to transfer the master data from a back-end system, you can use

WebDAV to specify which fields you want to use in the cFolders application.

WebDAV access must be specified in the SAP AS using HTTP services.

The following settings are possible:

WebDAV Settings

Attributes: fields, mandatory entries for material masters or bills of material

GenericObjects: document structures, functional locations

Languages

ObjectCategories: CAD structure

SystemSettings: ECL viewer, network settings

SystemSettingsUser: standard user

UserSettings: user settings



22/207


cFolders Settings

Within the cFolders application, you can define your own settings to personalize

the application. In addition to the general settings, this also includes definitions for

meetings or role assignment, if these were not already defined in the SAP Web AS.

General Settings

Used scenarios: collaborative, competitive, or standard scenario

Special functions: plug-ins or thumbnails

Display: Display icons and logos

Meetings using WebEx

Receive notifications as e-mail

Role assignment

If you want to involve your suppliers or development partners in the development

of a new product, for example, you can hold Internet meetings using WebEx.

If you want to distribute new information to your suppliers or development

partners, you can specify whether you want to receive message by e-mail,

assuming SAPconnect has been set up accordingly.

Administrator

An administrator has the most entries within the cFolders scenario. This enables

the administrator to make the required network or cFolders settings or to manage

users.

Administrator's Tasks

Specifying scenarios: collaborative/competitive

Object types: master material, bills of material, iPPE objects, and so on

Scenario layout

Settings for meetings and e-mail

User administration



23/207


Exercise 1: System Settings

Exercise Objectives

After completing this exercise, you will be able to:

Check the SAP back-end settings

Check the cFolders settings

Business Example

You are responsible for making the basic settings for cFolders. SAP cProject Suite

has been installed; the first thing you want to do is check your user.

Caution: All exercise objects are indicated with ##. Replace this with

your group number:

## = Group number = 01 30

Task:

You need to check the initial data in the SAP back-end system and in the cFolders

system.

1. First check your user. As your user, use:

PLM512-##

2. Check theRolestab page. All cFolders roles that exist are listed. All roles

begin with the prefix:

SAP_CFX*

3. You now want to start the cFolders application. To do this, navigate to and

choose the required option in the user menu.

Microsoft Internet Explorer is started.

Log on using your SAP user:

User PLM512-##

Password Your SAP password

4. Check your settings: Display each of the tab pages.

Continued on next page



24/207


Tab Page: General

Language German or English

Scenarios Collaborative and Competitive Scenarios

Standards Selected

Homepage As required

Thumbnails Display

Save the data.

Tab Page: Layout

Experienced User Select indicator

Display Icons Select indicator

Save the data.

Tab Page: Notifications

Receive Notification as E-Mail Never

Save the data.

Check the remaining settings.

5. Check the settings for cFolders administration. Keep the default settings.

6. Check the settings for network administration. Keep the default settings.

7. Optional: Generate the relevant URL in the ABAP Workbench.

Start the ABAP Workbench. Use the Repository Browser and as the object

use:

BSP Application CFX_RFC_UI

Display the data.

Open thePages with Flow Logic folder.

Using the secondary mouse button, select default.htmand chooseTest.

Log on to the cFolders scenario again.



25/207


Solution 1: System Settings

Task:

You need to check the initial data in the SAP back-end system and in the cFolders

system.

1. First check your user. As your user, use:

PLM512-##

a) To do this, start transaction SU01. Change your user.

2. Check theRolestab page. All cFolders roles that exist are listed. All roles

begin with the prefix:

SAP_CFX*

a) Choose the relevant tab page.

b) On this tab page, you can enter each of the roles individually or use the

F4 help to select the relevant roles.

SAP_CFX_ADMINISTRATOR

SAP_CFX_CFOLDERS_ADMINISTRATOR

SAP_CFX_COL_CREATOR

SAP_CFX_COL_DELETOR

SAP_CFX_COMP_CREATOR

SAP_CFX_COMP_DELETOR

SAP_CFX_EMAIL_SYSTEM_USER

SAP_CFX_NETWORK_ADMINISTRATOR

SAP_CFX_STATUS_PRF_CREATOR

SAP_CFX_STATUS_PRF_DELETOR

SAP_CFX_STD_CREATOR

SAP_CFX_STD_DELETOR

SAP_CFX_SUPER_USER_ADMIN

SAP_CFX_USER

SAP_CFX_USER_ADMINISTRATOR

SAP_CFX_USRGRP_CREATOR

SAP_CFX_USRGRP_DELETOR

3. You now want to start the cFolders application. To do this, navigate to and

choose the required option in the user menu.

Microsoft Internet Explorer is started.

Log on using your SAP user:




26/207


User PLM512-##

Password Your SAP password

a) Proceed as described in the exercise.

Use the following menu path:

User menuEnvironment! Collaboration! cFolders! cFolders

Scenario

4. Check your settings: Display each of the tab pages.

Tab Page: General

Language German or English

Scenarios Collaborative and Competitive Scenarios

Standards Selected

Homepage As required

Thumbnails Display

Save the data.

Tab Page: Layout

Experienced User Select indicator

Display Icons Select indicator

Save the data.

Tab Page: Notifications

Receive Notification as E-Mail Never

Save the data.

Check the remaining settings.

a) Proceed as described in the exercise by choosingSettingsin the header

bar for the page. An overview of your personal settings is displayed.

5. Check the settings for cFolders administration. Keep the default settings.

a) In the toolbar, choosecFolders Administration.

6. Check the settings for network administration. Keep the default settings.

a) In the toolbar, chooseNetwork Administration.




27/207


7. Optional: Generate the relevant URL in the ABAP Workbench.

Start the ABAP Workbench. Use the Repository Browser and as the object

use:

BSP Application CFX_RFC_UI

Display the data.

Open thePages with Flow Logic folder.

Using the secondary mouse button, select default.htmand chooseTest.

Log on to the cFolders scenario again.

a) Use transaction SE80. Select the relevant entry for the BSP application.

Display the BSP application as required by the exercise.



28/207


Lesson Summary

You should now be able to: Provide an overview of all the settings required for SAP Application Server





29/207

PLM512 Unit Summary

Unit Summary

You should now be able to:








30/207

Unit Summary PLM512



31/207

Unit 2cFolders Scenarios

Unit Overview

This unit provides an overview of the three scenarios that you can use in a

cFolders application. In addition to the collaborative scenario, this also includes

the competitive scenario and standard scenario.

Unit Objectives


Make the initial settings

Create cFolders scenarios

Create a competitive scenario

Define work areas

Create a collaboration within the competitive scenario Create a standard scenario

Unit Contents

Lesson: Collaborative Scenarios .. ... ... .. .. ... .. .. ... .. ... ... .. .. ... ... .. ... .24

Exercise 2: Collaborative Scenarios .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..27

Lesson: Competitive Scenarios................................................32Exercise 3: Competitive Scenarios........................................37

Lesson: Standard Scenarios ...................................................42Exercise 4: Standard Scenarios ... ... .. ... .. ... ... .. ... .. .. ... ... .. ... .. ..45



32/207

Unit 2: cFolders Scenarios PLM512

Lesson: Collaborative Scenarios

Lesson Overview

This lesson provides an overview of collaborative scenarios in the cFolders

solution.

Lesson Objectives




Business Example

The development department of the Precision Petrol Company has the task of

developing a new oil pump. Collaboration with all external partners involved in

this development is currently supported by e-mail and fax.

Company management has decided to replace this form of collaboration with

the Internet-based platform provided by the cFolders application. You are now

considering using a collaborative scenario because you favor an open exchange

with your development partners and do not require secure work areas.

Collaborative ScenariosThe cFolders solution provides two scenarios:

Collaborative Scenario

Creation and management of engineering and design data

Collaboration in a public area

Competitive Scenario

Creation and management of engineering and design data in a collaboration

Request and evaluation of quotations and data from various partners andsuppliers

Collaboration using separate, partner-specific work areas



33/207

PLM512 Lesson: Collaborative Scenarios

Figure 9: Collaborative Scenario

You want to use the collaborative scenario to coordinate product development for

the new pump prototype. To do this, you create the required product structures as

structured folders.

Within the folders, you assign the relevant objects, such as documents, materials,

BOMs, notifications, or generic objects.

The selected development partners are assigned a user and the relevant

authorizations.

The collaborative scenario is characterized primarily by the fact that all those

involved collaborate. Although you control the individual authorizations for each

object, the scenario is actually open for all involved.



34/207




35/207


Exercise 2: Collaborative Scenarios

Exercise Objectives


Create a collaborative scenario

Business Example

Company management has decided to start using the cFolders application. Within

this application, you are now considering using a collaborative scenario because

you favor an open exchange with your development partners and do not require

secure work areas.

Task:

After you maintain the initial data in the cFolders system, you create the first

Collaborative Scenario.

1. In the navigation bar, chooseCollaborative Scenarios.

On the initial screen, the scenarios created by the instructor and other course

participants are displayed. Create your own scenario using the following

data:

Name PLM512-##

Description Oil Pump Prototype PLM512-##

Indicator Template

Save the data.

2. Rename the first folder:

Name: First Prototype

Save the data.

3. The first prototype is characterized by the fact that it has different

development statuses. You are to document each of these using separatefolders. You therefore need to create the following content:

Folder As designed

Folder As engineered

Folder As built

4. In theAs engineeredfolder, create the following content:




36/207


Folder Documents

Folder Material master

Folder Bill of material

Folder Miscellaneous

5. Sort the items on this last level alphabetically. To do this, choose the relevant

pushbutton on the initial level.

Change the sequence of your folders as required.

Exit your entries and return to the initial navigation level.



37/207


Solution 2: Collaborative Scenarios

Task:

After you maintain the initial data in the cFolders system, you create the first

Collaborative Scenario.

1. In the navigation bar, chooseCollaborative Scenarios.

On the initial screen, the scenarios created by the instructor and other course

participants are displayed. Create your own scenario using the following

data:

Name PLM512-##

Description Oil Pump Prototype PLM512-##

Indicator Template

Save the data.

a) Make the required settings. ChooseCreate. The first folder is created

automatically when you create the collaboration. The folder is

displayed automatically once you save the data.

Hint: Remember to select theUse as Template indicator.

2. Rename the first folder:

Name: First Prototype

Save the data.

a) Make the required settings.

3. The first prototype is characterized by the fact that it has different

development statuses. You are to document each of these using separate

folders. You therefore need to create the following content:

Folder As designed

Folder As engineered

Folder As built

a) Choose the relevant pushbutton to create new objects.

ChooseFolder.

4. In theAs engineeredfolder, create the following content:




38/207


Folder Documents

Folder Material master

Folder Bill of material

Folder Miscellaneous

a) To do this, choose the relevant pushbutton to create new objects.

ChooseFolder.

5. Sort the items on this last level alphabetically. To do this, choose the relevant

pushbutton on the initial level.

Change the sequence of your folders as required.

Exit your entries and return to the initial navigation level.

a) Choose the relevant pushbuttons in the toolbar.



39/207


Lesson Summary

You should now be able to: Make the initial settings




40/207


Lesson: Competitive Scenarios

Lesson Overview

This lesson provides an overview of competitive scenarios.

Lesson Objectives



Define work areas

Create a collaboration within the competitive scenario

Business Example

The engineering department of the Precision Petrol Company is responsible for

the development of the new pump prototype. The department works not only

with development partners, but also with external suppliers, some of which are

competitors.

You are therefore considering using a scenario within the cFolders application in

which suppliers are each assigned secure work areas.



41/207

PLM512 Lesson: Competitive Scenarios

Competitive Scenario

Figure 10: Public Area and Work Areas

In the competitive scenario, you automatically start by creating the public work

area. You are then prompted to assign either authorizations for users or new workareas to the public folderObjects.

The folders are always created in the public area. They are therefore available

to the work areas.

Within the work areas, you or the suppliers can create objects for the folders.

Any objects created in the public area after the work areas are created are not

automatically copied to the work areas. They have to be subsequently copied

to the relevant work areas manually.



42/207


Figure 11: Folder and Area Concept

Users from different work areas have different views of the scenario. They can

view only the relevant parts for which they have read authorization.

Example in a competitive scenario: two suppliers who supply different products.

Supplier 1 supplies motherboards, sound cards, memory chips, and video

cards.

Supplier 2 supplies motherboards, sound cards, and memory chips, but not

video cards.

A specification for a sound card is sent to both suppliers.

The specification for the video card is sent to supplier 1 only.



43/207


Figure 12: Setting Up a Competitive Scenario

When you create a competitive scenario, a public area to be used as a collaboration

is first generated. In this area, you provide all the relevant information for

individual suppliers. You work together with all suppliers on the public data in the

collaboration and with individual suppliers in the secure work areas.

You are responsible for creating these work areas. When you open a work area, the

folder structure of the public area is displayed. You cannot create folders within

the work areas; you can only use those available in the public area. However, youcan create all other types of objects; these are then available in the work area only,

and not in the public area. As the person responsible for the competitive scenario,

you can access the data for each of the various work areas.

Finally, you assign the relevant authorizations for each of the work areas, whereby

read authorization is automatically provided for the public area.



44/207




45/207


Exercise 3: Competitive Scenarios

Exercise Objectives



Business Example

The engineering department of the Precision Petrol Company is responsible for

the development of the new pump prototype. The department works not only

with development partners, but also with external suppliers, some of which are

competitors.

Task:

Since you work with several suppliers, you decide to create a competitive scenario.

You need to create the required data.

1. Create a competitive scenario. To do this, use the collaborative scenario as a

template. Create the first folder with the following data:

Create with Template PLM512-##

Name PLM512-##-A

Description Competitive ScenarioPLM512-##-A

Hint: Do not forget the template.

Save the data.

The data is copied from the collaborative scenario.

2. In the competitive scenario, select the first entry in the navigation bar:

PLM512-##-A

This entry contains a list of your work areas. The list currently containsjust the public area.

ChooseCreateto create additional work areas.

Create the following work area:

- Name: PLM512-##-A1

- Description: Work Area Supplier A1

Save.




46/207


Create the second work area:



Save.

3. Choose the competitive scenario. In the dropdown menu, selectPublic Area.

Navigate to theAs designedfolder. ChooseCreateand thenNote.

Enter the following details:

- Name: PLM512-##

- Description: Prototype PLM512-##

- Note: Product Description Prototype PLM512-##

Save.

4. Choose the competitive scenario. In the dropdown menu, selectWork

Area PLM512-##-A1. Navigate to theAs designed folder. Choose Create

and thenNote.



- Description: Prototype PLM512-##-A1

- Note: Supplier Data for Prototype PLM512-##

Save.



47/207


Solution 3: Competitive Scenarios

Task:

Since you work with several suppliers, you decide to create a competitive scenario.

You need to create the required data.

1. Create a competitive scenario. To do this, use the collaborative scenario as a


Create with Template PLM512-##

Name PLM512-##-A

Description Competitive Scenario

PLM512-##-A


Save the data.


a) Select the relevant entry in the toolbar and create a new scenario.


2. In the competitive scenario, select the first entry in the navigation bar:

PLM512-##-A

This entry contains a list of your work areas. The list currently contains

just the public area.

ChooseCreateto create additional work areas.

Create the following work area:



Save.

Create the second work area:



Save.





48/207


3. Choose the competitive scenario. In the dropdown menu, selectPublic Area.

Navigate to theAs designedfolder. ChooseCreateand thenNote.


- Name: PLM512-##

- Description: Prototype PLM512-##

- Note: Product Description Prototype PLM512-##

Save.


4. Choose the competitive scenario. In the dropdown menu, selectWork

Area PLM512-##-A1. Navigate to theAs designed folder. Choose Create

and thenNote.



- Description: Prototype PLM512-##-A1

- Note: Supplier Data for Prototype PLM512-##

Save.




49/207


Lesson Summary

You should now be able to: Create a competitive scenario

Define work areas




50/207


Lesson: Standard Scenarios

Lesson Overview

This lesson provides an overview of the standard scenario that you can use as a

copy template. Documents assigned here are available in the cFolders system.

Lesson Objectives


Create a standard scenario

Business ExampleFor the development of the new prototype, you use the cFolders scenario. The

development process uses data that can be reused repeatedly; you therefore want

to store this data at a central location in the cFolders scenario. As a result, you are

considering using a standard scenario.

Standard Scenario

The standard scenario is used as a copy template for objects that are required in

the collaborative or competitive scenarios. The objects can be physically copied

or can be referenced using a bookmark.

A scenario can be the BOM maintenance in which existing materials or documentsare assigned. These are searched for in the current work area or in the standard

work area.

Figure 13: Standard Scenario



51/207

PLM512 Lesson: Standard Scenarios

The functions available in a collaborative or competitive scenario are also provided

in the standard scenario. In this scenario, however, you can search for materials or

documents that exist in either the same work area or in the standard scenario.



52/207




53/207


Exercise 4: Standard Scenarios

Exercise Objectives



Business Example

For the development of the new prototype, you use the cFolders scenario. The

development process uses data that can be reused repeatedly. This data should

therefore be stored at a central location in the cFolders scenario.

Task:You create the standard scenario so that you can store documents that are reused in

all collaborative or competitive scenarios.

1. Create a standard scenario. To do this, use the collaborative scenario as a


Create with template PLM512-##

Name PLM512-##-S

Description Standard Scenario PLM512-##-S


Save the data.




54/207


Solution 4: Standard Scenarios

Task:

You create the standard scenario so that you can store documents that are reused in

all collaborative or competitive scenarios.

1. Create a standard scenario. To do this, use the collaborative scenario as a


Create with template PLM512-##

Name PLM512-##-S

Description Standard Scenario PLM512-##-S


Save the data.


a) Select the relevant entry in the toolbar and create a new scenario.




55/207


Lesson Summary

You should now be able to: Create a standard scenario



56/207

Unit Summary PLM512

Unit Summary

You should now be able to:




Define work areas





57/207

Unit 3Master Data

Unit Overview

This unit provides an overview of the objects you can use in a cFolders scenario.

Unit Objectives


Create material masters in the cFolders application

Transfer material masters from the back-end system and transfer back the

changed data

Create BOMs in cFolders

Transfer BOMs to the back-end system and transfer back the changed data

Compare BOMs

Export BOMs

Unit Contents

Lesson: Material Masters ... .... .... .... ... .... ... .... .... .... ... .... ... .... .... 50Exercise 5: Material Masters...............................................55

Lesson: Bills of Material..... .... .... .... ... .... ... .... .... .... ... .... ... .... .... 62

Exercise 6: Bills of Material ................................................69



58/207

Unit 3: Master Data PLM512

Lesson: Material Masters

Lesson Overview

In this lesson, you create material masters as a development partner within a

collaborative scenario. You also transfer data from the SAP ERP back-end system

to the cFolders scenario (collaborative and competitive) as an employee in the

engineering department.

Lesson Objectives


Create material masters in the cFolders application

Transfer material masters from the back-end system and transfer back thechanged data

Business Example

To develop the new oil pump prototype, the engineering department works with

development partners and suppliers. You want to use both the collaborative and

competitive scenario within the cFolders platform.

The data with which you are working consists not only of external documents, but

also of master data, such as material masters, which you and your development

partners make available in the back-end system.

Creating Material Masters in the cFolders Scenario

You can create master data as materials in both the cFolders scenario and in the

SAP ERP back-end system; you can then transfer this data between the systems.

To do this, the material master has to be treated in the same way that it is treated in

the back-end system.

A material master is used to describe an object (product, goods) that is

manufactured, used, traded, or consumed in production.

A material master is specified uniquely using a material number, industry, and

material type. Within the cFolders scenario, you can also assign an internalnumber if you do not want to use a material number. When you transfer the data

to the back-end system, you can either assign the material number manually, and

thus externally, or you can assign a number internally.

As in the back-end system, you can also link documents in the cFolders scenario;

these are then copied to the back-end system.



59/207

PLM512 Lesson: Material Masters

Figure 14: Material Master Attributes

To change the material name, the attributesDescriptionand Numberhave to be

changed in the current material version. The system administrator can assign

read authorization to individual attributes. When you create a new material, you

can assign values to these attributes; once these values are assigned, you cannot

change them.

If documents are linked with a material, you can use a search function to search

for documents. Only documents from the same collaboration or from the same

work area in a competitive scenario can be linked with materials.

A material can be used only once as the header material for a bill of material

(BOM). It can also be used simultaneously as a component in another BOM (in

the same collaboration or work area).

Materials can be copied within the same collaboration or the same work area of

a competitive scenario. They are copied with all attributes and document links.

Materials can also be copied with all attributes to another work area.

If a copy exists for linked documents in the target work area, the link is copied. If

neither the document nor a copy exists in the target work area, the document and

the link are copied. The link to a BOM is not copied.

When a new version of a material is created, the newest version is copied first.You can then change the new version.



60/207


Figure 15: Material Master Attributes in XML

If you make the cFolders settings using WebDAV, you can edit the XML object for

the material master. You can specify exactly which material master fields are to be

displayed and which of these can and cannot be changed.

You also define something similar to the F4 help in the cFolders scenario. It is

important that you do this with the back-end system in mind, since the data istransferred to the back-end system, or master data, such as a material master,

is loaded from the back-end system.



61/207


Transferring Material Masters to the SAP ERPBack-End System

Figure 16: Importing a Material Master from cFolders

If a development partner creates the material masters in your cFolders scenario,

you may want to transfer this data to the ERP back-end system at some point. It

is therefore useful if you can send the material masters in the cFolders scenario

without material numbers and then create the material masters with internal

numbers in the back-end system.

If the material masters are sent with numbers, the system checks whether the

numbers already exist in the system. If a number already exists, an error message

is displayed.

If you use the data in the back-end system and then change it, you may want

to consider updating the original data.



62/207


Figure 17: Exporting a Material Master to cFolders

If you want to transfer data from the SAP back-end system to the cFolders system,

first select the relevant data in the SAP system. If this data consists solely of

documents, you can use the relevant transaction to select the documents directly.

If the data to be transferred consists of material masters or BOMs, you use the

product structure browser.You select the data in the product structure browser and transfer it to a

corresponding table. You then choose to which target folder you want to transfer

the data. You can either use a different folder for each object or define a standard

folder for all objects. The data is then transferred to the cFolders scenario, where

it is then available for use.



63/207


Exercise 5: Material Masters

Exercise Objectives


Create material masters in the cFolders system

Transfer material masters to and from the back-end system

Business Example

To develop the new oil pump prototype, the engineering department works with

development partners and suppliers.

The data with which you are working consists not only of external documents, butalso of master data, such as material masters, which was defined in the back-end

system and in the cFolders platform.

Task 1:

In this exercise, you create the material masters in the cFolders scenario and

transfer them to the back-end system.

1. In the PLM512-## collaborative scenario, navigate to theAs designedfolder

and create some material masters. These material masters are subsequently

used for a BOM.

Caution: Remember to always save your data.

Hint: Material numbers are not used because the development

partner who is creating this data cannot specify the material numbers

in the back-end system. You have to specify these material numbers.

Create the first material master:

Short Text Prototype PLM512-##

Material Number No entry

Industry Mechanical Engineering

Material Type Finished Product

Plant 1000

2. Create the second material master:




64/207


Short Text Housing PLM512-##




3. Create the third material master:

Short Text Shaft PLM512-##




Task 2:

Transfer the data to the back-end system.

1. In the back-end system, start the relevant transaction to import objects from

the cFolders scenario.

Select the following entry:

- cFolders Application: cFolders Training

ChooseSelect cFolders Object.

In the dialog box that is displayed, select your collaborative scenario and

navigate to theAs designedfolder.

Choose the first material. The material is then added to the list of the

materials to be transferred.

Repeat this procedure for the other material masters.

2. Check the data before you transfer it by choosingCheck.

Caution: Material numbers are now assigned to the material

masters. (This is internal number assignment.)

Add the following information:

Material Group: 001

Plant: 1000

Hint: For one of the materials, a value was already entered in the

cFolders application.




65/207


The traffic light is now green.

ChooseCopy Objects.

3. When the internal numbers were assigned in the back-end system, new

versions of the materials were created in the cFolders application. Check

the data.

Log on to the cFolders system.

Navigate to yourCollaborative Scenarioand then to theAs designedfolder.

Check the versions. The transferred material numbers are displayed.



66/207


Solution 5: Material Masters

Task 1:

In this exercise, you create the material masters in the cFolders scenario and

transfer them to the back-end system.

1. In the PLM512-## collaborative scenario, navigate to theAs designedfolder

and create some material masters. These material masters are subsequently

used for a BOM.

Caution:Remember to always save your data.

Hint: Material numbers are not used because the developmentpartner who is creating this data cannot specify the material numbers

in the back-end system. You have to specify these material numbers.

Create the first material master:

Short Text Prototype PLM512-##




Plant 1000

a) Create the data. Return to theAs designedfolder and create an

additional material.

2. Create the second material master:

Short Text Housing PLM512-##




a) Create the data. Return to theAs designedfolder and create an

additional material.

3. Create the third material master:




67/207


Short Text Shaft PLM512-##




a) Create the data.

Task 2:

Transfer the data to the back-end system.

1. In the back-end system, start the relevant transaction to import objects from

the cFolders scenario.

Select the following entry:


ChooseSelect cFolders Object.

In the dialog box that is displayed, select your collaborative scenario and

navigate to theAs designedfolder.

Choose the first material. The material is then added to the list of the

materials to be transferred.

Repeat this procedure for the other material masters.

a) Start the import by choosing:

Environment! Collaboration! cFolders! Import Objects from

cFolders

2. Check the data before you transfer it by choosingCheck.

Caution: Material numbers are now assigned to the material

masters. (This is internal number assignment.)

Add the following information:

Material Group: 001

Plant: 1000

Hint: For one of the materials, a value was already entered in the

cFolders application.

The traffic light is now green.




68/207


ChooseCopy Objects.


3. When the internal numbers were assigned in the back-end system, new

versions of the materials were created in the cFolders application. Check

the data.

Log on to the cFolders system.

Navigate to yourCollaborative Scenarioand then to theAs designedfolder.

Check the versions. The transferred material numbers are displayed.

a) Using your user and password, log on to the cFolders application again.

Navigate as described above. The list for the material masters includes a

column that indicates the current version. This version was incremented

automatically when you assigned internal material numbers to the

material masters in the back-end system and copied the data.



69/207


Lesson Summary

You should now be able to: Create material masters in the cFolders application

Transfer material masters from the back-end system and transfer back the

changed data



70/207


Lesson: Bills of Material

Lesson Overview

This lesson explains the functions for bills of material (BOMs) in the cFolders

scenario and how they are integrated in the back-end system. It explains how to

compare or explode BOMs and how to use BOM filters.

Lesson Objectives


Create BOMs in cFolders

Transfer BOMs to the back-end system and transfer back the changed data

Compare BOMs

Export BOMs

Business Example

In your engineering department, you have created some material masters as your

master data. However, since the pump prototype requires a materials list, you

are considering using a BOM.

You also need to transfer your data to the SAP ERP back-end system. This data

transfer channel, however, needs to be bidirectional because you also want to be

able to transfer BOMs to the cFolders system. In addition, you want to be able tocompare BOMs because you want to transfer all changes made in the back-end

system back to the cFolders system. The development partners must also be able

to use these BOMs in their systems. For this reason, you are considering exporting

the data using XML or CSV format.

Working with Bills of Material

You are considering using BOMs within the cFolders scenario for your product

development. However, before you can define BOMs, you require the relevant

materials in the same way that you have the BOM scenario in the SAP ERP

back-end system.

You first select the material for the BOM header. You need to consider in which

area the BOM is to be used engineering, production, or sales. You also need to

consider whether the BOM requires information about the plant.

The following restrictions apply:

One material is assigned as the BOM header.

The material can be the header material for just one BOM; it cannot be

assigned to a second BOM.



71/207

PLM512 Lesson: Bills of Material

You also need to keep in mind that you can select materials from the same

collaboration or the same work area only. The name for the BOM is derived from

the name for the header material; you cannot change this name.

Lastly, you specify the BOM components. You can change these at any time. You

can also link them to documents that have been defined in the collaborative or

standard scenario.

Figure 18: Attributes for a Bill of Material

Figure 19: Detail Screen for a Bill of Material



72/207


BOMs can be copied within the same collaboration or work area. The BOM,

including all its attributes, components, and document links, is copied to the target

folder. Since the header material can only be used once for a BOM, the new headermaterial must be a copy of the original; if a copy already exists, this existing copy

is used. If no copy exists, the components and BOM header are copied.

If a copy exists for linked documents in the target work area, the link is copied.

If neither the document nor a copy exists in the target work area, the document

and the link are copied.

Figure 20: XML File for a Bill of Material

You can define an XML file for the BOM in the same way that you can define

XML for material masters. You can specify, for example, possible BOM usages or

units of measure.



73/207


Transferring BOMs to and from the Back-End System

Figure 21: Importing a Bill of Material from cFolders

If a development partner creates material masters and BOMs in your cFolders

scenario, you may want to subsequently transfer this data to the ERP back-end

system.

When you transfer the data, you can specify whether you want to transfer multiplelevels of the material BOM and whether you want to include linked documents.

Since the master data in SAP back-end systems is often created with a change

number, you can also create master data using a change master record, for example.

Before you complete the data transfer, the system displays a result screen

containing the changes to the BOM.



74/207


Figure 22: Exporting a Bill of Material to cFolders

If you want to transfer BOMs and their material masters from the SAP back-end

system to the cFolders system, you first select the relevant data in the SAP system.

You use the product structure browser to do this.

In the product structure browser, you select the data and then transfer it to a

corresponding table. You then select to which target folder you want to transfer

the data. You can either use a different folder for each object or define a standardfolder for all objects. The data is then transferred to the cFolders scenario, where

it is then available for use.



75/207


Additional Functions

Figure 23: Single-Level Bill of Material Comparison

If you have multiple versions of your BOM in the cFolders scenario, you can

compare these versions with one another. To do this, in the version overview, you

select the versions you want to compare. The detail screen is then displayed.

It provides an initial general overview. You can also display more detailed

information, for example, information about the items, components, or documents.

Using a table filter, you can change the display, for example, to display all

components, or just the changed components.

You can also specify exactly which attributes you want to display for the BOM,

components, or documents.



76/207


Figure 24: Bill of Material Comparison II

In addition to comparing various versions, you can also select a specific version

of the BOM and compare it with the current BOM. You can use this method to

highlight changes. The system first displays an overview of all changes; you can

use this overview to navigate to the detail screen.

Figure 25: Extracting Bills of Material in CSV or XML Format

If you extract BOMs in CSV (comma-separated values) or XML format, external

development partners can download the BOM information to their local PCs and

make it available in their system.

Before you download the data to your local PC, you can specify with which

parameters the BOM is to be transferred.



77/207


Exercise 6: Bills of Material

Exercise Objectives


Create BOMs in the cFolders scenario

Transfer BOMs to and from the back-end system

Compare BOMs

Business Example

In your engineering department, you have created some material masters as your

master data. However, since the pump prototype requires a materials list, you

use a bill of material (BOM).

You also need to transfer your data to the SAP ERP back-end system. This data

transfer channel, however, needs to be bidirectional because you also want to be

able to transfer BOMs to the cFolders system. In addition, you want to be able to

compare BOMs because you want to transfer all changes made in the back-end

system back to the cFolders system.

Task 1:

In this exercise, you create BOMs in the cFolders application and transfer them to

and from the back-end system.

1. Navigate to the As designedfolder of your collaborative scenario

PLM512-##.

ChooseCreateand thenBill of Materialto create a new BOM. On the screen

that appears, the material masters that you created earlier are displayed. You

can use these for your material BOM.

Select the material masterPrototype PLM512-##as your header material.

After you have selected the relevant radio button, chooseSelect.

Enter the following data:

Material Prototype PLM512-##

Plant No entry

Use Engineering and Design

Base Quantity 1

Status Active

Save the data.




78/207


2. Create two new items. In the bill of material overview, chooseCreate. You

select the material from the list of materials by choosing Assign.

To do this, you first need to search for the materials.

Repeat this procedure to assign the remaining material masters to the BOM.

Caution:Always use the quantity 1 and a four-digit item number:

0010 for the first material and 0020 for the second material.

Save the data.

3. Check your BOM. Display version 1. If you have completed this task

successfully, the material masters you assigned are displayed.

4. Transfer the data for the BOM to the back-end system.Start the relevant transaction in the back-end system; this is the Import

Objects from cFolders transaction.

Enter the following values:


- ChooseSelect cFolders Object.

In the dialog box that appears, navigate to your collaborative scenario

PLM512-##, then to theAs designedfolder and select the BOM.

ChooseCheck. The BOM is now assigned the internal number of the header

material.

ChooseCopy Objects.

The result preview appears. Using the result preview, you can determine

whether the BOM data was changed, or whether new data was created.

Save the data.

5. Check the BOM by displaying it in the back-end system.

Task 2:

You now want to make the data that you created in your development departmentavailable in the collaborative scenario.

1. Using the standard transactions, first display the following BOM in the

back-end system.:




79/207


Material T-F1##

Plant 1000

BOM Usage 1

2. You now want to transfer the BOM for material T-F1## to theAs engineered

folder of your scenario.

To do this, start the relevant transaction to export the BOM; this is the Export

Objects to cFolderstransaction.

Then start the product structure browser for material T-F1##.

Open the folder for the BOM and drag BOM T-F1##/1000/1/01 to the list of

selected objects by using drag and drop.

ChooseCopy Objects.

On the screen that appears, select the target folder. The data is to be

transferred to the Bill of materialarea in theAs engineeredfolder of the

PLM512-## collaborative scenario.

Select the Choose Standard Folderand navigate to the PLM512-##

collaborative scenario.

Select theAs engineeredfolder that you created and thenBill of material.

Keep the remaining settings.

Hint: No documents are transferred. The BOM is not exploded

on multiple levels.

ChooseCheck.

ChooseCopy Objects.

The system then displays a message that the objects have been transferred

successfully. Check whether the objects were transferred correctly.

3. Log on to the cFolders scenario again using user PLM512-##. Navigate to

yourPLM512-##collaborative scenario, then to the As engineeredfolder,and finally to theBill of materialfolder. The BOM and the corresponding

material masters are listed here.

4. Change the BOM in the back-end system.

In the back-end system, navigate in the user menu to the transaction for

changing the BOM. Use the following data:




80/207


Material T-F1##

Plant 1000

BOM Usage 1

Change the following items:

Change item 0040 Old: T-B4## New: 100-400

Change quantity for

item 0050

Old: 8 New: 16

Create new stock item

0070

Material: 100-500 Quantity: 1

Save your BOM.

5. Export the changed BOM to the cFolders scenario. Start the relevant

transaction.

On the initial screen for the product structure browser, enter material T-F1##.



ChooseCopy Objects.

On the screen that appears, select the target folder. The data is to be

transferred to the Bill of materialarea in theAs engineeredfolder in thecollaborative scenario. ChooseChoose Standard Folderand navigate to the

PLM512-## collaborative scenario. Select the As engineeredfolder that

you created and thenBill of material.

Keep the remaining settings.

Hint: No documents are transferred. The BOM is not exploded

on multiple levels.

ChooseCheck.

Hint: From the information displayed, you can see that the data

has been changed.

ChooseCopy Objects.


successfully. In the cFolders application, check that the objects were

transferred.




81/207


6. Log on to the cFolders scenario again using user PLM512-##. Navigate to

yourPLM512-##collaborative scenario, then to the As engineeredfolder,

and finally to theBill of materialfolder. The BOM and the relevant materialmasters are listed here; they now have a new version.

Hint: The BOM now has version 4; the changed material masters

now have version 2.

7. Compare the BOMs.

To do this, select the BOM; all four versions are then listed.

Select version 2 and version 4 and choose Compare.

The comparison results indicate which components were changed and whichwere added.

8. You now want to upload the multilevel BOM and any related object links.

In the back-end system, navigate to the relevant transaction to export the

BOM.

On the initial screen for the product structure browser, enter material T-F1##.



ChooseCopy Objects.

On the screen that appears, select the target folder.

The data is to be transferred to theBill of materialarea in the As engineered

folder in the collaborative scenario. ChooseChoose Standard Folderand

navigate to the PLM512-## collaborative scenario. Select the As engineered

folder that you created and then Bill of material.

Change the remaining settings as follows:

BOM Application PP01

Indicator Multilevel

Indicator Include Linked Documents

ChooseCheck.

Hint: From the information displayed, you can see that the data has

been changed and that material masters and documents have been

added.




82/207


ChooseCopy Objects.


successfully. In the cFolders application, check that the objects were

transferr