Scenario Overview – 1 Purpose and Benefits: Purpose Benefits

Präsentation zum Thema: "Scenario Overview – 1 Purpose and Benefits: Purpose Benefits"—  Präsentation transkript:

1 Make-to-Order Production w/o Variant Configuration SAP Best Practices Baseline Package

2 Scenario Overview – 1 Purpose and Benefits: Purpose Benefits
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 costing and period-end closing. Benefits Quotation history Billing plan including down payment Change management in production Key process flows covered 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

3 Scenario Overview – 2 SAP Applications Required: Required
SAP enhancement package 4 for SAP ERP 6.0 Company roles involved in process flows Engineering Specialist Production Planner Sales Administrator Billing Administrator Accounts Receivable Accountant Production Supervisor Warehouse Clerk Shop Floor Specialist Product Cost Controller

4 Scenario Overview – 3 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 clearing of a customer account after payment is received. Quotation processing is the first stage of the production process. The scenario starts with an incoming request for quotation. A quotation is then created in the SAP system in response to the customer's RFQ. The customer requests a change to the quotation and a follow-on quotation is created. Finally, the customer accepts the second quotation and a referenced sales order is created. An order confirmation is send to the customer and production 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 produced goods. The process can be enhanced individually by executing optional steps, like serial number creation, subcontracting, QM in production, credit management and plant- and company closing.

5 Process Flow Diagram Make-to-Order Production w/o Variant Configuration: Quotation Processing MTO Event Request for MTO Quotation Sales Administrator Plan Forecast for Finished Good (144) Quotation Processing MTO Quotation accepted? Create, Print and Send Sales Quotation to Customer Create Follow-On Quotation and Send to Customer Print Order Confirmation Yes No Optional: Use Easy DMS to Assign Customer Specification to Quotation Reject First Quotation MTO = Make-to-Order; DMS = Document Management System

6 Process Flow Diagram Make-to-Order Production w/o Variant Configuration: Parts Production for Subassembly Event Need of Raw Material for Subassembly Sales Administrator Create Sales Order with Reference to Follow-on Quotation and Print Order Confirmation Credit Issues Have to be Solved (108) Billing Administrator Create Invoice, Print Down Payment Request and Send to Customer Accounts Receivable Accountant Post Customer Down Payment Production Planner Procurement of Components Using Purchasing Processing (130) Evaluate Stock Requirements Situation

7 Process Flow Diagram Make-to-Order Production w/o Variant Configuration: Parts Production for Subassembly; Technical Change for Finished Good, Procurement of Stock for Final Assembly Event Planned Order Has to be Converted to Production Order Request for Technical Change (Finished Good) Production Planner Create Production Order (Subassembly) Release Production Orders Confirm Production Order Evaluate Stock / Requirements Situation after Technical Change Manu-facturing Material Staging Production Supervisor Review Order Confirmations Shop Floor Specialist Procurement of Components Using Purchasing Processing Post Goods Receipt manually Engineering Specialist Customer Change Request is Considered Product Cost Controller Recalculate Customer BOM Sales Adminis-tration Change Order, Print Order Confirmation and Send to Customer (after Adding Material) Buyer Procurement of Stock Material w/o QM (130) Procurement of Stock Material with QM (127) Procurement & Consumption of Consigned Inventory (139) MM Subcontracting (138) Repetitive Manufacturing (149)

8 Process Flow Diagram Make-to-Order Production w/o Variant Configuration: Final Assembly; Delivery Processing; Billing Processing Event Planned Order Has to be Converted to Production Order Production Planner Convert Planned Order to Production Order Evaluate Stock / Requirements Situation Release Production Orders Optional: Printing Shop Floor Papers Optional: Checking Serial Numbers in Production Order Confirm Assembly Activities facturing Manu Material Staging for Assembly Pick Components (Picking List) Shop Floor Specialist Issue Goods Manually Instead of Picking List Post Goods Receipt for Production Order with Serial Number Assignment Sales Administrator Sales Order Processing: Sales from Stock (109) Delete Billing Blocks Billing Adminsitr. Create Invoice, Print Payment Request and Send to Customer Create Invoice, Print Closing Payment Request and Send to Customer Accounts Receivable Acc. Post Milestone Invoice Post Closing Invoice End Process

9 Legend Symbol Description Usage Comments Symbol Description
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. Diagram Connection <Function> Hardcopy / Document External to SAP Financial Actuals Business Activity / Event Budget Planning Unit Process Manual Process Process Reference Existing Version / Data Sub-Process Reference System Pass/Fail Decision Process Decision

10 Copyright 2008 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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the 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. 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, product strategy, and/or development. 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 to the 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 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 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. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten.