Search Results preferred_location1

Overview

HRFV_DEPLOYMENT_FACTORS is an APPS-owned business view in the PER (Human Resources) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Per the ETRM documentation, it is described as a "business view template from which the flexfield view is generated." In the Oracle EBS "HRFV" naming convention, these views expose Human Resources data in a flattened, descriptive form suitable for reporting tools, flexfield-based descriptive flexfield (DFF) business components, and integration layers that need human-readable meaning rather than raw lookup codes. The view is central to deployment and mobility reporting, providing recruitment and deployment planners with a single row per person deployment profile, enriched with decoded lookup values and descriptive territory, location, and organization names.

Underlying Base Objects

The view is defined primarily over the deployment factors synonym PER_DEPLOYMENT_FACTORS, which holds the raw deployment preference data. It joins this to several HR base objects and packages documented in the view metadata:

• HR_BIS (package) — supplies the BIS_DECODE_LOOKUP function used to translate stored codes into meaningful descriptions.
• FND_TERRITORIES_VL (view) — used repeatedly (aliases TER1–TER6) to resolve preferred and avoid country territory short names.
• HR_LOCATIONS_ALL_TL (synonym) — resolves preferred location codes (HRL1TL–HRL3TL).
• HR_ALL_ORGANIZATION_UNITS_TL (synonym) — supplies the business group name.
• PER_PEOPLE_X (view), HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY (packages) — support person-level context and security filtering.
• PER_JOBS_TL and HR_ALL_POSITIONS_F_TL (synonyms) — for the person's job and position descriptors.

These referenced objects confirm the view is a multi-table reporting construct that joins deployment factors to descriptive HR reference data rather than a single-table projection.

Key Columns

The view exposes the identifier deployment_factor_id for each deployment profile row. Descriptive columns include:

• BUSINESS_GROUP_NAME — the HR business group the record belongs to.
• WORK_ANY_COUNTRY, WORK_ANY_LOCATION, RELOCATE_DOMESTICALLY, RELOCATE_INTERNATIONALLY, TRAVEL_REQUIRED — decoded YES/NO flags describing work and mobility flexibility.
• PREFERRED_COUNTRY1–3 and AVOID_COUNTRY1–3 — territory short names for geographic preferences and exclusions.
• WORK_DURATION, WORK_SCHEDULE, WORK_HOURS, FTE_CAPACITY — decoded work pattern attributes.
• VISIT_INTERNATIONALLY, ONLY_CURRENT_LOCATION, AVAILABLE_FOR_TRANSFER — further YES/NO mobility flags.
• RELOCATION_PREFERENCE, RELOCATION_REQUIRED, PASSPORT_REQUIRED — decoded relocation attributes.
• PREFERRED_LOCATION1–3 — location codes for preferred work locations.
• EARLIEST_AVAILABLE_DATE, COMMENTS, OTHER_REQUIREMENTS — free-form and date fields.

Common Use Cases and Queries

This view is typically queried for deployment and global mobility reporting, and to feed downstream integration or BI extracts. A common pattern is searching by the deployment factor identifier returned when users query "deployment_factor_id":

• Retrieve a full deployment profile for a person: SELECT deployment_factor_id, business_group_name, work_any_country, relocate_internationally FROM apps.hrfv_deployment_factors WHERE deployment_factor_id = :p_id;
• Report candidates available for international transfer.
• Produce mobility dashboards decoding relocation and travel preferences.

Because the view decodes codes through HR_BIS, it should be preferred over querying PER_DEPLOYMENT_FACTORS directly when human-readable output is required. Note that referenced packages (HR_SECURITY, HR_GENERAL) may impose business-group security filters, so query results respect the caller's HR security profile, and joins to person tables should use the standard HR person keys.