Results for “per_proposal_templates_v”

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

Overview

PER_PROPOSAL_TEMPLATES_V is a database view owned by the APPS schema in Oracle E-Business Suite. It is registered as a VALID object and is classified under the PER (Human Resources) product family. The view is described in the ETRM metadata as the "HR Web Offer proposal template view," which identifies its functional role within the Oracle iRecruitment and HR Web Offer / Applicant Offer process. The underlying table PER_PROPOSAL_TEMPLATES stores the reusable proposal templates that drive the HR Web Offer feature; the view exposes a controlled, denormalized projection of that data for consumption by the offer-generation pages and by downstream reporting.

In practical terms, PER_PROPOSAL_TEMPLATES_V gives callers a read-oriented surface onto proposal template master data. Rather than requiring each consumer to touch the base table directly, the view presents the four attributes most commonly required by offer creation logic: the template identifier, the template name, the template type, and a free-text description. This makes the view useful both to EBS internal code paths and to customer-authored reports, interfaces, and extracts that need to reference the available Web Offer proposal templates.

Underlying Base Objects

The view is defined over a single base object, identified in the documented metadata as the synonym PER_PROPOSAL_TEMPLATES. The view text is a straightforward projection:

• SELECT PROPOSAL_TEMPLATE_ID, PROPOSAL_NAME, TYPE, DESCRIPTION FROM PER_PROPOSAL_TEMPLATES

No joins, aggregations, DISTINCT clauses, or filter predicates (such as a WHERE on a status or enabled flag) are present in the view text. The definition is therefore a one-to-one column-level mapping between the view and its base object, filtered only in the sense that it restricts the visible column list to four attributes. Because the base object is a synonym resolving to the APPS-owned proposal template table in the PER schema, the view inherits its partitioning, indexing, and constraint behavior from that table. Referential relationships, such as any link between a proposal template and the offers generated from it, remain defined at the base table level and are not surfaced through this view.

Key Columns

• PROPOSAL_TEMPLATE_ID — The primary key of the proposal template. This is the value used as a foreign key from offer and applicant records that reference the template. It is the natural join key for any query that must associate a specific Web Offer with the template that produced it.
• PROPOSAL_NAME — The user-facing name of the template. This is the column most commonly searched and displayed; the search term "proposal_name" corresponds directly to it. It is the appropriate column to filter on when an end user identifies a template by its label rather than by its identifier.
• TYPE — The template type classification. This distinguishes proposal templates by their category or usage within the Web Offer framework, allowing consumers to restrict a list to the relevant variety of template.
• DESCRIPTION — A free-text description of the template, typically used to explain the template's purpose or content to the recruiter or HR administrator selecting it.

Common Use Cases and Queries

Typical uses include presenting a list of available proposal templates in a custom offer form, validating that a template referenced in an interface exists before loading offers, and extracting template master data for data-warehouse or audit reporting. Because the view carries no status filter, any active/inactive or end-dated logic must be applied by the caller against the base table, not assumed from the view.

Retrieve all templates:

• SELECT proposal_template_id, proposal_name, type, description FROM apps.per_proposal_templates_v ORDER BY proposal_name;

Search by the template name — the pattern that matches the "proposal_name" search:

• SELECT proposal_template_id, proposal_name, description FROM apps.per_proposal_templates_v WHERE proposal_name LIKE :p_name || '%';

Look up a single template by identifier or filter by type:

• SELECT proposal_name, description FROM apps.per_proposal_templates_v WHERE proposal_template_id = :p_template_id;
• SELECT proposal_template_id, proposal_name FROM apps.per_proposal_templates_v WHERE type = :p_type ORDER BY proposal_name;

These queries should be issued with the APPS schema context (or via the appropriate MO or custom application grants) consistent with standard EBS read-only reporting practice.