Results for “bis_hr_quarters_v”

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

Overview

BIS_HR_QUARTERS_V is a reporting view in the Oracle EBS Applications BIS (Business Intelligence System / Business Information System) module. Its purpose is to present a rolling five-quarter calendar window relative to the current system date, allowing HR and organizational reporting to reference a standardized set of quarter definitions without computing them at runtime in each report. The view does not store transactional data; instead it synthesizes quarter descriptors on the fly using the ADD_MONTHS and TRUNC date functions applied to SYSDATE.

Per the ETRM metadata, the object is documented as "Not implemented in this database," meaning the view is defined as reference documentation rather than a physically deployed object in the source instance. In EBS 12.1.1 and 12.2.2 environments where it is deployed, it functions as a lookup-style helper view used by HR-related reporting and integration logic that requires a consistent, reusable quarter list.

Underlying Base Objects

The documented referenced base objects list is empty ("none documented"), and inspection of the view text confirms this. Every row is derived from DUAL via a chain of UNION operations. The view therefore depends on no application tables, no HR tables, and no date-dimension table. Its only inputs are the database session's SYSDATE and the built-in SQL functions ADD_MONTHS and TRUNC.

The five UNION branches correspond to five successive quarter offsets: -12 months, -9 months, -6 months, -3 months, and 0 months. Each branch computes the quarter label and boundary dates for that offset, so the view always returns a five-row result set representing the trailing one-year span of quarters, aligned to the current date.

Key Columns

• ID — A synthetic identifier formed by concatenating the literal 'HR QUARTER' with '+' and the quarter/year string, for example HR QUARTER+3 2024. It provides a stable, readable natural key for each row.
• VALUE — The quarter and year in 'Q YYYY' format (for example, 3 2024).
• Quarters — A literal column populated with the constant 'HR QUARTER', labeling the row type.
• Quarter Label — The formatted ADD_MONTHS result expressed as 'Q YYYY', used for display and grouping.
• Quarter Start Date — TRUNC(ADD_MONTHS(SYSDATE, offset), 'Q'), the first day of the quarter for that offset.
• Quarter End Date — Computed as TRUNC(ADD_MONTHS(SYSDATE, offset + 3), 'Q') - 1, yielding the last day of the quarter.
• Year — The four-digit calendar year of the quarter, cast to NUMBER.
• ORGANIZATION_ID and ORGANIZATION_TYPE — Passed through as TO_CHAR(NULL). In the delivered text these are null placeholders, and the trailing branches contain a typographic variant "ORGANAZTION_ID" that is a known defect in the seeded source.

Common Use Cases and Queries

Because the view is keyed to SYSDATE, its output shifts automatically as time advances, making it suitable for report parameters, LOV sources, and period-to-date calculations that must always span the trailing year.

• Populating a quarter selector in an HR reporting parameter form.
• Mapping attendance, headcount, or payroll facts to rolling quarter boundaries.
• Generating consistent quarter labels for concurrent program outputs.

Sample query retrieving the current reporting window:

SELECT id, value, TRUNC_QUARTER_START, QUARTER_END, year
FROM   bis_hr_quarters_v
ORDER BY year, value;

A typical filter for the current quarter and the prior quarter:

SELECT value, quarter_start_date, quarter_end_date
FROM   bis_hr_quarters_v
WHERE  TRUNC(SYSDATE,'Q') BETWEEN quarter_start_date AND quarter_end_date
   OR  ADD_MONTHS(TRUNC(SYSDATE,'Q'),-3) = quarter_start_date;

Because the view returns only five synthesized rows and targets no base tables, it performs predictably and can be freely joined against any HR fact set using the quarter start and end columns as range predicates.