Results for “time_normal_finish”

50+ results




Overview
Explore in AI Chat

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

Overview

HR_POSITIONS_LOV_V is a VALID Oracle E-Business Suite view owned by the APPS schema within the PER (Human Resources) product family. It is documented in ETRM under Oracle EBS 12.1.1 and 12.2.2 as a list-of-values (LOV) view used to populate the LOV on the Mass Move form. Rather than storing data itself, the view presents a read-only projection of position records so that the Mass Move form can display a filtered, security-aware list of positions from which the user may select.

Because the view is defined as a simple SELECT over HR_POSITIONS with no DISTINCT clause, aggregation, or join, it inherits the row-per-position grain of the source view. Its primary role in EBS reporting and integration is therefore as a lightweight, stable interface for retrieving position attributes—particularly scheduling and probation data—without requiring the calling form, report, or interface to query HR_POSITIONS directly.

Underlying Base Objects

The documented view text is a SELECT from a single base object, HR_POSITIONS, which is itself a view over the physical HR_ALL_POSITIONS_F (and related) tables that hold the position definition. The view does not join to HR_ALL_ORGANIZATION_UNITS or PER_JOBS directly; ORGANIZATION_ID and JOB_ID are carried through from the underlying position row.

The ETRM metadata records that the view depends on supporting objects that participate in resolution and security rather than in the row-by-row SELECT. HR_GENERAL is referenced for general HR utility functions, FND_PROFILE supplies the current runtime profile values used during LOV resolution, and HR_SECURITY applies the security profile logic that restricts which positions a given responsibility or user may see. This means a query executed against the view through the application is subject to the same security constraints as the Mass Move form, whereas a direct SQL query by a privileged account generally returns all rows.

Key Columns

The view exposes sixteen columns. The following are the most commonly referenced:

  • POSITION — the position name (aliased from P.NAME), used as the displayed LOV value.
  • POSITION_ID — the unique surrogate key of the position; the LOV return value and the join key to HR_ALL_POSITIONS_F.
  • BUSINESS_GROUP_ID — the enterprise business group that owns the position.
  • ORGANIZATION_ID — the organization to which the position belongs.
  • JOB_ID — the job associated with the position.
  • WORKING_HOURS — the standard number of working hours defined for the position.
  • FREQUENCY — the frequency code accompanying WORKING_HOURS, establishing the period over which the hours are measured (for example, weekly or monthly).
  • TIME_NORMAL_START / TIME_NORMAL_FINISH — the normal start and end times for the position's working day.
  • PROBATION_PERIOD and PROBATION_PERIOD_UNITS — the probation duration and its unit of measure; the units column is aliased from PROBATION_PERIOD_UNIT_CD.
  • DATE_EFFECTIVE and DATE_END — the effective date range of the position definition.
  • STATUS — the position status, useful for filtering to active positions.
  • LOCATION_ID and POSITION_DEFINITION_ID — the location and the underlying definition identifier.

Common Use Cases and Queries

The view is typically used to drive LOV selection logic, to extract position scheduling and probation attributes for reporting, and to supply position defaults into interfaces or mass updates. A basic lookup by position name uses the POSITION alias:

  • SELECT position_id, position, organization_id, working_hours, frequency FROM hr_positions_lov_v WHERE position LIKE :search ORDER BY position;
  • SELECT position_id, working_hours, frequency, time_normal_start, time_normal_finish FROM hr_positions_lov_v WHERE business_group_id = :p_business_group_id AND status = 'ACTIVE';
  • SELECT p.position, p.probation_period, p.probation_period_units, p.date_effective, p.date_end FROM hr_positions_lov_v p WHERE p.position_id = :p_position_id;

Because the view is a pass-through over HR_POSITIONS, it should be treated as a convenience interface rather than an authoritative source of position history; for date-tracked reporting, queries against the base tables remain preferable.