Search Results oe_credit_balances_all




Overview
Explore in AI Chat

Overview

OE_CREDIT_BALANCES_ALL is a transactional table owned by the ONT (Order Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the current credit exposure data for each individual customer and customer site that carries a credit limit. For every customer or site, the table maintains one row per valid credit check rule defined in the system, including default limits. This design allows Order Management to evaluate credit exposure against multiple credit rules simultaneously, which is essential for organizations running rule-based credit checking at order entry or pick release.

From a dimensional modeling perspective, the ETRM heuristic classifies this table as standalone — it does not participate in a traditional Data Vault hub or link pattern in the mined FK structure. However, functionally it behaves like a satellite recording the current state of credit exposure, keyed by customer account, credit profile amount, and credit check rule. Its volatility (updated each time credit exposure is recalculated) and its role as a snapshot of current exposure support this interpretation.

Key Information Stored

The table contains 36 documented columns. The most significant are:

Common Use Cases and Queries

Credit analysts and Order Management implementers query this table to inspect a customer's current exposure, diagnose credit holds, and build credit dashboards. A typical query joins to HZ_CUST_ACCOUNTS to resolve the customer name:

  • Exposure by customer: SELECT cust_account_id, credit_check_rule_id, overall_exposure, orders, orders_on_hold FROM oe_credit_balances_all WHERE cust_account_id = :p_account_id AND org_id = :p_org_id;
  • Rule-level breakdown: filter by CREDIT_CHECK_RULE_ID to see which rule drives a hold.
  • Overdue and at-risk reporting: aggregate PAYMENTS_OVERDUE and PAYMENTS_AT_RISK across customers for a collections view.
  • Orders on hold analysis: identify customers with large ORDERS_ON_HOLD values to prioritize release approvals.

Because rows are refreshed when credit exposure is recalculated, the table reflects current state rather than history. Historical trend reporting requires capturing periodic snapshots.

Related Objects

The documented foreign keys and surrounding Order Management / Receivables objects most relevant to this table include:

  • HZ_CUST_ACCOUNTS — joined on CUST_ACCOUNT_ID; the master customer account record.
  • HZ_CUST_PROFILE_AMTS — joined on CUST_ACCT_PROFILE_AMT_ID; the customer account profile amount (assigned credit limit).
  • HZ_CREDIT_PROFILE_AMTS — joined on CREDIT_PROFILE_AMT_ID; the credit profile amount definition.
  • OE_CREDIT_CHECK_RULES — provides the rule definitions referenced by CREDIT_CHECK_RULE_ID.
  • OE_ORDER_HEADERS_ALL — source of order values rolled into ORDERS and ORDERS_ON_HOLD.
  • AR_PAYMENT_SCHEDULES_ALL — source of overdue and at-risk payment amounts.
  • HZ_CUST_SITE_USES_ALL and HZ_CUST_ACCT_SITES_ALL — site-level context for site-specific credit limits.
  • OE_CREDIT_SUMMARY and the Credit Check concurrent program — populate and refresh OE_CREDIT_BALANCES_ALL.

Together these objects support the credit-to-cash flow within Oracle EBS Order Management and Receivables.