Results for “ar_statement_cycle_dates_all”

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

Overview

AR_STATEMENT_CYCLE_DATES_ALL is an Oracle Receivables (AR) transactional table that stores the individual statement dates belonging to a statement cycle. A statement cycle is the user-defined grouping that governs how and when customer statements are generated and dispatched; the child table AR_STATEMENT_CYCLE_DATES_ALL holds the specific calendar dates at which statements are produced within each cycle. Each row therefore represents one scheduled or historical statement date for a given cycle, together with its printing status and audit lineage. In Oracle EBS 12.1.1 and 12.2.2 the object resides in the AR schema, is documented as VALID with 15 columns, and carries the primary key AR_STATEMENT_CYCLE_DATES_PK.

Under a heuristic Data Vault classification mined from the foreign-key structure, the table leans toward a satellite role: it depends on a parent entity for its business meaning and records descriptive, time-stamped attributes about that parent. It should be treated less as an independent hub and more as a dependent structure describing cycle scheduling detail.

Key Information Stored

The dominant attribute is STATEMENT_DATE, the actual calendar date on which statements are issued; it is also documented as a business-key candidate under unique index AR_STATEMENT_CYCLE_DATES_UK1. The structural parent link is STATEMENT_CYCLE_ID, which references AR_STATEMENT_CYCLES and identifies the owning cycle; it participates in unique index AR_STATEMENT_CYCLE_DATES_UK2 and is the column through which all parent-child joins are made.

• STATEMENT_CYCLE_DATE_ID — surrogate primary key (AR_STATEMENT_CYCLE_DATES_PK); also the business-key candidate in AR_STATEMENT_CYCLE_DATES_U1.
• STATEMENT_CYCLE_ID — foreign key to AR_STATEMENT_CYCLES; the cycle to which the date belongs.
• STATEMENT_DATE — the scheduled or actual statement run date.
• PRINTED — flag indicating whether statements for this date have been printed.
• PRINT_DATE — timestamp recorded when printing completed.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit context identifying the process that generated or updated the row.
• ORG_ID — operating unit identifier supporting multi-org (MOAC) data access.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and concurrency tracking.

The distinction between the surrogate key (STATEMENT_CYCLE_DATE_ID) and the business-key candidates (STATEMENT_DATE, and the composite involving STATEMENT_CYCLE_ID) matters when resolving duplicates, building integration extracts, and validating statement schedules.

Common Use Cases and Queries

Typical scenarios include auditing upcoming statement schedules, tracking which dates have been printed, and reporting missed or pending runs. A representative query joins to the parent cycle to list planned dates for a customer cycle:

• SELECT d.STATEMENT_DATE, d.PRINTED, d.PRINT_DATE FROM AR_STATEMENT_CYCLE_DATES_ALL d, AR_STATEMENT_CYCLES c WHERE d.STATEMENT_CYCLE_ID = c.STATEMENT_CYCLE_ID AND c.NAME = :cycle;
• Filter on d.PRINTED = 'N' AND d.STATEMENT_DATE <= SYSDATE to identify overdue, unprinted statements.
• Group by STATEMENT_CYCLE_ID to count scheduled dates per cycle for capacity planning.
• Restrict by ORG_ID for multi-org reporting, and use REQUEST_ID/PROGRAM_ID to trace which concurrent process populated a date.

Because the table is an audit-bearing child of the cycle definition, reporting should generally drive from AR_STATEMENT_CYCLES and outer-join the date rows to preserve cycles that have no scheduled dates.

Related Objects

The primary relationship is the foreign key from STATEMENT_CYCLE_ID to AR_STATEMENT_CYCLES, which is the parent entity defining cycle behavior. Statement generation reads this table in conjunction with customer and transaction data used by the AutoInvoice and statement printing programs. Significant related objects include:

• AR_STATEMENT_CYCLES — parent table; join on STATEMENT_CYCLE_ID.
• AR_CUSTOMERS / HZ_CUST_ACCOUNTS — statement recipients linked to cycles.
• AR_STATEMENT_CYCLE_HEADERS — cycle header groupings.
• AR_STATEMENTS — generated statement records referencing statement dates.
• AR_STATEMENT_HISTORY / AR_CUSTOMER_STATEMENTS — historical statement output.

Concurrent programs such as the Statement Generation and Print Statements processes populate PRINTED, PRINT_DATE, and the request/program columns during execution.