Search Results transfer_out_date

Overview

HRFV_TRANSFERS_OUT is a business view template owned by the APPS schema in Oracle E-Business Suite, catalogued under the PER (Human Resources) product family. As stated in the ETRM metadata, it is a "business view template from which the flexfield view is generated," meaning it serves as the definitional basis for generating a flexfield-enabled view used by Oracle HRMS reporting and integration surfaces, most notably the HR Discoverer workbooks and related BI objects. The view is registered with a VALID status in the ETRM repository and is present in both Oracle EBS 12.1.1 and 12.2.2.

The view presents a denormalised, person-centric picture of employee transfer-out activity — that is, assignments whose movement out of an organization is captured through the assignment and assignment status relationships. Rather than exposing raw foreign keys alone, the template resolves organization, grade, job, position, location, person type, and lookup values into descriptive names so that downstream reports can be authored without repeated joins. The column names visible to the reporting layer include BUSINESS_GROUP_NAME, PERSON_NAME, TRANSFER_OUT_DATE, and the key organization column TRANSFER_ORGANIZATION_ID, which is precisely the identifier users search for when filtering transfer-outs in HR reports.

Underlying Base Objects

The view is defined over a substantial set of HRMS base objects. Documented base synonyms and views include HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, PER_GRADES_TL, PER_JOBS_TL, PER_PERSON_TYPES, PER_PERSON_TYPES_TL, and PER_PEOPLE_F. The definition text also references HR_LOOKUPS, PER_GRADES, PER_JOBS, PER_ALL_POSITIONS, PER_PERSON_TYPE_USAGES_F, and HR_ALL_ORGANIZATION_UNITS_TL for both the source and destination organizations.

Packages and utilities consulted at runtime include HR_BIS (for BIS_DECODE_LOOKUP), HR_DISCOVERER (CHECK_END_DATE), HR_SECURITY, HR_GENERAL, HR_API, HR_PERSON_NAME, and HRI_BPL_PERSON_TYPE. The view joins PER_ALL_ASSIGNMENTS_F twice (aliased PAF and PAF2) to distinguish the current assignment from the prior or target assignment, with PAF2.ORGANIZATION_ID surfacing as TRANSFER_ORGANIZATION_ID. This dual-alias construct is central to how the view derives transfer-out semantics.

Key Columns

• TRANSFER_ORGANIZATION_ID — the destination organization identifier, drawn from the second PER_ALL_ASSIGNMENTS_F alias (PAF2.ORGANIZATION_ID). This is the column most commonly used to filter transfer-out events.
• ORGANIZATION_NAME — the source organization name, from HOUT in the definition text.
• NEW_ORGANIZATION_NAME — the destination organization name, from ORG2T.
• TRANSFER_OUT_DATE — derived via HR_DISCOVERER.CHECK_END_DATE on PAF.EFFECTIVE_END_DATE.
• PERSON_NAME, EMPLOYEE_NUMBER — descriptive identity fields via PER_PEOPLE_F.
• ASSIGNMENT_NUMBER, ASSIGNMENT_ID — the assignment context for the transfer.
• BUSINESS_GROUP_NAME, BUSINESS_GROUP_ID — the operating business group.
• PERSON_TYPE, EMPLOYMENT_CATEGORY, BUDGET_MEASUREMENT_TYPE — decoded lookups via HR_BIS.BIS_DECODE_LOOKUP.
• GRADE_NAME, JOB_NAME, POSITION_NAME, LOCATION_NAME — decoded descriptive attributes for the assignment.

Common Use Cases and Queries

Typical uses include headcount movement reporting, organizational transfer audit, and HR Discoverer workbooks that need an enriched transfer-out listing. Because the view resolves descriptors and applies HR security semantics through its package references, it is often preferred over hand-written joins against PER_ALL_ASSIGNMENTS_F. A representative query filtering by destination organization is:

SELECT person_name,
       employee_number,
       organization_name,
       new_organization_name,
       transfer_out_date,
       transfer_organization_id
  FROM apps.hrfv_transfers_out
 WHERE transfer_organization_id = :p_org_id
   AND transfer_out_date BETWEEN :p_start AND :p_end;

Analysts commonly group by TRANSFER_ORGANIZATION_ID to summarise inbound transfers per organization, or constrain by BUSINESS_GROUP_ID to scope results to a single legislative entity. Because the view is a flexfield view template, users should note that its effective exposure of key flexfield segments depends on how the flexfield view was generated, and that row-level visibility of person data honours HR_SECURITY. In 12.2.2 the same base objects and package dependencies documented above remain in force, making queries portable between 12.1.1 and 12.2.2.