Search Results ce_interest_rates




Overview
Explore in AI Chat

Overview

CE_INTEREST_RATES is a Cash Management (CE) module table in Oracle E-Business Suite, owned by the CE schema. As documented in the ETRM repository, its purpose is to store interest rate information used by Cash Management functionality. The table is classified as VALID and contains ten documented columns in release 12.2.2. Its primary key is defined by the unique index CE_INTEREST_RATES_U1 on the INTEREST_RATE_ID column, confirming that each row represents a single, uniquely identifiable interest rate record.

The heuristic Data Vault classification mined from the foreign key structure identifies CE_INTEREST_RATES as standalone. In Data Vault modeling terms, this suggests the table functions largely as an independent reference or lookup object rather than a transactional hub or a dependent satellite. The single documented foreign key — BALANCE_RANGE_ID referencing CE_INTEREST_BAL_RANGES — indicates a lightweight hierarchical dependency: interest rate values are segmented by balance range, but the table is not deeply integrated into a wider network of foreign key constraints. This modeling suggestion should be treated as guidance, not as a definitive architectural statement.

Key Information Stored

The table is anchored by its surrogate primary key, INTEREST_RATE_ID, which is the sole column in the unique index CE_INTEREST_RATES_U1. Because no separate business-key unique index is documented, INTEREST_RATE_ID serves as both the technical identifier and the only documented uniqueness guarantee. Among the ten documented columns, the most significant are:

  • INTEREST_RATE_ID — surrogate primary key uniquely identifying each rate row.
  • BALANCE_RANGE_ID — foreign key to CE_INTEREST_BAL_RANGES, linking a rate to the balance tier it applies to.
  • INTEREST_RATE — the numeric interest rate value itself, the principal business fact of the row.
  • EFFECTIVE_DATE — the date from which the stored rate becomes applicable, supporting temporal rate versioning.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle EBS framework to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns providing audit lineage for every insert and change.

The combination of BALANCE_RANGE_ID, INTEREST_RATE, and EFFECTIVE_DATE constitutes the practical business identity of a rate record, even though no alternate unique index is documented.

Common Use Cases and Queries

Typical reporting scenarios include retrieving the currently effective rate for a given balance range and auditing historical rate changes. A representative query joining to the balance range table follows:

  • SELECT r.INTEREST_RATE_ID, r.BALANCE_RANGE_ID, r.INTEREST_RATE, r.EFFECTIVE_DATE FROM CE.CE_INTEREST_RATES r WHERE r.BALANCE_RANGE_ID = :range_id AND r.EFFECTIVE_DATE = (SELECT MAX(r2.EFFECTIVE_DATE) FROM CE.CE_INTEREST_RATES r2 WHERE r2.BALANCE_RANGE_ID = r.BALANCE_RANGE_ID AND r2.EFFECTIVE_DATE <= SYSDATE) — returns the latest effective rate per range.
  • SELECT r.*, b.* FROM CE.CE_INTEREST_RATES r, CE.CE_INTEREST_BAL_RANGES b WHERE r.BALANCE_RANGE_ID = b.BALANCE_RANGE_ID — joins rates to their balance tier descriptions.
  • Audit queries filtering on LAST_UPDATE_DATE or LAST_UPDATED_BY to trace rate maintenance activity.

Because CDD (Cash Management) rate lookups are date-driven, any query that omits EFFECTIVE_DATE filtering risks returning multiple rows per range and producing overstated results in accrual or interest projection reports.

Related Objects

The most significant related objects, drawn from the documented foreign key relationship and the surrounding Cash Management schema, include:

  • CE_INTEREST_BAL_RANGES — parent of the documented foreign key CE_INTEREST_RATES.BALANCE_RANGE_ID; defines the balance tiers to which rates apply.
  • CE_INTEREST_RATES_U1 — the unique index enforcing the INTEREST_RATE_ID primary key.
  • CE_INTEREST_RATES base-table views or Cash Management interest calculation programs that consume rate data for interest computation.
  • Cash Management setup and rate maintenance forms and concurrent programs that insert and update rows, populating the standard audit columns.
  • Any CE interest calculation engine that resolves BALANCE_RANGE_ID to select the effective INTEREST_RATE for a given account balance.

Because the table is classified standalone with only one documented outbound foreign key, its dependency footprint is narrow; effective master-detail reporting centers on the CE_INTEREST_BAL_RANGES link.