149 erp606 process overview en xx
Post on 14-Apr-2018
212 Views
Preview:
TRANSCRIPT
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 1/7
Repetitive Manufacturing
SAP Best Practices
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 2/7
© 2013 SAP AG. All rights reserved. 2
Purpose, Benefits, and Key Process Steps
Purpose
Repetitive Manufacturing is commonly used when a production process meets the followingcriteria:o The same or similar products are produced over a lengthy period of time.
o The products produced are not manufactured in individually defined lots. Instead, a total quantity isproduced over a certain period at a certain rate per part-period.
o The products produced always follow the same sequence through the machines and work centers inproduction.
o Routings tend to be simple and do not vary much.
Benefits
Simplified handling of the production process with full cost control
Key Process Steps Creating Planned Independent Requirements
Material Requirements Planning at Plant Level
In-House Production
Confirming Assembly Activities
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 3/7
© 2013 SAP AG. All rights reserved. 3
Required SAP Applications and Company Roles
Required SAP Applications
Enhancement package 6 for SAP ERP 6.0
Company Roles
Shop Floor Specialist
Production Planner Warehouse Clerk
Production Supervisor
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 4/7
© 2013 SAP AG. All rights reserved. 4
Detailed Process Description
Repetitive ManufacturingMake to stock production REM
Repetitive Manufacturing is in this case a purely for make-to-stock production based on runschedule headers. This means that production is controlled without a direct reference to thesales order. Run schedule quantities determine the dates and quantities. Requirements arecreated in Demand Management.
Make to stock production REM-Material requirement Planning
The daily MRP run generates planned orders for the material that is to be produced. Thesystem automatically generates purchase requisitions for purchased parts within the 3-month opening period for the planned order.
Make to stock production REM-Planning table
Within the framework of repetitive manufacturing, planning and control is carried out on thebasis of time buckets. Starting from the existing requirements situation.
Make to stock production REM-Backflushing
Production completion confirmations are simplified and are made with reference to thematerial being produced. The completion confirmation includes the backflushing of components and the posting of production costs
Make to stock production REM-Cost Object Controlling
In repetitive manufacturing, cost will be determined per production version via a productcost collector (product cost per period).
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 5/7
© 2013 SAP AG. All rights reserved. 5
Process Flow DiagramRepetitive Manufacturing
S t r a t e g i c
P l a n n e r
P r o d u c t i o n
P l a n n e r
W a r e h o u s e
C l e r k
E v e
n t
P r o d u c t i o n
S u p e r v i s o r
Operative MRP
Beginning of
Planning Cycle
CO-PA =Profitability Analysis, MRP = Material Requirements Planning, GI/GR = Goods Issue/Goods Receipt
Periodic Plan
Revision
Logistics Planning(144)
Planning Table
CreatePlanned
IndependentRequirements
Range of Coverage
Procurementof Stock
S h o p F l o o r
S p e c i a l i s t
MaterialStaging
RepetitiveManufacturing
Backflush
PostProcessing
List
P l a n t
C o n t r o l l e r
Period-EndClosing“General”
Plant FinancialAccounting
(181)
End Process
Pick List
ReprocessingListGI/GR Slip
InventoryConsumption @Standard Cost
InventoryReceipt @
Standard Cost
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 6/7
© 2013 SAP AG. All rights reserved. 6
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
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
Budget Planning: Indicates abudget planning document
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
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 theprocess 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 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 ina scenario process or a 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 number and name here.
Corresponds to a taskstep in the document
Sub-Process Reference: If the scenario referencesanother scenario in part, put the scenario number,name, and the step numbers from that scenariohere
Corresponds to a taskstep in the document
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 >
7/29/2019 149 ERP606 Process Overview en XX
http://slidepdf.com/reader/full/149-erp606-process-overview-en-xx 7/7© 2013 SAP AG. All rights reserved. 7
© 2013 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.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP 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 other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
top related