Presentation on theme: "Scenario Overview – 1 Purpose and Benefits: Purpose Benefits"— Presentation transcript:
1 Repetitive Manufacturing of Cement: 389 SAP Best Practices for Building Materials (U.S.)
2 Scenario Overview – 1 Purpose and Benefits: Purpose Benefits Repetitive Manufacturing is commonly used when a production process meets the following criteria:The same or similar products are produced over a lengthy period of timeThe products produced are not manufactured in individually defined lots. Instead, a total quantity is produced over a certain period at a certain rate per part-periodThe products produced always follow the same sequence through the machines and work centers in productionRoutings tend to be simple and do not vary muchBenefitsSimplified handling of the production process with full cost controlKey process flows coveredCreating Planned Independent Requirements and Material Requirements PlanningRepetitive Manufacturing of Portland Cement – looseRepetitive Manufacturing of Portland Cement - 50 lb
3 Scenario Overview – 2 SAP Applications Required: Required SAP enhancement package 4 for SAP ERP 6.0Company roles involved in process flowsShop Floor SpecialistProduction PlannerWarehouse ClerkProduction Supervisor
4 Scenario Overview – 3 Detailed Process Description: Repetitive ManufacturingCreating Planned Independent Requirements and Material Requirements PlanningPlanned independent requirements are used to perform demand management functions. A planned independent requirement contains one planned quantity and one date, or a number of planned independent requirements schedule lines, that is, one planned quantity split over time according to dates.The daily MRP run generates planned orders for the material that is to be produced.Repetitive Manufacturing of Portland Cement – loosePlanning Table for ProductionProcurement of Stock for ProductionRange of Coverage OverviewProcurement of Stock MaterialMaterial Staging for ProductionRepetitive Manufacturing Backflush for ProductionRepetitive Manufacturing of Portland Cement - 50 lb
5 Process Flow DiagramRepetitive Manufacturing of Cement
6 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 eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the documentUnit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the documentProcess 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 hereProcess 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 executionSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: Identifies a printed document, report, or formDoes 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 linesFinancial Actuals: Indicates a financial posting documentBudget Planning: Indicates a budget planning documentManual Process: Covers a task that is manually doneDoes 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 processDoes 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 linesSystem Pass / Fail Decision: This block covers an automatic decision made by the softwareDoes 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 / DocumentExternal to SAPFinancial ActualsBusiness Activity / EventBudget PlanningUnit ProcessManual ProcessProcess ReferenceExisting Version / DataSub-Process ReferenceProcess DecisionSystem Pass/Fail Decision
Your consent to our cookies if you continue to use this website.