Based on testing in 25R2, using Generate Orders for Subassembly pegs the Constraint Date to the Parent Order Start Date (not the individual Operation Start Dates) for the Subassembly orders that are generated.

The Due Date is smart enough to look at the Operation Start Date for when the Painted Assembly is actually needed, but Due Date has no impact in the Generate Orders for Subassembly action.
We’d like the Constraint Dates for the child orders to be pegged to the OPERATION start date, not the ORDER start date. Is there a configuration we’re missing? We do not use APS.
Other areas of the system seem to look at OPERATION start date to determine Constraint Dates/Promise Dates/Demand Dates. I know on the Order Type you can force the MRP system to “Use Order Start Date for MRP”, which pegs all Constraint dates to the ORDER start date, but there is no setting for generating production orders that says “Use Order Start Date [for pegging demand dates]”. This behavior seems inconsistent with the rest of the system.




