Results for “edw_hr_ract_act_type_lcv”

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

Overview

EDW_HR_RACT_ACT_TYPE_LCV is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the HRI (Human Resources Intelligence) product family. It exposes recruitment activity type list-of-values information in a denormalized form suitable for reporting, extraction, and integration workloads. The LCV suffix indicates that the object is a list-of-values view, meaning it is designed to present a clean, human-readable projection of code values rather than to serve as a transactional object. Its principal purpose is to translate the internal primary key and foreign key identifiers used by the recruitment activity type entity into the descriptive code, name, and display values that downstream consumers — Oracle Business Intelligence, HR data warehouses, and custom ETL routines — can use without traversing base tables directly.

The view is defined in the ETRM repository as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its header comment ($HEADER: HRIVIEW.LDT 115.3 2001/09/18 10:51:35 PKM SHIP $) identifies it as a generated HR Intelligence view, shipped with the standard HRI layer rather than as a customer modification.

Underlying Base Objects

ETRM documentation for the 12.2.2 release records no explicitly documented base objects for this view. The view text itself, however, defines it entirely as a selection from EDWBV_HR_RACT_ACT_TYPE_LCV, which in the HRI naming convention is a business view (BV) layer object. The APPS-level view therefore acts as a thin pass-through wrapper over the HRI business view, which in turn resolves to the underlying recruitment activity type base tables and their translations. No joins, aggregations, or filters appear in the view definition; the column list is projected directly, and five user attribute columns are hard-coded as NULL.

Because the view is a single-source projection, it inherits the row cardinality and row-level security behavior of the underlying business view. No DML is permitted against it; it is strictly read-only.

Key Columns

• ACTIVITY_TYPE_PK — Surrogate primary key of the recruitment activity type. Used as the join key to transactional recruitment activity records.
• ALL_FK — The foreign key column that joins this lookup to the parent recruitment activity or activity group entity.
• ACTIVITY_TYPE_CODE — The code value that users search on when they query "activity_type_code". This is the business identifier for the activity type and the column most commonly referenced in filters and extract criteria.
• NAME — The descriptive name of the activity type, typically the translated or user-facing label.
• ACTIVITY_TYPE_DP — The display value for the activity type, used in list-of-values presentation.
• INSTANCE — Identifies the HRI instance or source system context for the row.
• LAST_UPDATE_DATE / CREATION_DATE — Standard audit columns supporting incremental extract logic and change detection.
• USER_ATTRIBUTE1–USER_ATTRIBUTE5 — Placeholders, populated as NULL by this view; retained for structural compatibility with the underlying HRI business view.

Common Use Cases and Queries

The view is most often used to resolve activity type codes into names for recruitment reports, and to drive list-of-values selections in custom concurrent programs or OAF pages. A typical lookup by the code the user searched for:

SELECT activity_type_code, name, activity_type_dp
FROM apps.edw_hr_ract_act_type_lcv
WHERE activity_type_code = :p_activity_type_code;

To enumerate all available activity types for a parameter list of values:

SELECT activity_type_code, name
FROM apps.edw_hr_ract_act_type_lcv
ORDER BY name;

For incremental warehouse loads, the audit columns support delta extraction:

SELECT activity_type_pk, activity_type_code, name, last_update_date
FROM apps.edw_hr_ract_act_type_lcv
WHERE last_update_date >= :p_since_date;

Because the view is read-only and unfiltered, consumers should apply their own instance and date predicates, and should join to transactional recruitment tables on ACTIVITY_TYPE_PK rather than on the code column, which is not guaranteed to be unique across instances.