Search Results hri_loss_types




Overview
Explore in AI Chat

Overview

The view APPS.EDWBV_HR_MVMT_LOSS_1_LCV is an Oracle E-Business Suite (EBS) Business Intelligence / Enterprise Data Warehouse (EDW) seed view that exposes the top level (Level 1) of the human-resources personnel-movement "loss" hierarchy. It belongs to the standard EDW_HR_MVMT_* family of movement-analytics views shipped with Oracle HRMS Intelligence (HRMSi) and the ETRM deliverables, and it is designed to be consumed by the Daily Business Intelligence (DBI) and HRMS Intelligence reporting layers rather than by transactional forms.

The name is composed of the EDWBV prefix (Enterprise Data Warehouse Business View), the subject area HR_MVMT_LOSS, the hierarchy level indicator _1_, and the LCV suffix, which denotes a "Localized/last-cached view" or load-ready materialization view typically refreshed into the EDW staging layer. In the context of Oracle EBS 12.1.1 and 12.2.2, this view plays the role of a Level 1 lookup dimension for loss events — that is, the most granular classification detail of employee terminations and losses when reported to downstream analytics engines.

A user searching for hri_loss_types would reach this view because the loss-event lookup code is resolved through the HR_LOOKUPS table's HRI_LOSS_TYPES lookup type — a common join target for HR termination and loss analytics in EBS.

Underlying Base Objects

The view is defined over five source objects, join conditions notwithstanding, and all of them are exposed directly in the inline SQL of the view definition:

  • HRI_EDW_EVENT_HRCHYS lss — The HR event hierarchy table. The join restricts rows to hierarchy = 'Loss' and level_number = 1, so only level-1 loss events are returned.
  • HRI_EDW_USER_EVENTS usr — Optional user-defined event override table, outer-joined on user_event_type.
  • HR_LOOKUPS hrl — The standard lookup table supplying the descriptive meaning for each event code. The lookup type resolves via NVL(lss.user_event_type, 'HRI_LOSS_TYPES'), meaning the default lookup type is HRI_LOSS_TYPES but a user-defined type can override it.
  • EDW_HR_MVMT_LOSS_2_LCV ls2 — The parent (Level 2) loss view. Level 1 rows are linked to their Level 2 parent via lss.parent_event_id = ls2.loss_type_lvl2_id.
  • EDW_LOCAL_INSTANCE inst — The local instance registry providing the instance code used in the composite key.

The ETRM 12.2.2 metadata records no additional base-object dependencies, and the view is declared WITH READ ONLY.

Key Columns

  • loss_type_lvl1_pk — Composite primary key built as lvl2_pk || '-' || event_code || '-' || instance_code.
  • loss_type_lvl2_fk — Foreign key to the parent Level 2 loss view.
  • instance — Instance code of the local EBS instance.
  • name / loss_type_lvl1_dp — Display name taken from HR_LOOKUPS.meaning.
  • lookup_code — The event code (event_code or user override).
  • loss_type_lvl1_id — The underlying event_id.
  • last_update_date, creation_date — Audit columns; last_update_date is the greatest of the event and lookup timestamps, defaulting to 01-01-2000 when null.

Common Use Cases and Queries

The view is typically used to drive loss-analysis dashboards and to translate termination event codes into human-readable descriptions.

  • Reporting level-1 loss reasons alongside their level-2 parent categories.
  • Joining loss facts (headcount, turnover) back to this dimension via loss_type_lvl1_pk.
  • Reconciling lookup values against HRI_LOSS_TYPES to validate custom codes.

Sample query:

SELECT loss_type_lvl1_pk,
       loss_type_lvl2_fk,
       name,
       lookup_code,
       instance
FROM   apps.edwbv_hr_mvmt_loss_1_lcv
WHERE  instance = 'VISION'
ORDER  BY name;

To trace lookup definitions, join this view to FND_LOOKUP_VALUES on lookup_code where lookup_type = 'HRI_LOSS_TYPES'. Because the view is read-only and lightweight, it is safe to query directly from BI Publisher and OBIEE data models in both 12.1.1 and 12.2.2.