Credit Checking Using Operating Unit Default Limits When Credit Check Is Not Enabled At Customer Site Or Account level (Doc ID 1490376.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Find that Credit Check is NOT enabled at the site or account level for the customers but the credit checking is picking the operating unit default limit set at Operating Unit .

EXPECTED BEHAVIOR
-----------------------
Expected is if the Credit Check is NOT enabled at the site or account level it should not go to the Operating Unit default limits,

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Define Credit Limits at Operating Unit Level (OM User -> Setup ->Credit-> Define Credit Profiles;  Choose Credit Profile type as ‘Operating Unit Default' and for the OU set limits for the currency used.
2. Create a Credit Check Rule and assign it to Transaction Type at Booking Event.                                                      
3. Uncheck Credit Check at Customer / Site level.                  
4. Create a SO and book it (order amount greater than available Exposure). Observe that Orders goes on  Credit failure hold  due to Default Limit even though the Credit Check is NOT enabled at the site or account level.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms