Search Results hrfv_movements_summary




Overview
Explore in AI Chat

Overview

HRFV_MOVEMENTS_SUMMARY is a business view template owned by the APPS schema within the Oracle E-Business Suite Human Resources (PER) product family. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, its stated purpose is to serve as the business view template from which a corresponding flexfield view is generated. The view consolidates assignment-based movement events — most notably hires and terminations — into a single, report-friendly structure that exposes headcount activity across business groups and organizations. It is a standard component of the Oracle HRMS reporting and analytics layer, and consequently it is frequently referenced by Discoverer workbooks, BIS (Business Intelligence System) reports, and custom extracts that need a normalized view of workforce movements.

Because the object is defined as a template rather than a purely transactional query, it plays a dual role: it provides a queryable business abstraction for movement data, while also acting as the seed definition for generated flexfield views in the HR reporting architecture.

Underlying Base Objects

The documented view metadata identifies the following referenced base objects: HR_ALL_ORGANIZATION_UNITS_TL, HR_API, HR_BIS, HR_DISCOVERER, HR_GENERAL, HR_LOOKUPS, HR_SECURITY, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, and PER_PERIODS_OF_SERVICE.

The core data originates from PER_PERIODS_OF_SERVICE and PER_ASSIGNMENTS_F. The primary assignments view supplies the assignment identifier, business group, organization, assignment type, and primary flag, while the periods-of-service entity supplies the start date (used as the hire movement date) and the actual termination date (used as the termination movement date). HR_ALL_ORGANIZATION_UNITS_TL is joined twice — once aliased as HOUT to resolve the organization name and once as BGRT to resolve the business group name — with both joins restricted to the user's session language via USERENV('LANG'). HR_LOOKUPS is joined on the BUDGET_MEASUREMENT_TYPE lookup type to supply the measurement code, and the HR_BIS package is invoked through BIS_DECODE_LOOKUP to decode that code into a readable value. The security packages HR_SECURITY and HR_BIS (GET_SEC_PROFILE_BG_ID) enforce business group security filtering.

Key Columns

  • BUSINESS_GROUP_NAME — Name of the business group derived from HR_ALL_ORGANIZATION_UNITS_TL.
  • BUDGET_MEASUREMENT_TYPE — Decoded description of the budget measurement type, via HR_BIS.BIS_DECODE_LOOKUP.
  • BUDGET_MEASUREMENT_CODE — The raw lookup code from HR_LOOKUPS for the BUDGET_MEASUREMENT_TYPE lookup type.
  • ORGANIZATION_NAME — Name of the organization associated with the assignment.
  • MOVEMENT_DATE — Date the movement occurred; the period-of-service start date for hires, and the actual termination date for terminations.
  • MOVEMENT_TYPE — Literal discriminator column returning 'HIRE' or 'TERMINATION'. This is the column most relevant to the "movement_type" search, since it is the filter and grouping key users typically target.
  • ASSIGNMENT_ID — Identifier of the underlying assignment in PER_ASSIGNMENTS_F.
  • BUSINESS_GROUP_ID — Business group identifier, used for security and partitioning.
  • ORGANIZATION_ID — Organization identifier tied to the assignment.

Common Use Cases and Queries

The view is typically used to report headcount gains and losses by period, business group, or organization. A representative query filtering on movement type is shown below.

  • Headcount movement listings filtered by event type.
  • Hire and termination trend reporting by business group or organization.
  • Reconciliation of period-of-service start and actual termination dates against assignment records.
  • Feeding Discoverer or BIS workbooks that depend on the generated flexfield view.

Sample SQL: SELECT business_group_name, organization_name, movement_type, movement_date, assignment_id FROM apps.hrfv_movements_summary WHERE movement_type = 'TERMINATION' ORDER BY movement_date;

Restricting on movements of a single type, or grouping by MOVEMENT_TYPE and MOVEMENT_DATE, provides a straightforward basis for period-over-period workforce movement analysis. Users should remain aware that business group security is enforced internally, so result sets are scoped to the business groups accessible to the connecting user.