Search Results requisition_id




Overview

EDW_HR_RQVC_REQUISTN_LCV is an Oracle EBS view owned by the APPS schema and classified under the HRI (Human Resources Intelligence) product family. It forms part of the Oracle HRMS Intelligence (HRMSi) reporting and data-warehouse layer, which predates and complements the later Oracle Business Intelligence Applications. The suffix "LCV" conventionally denotes a "List of Values" (LOV) view within the HRMSi/EDW naming conventions, while "RQVC" abbreviates Requisition Version Current. The view therefore exposes a current-version, LOV-friendly projection of HR requisition data suitable for concurrent-program extracts, Discoverer workbooks, and downstream warehouse staging.

For users searching on the column requisition_id, this view is significant because it explicitly projects REQUISITION_ID alongside the surrogate primary key REQUISITION_PK and a set of descriptive attributes. This makes it a convenient access point when a requisition identifier must be resolved to its business-group context, effective dates, or denormalized version attributes without joining the full base requisition table set.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined directly over a single underlying object: EDWBV_HR_RQVC_REQUISTN_LCV. The "EDWBV" prefix indicates an Enterprise Data Warehouse Base View, itself a lower-tier HRMSi view layered over the physical HR_ requisition tables (typically HR_ALL_POSITIONS or the requisition version entities such as PER_REQUISITIONS and its _F/_VL variants).

The view text is minimal and involves no joins, aggregations, or filter predicates. It performs a straight column projection with five literal NULL placeholders appended for USER_ATTRIBUTE1 through USER_ATTRIBUTE5. The documentation lists no referenced base tables, confirming that all physical-table access is encapsulated within EDWBV_HR_RQVC_REQUISTN_LCV. Consequently, the effective grain of this LCV is one row per requisition version record as returned by the base view.

The header comment $HEADER: HRIVIEW.LDT 115.3 2001/09/18 10:51:35 PKM SHIP $ dates the object to the original HRMSi 11i development cycle; the same definition is carried forward into 12.1.1 and 12.2.2 without modification.

Key Columns

  • REQUISITION_ID — the operational requisition identifier, the primary search key and the join column to transactional requisition tables.
  • REQUISITION_PK — the surrogate primary key of the requisition entity within the EDW.
  • REQUISITION_DP — the "display" or descriptive name value used in LOV pickers.
  • NAME — the requisition name exposed for display and reporting.
  • BUSINESS_GROUP_ID — the HR business group (legislative/operating unit) to which the requisition belongs; essential for multi-organization filtering.
  • ALL_FK — the warehouse "all foreign key" surrogate used for star-schema dimension joins.
  • INSTANCE — identifies the source EBS instance or warehouse load instance.
  • START_DATE / END_DATE — the effective date range of the requisition version.
  • CREATION_DATE / LAST_UPDATE_DATE — audit stamps propagated from the base record.
  • USER_ATTRIBUTE1–5 — present in the select list as literal NULLs, retained for uniform shape compatibility with the base view definition.

Common Use Cases and Queries

Typical uses include LOV population in custom Forms, HRMSi extract programs, and ad-hoc reporting where requisition identifiers must be enumerated with their business group and effective dates.

Listing requisitions for a business group:

SELECT requisition_id, name, business_group_id, start_date, end_date
FROM   apps.edw_hr_rqvc_requistn_lcv
WHERE  business_group_id = :p_bg_id
ORDER  BY name;

Resolving a known requisition identifier:

SELECT requisition_pk, name, requisition_dp, creation_date
FROM   apps.edw_hr_rqvc_requistn_lcv
WHERE  requisition_id = :p_requisition_id;

Because the view is unpredicated, always constrain by BUSINESS_GROUP_ID, REQUISITION_ID, or effective dates to avoid full-view scans, and reference the EDWBV base view directly if the underlying source instance must be inspected.