Results for “proposal_id”

50+ results




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

Overview

The IGW_PRINTABLE_PROPOSALS_V view is a security-filtered reporting object within the Oracle E-Business Suite Grants Proposal (IGW) module. It exposes the subset of grant proposals that the currently logged-in application user is authorized to print. Unlike a conventional view that simply joins or reshapes base table data, this view applies Oracle EBS row-level security at query time by invoking the IGW_SECURITY.ALLOW_CREATE function. As a result, the set of rows returned depends dynamically on the runtime user context supplied by FND_GLOBAL.USER_ID.

The view is owned by the APPS schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2. Its principal role is to support printable proposal reporting, particularly where a proposal number must be displayed or selected for printing, while simultaneously enforcing the Grants Proposal security model so that users cannot see or print proposals belonging to other users or organizations without the requisite privileges. Because it returns only two columns, it functions as a lightweight lookup or validation source rather than a comprehensive reporting view.

Underlying Base Objects

The view is defined directly over a single base table, IGW_PROPOSALS. The documented view text is:

IGW_PROPOSALS is the primary transactional table storing grant proposal headers in the IGW module. The view does not perform any joins to other tables; its filtering logic is entirely delegated to the IGW_SECURITY package function. The ALLOW_CREATE call is passed the function or action name 'PRINT_PROPOSAL', the specific PROPOSAL_ID being evaluated, and the current session user ID. The function returns 'Y' only when the user is permitted to print that proposal. Consequently, the view inherits the full security rules configured for the PRINT_PROPOSAL action, including any grants, roles, or organizational assignments maintained in the IGW security setup. No additional referenced base objects are documented for this view.

Key Columns

The view exposes exactly two columns:

  • PROPOSAL_ID — The unique surrogate primary key of the proposal in IGW_PROPOSALS. It is the identifier used throughout the IGW module to relate proposals to their associated lines, budgets, personnel, and attachments, and it is the value passed into the security function for evaluation.
  • PROPOSAL_NUMBER — The user-facing business identifier of the proposal. This is the value users typically recognize and reference in correspondence, reports, and search criteria, and it is the column most relevant to users who search on "proposal_number."

Because the view returns only these two columns, it is best suited for lookup and validation purposes. Any reporting that requires proposal descriptions, statuses, dates, or amounts must join the returned PROPOSAL_ID back to IGW_PROPOSALS or to other IGW tables.

Common Use Cases and Queries

The most common use is populating a list of values or a selection screen that allows a user to choose a printable proposal, restricted automatically to proposals the user is authorized to print:

  • SELECT PROPOSAL_ID, PROPOSAL_NUMBER FROM APPS.IGW_PRINTABLE_PROPOSALS_V ORDER BY PROPOSAL_NUMBER;
  • SELECT PROPOSAL_ID FROM APPS.IGW_PRINTABLE_PROPOSALS_V WHERE PROPOSAL_NUMBER = :p_proposal_number;

A second use case is validating a proposal number entered by a user before launching a print or report request, ensuring both existence and print authorization. The view may also be joined to IGW_PROPOSALS for richer reporting:

Because results depend on FND_GLOBAL.USER_ID, answers in any data-extraction or integration process vary by the invoking user context. For concurrent programs or interfaces requiring a fixed, unrestricted result set, the view is not appropriate; the base table IGW_PROPOSALS should be used with explicit security logic instead.