Issue with MRP Re-Pegging When Switching Item from Project-Specific to Common Inventory

There are cases where an item's operational status is switched from “initially procured as project-specific inventory → managed as common inventory in the future.”

 

Purchase requests created with the item's hard pegging level set to “Project” are linked to specific projects or tasks.

However, when subsequently changing the item's hard pegging level to “None” to treat it as shared inventory and then running MRP, existing purchase requests with assigned projects/tasks exhibit the behavior of being re-pegged to demand from different projects.

 

Are there any users experiencing challenges with this operational scenario?

Could you advise on the settings required to achieve our desired operational outcome?