Why Did Sales Order Go On A Credit Check Failure Hold when 'Include Payments at Risk' is not enabled?
(Doc ID 788261.1)
Last updated on SEPTEMBER 05, 2024
Applies to:
Oracle Order Management - Version 11.5.10.2 to 12.0.6 [Release 11.5.10 to 12.0]Oracle Order Management - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Order Management - Version 12.2.4 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.
OEXOEORD.fmb
Symptoms
In Applications Release 11i or 12 you are finding that a Sales Order with a value of (say) $986.00 went onto 'Credit Check Failure' Hold at booking despite the fact that the Customer's Credit Limit is $5000.00 and the outstanding receivables balance is zero.
The issue happens for many Customers, so is not a setup problem for any one Customer.
In the reported case, the 'Credit Exposure Report' for this Customer is showing $14,878.12, which seems incorrect since the 'Customer Credit Snapshot' shows that all Sales have payments against them.
Your expectation is that Orders should not go on Credit Check Hold when the outstanding receivables balance is zero and 'Include Payments at Risk' is not checked on the relevant Rule.
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 |
| References |