Search Results ar_cons_bill_cycles_b_pk

Overview

The AR_CONS_BILL_CYCLES_B table is a Receivables (AR) module table that stores the definition of billing cycles used in the Oracle EBS Consolidated Billing process. Receivables creates one row for each billing cycle that a user defines, and this information is used to distinguish which activity to include on a bill. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the AR schema and is identified as VALID and available for use in the corresponding ETRM documentation set. Its role is fundamentally configuration-oriented: it defines the temporal rhythm according to which consolidated bills are generated for a set of customer or billing accounts, rather than transactional data itself. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table is not acting as a hub, link, or satellite within the surrounding FK web. As a modeling suggestion, this implies AR_CONS_BILL_CYCLES_B can be treated as a self-contained reference or configuration entity when designing downstream data vault or dimensional models.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists 56 columns. The most important columns are summarized below.

• BILLING_CYCLE_ID — the surrogate primary key of the table, defined by the unique constraint AR_CONS_BILL_CYCLES_B_PK. It uniquely identifies each billing cycle.
• BILL_CYCLE_TYPE — indicates the type of billing cycle, distinguishing the scheduling category used by Receivables.
• START_DATE — the effective start date for the cycle definition.
• CYCLE_FREQUENCY — the frequency with which the cycle repeats, driving how bills are scheduled across periods.
• LAST_DAY — a flag indicating whether the cycle is anchored to the last day of the period.
• DAY_1 through DAY_31 — day-of-month selection columns that mark which calendar day (or days) the billing cycle is triggered.
• DAY_MONDAY through DAY_FRIDAY, DAY_SATURDAY, DAY_SUNDAY — day-of-week selection columns controlling weekly cycle behavior.
• SKIP_WEEKENDS and SKIP_HOLIDAYS — flags that determine whether billing activity is suppressed when it falls on a weekend or holiday.
• REPEAT_DAILY, REPEAT_WEEKLY, REPEAT_MONTHLY — flags describing the repetition pattern of the cycle.
• DAY_TYPE — categorizes the day selection basis (for example, calendar-day versus working-day behavior).
• OBJECT_VERSION_NUMBER — used by the framework for optimistic locking and concurrent update control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns present on Oracle EBS tables.
• ZD_EDITION_NAME — the editioning column associated with the 12.2.2 Online Patching / EBR architecture; note that the unique index AR_CONS_BILL_CYCLES_B_U1 is defined on (BILLING_CYCLE_ID, ZD_EDITION_NAME).

The surrogate primary key is therefore BILLING_CYCLE_ID through the PK constraint, while the documented business-key candidate is the combination of BILLING_CYCLE_ID and ZD_EDITION_NAME captured by the unique index AR_CONS_BILL_CYCLES_B_U1.

Common Use Cases and Queries

Typical uses center on configuring, reporting, and validating billing cycle definitions before or during bill generation.

• Listing all defined billing cycles with their frequency and day settings:

  SELECT billing_cycle_id, bill_cycle_type, start_date, cycle_frequency,
         last_day, repeat_daily, repeat_weekly, repeat_monthly
  FROM   ar.ar_cons_bill_cycles_b
  ORDER  BY billing_cycle_id;

• Identifying cycles that skip weekends or holidays:

  SELECT billing_cycle_id, skip_weekends, skip_holidays
  FROM   ar.ar_cons_bill_cycles_b
  WHERE  skip_weekends = 'Y' OR skip_holidays = 'Y';

• Determining cycles anchored to the last day of the month:

  SELECT billing_cycle_id, last_day
  FROM   ar.ar_cons_bill_cycles_b
  WHERE  last_day = 'Y';

• Enumerating monthly cycles by the day-of-month selection:

  SELECT billing_cycle_id, day_1, day_15, day_31
  FROM   ar.ar_cons_bill_cycles_b
  WHERE  cycle_frequency = 'MONTHLY';

Related Objects

The metadata classifies the table as standalone, so no foreign-key parents or children are documented. The most significant related objects are as follows.

• AR_CONS_BILL_CYCLES_B_PK — the primary-key constraint on BILLING_CYCLE_ID, enforcing uniqueness in the base table.
• AR_CONS_BILL_CYCLES_B_U1 — the unique index on (BILLING_CYCLE_ID, ZD_EDITION_NAME) supporting edition-aware lookups.
• AR_CONS_BILL_CYCLES_TL — the translation table typically paired with a _B table for multilingual names and descriptions.
• AR_CONS_BILL_CYCLES_VL — the view joining the _B and _TL tables, commonly used in forms and reports.
• AR_CONS_BILL_CYCLES — the synonym or legacy reference used in client SQL.
• Consolidated Billing concurrent programs/APIs — the Receivables programs that read the cycle definition to determine bill inclusion activity.
• AR_CONS_INV_HEADERS / bill generation logic — the transactional side that consumes the cycle when producing consolidated invoices.