Getting a warning when new demand jeopardizes projected availability?

How can I get a warning when entering a sales order so I am aware that this demand jeopardizes availability for other demands? That is the Avail. Check Warning functionality. Nothing new. But, I would like to bring focus to this functionality to emphasize the relevance it has.

There are two parameters in Company Information which are relevant here:

  • "Check Avail. Period Calc.": this defines the period from demand due date where availability calculation will take place. As an example, if this is a sales order, it will check "Shipment Date" + "Check Avail. Period Calc" to determine what is the availability within that period. If availability goes negative, a warning will then arise.
  • "Check Avail. Time Bucket": this defines the bucket of this period. As an example, if we define Month, availability will be rounded to first date of next month when determining the availability period.

Based on this two, together with the demand due date (ie. "Shipment Date" in the Sales Order), the availability calculation is executed to determine if there would be any availability issue in the future when this new demand is entered (ie. projected inventory goes negative). If so, warning arises. This is an indication to the user for action:

  • Should we go ahead and create the demand as is?
  • Should we try to promise (ATP or CTP) this or any of the other demands ahead to remove negative projected availability?
  • ...

This warning should be considered as a tool to anticípate issues before planning is run. If we let planning to resolve this issue we might end on these undesiderable scenarios:

  • Lead time does not allow us to react and planning shows an exception (ie. we might require to consume safety stock to address this demand)
  • Demand is now on the frozen zone and this might mean negative stock in the starting date which is shown as an emergency action

We don't want to run into exception or emergencies in our business. Of course, it might well be the case that planning is able to provide a meaningful action line for our business (ie. this availability issue is later enough that we can react within our lead times and create new replenishment). But, I would still encourage the user to be proactive and check availability when Avail. Check Warning arises.

Comments (2)

  1. Oliver Michael says:

    Hi Sigfredo,

    I agree in that concept, so did a brief test with a simple example. But I'm afraid the system does not behave the way you described – I was easily able to jeopardize without a warning. Will it be possible to have a small chat?



  2. Hi Oliver,

    We already exchanged emails. Thanks for that. And, thanks for your comment here!

    As we found on your scenario, having a short "Check Avail. Time Bucket" results that availability is only checked within that Time Bucket after Shipment Date and this is positive (no availability issue). Thus, it does not go through the entire period (as defined in Check Avail. Period Calc.). This is stated on the note here from MSDN:…/Hh169986(v=nav.71).aspx

    The key here is where it mentions: "Availability is normally checked for the entire period that you define in the Check-Avail. Period Calc. field. However, if supply exists after the planned shipment date that covers all demand at the end of that time bucket, then availability is only checked until the end of that time bucket. For this reason, you may want to increase the period in the Check-Avail. Time Bucket field to discover any existing demand later on the timeline. This will ensure that you get a stockout warning when entering a demand line that cannot be covered because of such later demand".

    To re-phrase the above note, if there is sufficient replenishment after the planned shipment date that covers also the time bucket, the logic will stop there.

    Check Avail. Time Bucket should have some relation with the Check Avail. Period Calc. As an example, if period is 90D and you would like to ensure it is checked till the end of the horizon, we might need to set this bucket to Quarter as an example.

    Thanks for your availability!


Skip to main content