Search Results option_sql_text

Overview

The PER_PROPOSAL_QUESTION_TYPES_V view is a dictionary-defined reporting and integration object owned by the APPS schema within the Oracle E-Business Suite. It resides in the PER (Human Resources) product family and is documented in ETRM as the "HR Web Offer question types view." The object carries a status of VALID and is classified as a VIEW, meaning it exposes no independent storage of its own; instead, it projects the columns of a single underlying base object in a fixed, published shape.

The view serves a supporting role rather than a transactional one. It describes the metadata that drives the presentation of proposal questions presented to candidates and employees through HR self-service and web offer flows. In EBS 12.1.1 and 12.2.2 the view is commonly reached through custom reports, data extraction routines, and interface programs that must reproduce or audit the configuration of offer and proposal questionnaires. Because it is an APPS-owned view, access should be granted through the standard APPS synonym layer rather than to underlying objects directly.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: the synonym PER_PROPOSAL_QUESTION_TYPES. The view text confirms a direct, non-join projection over that object, with no WHERE clause, GROUP BY, or join predicates present in the definition. Consequently, PER_PROPOSAL_QUESTION_TYPES_V returns one row for every row stored in the base object, and no data transformation, filtering, or aggregation is applied.

The definition is a straight column list: PROPOSAL_QUESTION_NAME, FULL_TEXT, ALIGN, QUESTION_HEADER, HELP_TEXT, NOTE_TEXT, HTML_TYPE, WIDTH_SIZE, HEIGHT_SIZE, MAXLENGTH, DEFAULT_VALUE_TYPE, DEFAULT_VALUE, LOOKUP_TYPE, OPTION_SQL_TEXT, PROVIDE_FIND, TYPE, FIND_FILTER_COLUMN, and FIND_SELECT_SQL. The columns map one-to-one in name and order to those of the underlying base object, which is characteristic of an EBS "V" view used to decouple consumer code from direct table references. From a patching and upgrade standpoint, the view is the supported interface: Oracle can alter the base object's internal structure while preserving the column contract exposed by the view.

Key Columns

• PROPOSAL_QUESTION_NAME — Identifier for the configured proposal question; the primary means of referencing a question definition.
• FULL_TEXT and QUESTION_HEADER — The question prompt and the header displayed above it in the web offer page.
• HELP_TEXT and NOTE_TEXT — Supplementary guidance and note content rendered alongside the question.
• HTML_TYPE — The rendering control (for example text field, text area, or list) used to present the question, which governs how the remaining display attributes are interpreted.
• WIDTH_SIZE, HEIGHT_SIZE, and MAXLENGTH — Sizing attributes applied to the rendered control and the maximum permissible input length.
• ALIGN — Alignment setting for the question presentation.
• DEFAULT_VALUE_TYPE and DEFAULT_VALUE — Define how a default response is derived and the default itself.
• LOOKUP_TYPE — References the lookup used to populate a list of valid responses.
• OPTION_SQL_TEXT — SQL text used to generate dynamic list options when applicable.
• PROVIDE_FIND, FIND_FILTER_COLUMN, and FIND_SELECT_SQL — Control the availability of a find/Lov mechanism and the SQL used to filter and retrieve selectable values.
• TYPE — Classifies the question type as understood by the HR web offer framework.

Common Use Cases and Queries

The principal practical uses are configuration auditing, migration of question setups between environments, and troubleshooting of offer or proposal page rendering. A simple extraction of all configured questions is the most frequent starting point:

SELECT proposal_question_name,
       question_header,
       html_type,
       type,
       lookup_type
FROM   apps.per_proposal_question_types_v
ORDER  BY proposal_question_name;

To review the display configuration for questions that use a list of values:

SELECT proposal_question_name,
       html_type,
       width_size,
       height_size,
       maxlength,
       lookup_type,
       provide_find
FROM   apps.per_proposal_question_types_v
WHERE  lookup_type IS NOT NULL;

To inspect dynamically sourced options and their find mechanisms:

SELECT proposal_question_name,
       option_sql_text,
       find_filter_column,
       find_select_sql
FROM   apps.per_proposal_question_types_v
WHERE  option_sql_text IS NOT NULL
   OR  find_select_sql IS NOT NULL;

Because the view performs no filtering, any restriction on question type, HTML control, or default behavior must be applied by the calling query. When comparing environments, select the full column list and diff the results by PROPOSAL_QUESTION_NAME; this reliably surfaces missing or divergent question definitions between a source and target instance.