What an available-to-promise date means
An ATP date at order entry is a defined estimate. Learn what it counts, how fine it is and whether checking it reserves stock, before your desk accepts it.
Treat an available-to-promise date as a defined estimate until you have checked four things: what supply and demand it counts, how fine the date is, whether the check reserves stock, and who can override it. Accept it as a commitment only when your own system settings answer those four. This explainer rests on vendor documentation for Oracle Order Management, Oracle Order Entry/Shipping and PeopleSoft.
What is the date you are about to promise?
If your order desk quotes a date from a screen, that date is the output of a definition. When a buyer asks “can you ship by Friday,” the answer depends on what the system counts.
Oracle’s Order Management documentation defines the ATP date as the date that a requested quantity will be available to promise. The same documentation defines ATP quantity as current on-hand stock, outstanding receipts and planned production not already committed to sales orders or other sources of demand. We would read both definitions as the starting point, not as proof that the date will hold.
What does an ATP date certify, and what does it not?
Oracle’s Order Management documentation says automatic scheduling in that product can only be at the day level. It also describes the availability check as a quick, rough-cut estimate that views availability by days, not hours. If your customers promise delivery windows within a day, we would ask how that gap is handled.
Oracle’s documentation for ATP inquiry in Order Entry/Shipping says the inquiry is for informational purposes only and does not place demand or reserve on-hand inventory. Its ATP date reflects the first date after the schedule date that the ordered quantity is available. The available quantity represents the quantity available on the schedule date.
PeopleSoft documentation says over-promising can occur when simultaneous reservation runs each exclude the other’s order lines from the ATP calculation. PeopleSoft documentation names the Item/Product Availability Inquiry page, along with the Shortage Workbench, as the tools to monitor and correct situations of over-promising. Oracle Order Management documentation says authorized users can override the ATP schedule date from the sales order window for exceptions.
Is the date a commitment or an estimate?
We would decide by asking what each kind of date is for, then testing it against your own orders.
| Option | We would choose it when | What we would check first |
|---|---|---|
| Quote the system date as is | The check runs against current orders and the time resolution fits the promise | Whether the date is only an inquiry result or is tied to the placed order |
| Quote the date with a stated margin | Customers need a window, not an exact day | Whether the date is at day level or finer |
| Require a second check before confirming | Several lines for the same item are entered close together | Which report shows over-promised items |
| Route overrides to an approver | Exceptions are frequent enough to matter | Who holds the override right |
What to do this quarter
These are our proposals:
- Pull ten recent orders and compare the promised date with the actual ship date.
- Name the person who may override a promised date, and log each override with a reason.
- Write down which supply sources and demand sources your ATP check counts.
- Measure how many promised dates were later changed, by reason.
- Ask whether the check you run at order entry reserves stock or only informs.
What this means for a bottleneck worth $1M or more
We would treat promise-date errors as a redesign topic when they feed rework, expediting and credit requests across many orders, not when they are a one-off. The method we would apply: rules for the predictable promise checks, AI for the messy inputs such as email orders and substitutions, and people approving consequential overrides. AI never decides a promise alone. The wider problem is covered in order entry exceptions. If the real question is a tool or a flow, see order capture tool or order flow redesign. A similar discipline applies to capturing changes in project information.
Limits of this evidence
The sources are vendor documentation describing features. They do not show how often ATP dates are wrong, how often they are overridden, or what they cost in late deliveries. The Oracle and PeopleSoft pages define ATP and its inputs in their own terms, so the claims describe one product at a time. The PeopleSoft material is a fragmented extract, and one Oracle page is a feature overview with limited detail. Nothing here compares manual checks with automated promising or shows effects on customer outcomes.
Questions buyers ask
Does Oracle's ATP inquiry reserve stock?
Oracle's documentation for ATP inquiry in Order Entry/Shipping says the inquiry is for informational purposes only and does not place demand or reserve on-hand inventory.
What does the ATP quantity include?
Oracle's Order Management documentation defines it as on-hand stock, outstanding receipts and planned production not already committed to sales orders or other sources of demand.
Can a promised ATP date still be changed?
Oracle's Order Management documentation says authorized users can override the ATP schedule date from the sales order window for exceptions. PeopleSoft documentation names the Shortage Workbench as a tool to correct over-promising.
Sources
Sources give context. Dates show when each was last checked.