662: Collaboration with cFolders SAP Best Practices IM&C Package (China) SAP Best Practices

662: Collaboration with cFolders SAP Best Practices IM&C Package (China)

SAP Best Practices

Scenario Overview – 1

Purpose and Benefits:

Purpose Product Lifecyle Management refers to the management of all product-related

information, such as information on specifications and configuration. This information manages the entire life cycle of a product

Benefits

Product design, development andconfiguration using project system

CAD Integration (Viewer) Design changes Easy Document Management cFolders Setup BOM generation from document structure


SAP ECC 6.0 EhP3 ECL Viewer 6.00 Easy Document Management 6.0

Customer Engineering Partner Engineering Specialist Project Manager Sales Administration

SAP Applications Required:

Company Roles Involved in Process Flows:


Detailed Process Description:

The robot manufacturer (customer) want to order a design of an assembly robot, they send the order and specification to their engineering partner on cFolder

The engineering partner create a project based on a project template and then assign the order and customer’s specifications to this project

Engineering partner creates a sales order for service processing

Adding a document using EasyDMS

After the design, the document BOM is available for the assembly robot.

On the CAD desktop, the material master for this assembly robot will be created and its Engineering BOM will also be created by its document BOM


Detailed Process Description:

Design draft will be sent to the customer by cFolders (including Material and CAD Drawings)

The customer informs the engineering partner via cFolders (by redlining the Drawing) that the design still need to be changed

At the end of the process copy the Engineering BoM to Production BoM

Engineering partner confirm the project with activity allocated to it and use cross-Application Time Sheet to record the labor effort

CO-PA Integration: the project will be settled to CO-PA

After the project is finished, create an invoice for billing the sales order.

Set the status of the project to closed after everything is finished

Process Flow DiagramCollaboration with cFolders

En

gin

eeri

ng

S

pec

ialis

tP

roje

ct

Man

ager

Cu

sto

mer

Sal

es

Ad

min

istr

atio

n

En

gin

eeri

ng

P

artn

er

Uploading Specification and Order to

cFolder

Reviewing Documents in cFolders

Importing Specification Document to PLM Backend

Creating a Design Project

Reviewing and Importing Customer

Order to PLM Backend

Assigning Documents to

WBS and Releasing

Project

Creating Sales Order

Adding a document with

EasyDMS

Linking the CAD-document to the EasyDMS folder

Creating the Header Material

Using the CAD Desktop

Creating Material

BOM Using CAD

Desktop

Changing the BOM

Changing Document

Status

Changing Document Status with EasyDMS

Exporting the

Objects to cFolders

Redlining in cFolders

Assigning New

Document Version to Material

Generating the Settlement

Rule

Time Recording

(211)

Billing the Sales Order

Closing Completed

Projects (technical

view)

Period End Closing

Projects(207)

Legend

Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.

The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario.

Role band contains tasks common to that role.

External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.

Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.

Connects two tasks in a scenario process or a non-step event

Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario

Does not correspond to a task step in the document

Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario

Corresponds to a task step in the document

Process Reference: If the scenario references another scenario in total, put the scenario number and name here.


Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here


Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.

Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution

Symbol Description Usage Comments

To next / From last Diagram: Leads to the next / previous page of the Diagram

Flow chart continues on the next / previous page

Hardcopy / Document: Identifies a printed document, report, or form

Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines

Financial Actuals: Indicates a financial posting document


Budget Planning: Indicates a budget planning document


Manual Process: Covers a task that is manually done

Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.

Existing Version / Data: This block covers data that feeds in from an external process

Does not generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any incoming flow lines

System Pass / Fail Decision: This block covers an automatic decision made by the software

Does not generally correspond to a task step in the document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.

<F

unct

ion>

Ext

erna

l to

SA

P

Business Activity /

Event

Unit Process

Process Reference

Sub-Process

Reference

Process

Decision

Diagram Connection

Hardcopy / Document

Financial Actuals

Budget Planning

Manual Proces

s

Existing Version /

Data

System Pass/F

ail Decisio

n

Copyright 2009 SAP AGAll Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

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

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

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

Oracle is a registered trademark of Oracle Corporation.

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

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

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

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

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

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

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.