Results for “hricv_hr_semiyear”

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

Overview

The view HRICV_HR_SEMIYEAR is an Oracle E-Business Suite database object owned by the APPS schema and registered as VALID in the ETRM repository. It belongs to the HRI (Human Resources Intelligence) product family, the Oracle EBS module responsible for HR analytics, workforce reporting, and dimensional data used in the Daily Business Intelligence and HR Intelligence dashboards. Its explicit purpose is to generate a rolling list of half-year reporting periods, each representing a six-month interval. Rather than storing physical period definitions, the view derives period rows on the fly using date arithmetic against the current system date, producing a symmetric window of semi-year periods spanning approximately one hundred years (fifty years into the past and fifty years into the future). Because the view is defined WITH READ ONLY, it functions purely as a reporting and lookup construct and never supports DML. In practice it acts as a time-dimension helper that standardizes how semi-year (half-yearly) periods are named, numbered, and bounded for HR reporting and integration.

Underlying Base Objects

According to the documented ETRM metadata, HRICV_HR_SEMIYEAR references two base objects: the package HR_API and the view HR_LOOKUPS. The view text itself shows that HR_LOOKUPS is used as the driving row source — a synthetic offset is computed by subtracting 100 from ROWNUM over rows returned from HR_LOOKUPS, multiplied by six months, and added to the first day of the current year rounded to the current semi-year block. Because HR_LOOKUPS is a standard HR lookup view, it supplies the arbitrary set of rows that the inline CALC1 subquery increments against, with the outer filter WHERE ROWNUM <= 200 capping the output at 200 semi-year rows (a 100-year span, i.e., ±50 years). The HR_API package is noted as a referenced object, typically providing HR date and calendar utilities relied upon elsewhere in the HRICV family. There are no physical base tables; the semi-year periods are entirely computed.

Key Columns

• ID — the period identifier, formatted as YYYY-MM-DD (the start date of the half-year).
• VALUE — the raw THIS_DATE value, mirroring the start date and serving as the canonical period value.
• PERIOD_SET_NAME — a constant literal 'HR_SEMIYEAR' identifying the period set to which every row belongs.
• PERIOD_NAME — descriptive name combining the date and a semi-year sequence, e.g., 2005-JAN-01 (SY1).
• START_DATE — first day of the six-month period (THIS_DATE).
• END_DATE — last day of the period, computed as ADD_MONTHS(THIS_DATE, 6) - 1.
• PERIOD_NO_IN_YEAR — the semi-year number within the calendar year (1 or 2).
• PERIOD_YEAR — the calendar year, derived via TRUNC(THIS_DATE,'YYYY').
• ORGANIZATION_ID / ORGANIZATION_TYPE — both returned as TO_CHAR(NULL), i.e., intentionally null placeholders so the view conforms to the organization-aware column contract used by HRICV period views.

Common Use Cases and Queries

The view is most often joined to HR transactional or analytic queries when reporting must be grouped by half-year periods that are not pre-seeded in the GL or HR period calendars. It is also used to drive date-bucket prompts in HR Intelligence dashboards. A representative query joining semi-year periods to assignment data is:

• SELECT period_name, start_date, end_date, period_no_in_year FROM apps.hricv_hr_semiyear WHERE period_year = 2024;
• SELECT s.period_name, COUNT(*) FROM apps.hricv_hr_semiyear s, apps.per_all_assignments_f a WHERE a.effective_start_date BETWEEN s.start_date AND s.end_date GROUP BY s.period_name;
• SELECT * FROM apps.hricv_hr_semiyear WHERE SYSDATE BETWEEN start_date AND end_date; to obtain the currently active half-year period.

Because the periods are generated relative to SYSDATE, results shift as the calendar advances; consumers should filter on PERIOD_YEAR or date ranges rather than assuming static row identity.