Results for “hr_scheduler_v”

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

Overview

HR_SCHEDULER_V is a VALID dictionary view owned by the APPS schema and registered under the PER – Human Resources product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM metadata, its stated purpose is to support the user interface rather than to serve as a general-purpose reporting object. The view exposes a generated list of time slots or scheduling rows, each carrying a start timestamp, an end timestamp, formatted start and end times, an availability indicator, and a schedule level value.

Because the row set is produced by invoking packaged PL/SQL functions rather than by reading stored data, HR_SCHEDULER_V is best understood as a presentation-layer construct. It is consumed by the Human Resources scheduling and calendar style user interfaces, which require a fixed number of pre-formatted rows to render selectable time bands. It has no persistent storage of its own and its output is entirely derived at query time.

Underlying Base Objects

The documented base objects referenced by the view are FND_COMMON_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), and HR_CALENDAR_PKG (PACKAGE). The view text is notable for a deliberate Cartesian join between two references to FND_COMMON_LOOKUPS, an inclusion explicitly annotated in the source as intentional. This self-join is used purely as a row generator: combined with the predicate ROWNUM <= HR_CALENDAR_PKG.SCHEDULE_ROWCOUNT, it multiplies the lookup rows to produce the required number of scheduling rows while capping the result set at the packaged row count.

All substantive column values come from HR_CALENDAR_PKG, which supplies START_DATE, END_DATE, AVAILABILITY_VALUE, and SCHEDULE_LEVEL_VALUE, each invoked with ROWNUM as the row index argument. FND_COMMON_LOOKUPS therefore contributes no lookup meaning to the output; it functions only as a driving row source. FND_GLOBAL is referenced for session context such as the effective user and responsibility, which influences the packaged logic. The dependency on FND_COMMON_LOOKUPS is of particular interest given that the search term associated with this object was "fnd_common_lookups"; the relationship is structural rather than semantic, and no lookup code, meaning, or description from FND_COMMON_LOOKUPS is projected by the view.

Key Columns

• START_DATE – Start timestamp of the generated slot, returned by HR_CALENDAR_PKG.START_DATE (ROWNUM).
• START_TIME – Character representation of the start time in HH24:MI format.
• END_DATE – End timestamp of the generated slot, returned by HR_CALENDAR_PKG.END_DATE (ROWNUM).
• END_TIME – Character representation of the end time in HH24:MI format.
• AVAILABILITY – Availability indicator returned by HR_CALENDAR_PKG.AVAILABILITY_VALUE, truncated to 80 characters via SUBSTR.
• SCHEDULE_LEVEL – Schedule level value returned by HR_CALENDAR_PKG.SCHEDULE_LEVEL_VALUE, used by the interface to classify the slot.

The number of rows returned depends entirely on HR_CALENDAR_PKG.SCHEDULE_ROWCOUNT at execution time, so the view is non-deterministic across sessions and configurations.

Common Use Cases and Queries

Because the view is UI-supporting, direct querying is uncommon and is generally restricted to diagnostics, data validation, or replicating interface behaviour in custom code. A basic inspection query is:

• SELECT start_date, start_time, end_date, end_time, availability, schedule_level FROM apps.hr_scheduler_v ORDER BY start_date;
• SELECT COUNT(*) FROM apps.hr_scheduler_v; – confirms the effective value of SCHEDULE_ROWCOUNT for the current session.
• SELECT * FROM apps.hr_scheduler_v WHERE availability = 'Y'; – filters slots flagged as available.

Users should be aware that the Cartesian join over FND_COMMON_LOOKUPS can be expensive relative to the small result set, and that results change with the session context established by FND_GLOBAL and the calendar package. Where slot data is needed for reporting, the underlying HR_CALENDAR_PKG functions should be called directly rather than depending on this view.