232 Scen Overview en De

8/3/2019 232 Scen Overview en De

1/7

Engineer-to-Order (ETO)

Quotation Processing

(232)

SAP Best Practices for

Discrete Manufacturing V1.603

(Germany)

SAP Best Practices


2/7

Scenario Overview 1

Purpose

This scenario describes the quotation processing in a standard Engineer-to-Order (ETO) environment.

SAP functionalities of Sales & Distribution (SD) and of Project System (PS) are in use to control the wholeprocess, from customer inquiry to the handover to project assembly (in BB 240, ETO Project Assembly).

The SAP configuration process with assignments of characteristic values and also purchasing functionalities special step long lead time procurement - are part of the process.

Benefits

Product configuration is in use from the first step of the process and rearrangements are easy to use Deep integration to the project structuring and calculation allows a consistently controlling of all steps and values

Copy functionalities e.g. from inquiry to quotation are facilitating compliance with the process rules

All values and parameters for the following process (ETO, 240) are available as default parameters

The option for the creation of project versions are allowing a continuous recording of all relevant values along thecontrolling process and a later comparison of the several si tuations

Transfer of material with the functionality of CN33 is easy to use and gives a guarantee of a current view to thematerials and the bill of material (BOM)

The long lead time procurement process is a good step to guarantee the placing of parts in time

Key process flows covered Creation of inquiry with the usage of configuration

Several creation steps for quotations with reference to the inquiry

Integration to the project, with calculation and scheduling functionalities

Controlling and Reporting along the whole process, without interruption

Purpose and Benefits:


3/7

Scenario Overview 2

Required

SAP EHP3 for SAP ERP 6.0

Company roles involved in process flows Sales Administration

Project Manager

SAP Applications Required:


4/7

Scenario Overview 3

Engineer-to-Order (ETO) Quotation Processing

This scenario describes a business process in a typical engineer-to-order(ETO) environment. Sales & Distribution (SD) and the Project System (PS)is used to control the complete process from the customer inquiry to theaccepted quotation. The process has a final step with the start of the longlead time procurement.

First process step is the creation of the inquiry with the usage of theconfiguration

Creation of the quotation, with reference to the inquiry and with a linkageto the customer project, is fulfilling the first activity block

Project structuring is the prerequisite for the above-mentioned step

Materials are transferred to the project with the functionality of the BOM-transfer (Bill of Material)

Project scheduling and calculation (basis for the quotation) are carried out

Reporting and project versions are completing the process

Long lead time procurement starts with the customer acceptance of thechanged quotation

Detailed Process Description:


5/7

Process Flow Diagram

Engineer-to-Order (ETO) Quotation Processing

ProjectManager

Sales

Administration

Linking project(WBS-element)with quotation

Creation ofInquiry

withconfiguration

Creates theproject with the

templatestructure

Completingquotation with

pricedetermination

TransferringBill of Material(BOM) to the

project

ProjectScheduling

Reporting

CustomerActivity /

Event

Creatingquotation with

reference to theinquiry

Project Costing

1

ProjectManager

Sales

Adm

inistration

Creates aproject version

Completingchanged

quotation withnew price

determination

Changes,according to

customers newspecification

TransferringBill of Material(new config. /BOM) to the

project

Project Re-Scheduling

Project Costing

1Change

quotation

Reporting(changedquotation)

Releasingnetwork activity(long lead timeprocurement)

ProcessETO 240Project

Assembly


6/7

Legend

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable 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 bandcontains tasks

common to thatrole.

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

scenario.

Flow line (solid): Line indicates the normal sequence

of steps and direction of f low 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 twotasks in ascenarioprocess or anon-step event

Business Activity / Event: Identifies an action thateither leads into or out of the scenario, or an outsideProcess that happens during the scenario

Does notcorrespond to atask step in thedocument

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

Corresponds toa task step inthe document

Process Reference: If the scenario references anotherscenario in total, put the scenario number and namehere.


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


Process Decision: Identifies a decision / branchingpoint, signifying a choice to be made by the enduser. Lines represent different choices emergingfrom different parts of the diamond.

Does notusuallycorrespond to atask step in thedocument;Reflects achoice to bemade after step

execution

Symbol Description Usage Comments

To next / From last Diagram: Leadsto the next / previous page of theDiagram

Flow chart continues on the next /previous page

Hardcopy / Document: Identifies aprinted document, report, or form

Does not correspond to a t askstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Financial Actuals: Indicates afinancial posting document

Does not correspond to a t askstep in a document; instead, it isused to reflect a document

generated by a task step; thisshape does not have any outgoingflow lines

Budget Planning: Indicates abudget planning document

Does not correspond to a t askstep in a document; instead, it isused to reflect a documentgenerated by a task step; thisshape does not have any outgoingflow lines

Manual Process: Covers a taskthat is manually done

Does not generally correspond toa task step in a document;instead, it is used to reflect a taskthat is manually performed, suchas unloading a truck in thewarehouse, which affects theprocess flow.

Existing Version / Data: This blockcovers data that feeds in from anexternal process

Does not generally correspond toa task step in a document;instead, this shape reflects datacoming from an external source;this step does not have anyincoming flow lines

System Pass / Fail Decision: Thisblock covers an automaticdecision made by the software

Does not generally correspond toa task step in the document;instead it is used to reflect anautomatic decision by the systemthat is made after a step has beenexecuted.

External

toSAP

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n


7/7

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 containedherein 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, DB1, DB1 Universal Database, OS/1, Parallel Sysplex, MVS/ESA, AIX, S/590, AS/400, OS/590, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, IntelligentMiner, 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 W5C are trademarks or registered trademarks of W5C, 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/5, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose withoutthe express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended

strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, productstrategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited tothe implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use ofthese materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot

links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Copyright 2008 SAP AG.All Rights Reserved

232 Scen Overview en De

Documents

Transcript of 232 Scen Overview en De