This action might not be possible to undo. Are you sure you want to continue?
SAP Best Practices for Electronics and Component Manufacturing
SAP Best Practices
The finished goods are received in sales order stock. Benefits Variants of a product were represented over one configurable material The material and capacity availability can be checked at the moment when the sales order is created . In the assemble-to-order strategy. The customer can choose the features of the configurable material. billing of material and routing are determined in accordance with the configuration in sales order. Material availability is checked at the moment when the sales order is created. key components are planned or stocked in anticipation of the sales order. a service contract can be created accordingly. It helps the customer or salesperson to put together specifications for the product. In the assembly order.Scenario Overview – 1 Purpose and Benefits Purpose This business scenario begins with the configuration of a configurable material at sales order entry. An assembly order is created immediately when the sales order is saved. The product is configured using the variant configuration functionality. If the customer requires after sales service.
material availability check at storage location dependent on BOM explosion Assembly-to-order processing: product assembly in accordance with the configuration (make-to-order production) Delivery processing with creation of serial numbers for configuable material Billing Service contract processing Characteristics inheritance from sales order to service contract Key Process Flows Covered . pricing by using the variant configuration functionality.0 Company Roles Involved in Process Flows Sales Administration Sales Billing Service Agent Production Planner Shop Floor Specialist Production Planner (IM&C) Warehouse Clerk Product Cost Controller Sales order processing with multilevel product configuration.Scenario Overview – 2 SAP Applications Required EhP3 for SAP ECC 6.
WIP analysis. assembly order confirmation.Scenario Overview – 3 Detailed Process Description: MTO Production with Variant Configuration and Assembly Process The product ordered by the customer is configured individually and interactively on the basis of attributes predefined in the sales order. The finished product is withdrawn from the sales order stock and delivered to the customer. and goods receipt. The The billing document is created in order to charge customer. . service contract is created according to the service requirements configured in the sales order. The serial numbers are assigned during delivery processing for after sales service. The data is passed directly to the assembly process and an assembly order is created in the background. The product is assembled in accordance with the configuration (make-to-order production) including: material staging.
Process Flow Diagram MTO Production with Variant Configuration and Assembly Processing .
Process Flow Diagram MTO Production with Variant Configuration and Assembly Processing .
. Line can also lead to documents involved in the process flow. this shape reflects data coming from an external source. Process Reference SubProcess Reference Sub-Process Reference: If the scenario references another Corresponds to a scenario in part. Lines represent different choices emerging from different parts of the diamond. Flow line (dashed): Line indicates flow to infrequently-used process or a nonstep event or conditional tasks in a scenario. or an outside Process that happens during the scenario Does not correspond to a task step in the document Financial Actuals Financial Actuals: Indicates a financial Does not correspond to a task step in posting document a document. report. rather than a specific role. that role. Business Activity / Event: Identifies an action that either leads into or out of the scenario. such as Accounts Payable Role band contains Clerk or Sales Representative. such as unloading a truck in the warehouse. it is used to reflect a document generated by a task step. To next / From last Diagram: Leads to the next / previous page of the Diagram Flow chart continues on the next / previous page Diagram Connection External Events: Contains events that start or end the scenario. This band can also identify tasks common to an organization unit or group. task step in the document Manual Proces s Does not generally correspond to a task step in a document. this shape does not have any outgoing flow lines Budget Planning: Indicates a budget planning document Business Activity / Event Budget Planning Does not correspond to a task step in a document. and the task step in the step numbers from that scenario here document Existing Version / Data 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. Does not usually correspond to a task step in the document. this step does not have any incoming flow lines Proces s Decisio n Process Decision: Identifies a decision / branching point. it is used to reflect a document generated by a task step. Reflects a choice to be made after step execution System Pass/F ail Decisio n System Pass / Fail Decision: This block Does not generally correspond to a covers an automatic decision made by task step in the document. it is used to reflect a task that is manually performed. The other process flow symbols in this table go into these rows. or influence the course of events in the scenario. instead. it is used to reflect a document generated by a task step. or form Does not correspond to a task step in a document. instead. name. instead.Legend Symbol Description Usage Comments Symbol Description Usage Comments <Function> Band: Identifies a user role. which affects the process flow. You have as many rows as required to cover all of the roles in the scenario. Hardcopy / Document Hardcopy / Document: Identifies a printed document. instead it is the software used to reflect an automatic decision by the system that is made after a step has been executed. signifying a choice to be made by the end user. instead. instead. this shape does not have any outgoing flow lines l an e x E r t PAS o t Flow line (solid): Line indicates the normal sequence of Connects two tasks in a scenario steps and direction of flow in the scenario.Corresponds to a step manner in the scenario task step in the document Manual Process: Covers a task that is manually done Unit Process Process Reference: If the scenario references another Corresponds to a scenario in total. put the scenario number. this shape does not have any outgoing flow lines Unit Process: Identifies a task that is covered in a step-by. put the scenario number and name here.
SAP does not warrant the accuracy or completeness of the information. 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. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. SAP shall have no liability for damages of any kind including without limitation direct. graphics. SAP NetWeaver. text. either express or implied. product strategy. SAP. SAP Business ByDesign. or consequential damages that may result from the use of these materials. 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. xApp. developments. The information contained herein may be changed without prior notice. . Duet.Copyright 2009 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. National product specifications may vary. and/or development. fitness for a particular purpose. Data contained in this document serves informational purposes only. This document is provided without a warranty of any kind. special. or other items contained within this material. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. or non-infringement. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. SAP assumes no responsibility for errors or omissions in this document. links. xApps. R/3. including but not limited to the implied warranties of merchantability. The information in this document is proprietary to SAP. ByDesign. The statutory liability for personal injury and defective products is not affected. This limitation shall not apply in cases of intent or gross negligence. This document contains only intended strategies. indirect.