Results for “projected_hire_date”

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

Overview

PER_APPLICATIONS is a Human Resources (PER) module table in the Oracle E-Business Suite HR schema, documented in ETRM 12.1.1 and 12.2.2 with status VALID. The table stores applications for employment — the record created when a candidate applies for a position within a business group. Each row captures the applicant's identity, the recruitment dates associated with the application, outcome indicators, and a set of descriptive flexfield segments for client-specific attributes. In the recruitment lifecycle, PER_APPLICATIONS sits between the candidate (person) record and the resulting assignment, acting as the transactional anchor that links a prospective employee to a hire decision.

From a heuristic Data Vault modeling perspective — mined from the documented foreign key structure — PER_APPLICATIONS is classified as satellite-leaning. It carries a surrogate primary key of its own while referencing a single parent (the business group), and it holds a wide set of descriptive and tracking attributes. This suggests it behaves principally as a descriptive satellite attached to a hub-level entity, rather than as a pure link resolving many-to-many relationships.

Key Information Stored

The documented physical schema contains 41 columns. The surrogate primary key is APPLICATION_ID, enforced by the unique index PER_APPLICATIONS_PK. The unique index list also includes SYS_IL0000043548C00041$$, which is a system-managed LOB index rather than a business-key candidate; the only true business-key candidate documented is the primary key itself.

• APPLICATION_ID — surrogate primary key uniquely identifying each employment application.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS, scoping the application to a business group.
• PERSON_ID — the person (applicant) associated with the application.
• DATE_RECEIVED — date the application was received.
• DATE_END — end date for the application record.
• PROJECTED_HIRE_DATE — anticipated hire date for the candidate.
• SUCCESSFUL_FLAG — indicates whether the application resulted in a successful hire.
• TERMINATION_REASON — reason recorded against the application outcome or termination.
• CURRENT_EMPLOYER — the applicant's current or prior employer.
• REQUEST_ID — concurrent request identifier for the process that created or updated the row.
• PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — concurrent program context and last program-driven update timestamp.
• APPL_ATTRIBUTE_CATEGORY and APPL_ATTRIBUTE1 through APPL_ATTRIBUTE20 — descriptive flexfield context and segment values for client extensions.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the HR APIs.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and COMMENTS.

Common Use Cases and Queries

Recruitment reporting typically joins PER_APPLICATIONS to person and organization data to produce applicant pipelines and hire-conversion metrics. A common pattern filters by business group and counts successful outcomes:

• Applicant tracking: list applications received within a date range for a business group.
• Source-to-hire analysis: use SUCCESSFUL_FLAG together with PROJECTED_HIRE_DATE to measure conversion.
• Integration auditing: use REQUEST_ID and PROGRAM_ID to trace rows written by concurrent processes.
• Flexfield reporting: group by APPL_ATTRIBUTE_CATEGORY and APPL_ATTRIBUTE1, etc., for client-defined dimensions.

A representative query joins the business group and traces applications that became assignments:

SELECT a.application_id, a.person_id, a.date_received, a.successful_flag
FROM per_applications a, per_all_assignments_f f
WHERE a.application_id = f.application_id
AND a.business_group_id = :p_business_group_id;

Related Objects

• HR_ALL_ORGANIZATION_UNITS — parent of PER_APPLICATIONS via BUSINESS_GROUP_ID; provides the business group context.
• PER_ALL_ASSIGNMENTS_F — references PER_APPLICATIONS through APPLICATION_ID; links a successful application to the resulting assignment.
• PER_ALL_PEOPLE_F — conceptually related through PERSON_ID for applicant identity.
• PER_APPLICATIONS_PK — the primary key constraint/index enforcing uniqueness on APPLICATION_ID.
• HR Applicant/Recruitment APIs and concurrent programs — populate REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID audit columns.