Scenario:
We have:
- Two customers - one "Very important" (VIP) and second "Not-so important" (Regular);
- One item (Golden fleece) on stock (qty = 100); Sales lead time: 2 days. Purchase lead time: 200 days


Story:
1. "Regular" customer orders 100 Golden fleeces. ATP calculates Confirmed ship date (CSD) to +2 days. "Regular" customer receives confirmation of CSD. He's happy, case closed.
2. Few hours later, "VIP" customer orders 50 Golden fleeces. ATP calculates CSD to +202 days (due to "Regular's" order, stock is not available and purchase is required - Purchase lead time is applied). "VIP" customer is disappointed, withdraws the order, resulting with tremendous loss for the organization


Required solution:
1. While simulating delivery dates, Sales person should be provided with easy to use view, which pinpoints the orders, that are blocking "VIP" customer from being served in first order. Additional information should be provided to make the contact as easy as possible.
2. "Release CSD" function should be provided, which should reset the CSD (and, if applied, remove reservation) from particular order from list above. That way, new delivery dates simulation will produce more friendly dates. No additional messages will be required - if the Sales persons want to know, that such release occured - they should set up appropriate alerts from standard d365 functions.


Current state:
At this moment it can be achieved by inefficient and obsolete workarounds (searching, filtering, reporting – lots of clicking to achieve the goal). Sales person has to have many skills, lots of time and patience. Naturally, such approach is not acceptable by customers and thus – modifications occur. Described requested solution could provide a great benefit for standard d365 approach.