SAP S/4HANA Project Manufacturing Management & Optimization

Hi Pablo,

Rahul has asked me to follow up.

Your question about "Effectivity" is a little vague.  The are various forms of "Effectivity" that uses Change Documents that controls which data set from the Master Data is to be used.  The is Date Effectivity, Serial Number Effectivity used by Serial Numbers on Order Headers for selecting the appropriate data set within the Master Data and a thing called Model-Unit  (say like F16 Tail# 1001 verses F16 Tail#1002).  For A&D, I will assume you are referring to Model-Unit.

Model-Unit specific data is tied to other nodes and branches at the top of the Engineering BOM tree that can be unique by tail#  (which can be the same as the MRP BOM tree depending on where on the Engineering BOM tree MRP planning starts while the top part of the Engineering BOM Tree can be built within Project Systems using Network-Activities).

FYI for other readers.   PMMO is an optimization tool to procure and manufacture common part numbers collectively on common Replenishment Orders used for supporting multiple projects to optimize the supply chain process.   PMMO Pegging program uses MRP logic to create records to identify the Project WBS Elements that share ownership of those orders so that PMMO Cost Distribution program can expense their costs to these WBS Elements.

PMMO (unlike GPD) could support a Model-Unit process.  Parameter effectivity by material number, date, serial number and characteristics/classification is used by MRP to find the appropriate Bill of Materials and Routing operation steps for planning while the Model-Unit number is a representation of the Engineering Change Number and the Serial Number as the End Product. For lower level assemblies (when appropriate) inherit the Model-Unit from the Top down.  FYI, PMMO Pegging records include Nexh Higher Order Number, qty and requirement date, as well as, the Top Level Customer Demand, qty and ship date.  MRP by material number within a planning segment still aligns supply with demand according to date using FIFO.  MRP must plan for Model-Unit so that PMMO can support Model-Unit.  Using the "Collective Order" process MRP can support Model-Unit.  From top down, each order within this chain would be supporting a common Model-Unit number because this chain of orders are planned separately from any other planniing segments within a plant MRP Area MRP, even when these Planned/Prod Orders have a Group WBS Element.   If multiple model-units for a particular part number are within the same MRP planning segment, there are no assurances that MRP planning/ execution is correct as to its NHA Order.

Recommend the Top Level Leading Order uses the Operative (Assigned) WBS Element as its account assignment.  Its material master needs to have its MRP Group number not have "Grouping" active.  This sets the "Fixed Peg". It is okay for the Lower Level orders in the Collective Order chain have group WBS Elements because the Top Level is fixed pegged to its WBS Element and all the Lower Level orders will inherit the same WBS Element.  PMMO pegs all of these orders in the Collective to the Leading Order in the "Leading Order Field" on the pegging records.  GPD does not have this feature which is why it can not support Model-Unit.

Date Effectivity and Serial Number Effectivity are single MRP level change controls, (unlike Model Unit which is multilevel) so that MRP knows with are the appropriate BOMs and Routings are needed for planning. Single level Parameter Effectivity types are supported by GPD and PMMO.

Hope this answers your questions.

Best of Luck.

Hank Schrandt