Results for “per_deployment_factors_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The PER_DEPLOYMENT_FACTORS_V view is an Oracle E-Business Suite Human Resources (PER) object owned by the APPS schema. In both EBS 12.1.1 and 12.2.2, its documented purpose is to support the user interface layer of the HR deployment and mobility functionality. The view consolidates deployment preference data stored in the base deployment factors entity and presents it alongside decoded descriptive values for countries, lookups, and locations, so that forms and pages can render human-readable text instead of raw coded identifiers.

Rather than storing data itself, the view acts as a read-only presentation layer over deployment factors records. It exposes location, travel, relocation, and work-schedule preferences for a given person, job, or position within a business group, joining to territory and lookup views to resolve meaning columns. Because it is an APPS-owned view based on a synonym to the underlying base table, it is typically referenced through the standard HR deployment pages rather than called directly, and it should be treated as subject to change with the underlying HR product.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects for PER_DEPLOYMENT_FACTORS_V:

• PER_DEPLOYMENT_FACTORS (SYNONYM) – the primary base table holding the deployment factor rows that drive the view.
• FND_TERRITORIES_VL (VIEW) – used to resolve territory short names for the COUNTRY1–3 and NO_COUNTRY1–3 columns.
• HR_LOOKUPS (VIEW) – used to resolve lookup meaning values for work duration, work schedule, work hours, FTE capacity, relocation preference, and service minimum.
• HR_LOCATIONS_ALL_TL (SYNONYM) and HR_LOCATIONS_NO_JOIN (VIEW) – used to derive location code meanings for LOCATION1–3.
• HR_API (PACKAGE) and HR_GENERAL (PACKAGE) – HR PL/SQL packages referenced by the view definition and its supporting logic.

These objects are joined mainly through primary and foreign key relationships on deployment factor ID, position, person, job, and business group identifiers, with outer joins to reference views so that meaning columns resolve to appropriate territory short names, lookup meanings, and location codes.

Key Columns

The view exposes identifiers such as DEPLOYMENT_FACTOR_ID, POSITION_ID, PERSON_ID, JOB_ID, and BUSINESS_GROUP_ID, which define the context of each deployment preference record. Preference columns include WORK_ANY_COUNTRY, WORK_ANY_LOCATION, RELOCATE_DOMESTICALLY, RELOCATE_INTERNATIONALLY, TRAVEL_REQUIRED, VISIT_INTERNATIONALLY, ONLY_CURRENT_LOCATION, AVAILABLE_FOR_TRANSFER, RELOCATION_REQUIRED, and PASSPORT_REQUIRED.

Geographic preferences are captured by COUNTRY1–3 and NO_COUNTRY1–3, each paired with decoded meanings such as COUNTRY1_MEANING and NO_COUNTRY1_MEANING derived from territory short names. LOCATION1–3 are similarly paired with LOCATION1_MEANING through LOCATION3_MEANING. Definitional attributes include WORK_DURATION, WORK_SCHEDULE, WORK_HOURS, FTE_CAPACITY, SERVICE_MINIMUM, and RELOCATION_PREFERENCE, all with associated meaning columns. Descriptive and audit columns include COMMENTS, EARLIEST_AVAILABLE_DATE, OTHER_REQUIREMENTS, OBJECT_VERSION_NUMBER, the DFF columns ATTRIBUTE_CATEGORY and ATTRIBUTE1–20, and standard created by and updated by audit fields.

Common Use Cases and Queries

A frequent requirement is retrieving a person's deployment preferences with decoded country values. Because users often search for the NO_COUNTRY1 column in the context of excluded or "not preferred" countries, the following pattern is typical:

• Reporting a person's relocation and travel preferences for a mobility dashboard.
• Identifying candidates available for international transfer, filtered on AVAILABLE_FOR_TRANSFER and RELOCATE_INTERNATIONALLY.
• Listing excluded countries using NO_COUNTRY1 and its decoded NO_COUNTRY1_MEANING.
• Validating deployment factor data during concurrent processing or interface loads.

A representative query is:

SELECT pdf.person_id, pdf.deployment_factor_id, pdf.country1, pdf.country1_meaning, pdf.no_country1, pdf.no_country1_meaning, pdf.relocate_internationally, pdf.available_for_transfer FROM apps.per_deployment_factors_v pdf WHERE pdf.person_id = :person_id;

Because the view is read-only and intended for user interface support, direct DML against it is not supported. All maintenance must be performed against the underlying PER_DEPLOYMENT_FACTORS base entity through the standard HR deployment pages or supported HR APIs. Adopting the version-specific naming (NO_COUNTRY1 versus any legacy alias) is important when migrating between 12.1.1 and 12.2.2, as the exposed column set reflects the 12.2.2 view definition.