ShowDoc

Page 1 of 2

My Oracle Support (the new MetaLink)

Bookmarks

Admin

Profile

Feedback

Sign Out

Help

Headlines Knowledge Browser Advanced Search

Knowledge

Service Request

Collector

Patches & Updates

Community

Certify

Bug Search Go Advanced Saved Searches

Quick Find Knowledge Base

Did this article help solve your problem? Select

Would you recommend this document to others? Select

Submit

TIP: Click help for a detailed explanation of this page.

Bookmark

Go to End

Subject: Credit Checking Limits Hierarchy Doc ID: 365866.1 Modified Date : 11-OCT-2007 In this Document
Purpose Scope and Application Credit Checking Limits Hierarchy

Type: BULLETIN Status: PUBLISHED

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:
Oracle Order Management - Version: 11.5.9 to 11.5.10 Information in this document applies to any platform.

Purpose
This document talks about how the credit limits are being used for Credit Checking in Order Management.

Scope and Application

Oracle Applications - Order Management 11.5.9 and 11.5.10 - Credit Checking

Credit Checking Limits Hierarchy

In Oracle Receivables, you can setup Credit limit (which is nothing but the overall credit limit) and order credit limit at the following levels: 1. Item category level 2. Site level 3. Customer level 4. Party level (This level is applicable only if Credit Management is installed) 5. Operating Unit Default level. For Customers in 11.5.10 - Before 11.5.10 CU2 (If OEXUCRCB.pls is less than 115.82.11510.2) 11.5.9 - Before Patch 4473667 (If OEXUCRCB.pls is less than 115.69.1159.14) 1.Item category level If Credit Check not enabled => Go for Site Level If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Site Level If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 2.Site level If Credit Check not enabled => Go for Customer level If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => No Credit Check If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 3.Customer level If Credit Check not enabled => Go for Party level is Credit Management is installed else go for Operating unit default level If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => No Credit Check If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them

https://metalink2.oracle.com/metalink/plsql/f?p=130:14:4024695488081550411::::p1... 18-08-2009

ShowDoc

Page 2 of 2

4.Party level (This level is applicable only if Credit Management is installed) If Credit Check not enabled => Go for Parent Party,if any available, else go to Operating Unit Default limits. If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => No Credit Check If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 5. Operating Unit Default Level If both credit limit and order credit limit are NULL/BLANK => No Credit Check If either credit limit or order credit limit is NOT NULL => Use them

For customers in 11.5.10 - After 11.5.10 CU2 (if OEXUCRCB.pls is equal or higher than 115.82.11510.2) 11.5.9 - After Patch 4473667 (if OEXUCRCB.pls is equal or higher than 115.69.1159.14) 1.Item category level If Credit Check not enabled => Go for Site Level If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Site Level If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 2.Site level If Credit Check not enabled => No Credit Check If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Customer level If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 3.Customer level If Credit Check not enabled => No Credit Check If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Party level is Credit Management is installed else go for Operating unit default level If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 4.Party level (This level is applicable only if Credit Management is installed) If Credit Check not enabled => No Credit Check If Credit Check is enabled and both credit limit and order credit limit are NULL/BLANK => Go for Parent Party, if any available, else go to Operating Unit Default limits.If party hierarchy is setup using Trading Community Architecture, then credit checking will look into this hierarchy also, to check if there is any parent available. If yes, then it looks into the limits of the parent also. If parent limits are also NULL, then it goes for Operating Unit Default level If Credit Check is enabled and either credit limit or order credit limit is NOT NULL => Use them 5. Operating Unit Default Level If both credit limit and order credit limit are NULL/BLANK => No Credit Check If either credit limit or order credit limit is NOT NULL => Use them Help us improve our service. Please email us your comments for this document. .
My Oracle Support (the new MetaLink)
Copyright 2006, Oracle. All rights reserved.

Bookmarks

Admin

Profile

Feedback

Sign Out

Help

Legal Notices and Terms of Use | Privacy Statement

https://metalink2.oracle.com/metalink/plsql/f?p=130:14:4024695488081550411::::p1... 18-08-2009