Results for “interest_schedule_id”

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

Overview

CE_INTEREST_SCHEDULES is a Cash Management (CE) reference table that stores interest rate schedule definitions. Each row describes a named schedule that governs how interest is calculated on a bank account balance, including the day-count convention, the basis used for the computation, and rounding behaviour. In Oracle EBS 12.1.1 and 12.2.2, the table belongs to the CE schema and is validated at the database level. The object acts as a configuration master whose identifiers are reused across Cash Management, Receivables, and Trading Community Architecture modules, so a single schedule can be attached to many consuming entities without duplicating the rate logic.

Applying a heuristic Data Vault classification to the documented foreign-key topology, CE_INTEREST_SCHEDULES is hub-leaning. Its surrogate primary key, INTEREST_SCHEDULE_ID, is referenced by numerous downstream tables, which is the pattern of a hub that anchors a stable business concept. The descriptive attributes carried on the same row (name, currency, day-count basis, rounding) would, in a strict Data Vault model, be candidates for a satellite attached to that hub.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is INTEREST_SCHEDULE_ID, enforced by the unique index CE_INTEREST_SCHEDULES_U1. The remaining columns fall into three groups.

• Identification: INTEREST_SCHEDULE_ID (primary key), SCHEDULE_NAME (the human-readable label used when selecting a schedule in the application).
• Calculation attributes: CURRENCY_CODE (the currency in which the schedule applies), DAY_COUNT_BASIS (the day-count convention used to accrue interest), BASIS (the balance basis the calculation draws upon), INTEREST_INCLUDES (defines what components are included in the interest computation), and INTEREST_ROUNDING (the rounding rule applied to the computed amount).
• Standard EBS audit and concurrency columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the last of which supports optimistic locking in the OAF-based 12.2.2 user interface.

No secondary unique index is documented in the ETRM metadata, so SCHEDULE_NAME should be treated as a business-key candidate rather than a guaranteed unique constraint.

Common Use Cases and Queries

The primary operational use case is bank account interest configuration: a cash manager creates a schedule, then associates it with one or more bank accounts so that interest can be computed and reported. A representative lookup query joins the schedule to the account:

• SELECT s.schedule_name, s.currency_code, s.day_count_basis, s.basis, b.bank_account_name FROM ce.ce_interest_schedules s, ce.ce_bank_accounts b WHERE b.interest_schedule_id = s.interest_schedule_id;

Reporting use cases include listing active schedules by currency, auditing the day-count and rounding conventions applied across a treasury portfolio, and validating that only one schedule is assigned per account. A typical configuration report selects SCHEDULE_NAME, CURRENCY_CODE, DAY_COUNT_BASIS, BASIS, and INTEREST_ROUNDING, ordered by SCHEDULE_NAME. Because downstream Receivables and customer-profile tables also carry INTEREST_SCHEDULE_ID, the same key supports reconciliation queries that confirm which interest terms apply to a given customer account or late-charge calculation. Integration queries commonly extract INTEREST_SCHEDULE_ID together with OBJECT_VERSION_NUMBER when synchronising Cash Management configuration into external treasury systems.

Related Objects

The documented foreign-key relationships show the principal consumers of this table:

• CE_BANK_ACCOUNTS — joins on INTEREST_SCHEDULE_ID; the most direct Cash Management consumer, linking a schedule to a bank account.
• CE_INTEREST_BAL_RANGES — joins on INTEREST_SCHEDULE_ID; stores the tiered balance ranges that accompany a schedule.
• AR_INTEREST_HEADERS_ALL — Receivables interest headers that reference the schedule for late-charge computation.
• RA_CUSTOMER_PROFILES_INT_ALL and HZ_CUST_PROFILE_AMTS, HZ_CUST_PROFILE_AMTS_M, HZ_CUST_PROF_CLASS_AMTS — customer profile and profile-class amounts that default interest terms from the schedule.
• AR_LC_CUST_SITES_T — customer site-level interest configuration referencing the schedule.

These dependencies confirm the hub role of CE_INTEREST_SCHEDULES within both Cash Management and the wider Receivables and TCA data model.