Last updated on MARCH 28, 2017
Applies to:Oracle Order Management - Version 126.96.36.199 to 12.0.6 [Release 11.5.10 to 12.0]
Information in this document applies to any platform.
***checked for relevance 19-May-2013***
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.
Credit Check Rule : Booking
Overall Limit = 5,000.00
Exposure = 14,878.12
Available = -9,878.12
All payments were made by credit card.
An OM Debug output was captured when booking this particular order, and it can be seen that the
'l_include_risk_flag = Y' even though the Credit Check Rule used 'Booking' does not have the box checked for 'Include Payments at Risk':
Credit rule setup values
l_uninvoiced_orders_flag = Y
l_orders_on_hold_flag = Y
l_include_tax_flag = Y
l_shipping_horizon = 31-DEC-12
l_include_risk_flag = Y
l_quick_cr_check_flag = N
l_freight_charges_flag = Y
l_open_ar_balance_flag = Y
l_incl_external_exposure_flag = N
l_include_returns_flag = N
and credit exposure seems to be including payments at risk:
Begin OM Exposure calculation
l_usage_total_exposure = 14878.12
l_cum_total_from_ar = 0
l_total_from_br = 0
l_cum_payments_at_risk = 14878.12
l_payments_at_risk = 14878.12
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms