Results for “position_definition_id”

50+ results




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

Overview

HRI_CL_POSITION_HX_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HRI (Human Resources Intelligence) product family. It exposes a flattened, denormalized representation of position records drawn from the PER_POSITIONS view, presenting each position as an ID/VALUE pair with effective-dating attributes and key foreign key references. Its principal role is to support Human Resources Intelligence reporting, dimensional modeling, and lookup/LOV-style integrations where a compact, current set of positions is required.

The view is defined with the WITH READ ONLY clause, so it can be queried but not modified. It is a common reference point for ETRM users searching on POSITION_DEFINITION_ID, since the view surfaces that column directly alongside the position identifier, business group, organization, and job context.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects for this view: HR_BIS (PACKAGE), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), PER_POSITIONS (VIEW), and DUAL (SYNONYM).

  • PER_POSITIONS — the primary source. The view selects POSITION_ID, NAME, DATE_EFFECTIVE, DATE_END, BUSINESS_GROUP_ID, ORGANIZATION_ID, JOB_ID, and POSITION_DEFINITION_ID from this view.
  • HR_GENERAL — supplies the sentinel constants END_OF_TIME and START_OF_TIME used in the NVL for DATE_TO and in the UNION ALL placeholder row.
  • HR_SECURITY and HR_BIS — HR security and business intelligence packages referenced by the underlying HR data model, supporting row-level security and BI extraction semantics.
  • DUAL — used to construct a synthetic "no selection" row (ID = -1) via UNION ALL.

Key Columns

  • ID — the position identifier (POS.POSITION_ID); the -1 placeholder row represents an unselected/none value.
  • VALUE — the position name (POS.NAME), used as the display value.
  • DATE_FROM — the position's date effective (POS.DATE_EFFECTIVE).
  • DATE_TO — the position's date end, defaulted to HR_GENERAL.END_OF_TIME when null.
  • BUSINESS_GROUP_ID — business group owning the position.
  • ORGANIZATION_ID — organization associated with the position.
  • JOB_ID — job linked to the position.
  • POSITION_DEFINITION_ID — identifier of the position definition record associated with the position; this is the column most frequently referenced in user searches.

Common Use Cases and Queries

The view is typically used for current-position LOVs, HR intelligence extracts, and joins that need position name plus definition context. Because the WHERE clause restricts rows to those whose DATE_END is null or in the future (TRUNC(SYSDATE) <= NVL(DATE_END, END_OF_TIME)), only active/current positions are returned.

List all current positions:

  • SELECT id, value, position_definition_id FROM apps.hri_cl_position_hx_v WHERE id > 0 ORDER BY value;

Filter by position definition:

  • SELECT id, value, job_id, organization_id FROM apps.hri_cl_position_hx_v WHERE position_definition_id = :p_def_id;

Join to a business group context:

  • SELECT p.id, p.value, p.job_id FROM apps.hri_cl_position_hx_v p WHERE p.business_group_id = :p_bg_id AND p.id > 0;

The synthetic ID = -1 row is provided for LOV implementations that require a null/none selection, and should generally be excluded in analytical queries by filtering id > 0.