Skip to Content
Author's profile photo Former Member

Why is repetitive manufacturing treated like a black sheep in the SAP functions family?

Repetitive manufacturing! It has its own menu area in SAP! It’s a bit scary to some, a mystery to most. Some people touched it back in the late nineties when it wasn’t quite ready yet and some heard this and that about it over the past few years. Most people I have dealt with, do not know why it is there and what it can do. And then there are a lot of people who guess and interpret the functionality in their own way. So please allow me to take a stab at it as well.

Unfortunately you can’t find much documentation about it. So you will have to do quite a bit of trial and error. Since I am a true believer in RepMan and a convinced advocate (there are probably some folks out there scratching their head and wondering when I will ever give up promoting it – my SAP Mentor shirt reads “Use MF50” on the back) I spent considerable time and effort making it work for my clients. I am not 100% there yet, but my never ending quest continues. Here are some thoughts. You will find more detailed suggestions on how to make it work in some future blogs. 

Misconception about repetitive manufacturing number 1: “since I am a discrete manufacturer I can’t use it!”

Repetitive manufacturing should not be classified as a third option after discrete and process manufacturing. Discrete manufacturing is roughly everything that after you put it together, you can take it apart again. An automobile, a telephone, a coffee maker. Process manufacturing is, as its name applies, a process to combine and mx ingredients into something you can NOT take apart anymore. Take orange juice, tomato soup or paint. Repetitive manufacturing has nothing to do with that classification but allows you to execute either one in a much more simplified way (no need to convert planned orders or post an individual goods issue for every component). RepMan ist just not good in a job shop environment where every part is different and needs its own order and spec. However, if you have standard parts and you make them again and again using the same instructions in a routing and BoM, you are a repetitive manufacturer. For some reason many people refuse to have their operations classified as a repetitive shop. In one instance the planners of a maker of water faucet filters vehemently defended their position that they don’t operate like a repetitive manufacturer. They put through 75,000,000 pieces per day in that one plant alone and have 12 different filters. This is not a blog to point out the advantages those planners would get from using SAPs repetitive manufacturing module. Otherwise I would write another 25 paragraphs on this. 

Misconception about repetitive manufacturing number 2: “you have to make millions of the same thing every day!”

Not true! Wouldn’t you say that if you only make one product a day, but it’s the same product, you repeat the process? Repetitive manufacturing with SAP allows you to schedule by takt, amongst other things, and that helps you to smooth a production program that suffers from uneven and unpredictable demand. It also allows you to schedule your basic make to stock products and let the make to orders flow in as required. This is very easy in RepMan and very difficult with regular production or process orders. So if you have repeatable products, no matter how small the volume, take advantage of the more efficient transactions. RepMan was developed by SAP coming from the need to plan and execute more efficiently. 

Misconception about repetitive manufacturing number 3: “we can’t control our cost with a cost collector!”

In RepMan you collect cost on a so-called product cost collector. So you don’t need to post cost for every order separately but for the product collectively. If your costing people tell you that that does not work for them, ask them to explain to you why. And don’t give up on having the opportunity to save a load of money in producing the right product at the right time in the right quantity at the right place just because someone says “I don’t know why, but we need to cost every order separately and we have done so for 50 years. 

Misconception about repetitive manufacturing number 4:  ” backflush is not an option for us and a must for repetitive manufacturing”

First: you do not have to backflush. Second: why not doing it? In my mind there is absolutely no need to have inventory management by the minute. The smallest unit in inventory management, planning or MRP is days. So it should be sufficient if you post a GR for the lines at the end of the day and have the items backflushed accordingly. (there is also reporting point backflush for cycle times in excess of one day)

Misconception about repetitive manufacturing number 5:  “repetitive manufacturing only has planned orders. I need production orders”

When MRP generates supply elements for products setup for repetitive manufacturing, it creates orders of the type PE (not LA which are planned orders which get turned into production orders). A PE type order does not need to be converted. It’s executable right away and it can use a rate routing, a recipe or a standard routing. It may also be immediately scheduled and costed and capacity checked and fixed. It’s a beautiful thing and makes your life as a planner much more enjoyable. 

Repetitive Manufacturing excites me (I know, I should get a life) with its simplicity in execution, effectiveness in usability and ability to automate a complex process. It has many features which allow you to practice ‘lean’ with its line balancing, sequencing board, takt-based scheduling and mixed model planning. It is worth looking into and has been proven to increase visibility into the process, reduce waste in the supply chain (lean) and improve flexibility to customer demand (agile).  “Use MF50!”

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Dear Uwe,

                      I appreciate your detail REM process myths over SAP community those uses PO. We are also mostly into REM knows the pain.But, I do not know why SAP stopped exploring this REM and continues with PO and PI. I want to ask you one thing regarding, how Version based costing can be done in REM.Since to backflush in REM, you required only one active Production version. How to achieve this ? How this can be achieved in PO scenario. ? pleas explain?



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Praveen

      forgive me if I misinterpret your question but if you ask how to make sure that the backflush - and therefore the costing - selects a specific production version, then I have the following answer:

      when the repetitive order is generated, a routing and a BOM is selected. The selection is done by way of picking a production version. The production version clearly identifies a routing and a BOM to be used. Should you have multiple production versions, the one production version which falls in either the validity range of the requirements date or the lot size range of the required quantity is selected

      Author's profile photo Former Member
      Former Member

      Dear Goehring,

                               Thanks for your reply. Yeah I know that there should be only one Production Version to be valid one for REM. IN addition to the SERIAL NUMBER Consumption in REM , I want to know if there is any work around to delete MF47 (Re Processing List) entries. I do not know why SAP provided this option.

      Is there any work around for above ones Sir.



      TAFE -India.

      Author's profile photo Ritesh Dube
      Ritesh Dube

      Nice Blog Uwe,

      REM is fantastic indeed, but can you commnet , why we dont have facility to comsume seriallised components here, see


      SAP Note 100621 - MFxx with components requiring serial


      Appriciate if you suggest some work around if its possible.



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      I'm sorry Ritesh, but I have never had to look into this problem...

      will let you know if anything develops on my side

      Author's profile photo Eric Chen
      Eric Chen

      Hi Uwe,

      a special documentation to introduce REM, good understanding of REM procedure,

      I have learn a lot from it, thanks a lot.

      BTW, I have same question of Ritesh, can not consume serialized components in REM with Notes 100621, appreciate your any suggestion.

      Author's profile photo kanapon gunprom
      kanapon gunprom

      For me i would like to propose customer to use REM because i think production planning is easier than production order.

      but i always struggle with one requirement.

      Can REM track and traceability from FG to RM?

      please kindly give an advise.

      Author's profile photo Former Member
      Former Member

      Yes you can track from FG to RM using MB56.


      Your problem would be if you don´t do backflush, because the planned order disappears and there is no reference that let you know if you consume the components or not... or if there is something pending...

      Author's profile photo Former Member
      Former Member

      I still believe discrete is better than repetitive in most of the cases...

      I think most of the plants wants control over their process... so for me in most of the cases is discrete or process unless it is really a repetitive manufacturer....


      some of the issues that I found with repetitive manufacturing.....

      Planned orders are deleted once you finish them, there is no way you can evaluate the efficiency of your lines once you finished production...

      Another problem is that you cannot use alternative unit of measure for the planned orders..

      Talking about converting orders in discrete or pp-pi?? is just one click.... you can create and release orders automatically.. you can even confirm order´s in mass...

      Another issue is that if you maintained separately the scrap % in the BOM, backflush does not consider it unless you implement a note to activate the flag in MFBF....


      I have implement SAP for 12 years and have use all types of manufacturing... REM has the advantage of not using reservations, that´s something good if you do backflush but if you don´t do it, then there is no reference of what is pending for components consumptions...


      This is just my opinion but I believe not everything works with REM.