Moving Average Price does not get updated for Project Stock

Question

Hello Experts
We have an Engineer-to-Order implementation for our client. Accordingly procurement is done per project. Each Project issues its PRs which are then converted to POs and recieved into Project Stock.
While assigning the material to the Network activity in Project (using material component) the system uses the price found in the material master (MAP or STD) as a planned cost appended to the project.
Problem:
while procuring the material, when we receive it into Project Stock (Mvt 101 Q + ) the Moving Average Price in the material master does not get updated. this way all newly created material master will never have a moving average price, thus whenever we try to assign them to the project we receive an error message (Cost for Material Component ###Mat.Num### cannot be determined.
Question:
How can I get the system to update moving average price (for all types of stock) based on procurement for project stock.???
Your help is kindly appreciated.

Answer 1

I'm sorry for the confusion
Case:
The T-code is CJ20N Project Builder in PS module
we are assigning material components to network activities under a certain WBS element in the project.
there is a function in the Project Builder to calculate the cost of a network. it uses the costing variant assigned to the network which is PS02 (We get the error here)
The costing variant has a valuation variant which lists a series of strategies  to get the material price. Planned 1 if not then STD if not then MAP. (you can choose between many options via a drop down menu) you can choose 5 consequent options.
The MAP that the valuation variant is coded to get is the Plant Stock MAP -- Or the Project Stock MAP but only Per WBS element.
The MAP that the Actual postings update is the Project Stock MAP only Per WBS element.
This means that if you use a material component to purchase material 123 Acc.As. Q for WBS X for 10 $ then you try to assign a new material component with the same material 123 to WBS Y, the system will not get a MAP. because it's stored in QBEW per WBS element.
This way the system will never get the MAP right.
However, we don't always use project stock to procure for projects, for some requirements we can assign and use plant stock as well for Projects. that way we need the MAP from plant stock.
In the Valuation Variant you can use a User Exit Strategy. The user exit's name is COPCP005
My Suggestion is:
Use the User Exit COPCP005 to calculate the { Total value / the total quantity (MAP) from QBEW + Total value / total quantity (MAP) from MBEW } / 2
which is the MAP for both plant and project stock together, since that we are going to use both.
Q: Is this correct !?