What Is Repetitive Manufacturing

Explain what is repetitive manufacturing.

Repetitive manufacturing is period based planning and not based on orders. Normally same products will be manufactured over longer period of time.  Products will not change frequently. 

Confirmation is from backflushing and settlement is through from product cost collector for the period. Confirmation will be without ref to planned orders. 

Planned orders are sufficient to carry out shop floor activity. In master data production versions and cost collector is a must where this is not mandatory in discrete.

You do these steps for rem production:

 MM01   : Material Master 
                -  MRP - 4 view you click rem
 CS01     : Create Bom
 CR01     : Create Work Center
 CA21     : Create Rate Routing
 MM02   : Prodn Version
 MD61    : Create PIR
 MC74    : Transfer PIR to Demand
 KKF6N  :  Create Product Cost Collector
 MB1c    :  Create Stock
 MD02    :  MRP run
 MFBF   : Rem Back Flush

The detailed sequence of T.Codes for REM including Std cost estimate:

Material master - MM01
BOM - CS01
Price Planning - KP26
Work Center - CR01
Rate Routing - CA21
Material Master Change, enter production version - MM02 (MRP 4 View)
Product Cost Collector - KKF6N
Costing - CK40N
Backflushing - MFBF

Get help for your SAP PP Problems
SAP PP Forum - Do you have a SAP PP Question?

SAP Production Planning Books
SAP PP Certification, Interview Questions and Configuration Books

SAP PP Tips
SAP PP Tips and Production Planning/Control Discussion Forum

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk.
 The content on this site may not be reproduced or redistributed without the express written permission of
www.erpgreat.com or the content authors.