Hi Dave, I think you are looking for the parameter value USERERBPC (Chapter VEN), that basically allows to decreased the quantity of the customer reservation by the quantity sold.

Use this parameter to define how customer reservations are consumed upon order allocation.

No

The customer reservations will never be consumed upon allocation to an order line.
They can still be consumed via the use of the different allocation processes (Allocation action on the Order, automatic allocation process of orders, allocation by product process).

Yes

The customer reservations will be automatically consumed on allocation on an order line.
They may not be consumed using the allocation processes.

On demand

Customer reservations will only be consumed upon allocation to an order line according to the user response to the message: ‘There are reservations for this customer. Do you want to use them for this allocation?’

Julien,

As always, thank you for your response. The issue I am seeing is that if the Sales Order is created but not yet allocated MRP generates WOS's for the sales order as opposed to netting it out from the customer allocations first. Once the sales order is allocated it is not an issue. Perhaps a solution would to be to setup automatic allocations so when the sales order is created it is automatically allocated from the customer allocation pool. Is there a way to control automatic allocations as a BP level?

Hi Dave,
I see your point, if you say 'yes' to the message

but finally remove the quantity allocated, then customer reservation remains unchanged (same if clicking on the No button). As a result, the MRP considers a total quantity needed of: 'initial customer reservation' + 'the newly sold quantity' (from the sales order).

A workaround, would be to automatically allocate the quantity on every sales order to decrease the allocation done againt the customer reservation. And after the sales order creation, you can deallocate the line(s).

To answer you new question, you can run the allocation process in mass by using the function FUNAUTALL (or deallocate using FUNDESALL). The customer range is a standard selection criteria. You can create as well a formula based on a bespoke field in SORDER for more flexibility. 

I hope this helps.

Thanks Julien. I will play around with it and see if I can get something to work the way we need it to.

Dave