Results for “all_fk”

50+ results




Overview
Explore in AI Chat

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

Overview

EDWBV_HR_RACT_ACT_TYPE_LCV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the HRI (Human Resources Intelligence) product family. It is part of the Oracle HRMS Intelligence / ETRM (Enterprise Technical Reference Manual) reporting layer, which supplies flattened, business-friendly views intended for extract, reporting, and analytical consumption rather than for transactional use.

The view presents a denormalized list of recruitment activity types, driven by the HR_LOOKUPS lookup type REC_TYPE and cross-joined to the local instance definition. Its header comment block ($HEADER: HRIVIEW.LDT 115.3 2001/09/18) indicates the object dates back to the early HR Intelligence releases and has remained stable across 12.1.1 and 12.2.2. In EBS 12.2.2 the view is reported in VALID status, meaning it compiles cleanly against the online edition of the APPS schema. The "_LCV" suffix denotes a "List of Values" style view, commonly used to populate selection lists, parameter values, and dimension source queries in HR Intelligence dashboards and custom extracts. Because it carries a fixed ALL_FK pseudo-key, it is designed to be joined loosely as a dimension rather than through a strict foreign key relationship.

Underlying Base Objects

The view is defined over two documented base objects within the APPS schema:

  • HR_LOOKUPS — the FND/HR lookup table holding lookup codes and their meanings. The view restricts this table to LOOKUP_TYPE = 'REC_TYPE', isolating recruitment activity classification values.
  • EDW_LOCAL_INSTANCE — the HR Intelligence local instance table providing the INSTANCE_CODE that identifies the current EBS instance. The query uses a Cartesian (cross) join, so every REC_TYPE lookup row is reproduced once per instance record.

No further base objects are documented in the ETRM metadata. The cross join is significant: if EDW_LOCAL_INSTANCE contains more than one row, the view will multiply the lookup rows accordingly. The recommended deployment is a single instance row per database.

Key Columns

  • ACTIVITY_TYPE_PK — synthetic primary key formed as LOOKUP_CODE concatenated with a hyphen and INSTANCE_CODE. Uniquely identifies an activity type within an instance.
  • ALL_FK — constant literal 'ALL'. Used as a dummy join key for outer-style joins when a consumer needs every activity type regardless of matching fact rows.
  • ACTIVITY_TYPE_CODE — the raw HR_LOOKUPS.LOOKUP_CODE value for the REC_TYPE lookup type.
  • NAME and ACTIVITY_TYPE_DP — display values rendered as MEANING(INSTANCE_CODE), combining the lookup meaning with the instance code for presentation in LOVs and reports.
  • INSTANCE — the EDW_LOCAL_INSTANCE.INSTANCE_CODE sourced from the local instance table.
  • LAST_UPDATE_DATE — the lookup's last update date, defaulted to 01-JAN-2000 when null, ensuring downstream incremental extracts never receive a null watermark.
  • CREATION_DATE — the creation date of the underlying HR_LOOKUPS row.

Common Use Cases and Queries

Typical usages include populating activity type LOVs in HR Intelligence recruitment reports, supplying dimension rows for activity type analysis, and acting as a validation reference for extracts. A representative query is:

  • SELECT ACTIVITY_TYPE_PK, ACTIVITY_TYPE_CODE, NAME, INSTANCE FROM APPS.EDWBV_HR_RACT_ACT_TYPE_LCV ORDER BY ACTIVITY_TYPE_CODE;
  • SELECT ACTIVITY_TYPE_DP FROM APPS.EDWBV_HR_RACT_ACT_TYPE_LCV WHERE INSTANCE = :p_instance;
  • Outer-join pattern to preserve all activity types against a fact set: ... FROM EDW_FACT F, EDWBV_HR_RACT_ACT_TYPE_LCV A WHERE F.ALL_FK = A.ALL_FK;

Because the view simply reads HR_LOOKUPS, any change to a REC_TYPE lookup — value, meaning, or disablement — is reflected immediately. Queries should be written to tolerate the absence of rows for inactive or end-dated lookups if only currently effective activity types are required.