Skip to Content
Author's profile photo Former Member

MRP: Planning Mode – why choose re-explode BOM and Routing?

Another of the many MRP settings within SAP is the Planning Mode setting.  The option reactivates unfirmed procurement proposals and, if necessary, adapts the quantity and date to the new planning situation. The BOM is re-exploded only for procurement proposals that are to be adapted.  It will reactivate unfirmed procurement proposals and, if necessary, adapts the quantity and date to the new planning situation. The BOM is always re-exploded; and regenerates unfirmed procurement proposals completely. (this description is from F1 help in transaction MD02 for the field)

This setting offers you three different options for the planning run. The first is Adapt Planning Data which is used for most normal executions for only considering updates to planned orders if there were changes to the planning situation for the material.  The third setting is the Delete and Recreate
Planning Data, which does exactly what it means; deletes and recreates the planned orders that have been marked for re-planning.  Now the second is Re-explode BOM and Routing which is a feature not fully appreciated. This is the topic that I want to quickly explain a little further.

re-explode BOM and routing 1.png

So what exactly does the re-explosion of the BOM and routing mean?  Pretty much what it says, but the important part is also included.  Whenre-exploding the routing, and assuming you are running with lead timescheduling and capacity requirements, this will mean that any updates to workcenters for scheduling available capacity will now be included in the planning run.  The benefit of this option is that it will pick up your updates and reallocate the capacity as required.  Additionally, the work will be scheduled across the work center according to the new scheduling parameters.

This is very beneficial for your capacity planners to know that the MRP planning run will begin picking up capacity and scheduling updates each time the planning run is executed. 

Assigned Tags

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

      Hi Michael,

      I was in the impression when option number 3 is used, besides recreating the planned orders, etc. it will read BOM and routing and it will take the latest one.

      so I thought option 3 is 2 plus deletion and recreation of new planned orders, isn't?

      thanks,

      neo

      Author's profile photo Caetano Almeida
      Caetano Almeida

      Hello

      Planning mode 3 should be avoided on a productive system. It causes performance issues and another side-effects described on the following document:

      Planning mode 2 should also be generally avoided, since MRP will take a lot of time to re-explode the BOM, the routing and scheduling all the planned orders again.

      In my personal opinion, planning mode 2 should only be used in case of mass master data changes.

      I also wrote the following document explaining why planning mode 3 should be avoided:

      MRP: Why shouldn’t I use planning mode 3 on a productive system?

      BR

      Caetano

      Author's profile photo Former Member
      Former Member

      Hi Caetano,

      We use mode 2 on the production system but on spot materials and once it a while.

      Let me read your document.

      Another question, have you created a document that explain the creation of planned order and or purchase reqs. in side the horizon? I am not able to grasp that really well.

      Ciao,

      neo

      Author's profile photo Caetano Almeida
      Caetano Almeida

      Hello Neo

      It's OK to run MRP with planning mode 2 from time to time, but on a daily basis it generally not necessary and leads to performance issues.

      Are you refering to the document Indicator 'Create Purchase Requisitions' is not considered by MRP?

      I wrote this document for an specific issue where this customizing setting is not considered. If you want to understand the underlying customizing in more detail, please read note 23922.

      If you still have further question, please open a thread.

      BR

      Caetano

      Author's profile photo Former Member
      Former Member

      I have read your document MRP: Why shouldn't I use planning mode 3? and I agreed with point 2. actually that is what I learnt and knew it.

      "in case a BOM change, a flag is marked on the planning file"

      Thanks for the other tips in there specially about the number ranges.

      thanks a lot,

      neo

      Author's profile photo Axel Vermeulen
      Axel Vermeulen

      Hi Caetano,

      I stumbled on this old blog post and your interesting comment. I'm interested in the reasons why planning mode 3 should be avoided in a productive system. Unfortunately, the link brought me to a page which says the content is no longer available

      Would it be possible to share the document again?

      Thanks a lot!

      Kind regards,

      Axel

      Author's profile photo Caetano Almeida
      Caetano Almeida

      Hello Axel

      It was a very old blog that was removed when SAP Communities migrated to the new platform.

      In Classic MRP, planning mode 3 should be avoided for several reasons:

      • Performance - There are too many deletions and inserts on the tables, as MRP needs to delete all the planned orders, explode the BOMs, read routings and schedule all the planned orders.
      • Number ranges - With constant deletion and recreation of planned orders and requisitions, number ranges will be consumed very quickly, which is something that should be avoided.
      • Too many entries being created in table EKET increase the risk of overflow in fieldĀ ETENR

      In general, it is enough to run MRP with planning mode 1, as it will automatically re-explode the planned order BOMs, in case of a BOM change.

      See note 78867 for details.

      Regards,
      Caetano

      Author's profile photo Axel Vermeulen
      Axel Vermeulen

      Many thanks!