You have implemented automatic requirements grouping for projects. Requirements are grouped for material "cabin" but not for "fork". What might be the reason?

Question

Options

• AThe grouping indicator of the top WBS element is set to a single MRP group
• BThe network is set to no grouping for specific MRP groups
• CThe MRP group for fork is deactivated for grouping
• DThe project definition is set to no project stock

• A
  3% (1)
• B
  6% (2)
• C
  78% (25)
• D
  13% (4)

Explanation

Option C is correct because requirements grouping in SAP Project System is controlled at the MRP group level - if the MRP group assigned to material "fork" has the grouping indicator deactivated in its configuration, requirements for "fork" will not be grouped, even though the feature is active system-wide. Since "cabin" belongs to an MRP group where grouping is enabled, it groups correctly, creating the exact selective behavior described.

Why the distractors are wrong:

• A is wrong because the grouping indicator on the top WBS element controls whether grouping is used at all for the project - it wouldn't cause one material to group while another doesn't.
• B is wrong because network-level settings do not selectively suppress grouping per material; the MRP group itself is the controlling object.
• D is wrong because the project stock setting affects inventory management and account assignment, not whether requirements are consolidated during the MRP run.

Memory tip: Think of it this way - the MRP group is like a "grouping passport" stamped on each material. If "fork's" passport has the grouping stamp missing (deactivated), it gets turned away at the gate, while "cabin" with a valid stamp passes through. The project and network settings are like the airport itself - they don't single out individual travelers.

No community discussion yet for this question.