For Internal Sales Orders, ATP Promises Date In Future, When Have Onhand In Stock, Items From Planned Order Ignored
(Doc ID 1413788.1)
Last updated on FEBRUARY 01, 2022
Applies to:Oracle Global Order Promising - Version 11.5.10 and later
Information in this document applies to any platform.
In an R11.5.10 Instance (Decentralized APS Environment, with ATP Based on Planning Output):
ATP promises date far in future, even when having on-hand in stock (items from planed order are ignored)
Example: Would like to transfer 5000 from M2 to M1 to cover the external sales order. And have 9000 on hand in M2, so this should not be a problem. However, when releasing the planned order in M1, the system only sees 4000 (9000-5000) available in M2. So, the system is trying to first cover the planned order demand and then the internal sales order. The internal sales order can only find 4000 available and the replenishment is therefore pushed to the 15th of December.
It means, that quantity from planned order was ignored. If there will be 10,000 onhand in M2, then dates will be correct. But why it should have double quantity, when quantity from planned order will be used for external sales order?
Not concerned of how the system is calculating when it gets 15th of Dec. That is not the point. The point is that there are quantities in stock in the source organization, which cannot be transferred because it is reserved to the external sales order.
The example provided may basically mean that customers cannot keep their promises to their customer.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document