Results for “oe_credit_check_rules”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OE_CREDIT_CHECK_RULES table is a core configuration object within the Oracle Order Management (ONT) module of Oracle E-Business Suite. It stores the user-defined credit check rules that determine how the order-to-cash credit checking process evaluates a customer's creditworthiness before an order is entered or shipped. Each row represents a named rule that bundles together a set of evaluation flags, tolerance thresholds, aging parameters, and result-handling behavior. When Order Management performs credit validation, it applies these rules against the customer's account balance, open receivables, un-invoiced orders, orders on hold, and other exposure sources.

In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the ONT schema and is considered a valid, active object. Under a heuristic Data Vault classification, OE_CREDIT_CHECK_RULES leans toward a hub, since it holds a stable business key (the rule name) referenced by dependent tables and does not itself act as a transactional link or pure descriptive satellite. This classification should be treated as a modeling suggestion rather than a definitive categorization.

Key Information Stored

The table is defined with 49 documented columns. The most operationally significant columns include:

• CREDIT_CHECK_RULE_ID — the surrogate primary key (via OE_CREDIT_CHECK_RULES_PK) that uniquely identifies each rule.
• NAME — the business-key candidate (via unique index OE_CREDIT_CHECK_RULES_U2, alongside ZD_EDITION_NAME), holding the rule's user-facing identifier.
• FAILURE_RESULT_CODE — determines the action taken when a credit check fails.
• OPEN_AR_BALANCE_FLAG, UNINVOICED_ORDERS_FLAG, ORDERS_ON_HOLD_FLAG, INCLUDE_RETURNS_FLAG, INCLUDE_EXTERNAL_EXPOSURE_FLAG — exposure-source inclusion flags.
• SHIPPING_INTERVAL and OPEN_AR_DAYS — aging windows used in balance evaluation.
• MAXIMUM_DAYS_PAST_DUE and TOLERANCE_AMOUNT, TOLERANCE_CURR_CODE, TOLERANCE_PERCENTAGE — threshold and tolerance controls.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating for the rule.
• CREDIT_CHECK_LEVEL_CODE, CREDIT_HOLD_LEVEL_CODE, DAYS_HONOR_MANUAL_RELEASE — hold and release behavior.
• NAME combined with ZD_EDITION_NAME also appears in unique index OE_CREDIT_CHECK_RULES_U1.

Standard audit and DFF columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, ATTRIBUTE1–15, CONTEXT) are also present.

Common Use Cases and Queries

A frequent requirement is identifying which rule is active on a given date, or listing rules by their failure behavior:

• Reporting the credit rule assigned to an order type: join to OE_TRANSACTION_TYPES_ALL on ENTRY_CREDIT_CHECK_RULE_ID or SHIPPING_CREDIT_CHECK_RULE_ID.
• Auditing tolerance configuration: filter rows where TOLERANCE_PERCENTAGE or TOLERANCE_AMOUNT exceed a threshold.
• Validating effective dating: query where SYSDATE falls between START_DATE_ACTIVE and END_DATE_ACTIVE.
• Finding exposure drivers: select rules where INCLUDE_EXTERNAL_EXPOSURE_FLAG = 'Y' or OPEN_AR_BALANCE_FLAG = 'Y'.

A representative join retrieves the entry check rule name for each transaction type:

SELECT ott.name, ccr.name FROM oe_transaction_types_all ott, oe_credit_check_rules ccr WHERE ott.entry_credit_check_rule_id = ccr.credit_check_rule_id;

Related Objects

The principal dependents and related objects are:

• OE_TRANSACTION_TYPES_ALL — references this table twice, through ENTRY_CREDIT_CHECK_RULE_ID and SHIPPING_CREDIT_CHECK_RULE_ID, linking a transaction type to its entry and shipping credit rules.
• OE_CREDIT_CHECK_RULES_PK — the primary-key index on CREDIT_CHECK_RULE_ID.
• OE_CREDIT_CHECK_RULES_U1 / _U2 — unique indexes defining the business-key candidates.

Rule attributes are consumed by the Order Management credit checking logic and exposed through the ordering APIs and the customer/order entry forms that let users assign and evaluate credit rules.