Planning attribute Project Code required for PLO of FG only not for Sub-assemblies and components.

In Oracle Fusion Supply Planning, when using Project Attribute–based planning netting rules with “Attributes for Planned Orders” enabled for the Project attribute and Demand Grouping based on Project Code, the system generates Planned Orders (PLOs) for sub-assemblies and components with the same Project Code as the Finished Good (FG) demand (Forecast and Sales Orders).

However, the business requirement is to associate the Project Code only at the Finished Good (FG) level and not propagate the Project Code to planned orders for sub-assemblies or components.

Even after defining the Hard Pegging Level as “None” for sub-assemblies and components, the system continues to generate PLOs for these items with the same Project Code.