Results for “ap_interest_periods”

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

Overview

AP_INTEREST_PERIODS is an Oracle Payables (AP) table that stores the interest rate definitions and effective date ranges used by Payables to calculate and generate Interest invoices. Interest invoices are created when a Payables installation is configured to charge interest on overdue supplier balances, late payment penalties, or similar financing arrangements. Each row in AP_INTEREST_PERIODS establishes an annual interest rate that is valid between a specific START_DATE and END_DATE, thereby allowing organizations to maintain a historical timeline of rate changes rather than overwriting a single rate value.

The table resides in the AP schema and is owned by the Payables product. It is a standalone object according to the Data Vault classification heuristic mined from its foreign key structure; no dependent foreign keys were identified. In Data Vault modeling terms, this object is best treated as a satellite-like reference table, since it captures descriptive rate and period attributes rather than representing a transactional hub or a relationship link between two business entities. It can be modeled as a standalone dimension or reference table when building reporting layers.

Key Information Stored

The documented physical schema for release 12.2.2 contains nine columns. The most significant are:

• INTEREST_PERIOD_ID — The surrogate primary key, enforced by the AP_INTEREST_PERIODS_PK constraint. This value uniquely identifies each rate period record and is system-generated.
• ANNUAL_INTEREST_RATE — The percentage rate applied to overdue balances for the period defined by the row. This is the core business attribute driving interest invoice calculations.
• START_DATE — The date on which the associated annual interest rate becomes effective.
• END_DATE — The date on which the associated annual interest rate ceases to be effective. Together with START_DATE, these columns define the validity window for the rate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS auditing columns (WHO columns) that record insert and update metadata for each row, supporting audit trails and change tracking.

The only documented unique identifier is the primary key INTEREST_PERIOD_ID. No alternate unique business key is documented in the metadata; the combination of START_DATE and END_DATE effectively functions as a business-key candidate in practice, since rate periods should not overlap, but this constraint is not documented as a database-enforced unique index.

Common Use Cases and Queries

Typical scenarios include retrieving the interest rate in effect on a given date, auditing historical rate changes, and validating that no overlapping periods exist. A common query pattern retrieves the active rate for a specific date:

• SELECT annual_interest_rate FROM ap.ap_interest_periods WHERE :query_date BETWEEN start_date AND end_date;
• SELECT interest_period_id, annual_interest_rate, start_date, end_date FROM ap.ap_interest_periods ORDER BY start_date;

Reporting use cases include generating a rate-change history report for treasury or finance review, reconciling interest invoices back to the rate period that produced them, and detecting gaps or overlaps between END_DATE and the following START_DATE. Because the table holds only a small number of rows relative to transactional tables, it is inexpensive to query in full and is frequently joined into reporting views that explain interest invoice amounts.

Related Objects

As a standalone reference table with no documented foreign keys, AP_INTEREST_PERIODS is not dependent on other tables through referential constraints. It is nonetheless referenced conceptually by the Payables interest invoice generation process and by related AP objects, including:

• AP_INVOICES_ALL — Holds the interest invoices whose amounts derive from the rate stored here.
• AP_INVOICE_LINES_ALL — Stores the interest invoice distribution lines calculated using the applicable rate.
• AP_INVOICE_PAYMENTS_ALL — Links payments to the interest invoices generated under these rate periods.
• AP_PAYMENT_SCHEDULES_ALL — Provides the due dates that determine whether an invoice becomes overdue and subject to interest.
• AP_INTEREST_PERIODS_PK — The primary key constraint that uniquely identifies each period row.

Because no foreign key columns are documented, joins to these objects are driven by business logic in the interest invoice programs rather than by database-enforced relationships. Administrators and developers should therefore validate rate periods carefully when troubleshooting interest invoice discrepancies.