Results for “as_rolling_calendars”

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

Overview

The AS_ROLLING_CALENDARS table resides in the OSM schema and belongs to the AS – Sales Foundation product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores rolling calendar definitions that drive sales forecast generation and period-based forecasting behavior. Rolling calendars allow forecasting engines to advance period windows dynamically, so that a forecast horizon (for example, six months forward) is continuously redefined against the current date rather than fixed to a static fiscal calendar. This makes the table a foundational configuration object for Oracle Sales forecasts and the downstream planning activities that consume them.

From a Data Vault modeling perspective, the mined relationship metadata classifies AS_ROLLING_CALENDARS as a standalone object. This heuristic classification suggests the table is best represented as a hub or reference entity in a Data Vault model, since it is not documented as the child of any foreign key relationship. Its business identity is anchored by the FREEZE_PERIOD attribute, which the unique index AS_ROLLING_CALENDARS_U1 promotes as the business-key candidate alongside the surrogate primary key AS_ROLLING_CALENDAR_PK.

Key Information Stored

The table carries 25 documented columns. The most functionally significant are:

• FREEZE_PERIOD — The business-key attribute of the calendar, and per the documented metadata the column associated with both the primary key index and the unique index AS_ROLLING_CALENDARS_U1. It identifies the specific rolling calendar configuration.
• PERIOD_NUMBER — Defines the period granularity or offset within the rolling calendar sequence.
• DESCRIPTION — Free-text label used by administrators to identify the calendar in setup and reporting.
• ENABLED_FLAG — Determines whether the rolling calendar is active and available for forecast generation.
• AUDIT COLUMNS — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard EBS audit trail information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) container columns, allowing customers to extend the table without schema modifications.

The surrogate key AS_ROLLING_CALENDAR_PK and the business-key unique index AS_ROLLING_CALENDARS_U1 are both documented against FREEZE_PERIOD. This dual anchoring is worth noting during integration design, as join predicates to downstream forecast tables typically resolve through these columns rather than a separate numeric identifier.

Common Use Cases and Queries

Typical use cases include validating forecast calendar setup, auditing which rolling calendars are enabled, and reconciling forecast output back to its defining calendar. A representative query listing active calendars follows:

• SELECT freeze_period, period_number, description FROM os m.as_rolling_calendars WHERE enabled_flag = 'Y' ORDER BY period_number;
• SELECT COUNT(*) FROM as_rolling_calendars WHERE enabled_flag = 'Y'; — used in integrity checks to confirm at least one calendar is active before running a forecast.
• A join pattern against forecast headers is common: SELECT * FROM as_forecasts f, as_rolling_calendars c WHERE f.freeze_period = c.freeze_period;

Reporting teams frequently extract the DFF attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE15) to categorize calendars by business unit or region. Because the table is a low-volume configuration object, it is commonly cached at the application tier to accelerate forecast processing.

Related Objects

Although the mined metadata classifies this table as standalone, the following objects are functionally significant in the Sales Foundation forecasting model and typically reference AS_ROLLING_CALENDARS through the FREEZE_PERIOD column:

• AS_FORECASTS / forecast header tables — consume the rolling calendar to define the forecast horizon.
• AS_FORECAST_LINES — inherit the period context established by the parent forecast and its rolling calendar.
• AS_ROLLING_CALENDAR_PERIODS (or equivalent period detail) — likely stores the expanded period rows associated with each calendar.
• AS_SALES_LEADS and associated Sales Foundation tables — rely on the same calendar infrastructure for period-based reporting.
• FND_FLEX_VALUES — validates DFF segment values entered through ATTRIBUTE_CATEGORY.

Administrators should treat AS_ROLLING_CALENDARS as a reference configuration table: changes to FREEZE_PERIOD values or ENABLED_FLAG status propagate directly into forecast generation logic.