665 Scen Overview en US

8/4/2019 665 Scen Overview en US

http://slidepdf.com/reader/full/665-scen-overview-en-us 1/7

665: Configuration MTO - Sales Order

Processing with order BOM and OCM

SAP Best Practices for IM&C (US)

SAP Best Practices



Scenario Overview – 1

Purpose

Make-to-order processing is typical for mechanical engineeringand is used by manufacturers of specialized machinery and by projectengineering companies

The degree of engineering on the end product varies depending on the

scope of the customer requirements. The engineer is confronted with theproblem of taking customer requirements into detailed considerationeven though the engineer can translate only a small percentage of thequotations into orders due to high international competition

Modification of the end product and its components according to specialcustomer requests is common and economically important, even afterthe procurement had been started

When an order is placed, a high degree of integration between thedifferent business areas is needed because of the product’s complex

structure. A high standard for data maintenance and data transfer isrequired to produce high quality, competitively priced products withinthe shortest possible period of time

Purpose and Benefits:




Production Planner

Warehouse Clerk

Sales Administrator

Shop Floor Specialist

Billing Administrator

Purchasing Manager

SAP Applications Required:

Company Roles Involved in Process Flows:

Key Process Flows Covered:

Sales Order Processing with configurable materials

Order BOM Processing with several levels and technical configuration

Collective Order Processing Sales Order Change Management

OCM: Production Order Change

Technical structure and equipment handling

Enhancement Package 4 for SAP ECC 6.0




Detailed Process Description:

Configuration MTO - Sales Order Processing with order BOMand OCM

Sales order creation and processing

Refining order BOM with technical configuration

Disposition using the stock/requirements list and the order tree

Collective order processing using a collective production order Sales order change management

OCM: Production order change for a configurable subassembly and thefinished product

Production order processing for subassemblies

Collective order processing for the finished product

Delivery processing

Billing

Technical structure and equipment handling



Process Flow Diagram Configuration MTO - Sales Order Processing with order BOM and OCM



Legend

Symbol Description Usage

Comments

Band: Identifies a user role, such as AccountsPayable Clerk or Sales Representative. This band canalso identify an organization unit or group, ratherthan a specific role.

The other process flow symbols in this table go intothese rows. You have as many rows as required tocover all of the roles in the scenario.

Role bandcontains taskscommon to thatrole.

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

Flow line (solid): Line indicates the normal sequenceof 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 alsolead to documents involved in the process flow.

Connects twotasks in ascenario

process 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 another

scenario in total, put the scenario number and namehere.

Corresponds to

a task step inthe document

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

Corresponds toa task step inthe document

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

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

Symbol Description Usage Comments

To next / From last Diagram: Leads

to 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 taskstep 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


Budget Planning: Indicates abudget planning document


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.

< F u n c t i o n >

E x t e r n a l

t o

S A P

BusinessActivity /

Event

Unit Process

ProcessReference

Sub-Process

Reference

Process

Decision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProces

s

ExistingVersion /

Data

SystemPass/F

ailDecisio

n



Copyright 2010 SAP AG

All Rights Reserved

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

may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, 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 othercountries.

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 C itrix 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 logosare 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 andservices 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 Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construedas constituting an additional warrant.

Documents

665 Scen Overview en US