Results for “ar_cons_bill_cycle_dates”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AR_CONS_BILL_CYCLE_DATES is a Receivables (AR) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Its documented purpose is to store billing dates associated with a given billing cycle. In the context of Oracle EBS consolidated billing, this table provides the calendar of billable dates that drive when invoices are generated for customers assigned to a particular billing cycle. It belongs to the AR schema and is registered with a VALID status in the ETRM repository.
From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. Because no FK-derived parent relationships were identified, the table behaves as an independent reference set rather than a junction or transactional link. Where a Data Vault suggestion is applied, the composite business key (BILLING_CYCLE_ID, BILLABLE_DATE) suggests the table functions as a satellite-like reference of billable dates keyed by cycle, rather than as a hub or link. This classification is heuristic and should be validated against the application's actual usage.
Key Information Stored
The table contains seven documented columns. The most significant are the two business columns that together form the primary key and the unique business-key candidate, plus the standard Oracle EBS audit columns.
- BILLING_CYCLE_ID — Identifies the billing cycle to which the billable date belongs. This is the leading column of both the primary key and the unique index.
- BILLABLE_DATE — The actual billing date associated with that cycle; the trailing column of the composite key and unique index.
- CREATED_BY — User identifier that created the row.
- CREATION_DATE — Timestamp when the row was inserted.
- LAST_UPDATE_LOGIN — Login that last modified the row.
- LAST_UPDATE_DATE — Timestamp of the most recent modification.
- LAST_UPDATED_BY — User identifier that last updated the row.
The surrogate/natural key is the composite BILLING_CYCLE_ID plus BILLABLE_DATE. There is no single surrogate primary key; the primary key constraint AR_CONS_BILL_CYCLE_DATES_PK is defined on the composite pair, and the unique index AR_CONS_BILL_CYCLE_DATES_U1 mirrors the same two columns as the business-key candidate. The absence of a dedicated sequence-generated surrogate key means the cycle-and-date pair is the authoritative row identifier.
Common Use Cases and Queries
Typical use cases center on determining valid billing dates for a cycle, validating that a customer's cycle produces the expected invoice generation dates, and reporting on billing schedules. A simple lookup pattern is:
- SELECT billing_cycle_id, billable_date FROM ar.ar_cons_bill_cycle_dates WHERE billing_cycle_id = :cycle_id ORDER BY billable_date;
- SELECT billable_date FROM ar.ar_cons_bill_cycle_dates WHERE billing_cycle_id = :cycle_id AND billable_date BETWEEN :start_date AND :end_date;
- Joining to a billing-cycle master to enumerate cycle names and their billable dates for a given period.
Reporting scenarios include audit reports validating that each active billing cycle has dates covering the current open period, and reconciliation queries confirming that generated invoices align to a documented billable date. Because the table carries standard audit columns, queries can also filter on creation or last-update timestamps to trace when a billing schedule was configured or changed.
Related Objects
The metadata describes the object as standalone, so no foreign-key parent is documented. Significant related objects are inferred from the enterprise structure and the billing-cycle context:
- AR_CONS_BILL_CYCLES (or the associated billing-cycle master) — joined on BILLING_CYCLE_ID to resolve cycle definitions and names.
- AR_CONS_BILL_CYCLE_DATES_PK — the primary-key constraint enforcing uniqueness of (BILLING_CYCLE_ID, BILLABLE_DATE).
- AR_CONS_BILL_CYCLE_DATES_U1 — the unique index providing the business-key candidate.
- AR_CUSTOMERS — supplies the customers assigned to a billing cycle whose invoice dates this table governs.
- AR_INVOICES / RA_CUSTOMER_TRX_ALL — transaction records whose generation dates may be validated against billable dates.
- AR Autoinvoice (RAXMTR) and consolidated billing programs — concurrent processes that consume cycle dates during invoice creation.
These relationships are presented as the most likely dependencies given the documented composite key; they should be confirmed against the actual referential model in the target 12.1.1 or 12.2.2 instance.
-
This table stores billing dates for given billing cycle.
-
This table stores billing dates for given billing cycle.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - AR Tables and Views 12.1.1
Territory information
-
eTRM - AR Tables and Views 12.2.2
Territory information