Results for “ar_statement_cycles”

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

Overview

AR_STATEMENT_CYCLES is the Oracle Receivables master table that defines statement cycles. A statement cycle is a reusable scheduling definition that controls when customer statements are generated and transmitted—for example, a monthly cycle that issues statements on the fifth of each month, or a weekly cycle that issues statements every Monday. Because a single cycle definition can be assigned to many customers, customer profile classes, and historical statement runs, the table functions as a shared reference object within the Receivables statement-generation process rather than as a transactional or audit table.

The table is owned by the AR schema and resides in the Receivables (AR) product module. It carries 29 documented columns in the ETRM 12.2.2 schema. From a Data Vault modeling perspective, the metadata exhibits a hub-leaning classification: AR_STATEMENT_CYCLES holds the stable business concept (the statement cycle) with a surrogate primary key and no defining foreign keys of its own, while dependent detail tables orbit it as satellites and downstream references act as links. This heuristic suggests modeling the cycle as a hub with its descriptive attributes separated into satellites if a Data Vault layer is constructed.

Key Information Stored

The most significant columns in AR_STATEMENT_CYCLES are:

• STATEMENT_CYCLE_ID — the surrogate primary key (AR_STATEMENT_CYCLES_PK). This is the value propagated to all dependent tables as a foreign key.
• NAME — the user-defined statement cycle name. It is a business-key candidate, carrying its own unique constraint (AR_STATEMENT_CYCLES_UK1).
• DESCRIPTION — free-text description of the cycle's purpose.
• INTERVAL — the recurrence interval that drives statement frequency.
• DAY — the day within the interval on which the statement is produced.
• STATUS — active/inactive flag controlling whether the cycle may be assigned or executed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle flexfield (descriptive flexfield) columns for customer-specific extensions.
• REQUEST_ID — the concurrent request that created or updated the row, useful for tracing batch statement runs.
• ZD_EDITION_NAME — editioning support column present in the 12.2.2 schema.

Note that a second unique index, AR_STATEMENT_CYCLES_UK2, is documented on STATEMENT_CYCLE_ID, and a unique index AR_STATEMENT_CYCLES_U1 is documented on the composite (STATEMENT_CYCLE_ID, ZD_EDITION_NAME), reflecting Edition-Based Redefinition support in 12.2.x.

Common Use Cases and Queries

Typical usage includes listing the active cycles available for assignment to customers, determining which cycle a given customer profile uses, and reporting statement history grouped by cycle. A simple lookup of active cycles can be written as:

• SELECT statement_cycle_id, name, description, interval, day, status FROM ar.ar_statement_cycles WHERE status = 'A';
• SELECT c.name, p.customer_id FROM ar.ar_statement_cycles c, ar.ar_customer_profiles p WHERE c.statement_cycle_id = p.statement_cycle_id AND c.name = :cycle_name;
• SELECT s.statement_cycle_id, COUNT(*) FROM ar.ar_statements_history_all s GROUP BY s.statement_cycle_id;

These patterns support reporting on statement frequency, validating that every cycle referenced by a profile exists and is active, and auditing the volume of statements produced per cycle over a period.

Related Objects

Several tables reference AR_STATEMENT_CYCLES through the shared STATEMENT_CYCLE_ID column, and understanding these relationships is essential for both query design and data-model impact analysis:

• AR_CUSTOMER_PROFILES.STATEMENT_CYCLE_ID — assigns a cycle directly to a customer profile.
• AR_CUSTOMER_PROFILE_CLASSES.STATEMENT_CYCLE_ID — assigns a default cycle at the profile class level, which individual profiles may override.
• HZ_CUSTOMER_PROFILES.STATEMENT_CYCLE_ID and HZ_CUSTOMER_PROFILES_M.STATEMENT_CYCLE_ID — the TCA (Trading Community Architecture) counterparts, including the multi-org (_M) variant.
• HZ_CUST_PROFILE_CLASSES.STATEMENT_CYCLE_ID — the TCA profile class reference.
• AR_STATEMENT_CYCLE_DATES_ALL.STATEMENT_CYCLE_ID — stores the generated statement dates derived from each cycle definition.
• AR_STATEMENTS_HISTORY_ALL.STATEMENT_CYCLE_ID — records the cycles actually executed against statements in prior runs.

Collectively these relationships confirm that AR_STATEMENT_CYCLES sits at the center of the Receivables statement subsystem, supplying the scheduling definition consumed by profile assignment and statement history.