Search Results repeat_weekly

Overview

AR_CONS_BILL_CYCLES_VL is a bilingual (MLS) view owned by the APPS schema in Oracle E-Business Suite Receivables. It presents consolidated billing cycle definitions used by the Bill Management and consolidated billing functionality within the Oracle Receivables (AR) module. A billing cycle defines the recurrence pattern by which consolidated invoices are generated for a customer or grouping, and this view surfaces the complete configuration of each cycle in the session's current language.

The "VL" suffix indicates a translated view that joins a base (_B) table to its translation (_TL) table and filters the translation by the user's active language via USERENV('LANG'). This makes the view the appropriate access point for both reporting and integration, since it returns CYCLE_NAME and DESCRIPTION already resolved into the user's session language. Oracle exposes such views for completeness of the Receivables data model; the underlying tables are more typically accessed directly by application forms, but the VL view is the canonical, language-aware query surface.

Underlying Base Objects

The view is defined over two synonyms that resolve to the underlying Receivables base tables:

• AR_CONS_BILL_CYCLES_B — the base table holding the non-translatable attributes of each billing cycle, including identifiers, frequency, scheduling flags, and audit columns.
• AR_CONS_BILL_CYCLES_TL — the translation table holding the language-dependent CYCLE_NAME and DESCRIPTION, keyed by BILLING_CYCLE_ID and LANGUAGE.

The join condition is T.BILLING_CYCLE_ID = B.BILLING_CYCLE_ID AND T.LANGUAGE = USERENV('LANG'). Because it is a straight equijoin with no outer join, only cycles that have a translation row in the session language are returned. The view also exposes B.ROWID as ROW_ID, an artifact of the translatable-table pattern used across EBS.

Key Columns

• ROW_ID, BILLING_CYCLE_ID — the row identifier and the primary key of the cycle.
• CYCLE_NAME, DESCRIPTION — translated, language-aware attributes drawn from the _TL table.
• BILL_CYCLE_TYPE, CYCLE_FREQUENCY, DAY_TYPE — classify the cycle and how it recurs.
• START_DATE, LAST_DAY — the effective start and the last-day-of-month flag for monthly cycles.
• DAY_1 … DAY_31 — flags designating which day numbers of the month the cycle triggers.
• DAY_MONDAY … DAY_SUNDAY — flags designating which days of the week apply.
• SKIP_WEEKENDS, SKIP_HOLIDAYS — determine whether weekend or holiday dates are excluded from the schedule.
• REPEAT_DAILY, REPEAT_WEEKLY, REPEAT_MONTHLY — the recurrence indicators, which together select the repeating interval. A user searching for repeat_weekly is looking at the flag that drives weekly recurrence.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical consumers include custom Receivables reports, data-conversion or migration scripts, and integration extracts that need the human-readable, language-resolved definition of a billing cycle. A common need is to identify all cycles configured to recur weekly:

SELECT billing_cycle_id, cycle_name, bill_cycle_type, cycle_frequency
FROM ar_cons_bill_cycles_vl
WHERE repeat_weekly = 'Y';

To list the weekly cycles that also observe weekend and holiday exclusions:

SELECT cycle_name, skip_weekends, skip_holidays, day_type
FROM ar_cons_bill_cycles_vl
WHERE repeat_weekly = 'Y'
AND (skip_weekends = 'Y' OR skip_holidays = 'Y');

Because the view is language-filtered, reports that require every language's name should query AR_CONS_BILL_CYCLES_TL directly rather than this VL view. When joining the view to invoice or billing schedule data, use BILLING_CYCLE_ID as the link key.