Explain SAP PP Internals: BOM, Routing, And MRP Logic

SAP Production Planning works through a chain of linked data. A material is not planned only because a demand exists. The system checks the BOM, reads the routing, applies planning settings, calculates requirements, and then creates the right planning proposals. Understanding this internal flow is important for anyone taking a SAP PP Course, because the real value of SAP PP comes from knowing what happens between demand and production.

SAP PP Is More Than a Production Order

The SAP PP process starts much earlier than the production order. The system needs a valid material master, BOM, routing, work centre, production version, and MRP settings before it can make a useful production proposal.

The internal logic can be understood as:

Demand → MRP calculation → BOM explosion → Component requirement → Procurement proposal → Production planning

Routing works beside this process. It tells SAP how the finished material will move through operations. It contains work centres, operation times, control keys, and sequence information. For learners attending SAP PP Training in Delhi, this connection is worth studying at the table and field level, not just through transaction screens. 

BOM Internals: How SAP Knows What to Produce?

A Bill of Material is a structured list of components required to produce a parent material. But SAP does not treat the BOM as a simple list.

A BOM contains information such as:

• Header data
• Item data
• Component quantity
• Item category
• Validity dates
• Plant assignment
• Alternative BOM
• Scrap settings
• Component status
• Engineering change information

The header identifies the BOM and its main control information. Items identify the components. During planning, SAP can perform BOM explosions. This means it breaks the finished product into lower-level components.

The technical structure may look like:

Level 0: Finished Material

↓

Level 1: Assembly A + Assembly B

↓

Level 2: Components under Assembly A

This is why a small change at a lower BOM level can affect several finished products.

BOM Explosion Is Controlled

SAP does not blindly explode every BOM it finds. It checks several conditions.

Important checks include:

1. Material and plant
2. BOM usage
3. Validity date
4. BOM status
5. Alternative BOM
6. Production version
7. Lot size
8. Change number
9. Special procurement settings

The production version becomes especially important when more than one valid production structure exists.

Routing Internals: How SAP Defines the Process?

BOM answers what is required. Routing answers how the material is produced. A routing contains a sequence of operations. Each operation can be linked to a work center. It can also contain standard values for activities such as machine time, labor time, setup time, and processing time. A simplified routing structure is:

The work center is important because it connects routing information with capacity and scheduling. This is where SAP PP becomes different from a simple material planning system. It does not only calculate material quantity. It can also calculate when work should happen and where capacity is required.

Also Visit to Related Courses:

SAP CPI Course

SAP Material Management Course

SAP SuccessFactors Course

SAP HCM Course

SAP S4 HANA Course

SAP QM Course

SAP EWM Course

SAP FICO Course

How BOM and Routing Work Together?

BOM and routing have different jobs, but production planning needs both.

BOM tells SAP:

Which materials are required?

Routing tells SAP:

Which operations are required?

A production order brings these structures into one execution object. When a production order is created, SAP can copy relevant BOM components and routing operations into the order. The production order then becomes a working document for production. This also explains why changing a master record does not always change an already created production order. The order may already contain copied data.

That is an important internal concept:

Master data is the source. Production order data is the execution snapshot.

Therefore, changing a BOM after an order has been created does not automatically mean that the existing order will contain the new component.

MRP Logic: Where Planning Becomes Dynamic

MRP, or Material Requirements Planning, calculates whether the available supply can cover the required demand.

The basic calculation is:

Available Stock + Receipts − Requirements = Net Requirement

But actual MRP processing involves many more checks.

SAP considers:

• Stock
• Sales requirements
• Planned independent requirements
• Existing purchase orders
• Production orders
• Planned orders
• Reservations
• Safety stock
• Lot size
• Procurement type
• Scheduling data
• BOM structure
• Planning strategy

If available supply is not enough, MRP can create a procurement proposal. For an internally produced material, this may be a planned order. For an externally procured material, it may create a purchase requisition, depending on configuration. The important point is that MRP does not directly mean “buy this material.” It first determines the shortage and then applies procurement rules.

MRP Does Not Plan Everything in One Step

MRP usually works from the top-level requirement down through the product structure.

Suppose a finished material needs an assembly. MRP first identifies the requirement for the finished material. After the BOM explosion, it creates a dependent requirement for the assembly.

The assembly may then require its own components.

So the internal planning chain becomes:

Independent Demand

↓

Finished Product Requirement

↓

BOM Explosion

↓

Dependent Requirement

↓

Lower-Level BOM Explosion

↓

Procurement Proposal

This multi-level logic is one of the most important areas to understand in advanced SAP PP.

MRP Type Changes the Planning Logic

The MRP type in the material master controls how the material is planned.

Common planning approaches include:

• MRP-based planning
• Reorder point planning
• Forecast-based planning
• Consumption-based approaches

With standard MRP, SAP looks at requirements and available supply. With reorder point planning, the planning trigger can be linked to a stock level. This means two materials can have the same stock quantity but receive different planning results because their MRP settings are different.

For students doing SAP PP Training in Noida, this is a useful area for practical work because MRP results become easier to understand when you compare the same material under different planning settings.

Lot-Sizing: Why MRP May Suggest a Different Quantity

A common mistake is to assume that MRP always creates the exact shortage quantity. It does not. Lot-sizing rules can modify the proposed quantity. Suppose the net requirement is 75 units. If the lot size is fixed at 100, MRP may propose 100 units.

Other rules can include:

• Exact lot size
• Fixed lot size
• Minimum lot size
• Maximum lot size
• Rounding value
• Period lot sizing

This is why the MRP result must be read together with the material's planning settings.

Scheduling Connects MRP With Time

Quantity alone is not enough for production. SAP also needs to determine dates. Basic scheduling considers:

Basic start date → Operation scheduling → Basic finish date

Lead times, operation durations, work center calendars, and scheduling parameters influence these dates.

The routing provides operation-level information. Work centers provide capacity-related information. MRP uses scheduling logic to determine when procurement or production should begin.

This creates a link between:

Material requirement date → Production start → Operation dates → Component availability

If the dates are wrong, production may start too late even when the quantity calculation is correct.

Production Version Is a Key Control Point

Production versions are often treated as basic master data, but they can become a major control point in complex planning.

A production version can define:

• Which BOM is used
• Which routing is used
• Validity period
• Lot-size range

This becomes useful when a material has different manufacturing methods. Instead of treating BOM and routing as unrelated objects, the production version can connect the correct combination. This helps avoid a common planning problem where the system has multiple valid structures but needs a clear rule for selecting one.

The second important lesson for an SAP Online Course is that MRP results should always be traced back to the master data used during planning. Looking only at the final planned order is not enough.

Where MRP Problems Usually Start

Many MRP issues are not caused by the MRP run itself. They often begin with master data.

Typical causes include:

• Incorrect BOM quantity
• Wrong BOM validity
• Missing production version
• Incorrect procurement type
• Wrong lot size
• Incorrect MRP type
• Missing routing operation
• Incorrect work center
• Wrong lead time
• Incorrect scheduling settings
• Incorrect component stock
• Wrong special procurement key

A good SAP PP consultant does not immediately change the MRP configuration. The better approach is to trace the result backward.

Planned Order → Material → MRP Settings → Production Version → BOM → Components → Demand/Supply

This method helps identify the actual source of the problem.

FAQs

What is the main difference between BOM and routing?

BOM defines the components required for production. Routing defines the operations needed to produce the material. MRP mainly uses the BOM structure for material requirements, while routing is important for operation scheduling, capacity, and production execution.

Why is the production version important in SAP PP?

The production version can connect a material with the correct BOM and routing. It also controls validity and lot-size conditions. This becomes important when a material has multiple manufacturing structures.

Can MRP create different quantities for the same shortage?

Yes. Lot-sizing rules can change the planned quantity. Minimum lot size, fixed lot size, rounding value, and maximum lot size can all affect the final proposal.

Does changing a BOM immediately change an existing production order?

Not necessarily. Production orders contain their own copied execution data. A BOM change mainly affects future planning or orders, depending on the relevant update and change-control process.

Why can MRP give an unexpected result?

The reason can be in demand, stock, receipts, MRP type, lot sizing, procurement type, BOM selection, production version, scheduling, or other master-data settings. The result should be traced back through these objects instead of assuming the MRP run is wrong.

Sum up,

SAP PP becomes easier to understand when BOM, routing, and MRP are treated as one connected system. BOM controls the material structure. Routing controls the production process. MRP connects demand with available supply and creates planning proposals. Production versions help SAP select the right manufacturing structure. The real technical skill is not memorizing transactions. It is tracing how SAP moves from demand to components, operations, dates, and supply proposals.