Search Results hr_assignments

Overview

PER_ASSIGN_PROPOSAL_ANSWERS is a transactional table in the Oracle EBS HR schema that stores the answers a hiring manager entered on the Web Offers form in response to Candidate Offer questions associated with a specific candidate assignment. The table is registered under FND Design Data as PER.PER_ASSIGN_PROPOSAL_ANSWERS and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It is central to the recruiting and offer-management flow, capturing question-and-answer detail at the assignment level so that offer or appraisal questionnaire responses can be retrieved, audited, and reported against the candidate, the assignment, and the proposal template that generated the questions.

Based on the foreign-key structure mined from the documented relationships, the heuristic Data Vault classification for this object is link. This is a modeling suggestion rather than a physical constraint: the table resolves relationships between an assignment, a person, a proposal template, and the specific question members and question types that form the questionnaire, rather than acting as a standalone hub of business entities. The primary key, PER_ASSIGN_PROPOSAL_ANSWER_PK, is defined on PROPOSAL_ANSWER_ID, which is a system-generated surrogate key rather than a natural business key.

Key Information Stored

The table contains 14 documented columns. The most consequential are summarized below.

• PROPOSAL_ANSWER_ID (NUMBER, 15) — System-generated primary key. This is the surrogate identifier and the only column enforced by the unique index PER_ASSIGN_PROPOSAL_ANSWER_PK; it is not itself a business-key candidate.
• ASSIGNMENT_ID (NUMBER, 10) — Foreign key to HR_ASSIGNMENTS, tying each answer to the candidate's assignment. Indexed non-uniquely via PER_ASSIGN_PROPOSAL_ANSWERS_N1.
• PERSON_ID (NUMBER, 10) — Denormalized foreign key to PER_ALL_PEOPLE_F identifying the candidate/person. Indexed non-uniquely via PER_ASSIGN_PROPOSAL_ANSWERS_N2.
• PROPOSAL_QUESTION_MEMBER_ID (NUMBER) — Foreign key to PER_PROPOSAL_QUESTION_MEMBERS, identifying the specific question instance. Indexed non-uniquely via PER_ASSIGN_PROPOSAL_ANSWERS_N3.
• PROPOSAL_QUESTION_NAME (VARCHAR2, 60) — Foreign key to PER_PROPOSAL_QUESTION_TYPES, identifying the question category/type.
• PROPOSAL_TEMPLATE_ID (NUMBER) — Denormalized foreign key to PER_PROPOSAL_TEMPLATES, indicating the template that generated the questionnaire.
• ANSWER_VALUE (VARCHAR2, 2000) — The actual answer text the hiring manager typed into the Web Offers page.
• TYPE (VARCHAR2, 30) — Distinguishes whether the answer belongs to a Candidate Offer or an Appraisal Questionnaire.
• ANSWER_FOR_KEY (VARCHAR2, 30) — A generic foreign-key holder; currently stores the PER_APPRAISALS identifier when TYPE is 'Appraisal'.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard WHO audit columns recording creation and modification metadata.

Common Use Cases and Queries

Typical usage centers on retrieving offer questionnaire responses for a candidate or assignment, auditing who answered what and when, and reporting answer distribution by proposal template or question type. A common query pattern joins back to the assignment and person to reconstruct the full offer context.

• Retrieve all answers for a given assignment:

SELECT proposal_answer_id, proposal_question_name,
       answer_value, type, creation_date
FROM   per_assign_proposal_answers
WHERE  assignment_id = :assignment_id;

• Filter to appraisal responses only by testing TYPE and joining ANSWER_FOR_KEY to PER_APPRAISALS.
• Report candidate offers by person, aggregating answer counts per PROPOSAL_TEMPLATE_ID.
• Audit changes using LAST_UPDATED_BY and LAST_UPDATE_DATE across a date range.

Because ASSIGNMENT_ID, PERSON_ID, and PROPOSAL_QUESTION_MEMBER_ID each carry their own non-unique index, these columns are the efficient predicates for most operational queries.

Related Objects

The most significant related objects are those referenced by the documented foreign keys and the parent entities around the assignment and person.

• HR_ASSIGNMENTS — joined on PER_ASSIGN_PROPOSAL_ANSWERS.ASSIGNMENT_ID; the core assignment entity.
• PER_ALL_PEOPLE_F — joined on PERSON_ID; supplies candidate/person attributes.
• PER_PROPOSAL_QUESTION_TYPES — joined on PROPOSAL_QUESTION_NAME.
• PER_PROPOSAL_QUESTION_MEMBERS — joined on PROPOSAL_QUESTION_MEMBER_ID.
• PER_PROPOSAL_TEMPLATES — joined on PROPOSAL_TEMPLATE_ID.
• PER_APPRAISALS — referenced indirectly through ANSWER_FOR_KEY when TYPE is 'Appraisal'.
• Web Offers / iRecruitment offer pages and related offer APIs, which populate this table during candidate offer and appraisal questionnaire processing.