Vous êtes sur la page 1sur 9

662: Collaboration with cFolders

SAP Best Practices


Purpose, Benefits, and Key Process Steps

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 and
configuration using project system
CAD Integration (Viewer)
Design changes
Easy Document Management
cFolders Setup
BOM generation from document structure

2011 SAP AG. All rights reserved. 2


Required SAP Applications and Company Roles

SAP Applications Required


Enhancement package 5 for SAP ERP 6.0
ECL Viewer 7.0
Easy Document Management 7.1

Company Roles Involved in Process Flows:


Engineering Specialist
Project Manager
Sales Administrator

2011 SAP AG. All rights reserved. 3


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 customers 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

2011 SAP AG. All rights reserved. 4


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

2011 SAP AG. All rights reserved. 5


Process Flow Diagram
Collaboration with cFolders

Customer (Robot
Manufacturer) Uploading the 1
Specification and Order to
Event

cFolder

Engineering Partner: Engineering Partner: Reviewing Optional: Engineering Engineering Partner: Engineering
Reviewing and Importing and Importing Customer Order Partner: Linking CAD Creating Header Partner:
Specification Document to to PLM Backend Documents to EasyDMS Material using CAD ChangeBOM
Engineering Specialist

PLM Backend folder Desktop

Engineering Partner:
Create Material BOM
using CAD Desktop

Engineering
Project Manager

Partner: Engineering Partner:


Creating a Assigning Documents to
Design Project WBS of Project and
Releasing Project

Optional: Engineering
Sales Administrator

Engineering Partner: Partner: Adding a


Creating Sales Order Document with
EasyDMS

2011 SAP AG. All rights reserved. 6


SAP 2009 / Page 6
Process Flow Diagram
Collaboration with cFolders

1 Time Period End


Recording Closing
Event

(211) Projects (207)

Engineering Partner: Engineering Partner:


Engineering Engineering Partner:
Export Objects (Material Assigning New
Partner: Change Change Document
and CAD Drawing) to Document Version to
Document Status Status with EasyDMS
Engineering Specialist

cFolders Material

Engineering Partner:
Project Manager

Engineering Partner:
Generate Settlement Close Completed
Rule Projects (Technical
View)

Engineering Partner:
Sales Administrator

Billing the Sales Order

2011 SAP AG. All rights reserved. 7


SAP 2009 / Page 7
Legend

Symbol Description Usage Comments Symbol Description Usage Comments

Band: Identifies a user role, such as Accounts Role band contains


Payable Clerk or Sales Representative. This band tasks common to that To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
<Function>

can also identify an organization unit or group, role. Diagram


rather than a specific role. Diagram
Connection
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.
Hardcopy / Document: Identifies a Does not correspond to a task
External Events: Contains events that start or end printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External

the scenario, or influence the course of events in generated by a task step; this
to SAP

the scenario. Document shape does not have any


outgoing flow lines

Flow line (solid): Line indicates the normal Connects two tasks in
sequence of steps and direction of flow in the a scenario process or Financial Actuals: Indicates a Does not correspond to a task
a non-step event financial posting document step in a document; instead, it is
scenario. used to reflect a document
Flow line (dashed): Line indicates flow to Financial generated by a task step; this
infrequently-used or conditional tasks in a Actuals shape does not have any
scenario. Line can also lead to documents outgoing flow lines
involved in the process flow.

Business Activity / Event: Identifies an action that Does not correspond Budget Planning: Indicates a Does not correspond to a task
either leads into or out of the scenario, or an to a task step in the budget planning document step in a document; instead, it is
Business outside Process that happens during the scenario document used to reflect a document
Activity / Event Budget generated by a task step; this
Planning shape does not have any
outgoing flow lines
Unit Process: Identifies a task that is covered in a Corresponds to a task
step-by-step manner in the scenario step in the document
Unit Process Manual Process: Covers a task Does not generally correspond to
that is manually done a task step in a document;
instead, it is used to reflect a task
Manual that is manually performed, such
Process Reference: If the scenario references Corresponds to a task Process as unloading a truck in the
another scenario in total, put the scenario number step in the document warehouse, which affects the
Process and name here. process flow.
Reference

Existing Version / Data: This block Does not generally correspond to


Sub-Process Reference: If the scenario references Corresponds to a task covers data that feeds in from an a task step in a document;
another scenario in part, put the scenario number, step in the document external process instead, this shape reflects data
Sub- name, and the step numbers from that scenario Existing coming from an external source;
Process here Version / this step does not have any
Reference Data incoming flow lines

Process Decision: Identifies a decision / branching Does not usually


point, signifying a choice to be made by the end correspond to a task System Pass / Fail Decision: This Does not generally correspond to
user. Lines represent different choices emerging step in the document; block covers an automatic a task step in the document;
from different parts of the diamond. Reflects a choice to decision made by the software instead it is used to reflect an
Process be made after step System automatic decision by the system
Decision execution Pass/Fail that is made after a step has been
Decision executed.

2011 SAP AG. All rights reserved. 8


2011 SAP AG. All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
without the express permission of SAP AG. The information contained herein may be Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
changed without prior notice. mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
registered trademarks of Sybase, Inc. Sybase is an SAP company.
Corporation.
All other product and service names mentioned are the trademarks of their respective
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
companies. Data contained in this document serves informational purposes only. National
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
product specifications may vary.
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, The information in this document is proprietary to SAP. No part of this document may be
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, reproduced, copied, or transmitted in any form or for any purpose without the express prior
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, written permission of SAP AG.
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered This document is a preliminary version and not subject to your license agreement or any
trademarks of IBM Corporation. other agreement with SAP. This document contains only intended strategies, developments,
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. and functionalities of the SAP product and is not intended to be binding upon SAP to any
particular course of business, product strategy, and/or development. Please note that this
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
document is subject to change and may be changed by SAP at any time without notice.
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
Oracle and Java are registered trademarks of Oracle Corporation.
warrant the accuracy or completeness of the information, text, graphics, links, or other items
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. contained within this material. This document is provided without a warranty of any kind,
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are either express or implied, including but not limited to the implied warranties of
trademarks or registered trademarks of Citrix Systems, Inc. merchantability, fitness for a particular purpose, or non-infringement.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World SAP shall have no liability for damages of any kind including without limitation direct,
Wide Web Consortium, Massachusetts Institute of Technology. special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well The statutory liability for personal injury and defective products is not affected. SAP has no
as their respective logos are trademarks or registered trademarks of SAP AG in Germany control over the information that you may access through the use of hot links contained in
and other countries. these materials and does not endorse your use of third-party Web pages nor provide any
warranty whatsoever relating to third-party Web pages.

2011 SAP AG. All rights reserved. 9