I found this as interesting presentation and wanted to share with you all.
Key Process covered:
- Sales Order processing for configurable materials
- Manufacturing
- Delivery
- Billing
- Plant Closing
- Company Closing
Presentation 'Make-to-Order Production with Variant Configuration SAP Best Practices Baseline Package SAP Best Practices.'
Slide 1
|
|
| Make-to-Order Production with Variant Configuration SAP Best Practices Baseline Package SAP Best Practices |
Slide 2
|
|
| Scenario Overview – 1 Purpose This scenario describes a business process, which is typical for companies which are manufacturer of products with variants. Benefits Variants of a product were represented over one configurable material Sales & Operations Planning can be done for predefined material variants Key process flows covered Sales order processing for configurable material Manufacturing Delivery Billing Plant closing Company closing Purpose and Benefits: |
Slide 3
|
|
| Scenario Overview – 2 Required SAP enhancement package 3 for SAP ERP 6.0 Company roles involved in process flows Production Planner Manufacturing Warehouse Clerk Plant Controller Buyer SAP Applications Required: |
Slide 4
|
|
| Scenario Overview – 3 Make-to-Order Production with Variant Configuration The scenario demonstrates sales order processing with materials with pre-selected characteristic values (material variants) and components that are produced according to sales quantities planned for these variants. If the sales order configuration is not available as a material variant, then customer service can configure the material on the order by choosing the required characteristic values. A sales order cost estimate is created on saving the order which is subsequently used to valuate the cost of goods sold. The process is triggered when an order for a configurable material is received from the customer. The customer order is recognized in the MRP run resulting in planned order for production of the material. If insufficient warehouse stock is available, purchase requisitions are created for the raw materials required. When the production order is created, target costs are calculated for the order lot size (preliminary costing). During the production process, costs incurred are updated on the order, which enables you to keep track of and compare target costs and actual costs at any time. Period-end-closing activities are applied to the order. This includes Work In Progress calculation and variance calculation. After this, Work in Progress is settled to financial accounting and production variances are settled to management and financial accounting. Production variances are settled to profitability analysis with the sales order as one of the characteristics. Detailed Process Description: |
Slide 5
|
|
| Process Flow Diagram Make-to-Order Production with Variant Configuration Event Manufact uring Sales Order Entry (MTO) Request for MTO Sales Order Order Confirmation Sales Configurati on is Available as Material Variant? Stock for Material Variant is Availabl e? Manufacturing Steps: Production Order Processing Make-to-Stock (MTS) (145) Transfer Order Processing (creation and confirmation in backround) Logistics Planning: Logistics Planning (144) Delivery Due List Billing Credit Managemen t (108) (Delivery Note) Credit Management (108) Sales Billing Credit Approv ed Credit accept ed(Cus t. 100003) Daily shipment worklist, enough inventory Yes No Make-to-Order Production Warehouse Clerk Credit accept ed(Cus t. 100003) Yes No Pick List Inventory COGS Delivery Note Customer Payment received AR Document Yes No Strategic Planner Customer Service Post Goods Issue |
Slide 6
|
|
Legend SymbolDescriptionUsage Comments 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. Corresponds to a task step in the document Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here Corresponds to a task step in the document 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.
SymbolDescriptionUsage 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 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 Budget Planning: Indicates a budget planning document 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 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. External to SAP Business Activity / Event Unit Process Process Reference Sub- Process Reference Process Decision Diagram Connection Hardcopy / Document Financial Actuals Budget Planning Manual Process Existing Version / Data System Pass/Fail Decision |
