Search Results requisition_dp

Overview

APPS.EDW_HR_RQVC_REQUISTN_LCV is a reporting-layer view in the Oracle E-Business Suite human resources data warehouse schema (EDW). It forms part of the HR requisition and vacancy (RQVC) family of objects and is maintained under the HRISVVC object definition file (hrisvvc.odf), whose header dates to the 11i release and remained in place through EBS 12.1.1 and 12.2.2. The view presents a consolidated, denormalised projection of requisition and vacancy records intended for extract, reporting, and downstream integration rather than for online transactional use.

The _LCV suffix denotes the lowest-level component view in the ETRM "collection view" naming convention, which supplies the grain and column set from which higher-level or language-specific collections are built. As with other EDW objects, the view is a read-only construct owned by APPS and is not part of the base Oracle HRMS application schema.

Underlying Base Objects

Per the documented view text, the sole referenced object is EDWBV_HR_RQVC_REQUISTN_LCV:

• SELECT requisition_pk, all_fk, instance, name, requisition_dp, business_group_id, requisition_id, start_date, end_date, creation_date, last_update_date, null, null, null, null, null FROM edwbv_hr_rqvc_requistn_lcv

The EDWBV_ prefix indicates a base (or "business") view in the warehouse layer that itself abstracts the underlying HRMS tables. ETRM documents no further base tables for EDW_HR_RQVC_REQUISTN_LCV; the six trailing NULL columns are placeholders that reserve positions for attributes supplied by other collection members. The view therefore functions as a thin, deterministic projection over EDWBV_HR_RQVC_REQUISTN_LCV, and any change to that base view flows directly through.

Key Columns

• REQUISITION_PK — surrogate primary key for the requisition row within the warehouse.
• ALL_FK — the "all" foreign key, a warehouse convention used to join this view to the shared dimension set.
• INSTANCE — identifies the source EBS instance, supporting multi-instance consolidation.
• NAME — the requisition or vacancy name/description as displayed to users.
• REQUISITION_DP — the requisition display/descriptive field; this is the column commonly targeted by searches for the term requisition_dp.
• BUSINESS_GROUP_ID — the HR business group that owns the record, used for security and organisation filtering.
• REQUISITION_ID — the operational requisition identifier from the source HRMS tables.
• START_DATE / END_DATE — the effective period during which the requisition is active.
• CREATION_DATE / LAST_UPDATE_DATE — standard audit columns recording row creation and the most recent modification.

Common Use Cases and Queries

The view is typically joined to date, business group, and organisation dimensions to produce requisition and vacancy extract reports, headcount demand analyses, and interfaces feeding external HR systems.

Retrieve all open requisitions for a business group:

• SELECT requisition_id, name, requisition_dp, start_date, end_date FROM apps.edw_hr_rqvc_requistn_lcv WHERE business_group_id = :p_bg_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Incremental extract for a warehouse load:

• SELECT requisition_pk, all_fk, instance, requisition_id, last_update_date FROM apps.edw_hr_rqvc_requistn_lcv WHERE last_update_date >= :p_since;

Search by descriptive text and instance:

• SELECT requisition_id, name, requisition_dp FROM apps.edw_hr_rqvc_requistn_lcv WHERE instance = :p_instance AND UPPER(requisition_dp) LIKE '%' || UPPER(:p_term) || '%';

Because the view is read-only and defined over a single base view, queries should be restricted by INSTANCE, BUSINESS_GROUP_ID, and LAST_UPDATE_DATE to limit scan cost in large multi-instance warehouse environments.