Search Results transfer_out_date

Overview

APPS.HRFV_TRANSFERS_OUT is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered in FND Design Data as PER.HRFV_TRANSFERS_OUT and carries a VALID status. The view exposes internal transfers of employees from one organization to another, and critically, the assignment information it returns relates to the organization out of which the employee has transferred. This "outbound" orientation distinguishes it from its counterpart views and makes it the appropriate source when reporting on the losing or originating side of an organizational move.

Because the view is designed as a BIS object, it is consumed primarily by Oracle HRMS Discoverer workbooks, HRMS reporting, and custom operational reports. The column of direct interest for the search term is TRANSFER_OUT_DATE, a DATE column that records the effective date on which the employee left the originating organization. Reporting users frequently filter or order by this column to produce transfer registers, attrition-style analyses by organization, and headcount movement trends.

Underlying Base Objects

The documented dependencies show that HRFV_TRANSFERS_OUT is not defined over a single table but is assembled by several HRMS packages and their related base and synonym objects. The referenced base objects include PER_ALL_ASSIGNMENTS_F and PER_ASSIGNMENT_STATUS_TYPES, which supply the assignment and status context; PER_PEOPLE_F and PER_PERSON_TYPES (with PER_PERSON_TYPES_TL) for person identity, system person type, and person type translations; HR_ALL_ORGANIZATION_UNITS_TL, HR_ALL_POSITIONS_F_TL, HR_LOCATIONS_ALL_TL, PER_GRADES_TL, and PER_JOBS_TL for the descriptive name attributes; and HR_LOOKUPS for lookup-backed values such as employment category. The view is also documented as referencing APPS.FND_GL (FND Design Data dependency), and it depends on the packages HR_BIS, HR_DISCOVERER, HR_GENERAL, HR_SECURITY, HR_API, HR_PERSON_NAME, and HRI_BPL_PERSON_TYPE.

The presence of HR_SECURITY is significant: queries against this view are filtered by the security profile of the connecting user or responsibility, so a report executed by a line manager will return a narrower row set than one executed by an HR super user.

Key Columns

• TRANSFER_OUT_DATE (DATE) — the effective date the employee transferred out of the originating organization; the primary date dimension for this view.
• ORGANIZATION_NAME (VARCHAR2 240) — the organization the employee left.
• NEW_ORGANIZATION_NAME (VARCHAR2 240) — the destination organization.
• TRANSFER_ORGANIZATION_ID (NUMBER 15) — identifier relating to the transfer organization.
• PERSON_NAME (VARCHAR2 240), PERSON_ID (NUMBER 10), EMPLOYEE_NUMBER, ASSIGNMENT_NUMBER, ASSIGNMENT_ID — person and assignment identification.
• BUSINESS_GROUP_NAME (VARCHAR2 240), BUSINESS_GROUP_ID (NUMBER 15) — the enterprise business group scope.
• BUDGET_MEASUREMENT_TYPE (VARCHAR2 4000), BUDGET_MEASUREMENT_CODE (VARCHAR2 30) — budgeting context for the assignment.
• GRADE_NAME, JOB_NAME, POSITION_NAME, LOCATION_NAME — descriptive attributes of the originating assignment, with GRADE_ID, JOB_ID, POSITION_ID, ORGANIZATION_ID and PERSON_TYPE_ID retained as keys.
• PERSON_TYPE, EMPLOYEE_PERSON_TYPE, USER_CONCAT_PERSON_TYPE, SYSTEM_PERSON_TYPE_CODE, EMPLOYMENT_CATEGORY — person-type and category classification values.

Common Use Cases and Queries

Typical scenarios include transfer registers by date range, cross-organization movement analysis, and reconciliations of headcount leaving a cost centre. The following example returns all transfers out during a fiscal year for a business group, ordered by transfer date.

• SELECT person_name, employee_number, organization_name, new_organization_name, transfer_out_date, job_name, grade_name FROM apps.hrfv_transfers_out WHERE transfer_out_date BETWEEN TO_DATE('01-JAN-2024','DD-MON-YYYY') AND TO_DATE('31-DEC-2024','DD-MON-YYYY') AND business_group_id = :p_bg_id ORDER BY transfer_out_date;
• Aggregate movements by originating organization: SELECT organization_name, COUNT(*) transfers FROM apps.hrfv_transfers_out WHERE transfer_out_date >= :p_start GROUP BY organization_name ORDER BY 2 DESC;
• Identify high-volume destination pairs: SELECT organization_name, new_organization_name, COUNT(*) FROM apps.hrfv_transfers_out GROUP BY organization_name, new_organization_name;

Because the view is secured, always bind the business group and validate results with an HR responsibility that has appropriate organization access.