Results for “proposal_name”

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

Overview

The PER_PROPOSAL_TEMPLATES table is a core configuration object within the Oracle EBS Human Resources (PER) module, residing in the HR schema. It stores the definitions of proposal templates that drive assignment proposals in Oracle Human Resources. An assignment proposal is a structured business process used to capture and route changes to an employee's assignment record — such as a reclassification, a promotion, a transfer, or a compensation adjustment — through a defined approval and data-capture workflow. Each row in this table represents a reusable template that governs the set of questions, categories, and answer structures presented to users when an assignment proposal is initiated.

Because the table holds the durable, independent identity of each proposal template, the ETRM heuristic Data Vault classification places it as hub-leaning. In dimensional or Data Vault modeling terms, this suggests treating PROPOSAL_TEMPLATE_ID as a hub key, with descriptive attributes such as name, description, and type carried as satellite or reference data.

Key Information Stored

The table is documented with nine physical columns in the 12.2.2 schema. The most important are:

• PROPOSAL_TEMPLATE_ID — the surrogate primary key, enforced by PER_PROPOSAL_TEMPLATES_PK. This is the value propagated to child tables to link proposals, answers, and category members back to their parent template.
• PROPOSAL_NAME — the business-key candidate, enforced by the unique index PER_PROPOSAL_TEMPLATES_UK1. It provides the human-readable identifier that users select when launching a proposal.
• DESCRIPTION — free-text narration explaining the purpose or scope of the template.
• TYPE — classifies the template, distinguishing the kind of proposal process it supports.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the last modification user, timestamp, and session login, supporting change tracking and concurrency auditing.

The distinction between the surrogate key (PROPOSAL_TEMPLATE_ID) and the unique business name (PROPOSAL_NAME) is critical: integrations should reference the surrogate key for joins, while end users and reports typically surface PROPOSAL_NAME.

Common Use Cases and Queries

Typical scenarios include listing available templates for setup review, auditing template usage across proposals, and validating template linkage during data migration or reconciliation.

• Retrieve all active templates by name and description:
  • SELECT PROPOSAL_TEMPLATE_ID, PROPOSAL_NAME, DESCRIPTION, TYPE FROM HR.PER_PROPOSAL_TEMPLATES ORDER BY PROPOSAL_NAME;
• Count answers captured per template by joining to PER_ASSIGN_PROPOSAL_ANSWERS on PROPOSAL_TEMPLATE_ID.
• Identify templates that have category members configured via PER_PROPOSAL_CATEGORY_MEMBERS.
• Audit recently changed templates using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance reporting.

Reporting frequently joins this hub to its children to build a complete proposal configuration picture.

Related Objects

The primary relationships are defined by foreign keys referencing this table:

• PER_ASSIGN_PROPOSAL_ANSWERS — references PER_PROPOSAL_TEMPLATES.PROPOSAL_TEMPLATE_ID via PER_ASSIGN_PROPOSAL_ANSWERS.PROPOSAL_TEMPLATE_ID; stores the individual answers collected.
• PER_PROPOSAL_CATEGORY_MEMBERS — references PER_PROPOSAL_TEMPLATES.PROPOSAL_TEMPLATE_ID via PER_PROPOSAL_CATEGORY_MEMBERS.PROPOSAL_TEMPLATE_ID; maps templates to proposal categories.

In practice these children are queried alongside the parent through the shared PROPOSAL_TEMPLATE_ID column. Setup and maintenance are generally performed through the Oracle HRMS assignment proposal configuration forms rather than direct DML, which helps preserve the integrity of the template-to-answer and template-to-category relationships.