Search Results per_assign_proposal_answer_pk




Overview
Explore in AI Chat

Overview

PER_ASSIGN_PROPOSAL_ANSWERS is a Human Resources (PER) table in the Oracle E-Business Suite HR schema that stores the answers a candidate or recruiter provides against an offer proposal generated for a specific assignment. In the Oracle iRecruitment / offer-management flow, a proposal template defines the set of questions presented to a candidate when an offer is extended; this table captures the actual response recorded for each question on each assignment. It therefore acts as the transactional record linking an assignment, a proposal template, the question definition, and the resulting answer value.

The ETRM metadata classifies this object, on a heuristic basis mined from its foreign-key structure, as a link table. This is a modeling suggestion rather than a certified Data Vault designation: the table sits between independent business entities (assignment, question template, question definition) and resolves a many-to-many style relationship between them, which is the classic role of a link construct. Secondary attributes such as ANSWER_VALUE and TYPE would conventionally be carried on an adjacent satellite in a formal Data Vault model.

Key Information Stored

  • PROPOSAL_ANSWER_ID — the surrogate primary key, enforced by the unique index PER_ASSIGN_PROPOSAL_ANSWER_PK. This is the sole documented business-key candidate.
  • ASSIGNMENT_ID — identifies the assignment (the candidate's placement context) to which the offer proposal and its answers belong.
  • PERSON_ID — the person (candidate or employee) associated with the proposal answer.
  • PROPOSAL_TEMPLATE_ID — the offer proposal template that framed the questions presented for that assignment.
  • PROPOSAL_QUESTION_NAME — the name of the question being answered, sourced from the question type definitions.
  • PROPOSAL_QUESTION_MEMBER_ID — the specific question member (individual question instance within a template) that the answer addresses.
  • ANSWER_VALUE — the recorded response supplied by the candidate or recruiter.
  • TYPE — categorises the answer or question type, distinguishing the nature of the response recorded.
  • ANSWER_FOR_KEY — a contextual key that qualifies or groups the answer.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who/when tracking for the row.

Common Use Cases and Queries

The most frequent requirement is reporting which answers a candidate gave against a specific offer or assignment. A representative query joins the answer rows to the proposal template and question definitions:

SELECT a.PROPOSAL_ANSWER_ID,
       a.ASSIGNMENT_ID,
       a.PERSON_ID,
       a.PROPOSAL_QUESTION_NAME,
       a.ANSWER_VALUE
FROM   HR.PER_ASSIGN_PROPOSAL_ANSWERS a
WHERE  a.ASSIGNMENT_ID = :assignment_id
AND    a.PROPOSAL_TEMPLATE_ID = :template_id;

Recruiters use these rows to reconstruct an offer as presented and accepted. HR reporting teams aggregate ANSWER_VALUE by PROPOSAL_QUESTION_NAME to analyse offer acceptance patterns across positions. Audit queries filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to track when offer responses changed. Integration extracts frequently pull answers by PERSON_ID to feed applicant-tracking systems.

Related Objects

These foreign-key relationships define the object's join topology and confirm its role as a connector between assignments, templates, and question definitions within the Oracle HR offer-management data model.