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
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
$ strings -a $ONT_TOP/patch/115/sql/OEXUCRCB.pls |grep '$Header'
阅读(1146) | 评论(0) | 转发(0) |
