OM: Prevent Booking For Line Generic Holds = Yes, but order still Booking?
(Doc ID 951030.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Order Management - Version 11.5.10.0 to 12.1.2 [Release 11.5.10 to 12.1]Information in this document applies to any platform.
Symptoms
Even with profile option "OM: Prevent Booking for Line Generic Holds is Set" = "Yes"
and placing the customer on "Credit Hold" when releasing the (incorrectly) assigned "Credit Check
Hold" for a newly entered sales order, this order can be subsequently (and unexpectantly) booked.
It is expected that the applied hold should be a system generated "Credit Hold", that
would similarly trigger the profile option into action and prevent booking.
-- Steps To Reproduce:
1. Place the customer of "Credit Hold"
2. Create a new order for this customer.
3. Order goes on Hold.
4. Remove the Credit Check Hold
(Not believed to be correct, "this should not be a "credit check hold" but a "credit hold"
which is systemic generated).
5. Once hold removed, attempt to book the order.
6. Order (unexpectantly) gets booked.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |