Currently it is documented that planning optimization forecast consumption does not consider sales orders once they have been picked, invoiced, shipped, delivered, etc. The demand is added back into forecast once the status on an open order moves into one of the above mentioned and PLOP is run again. There is a critical need in many business planning functions to consider these orders to prevent over purchasing and overproduction. 

Example Scenario: The "on-hand" or "minimum" stock point is truly a safety stock and used to handle variation in our forecast. It is not there to support customer weekly orders. 

We build weekly to forecast to support the forecasted demand, so as the week progresses we need the ability to see how many we have sold vs produced to ensure we are covering our forecasted demand. 

We have large volume customers that place orders daily and weekly. Once those orders ship and get added back into forecast after the next MRP run, we are going to appear very short to cover demand. This will trigger planning to cut more orders, buyers to expedite material, and the factory to work unnecessary overtime to produce parts that we truly do not need.

Please consider adding back to the consumption logic calculation for planning optimization to include all sales orders statuses. Picked, Invoiced, Shipped, Etc. to ensure accurate planning signals.

Microsoft issue 674900