Results for “ar_statement_cycle_intervals”

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

Overview

AR_STATEMENT_CYCLE_INTERVALS is a Receivables (AR) reference table that stores statement cycle interval definitions. Each row describes a named cadence — for example a monthly, semi-monthly, or weekly billing/statement run — expressed as a day range (LOW_DAY to HIGH_DAY) within a month. Oracle Receivables uses these intervals when generating customer statements so that a statement cycle can be mapped to specific calendar days in which statement generation should occur.

The table is owned by the AR schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. It is a small, low-volatility configuration table. Under the heuristic Data Vault classification supplied in the metadata, AR_STATEMENT_CYCLE_INTERVALS is treated as a standalone object — i.e., it has no dependent foreign-key children in the mined structure. From a modeling perspective it behaves as a reference/hub-style lookup: the natural business key is the interval name, and the descriptive columns act as attributes. It is best modeled as a standalone reference table rather than as a link to another entity, since no FK relationships were identified.

Key Information Stored

The documented physical schema contains 8 columns. The most significant are:

• INTERVAL_NAME — the business identifier for the interval (e.g., "Monthly", "Semi-Monthly"). It is part of the primary key.
• LOW_DAY — the low boundary of the day range within the cycle (the earliest day in the month that statements are considered due to be generated).
• HIGH_DAY — the high boundary of the day range within the cycle (the latest day that statements are considered due to be generated).
• CREATION_DATE, CREATED_BY — standard audit columns recording who inserted the row and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the login of the user who performed it.

The primary key is AR_STATEMENT_CYCLE_INTERVAL_PK, defined on INTERVAL_NAME. Because the primary key is expressed on the business name itself rather than a surrogate integer, INTERVAL_NAME serves simultaneously as surrogate and business key. LOW_DAY and HIGH_DAY are attribute columns describing the interval. The standard WHO columns (CREATION_DATE/CREATED_BY/LAST_UPDATE_DATE/LAST_UPDATED_BY/LAST_UPDATE_LOGIN) provide the audit trail consistent with other AR reference tables.

Common Use Cases and Queries

Typical uses include validating that a statement cycle is configured, reporting the available statement cycles for customer assignment, and confirming the day range applied to each cycle. Because the table is small and static, queries are usually simple lookups.

• List all defined cycles: SELECT interval_name, low_day, high_day FROM ar.ar_statement_cycle_intervals ORDER BY interval_name;
• Find the cycle applicable to a given day: SELECT interval_name FROM ar.ar_statement_cycle_intervals WHERE :day BETWEEN low_day AND high_day;
• Audit recent changes: SELECT interval_name, last_update_date, last_updated_by FROM ar.ar_statement_cycle_intervals WHERE last_update_date >= :since;
• Reporting use cases include statement-cycle coverage reports, confirming interval definitions before a statement run, and troubleshooting missing or overlapping day ranges across intervals.

Note that the table is configuration metadata; it is not transactional and does not itself store statement history.

Related Objects

AR_STATEMENT_CYCLE_INTERVALS is referenced by Receivables statement configuration and customer setup. The most significant related objects include:

• AR_STATEMENT_CYCLES (or the AR statement-cycle setup entity) — the parent configuration that associates an interval name with statement generation parameters, joined on INTERVAL_NAME.
• AR_CUSTOMERS / customer profile tables — customer statement preferences that consume the cycle definition.
• AR_STATEMENT_HISTORY — records of generated statements, useful for reconciling the configured interval against actual runs.
• AR_STATEMENT_CYCLE_INTERVAL_PK — the primary key constraint objects (index and constraint definitions) in USER_CONSTRAINTS/USER_INDEXES.
• FND_LOOKUPS / AR lookup types — may supply codes or descriptive values used alongside interval definitions.

Given the documented heuristic classification as standalone, no true child FK tables were mined; joins to the above objects are therefore by business key (INTERVAL_NAME) rather than by a surrogate FK.