148 ERP605 Process Overview en BR

7/31/2019 148 ERP605 Process Overview en BR

http://slidepdf.com/reader/full/148-erp605-process-overview-en-br 1/10

Make-to-Order Production w/o VariantConfiguration

SAP Best Practices



© 2011 SAP AG. All rights reserved. 2

Purpose, Benefits, and Key Process Steps

Purpose The business process encompasses all steps from the customer quotation to the delivery and billing of the finished good

and all dependent components in make-to-order production (MTO).

Furthermore, the scenario is supported by the main cost object controlling functions required, such as preliminary costingand period-end closing.

Benefits Quotation history

Billing plan including down payment Change management in production

Key Process Steps Creation of the quotation header

Creation of follow on quotation with reference to first quotation

Customer’s request to change the quotation

Create sales order with reference to accepted follow on quotation

Customers credit limit is checked

Order confirmation is sent to the customer and the production process is started

Milestone Billing – down payment after order confirmation

Customer requests a technical change

Sales order and bill of material are recalculated

Delivery and billing of the finished good




Required SAP Applications and Company Roles

Required SAP Applications

SAP enhancement package 5 for SAP ERP 6.0

Company Roles

Engineering Specialist

Production Planner Sales Administrator

Billing Administrator

Accounts Receivable Accountant

Production Supervisor

Warehouse Clerk

Shop Floor Specialist

Product Cost Controller




Detailed Process Description

Make-to-Order Production w/o Variant Configuration

This scenario describes the entire process sequence for a standard sales process (Make-to-Order) with a customer.The business process encompasses all steps from the customer quotation to the clearingof a customer account after payment is received.

Quotation processing is the first stage of the production process. The scenario starts withan incoming request for quotation. A quotation is then created in the SAP system inresponse to the customer's RFQ. The customer requests a change to the quotation and afollow-on quotation is created. Finally, the customer accepts the second quotation and areferenced sales order is created. An order confirmation is send to the customer andproduction process is started.Now, the customer requests a technical change. Sales order and bill of material are

therefore recalculated. The process ends with the delivery and the billing of the producedgoods.

The process can be enhanced individually by executing optional steps, like serial numbercreation, subcontracting, QM in production, credit management and plant- and companyclosing.




Process Flow DiagramMake-to-Order Production w/o Variant Configuration: Quotation Processing MTO

S

a l e s A d m i n i s t r a t i o n

E v e n t

Quotationaccepted

?

PlanForecast

for FinishedGood (144)

QuotationProcessing

MTO

Request forMTO Quotation

Reject

FirstQuotation

Print OrderConfirmation

MTO = Make-to-Order; DMS = Document Management System

Create, Print andSend Sales

Quotation toCustomer

Optional: UseEasy DMS to

AssignCustomer

Specification toQuotation

Create Follow-On Quotationand Send toCustomer

Yes

No




Process Flow DiagramMake-to-Order Production w/o Variant Configuration:Parts Production for Subassembly

S a l e s

A d m i n i s t r a t i o n

S a l e s B i l l i n

g

P r o d u c t i o n

P l a n n e r

E v e n t

A c c o u n t s

R

e c e i v a b l e

Procurement ofComponents

UsingPurchasingProcessing

(130)

Create Sales Orderwith Reference to

Follow-onQuotation and PrintOrder Confirmation

Need of Raw

Material forSubassembly

Credit IssuesHave to be

Solved (108)

Create Invoice,Print Down

Payment Requestand Send toCustomer

Post CustomerDown Payment

Evaluate StockRequirements

Situation


http://slidepdf.com/reader/full/148-erp605-process-overview-en-br 7/10 © 2011 SAP AG. All rights reserved. 7

Process Flow DiagramMake-to-Order Production w/o Variant Configuration: Parts Production for Subassembly;Technical Change for Finished Good, Procurement of Stock for Final Assembly

P r o d u c t i o n

P l a n n e r

S a l e s

A d m i n i s -

t r a t i o n

E v e n t

Planned OrderHas to be

Converted to

Production Order

M a n u -

f a c t u r i n g

CreateProduction

Order(Subassembly)

ConfirmProduction

Order

Evaluate Stock /RequirementsSituation after

TechnicalChange

CustomerChange

Request isConsidered

Manually IssueGoods

Request forTechnical Change

(Finished Good)

P

r o d u c t

C o s t

C o

n t r o l l e r

B u y e r Procurement of

Stock Materialw/o QM

(130)

Procurementof Stock

Material withQM (127)

Procurement &Consumptionof Consigned

Inventory (139)

MMSubcontractin

g (138)

RepetitiveManufacturing

(149)

Procurement ofComponents Using

PurchasingProcessing

MaterialStaging

ReleaseProduction

Orders

RecalculateCustomer

BOM

Change Order,Print Order

Confirmation andSend to Customer

(after AddingMaterial)

E n g i n e e r i n g

S p e c i a l i s t

S h o p

f l o o r

S p e c .

P r o d u c t i o

n

S u p e r v i s o

r Review Order

Confirmations



Process Flow DiagramMake-to-Order Production w/o Variant Configuration:Final Assembly; Delivery Processing; Billing Processing

P r o d u c t i o n

P l a n n e r

A c c o u n t s

R e c e i v a b l

e

E v e

n t

PlannedOrder Has to

beConverted toProduction

Order

M

a n u f a c t u r i n

g

ConvertPlanned Orderto Production

Order

ReleaseProduction

Orders

Optional:Checking

SerialNumbers inProduction

Order

S a l e s B i l l i n g

Post GoodsReceipt forProduction

Order with SerialNumber

Assignment

Evaluate Stock/

RequirementsSituation

ConfirmAssemblyActivities

S a l e s

A d m i n i s t r a t i o n

S h o p F l o o r

S p e c i a l i s t

Optional:Printing ShopFloor Papers

PickComponents (Picking

List)

IssueGoods

ManuallyInstead of

PickingList

MaterialStaging

forAssembl

y

SalesOrder

Processing: Sales

fromStock(109)

Delete BillingBlocks

Create Invoice,Print PaymentRequest and

Send toCustomer

Post MilestoneInvoice

Create Invoice,Print Closing

PaymentRequest and

Send toCustomer

Post ClosingInvoice

End Process



Legend

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

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

E x t e r n a l

t o

S A P

BusinessActivity / Event

Unit Process

ProcessReference

Sub-Process

Reference

ProcessDecision

DiagramConnection

Hardcopy /Document

FinancialActuals

BudgetPlanning

ManualProcess

ExistingVersion /

Data

SystemPass/FailDecision

Symbol Description Usage Comments

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

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

Role band containstasks common to thatrole.

External Events: Contains events that start or endthe scenario, or influence the course of events inthe scenario.

Flow line (solid): Line indicates the normalsequence of steps and direction of flow in thescenario.Flow line (dashed): Line indicates flow toinfrequently-used or conditional tasks in ascenario. Line can also lead to documents involvedin the process flow.

Connects two tasks ina scenario process ora non-step event

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

Does not correspondto a task step in thedocument

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

Corresponds to a taskstep in the document

Process Reference: If the scenario referencesanother scenario in total, put the scenario numberand name here.


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


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 not usuallycorrespond to a taskstep in the document;Reflects a choice tobe made after stepexecution

< F u n c t i o n >



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 bechanged without prior notice.

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

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

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 registeredtrademarks 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 orregistered 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 fortechnology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct 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 without the express priorwritten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or anyother 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 anyparticular course of business, product strategy, and/or development. Please note that thisdocument 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 notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties ofmerchantability, 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 of these 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 nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.

Documents

148 ERP605 Process Overview en BR