Results for “per_deployment_factors”

50+ results




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

Overview

PER_DEPLOYMENT_FACTORS is an Oracle Human Resources (PER) table that stores the deployment preferences and capacity constraints recorded against a person, a position, or a job. The table description defines its purpose precisely: it holds "a factor affecting a person's capacity to be deployed within an organization." Deployment factors are the criteria used by workforce deployment, global mobility, and resource-planning processes to determine whether an employee can be assigned to a particular opportunity, project, or position — covering willingness to relocate, travel expectations, country and location restrictions, availability dates, and FTE capacity.

The table resides in the HR schema and is valid in both EBS 12.1.1 and 12.2.2; the documented physical schema for 12.2.2 records 60 columns. From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This is a suggestion rather than a prescriptive design: the table carries descriptive, attribute-rich content keyed to a central business key, which is characteristic of a satellite attached to a hub or link rather than a hub or link itself. The absence of a unique row-level business identifier beyond the composite unique key reinforces that reading.

Key Information Stored

The surrogate primary key is DEPLOYMENT_FACTOR_ID, enforced by the constraint PER_DEPLOYMENT_FACTORS_PK. The business-key candidate is defined by the unique index PER_DEPLOYMENT_FACTORS_UK over the column set POSITION_ID, PERSON_ID, and JOB_ID, meaning a single deployment-factor record is qualified by the combination of position, person, and job. BUSINESS_GROUP_ID identifies the operating unit scope and is a foreign key to HR_ALL_ORGANIZATION_UNITS.

The most significant descriptive columns fall into several groups:

Common Use Cases and Queries

The principal use cases are global mobility eligibility screening, sourcing and deployment matching, and workforce planning reports. A typical lookup resolves a person's deployment profile by joining to PER_ALL_PEOPLE_F on PERSON_ID and filtering on the current effective date. A representative pattern:

  • Retrieve deployment eligibility for a person and position: SELECT pdf.* FROM per_deployment_factors pdf WHERE pdf.person_id = :person_id AND pdf.position_id = :position_id
  • Identify candidates open to international relocation: SELECT person_id, relocate_internationally, work_any_country FROM per_deployment_factors WHERE business_group_id = :bg_id AND relocate_internationally = 'Y'
  • Find deployable resources by FTE and availability: SELECT person_id, fte_capacity, earliest_available_date FROM per_deployment_factors WHERE fte_capacity >= 0.5 AND earliest_available_date <= SYSDATE
  • Validate exclusions against a target country before proposing a move: SELECT person_id FROM per_deployment_factors WHERE no_country1 = :country OR no_country2 = :country OR no_country3 = :country

Because the table carries ATTRIBUTE_CATEGORY and the twenty attribute columns, reporting queries frequently include the DFF block to surface client-specific deployment criteria defined during implementation.

Related Objects

The documented foreign-key relationships show this table as a dependent child referencing three master objects, and as a parent referenced by one join object:

  • PER_ALL_POSITIONS — joined on PER_DEPLOYMENT_FACTORS.POSITION_ID; supplies the position against which deployment capacity is evaluated.
  • PER_JOBS — joined on PER_DEPLOYMENT_FACTORS.JOB_ID; identifies the job for which the deployment factor applies.
  • HR_ALL_ORGANIZATION_UNITS — joined on PER_DEPLOYMENT_FACTORS.BUSINESS_GROUP_ID; establishes the business group or operating unit context.
  • PQH_PTX_DPF_DF — the deployment-factor descriptive flexfield table, joined on PQH_PTX_DPF_DF.DEPLOYMENT_FACTOR_ID = PER_DEPLOYMENT_FACTORS.DEPLOYMENT_FACTOR_ID. This is the object commonly referenced by the search term "pqh_ptx_dpf_df".
  • PQH_PTX_DPF_DF_SHADOW — the shadow table maintained for the same flexfield, also joined on DEPLOYMENT_FACTOR_ID.

Taken together, these relationships place PER_DEPLOYMENT_FACTORS at the centre of the person–position–job deployment model in Oracle Human Resources, with the PQH flexfield tables supplying the extensible attribute detail.