Search Results budget_measurement_type




Overview
Explore in AI Chat

Overview

APPS.HRFV_MOVEMENTS_SUMMARY is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates employee movement events—specifically hires and terminations—into a single, uniformly structured result set. It is part of the Oracle HRMS (Human Resources Management System) family of "HRFV" views, which are designed to present pre-joined, business-friendly data suitable for reporting, ad-hoc queries, and integration extracts. Rather than requiring report authors to reconcile assignment, period-of-service, organization, and lookup data across multiple tables, the view collapses this logic into a unified projection.

The view produces one row per qualifying movement, labelled either as a "Hire" or a "Termination". Each row is enriched with decoded descriptive attributes, including business group name and organization name (resolved through the translated organization table using the current session language), and a descriptive budget measurement type decoded from the BUDGET_MEASUREMENT_TYPE lookup. Because the view applies the security profile of the current business group, its output is implicitly filtered to the data the operating user is authorised to see.

Underlying Base Objects

The view is defined as a UNION ALL of two SELECT statements. The first branch captures hires, joining PER_PERIODS_OF_SERVICE, PER_ASSIGNMENTS_F (or its PER_ASSIGNMENTS_F synonym), HR_ALL_ORGANIZATION_UNITS_TL, HR_LOOKUPS, and org-unit translation tables. The second branch captures terminations using an analogous join set. Documented referenced base objects include HR_ALL_ORGANIZATION_UNITS_TL, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_ASSIGNMENT_STATUS_TYPES, and HR_LOOKUPS, together with the HR_API, HR_BIS, HR_DISCOVERER, HR_GENERAL, and HR_SECURITY packages.

Two packages are central to its behaviour. HR_BIS provides the bis_decode_lookup function used to translate the lookup code into the descriptive budget measurement type and the get_sec_profile_bg_id call that enforces business-group security. The JOIN to HR_LOOKUPS with lookup_type = 'BUDGET_MEASUREMENT_TYPE' restricts rows to assignments whose lookup values align with the budget measurement classification.

Key Columns

  • business_group_name — the translated name of the business group owning the assignment.
  • budget_measurement_type — the decoded, user-readable description from the BUDGET_MEASUREMENT_TYPE lookup (the column most directly associated with the search term "budget_measurement_type").
  • budget_measurement_code — the raw lookup code underlying the measurement type.
  • organization_name — the translated name of the organization to which the assignment belongs.
  • movement_date — the hire date (from period-of-service start) or the actual termination date, depending on the branch.
  • movement_type — a literal, either "Hire" or "Termination".
  • assignment_id, business_group_id, organization_id — key identifiers linking the row back to the HRMS entity model.

Common Use Cases and Queries

The view is typically used for headcount movement reporting, trend analysis of hires versus terminations, and reconciliation feeds into downstream HR or budgeting systems where the budget measurement classification must be applied. A representative query selecting movement activity for a business group would be:

  • SELECT movement_type, budget_measurement_type, organization_name, movement_date FROM apps.hrfv_movements_summary WHERE business_group_name = :p_bg ORDER BY movement_date;
  • SELECT budget_measurement_type, COUNT(*) FROM apps.hrfv_movements_summary WHERE movement_type = 'Hire' GROUP BY budget_measurement_type;
  • SELECT organization_name, movement_type, COUNT(*) FROM apps.hrfv_movements_summary GROUP BY organization_name, movement_type;

Because output is subject to the HR security profile, results returned by these queries reflect only the business groups and organizations the run-time user is permitted to access. Report designers should note that the view filters on primary, employee-type assignments only, so contingent worker or non-primary assignment movements are excluded by design.