Results for “date_end”

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

Overview

The HR_POS_LOV_V view is a synonym-backed database object owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is registered under the PER (Human Resources) product family and holds a VALID status in the data dictionary. Its primary function is to expose a filtered and denormalized list of positions suitable for use as a List of Values (LOV) source. The view name itself signals this purpose: the "_LOV_V" suffix indicates a view intended to populate LOV windows, flexfield pickers, and dependent value sets within Oracle Forms and OAF pages.

Because the view is defined over the position definition base and deliberately excludes invalid rows, it serves as a convenience access path for developers, report writers, and integration engineers who require a stable, pre-filtered set of position records without having to re-implement the validity logic. It is especially relevant to users searching for date_effective, since the view surfaces the date-effective control columns directly.

Underlying Base Objects

According to ETRM metadata, HR_POS_LOV_V is defined over the HR_POSITIONS_F view, itself a datetracked ("_F") object mapped to the HR_POSITIONS base table. The view text is a straight projection with a single filter predicate:

• HR_POSITIONS_F — the primary source supplying all seven projected columns; provides the datetrack effective-dating semantics.
• FND_PROFILE — the profile options package, typically invoked for business group context and security profile resolution.
• HR_GENERAL — the HR utility package used for date-effective and business-group filtering helpers.
• HR_SECURITY — enforces row-level security, restricting positions to those the current user is authorized to see based on their security profile.

The combined use of HR_SECURITY and FND_PROFILE means the view is context-sensitive: results are filtered by the runtime security profile and business group, not merely by the STATUS predicate shown in the view text.

Key Columns

• POSITION_ID — Primary identifier of the position record; the join key to HR_ALL_POSITIONS_F and assignment tables.
• BUSINESS_GROUP_ID — The enterprise group owning the position; critical for multi-organization filtering.
• DATE_EFFECTIVE — The effective start date of the position version. This is the column most associated with the user's "date_effective" search, governing which datetracked row is returned for a given point in time.
• DATE_END — The effective end date of the position version; NULL indicates the current active version.
• NAME — The position name displayed in LOVs.
• JOB_ID — Foreign key to the job assigned to the position.
• ORGANIZATION_ID — The organization (inventory/HR) to which the position belongs.

Common Use Cases and Queries

The view is most often consumed by custom reports, concurrent programs, and integration extracts that need a current, secure list of positions. A typical query resolving the latest effective version is:

• SELECT position_id, name, date_effective, date_end FROM apps.hr_pos_lo_v WHERE business_group_id = :p_bg_id AND (date_end IS NULL OR date_end > SYSDATE);
• Populating a position LOV in a custom Form or OAF page using the NAME and POSITION_ID pair.
• Joining to HR_ALL_POSITIONS_F or PER_ALL_ASSIGNMENTS_F on POSITION_ID to enrich assignment reporting with the position validity window.
• Datetrack-aware extraction: filtering on DATE_EFFECTIVE and DATE_END to reconstruct historical position structures for audit or BI analysis.

Because row-level security is applied, developers should always test with the appropriate HR security profile; otherwise the LOV may return fewer rows than expected. Where full datetrack history is required (including invalid or future-dated rows), querying HR_POSITIONS_F directly is preferable, as the LOV view suppresses invalid records by design.