Search Results proposal_title




Overview
Explore in AI Chat

Overview

IGW_PROPOSALS is a reporting and integration view in the Oracle E-Business Suite Grants and Proposal Management (Oracle Grants / IGW) application. It exposes proposal header information maintained by the Oracle Grants module, presenting a denormalized, security-filtered projection of the underlying proposal entity. The view is owned by the APPS schema and is intended to be queried by forms, concurrent programs, reports, and external integrations rather than accessed by direct table reads. Its principal role is to enforce organization-level security through the CLIENT_INFO mechanism while simultaneously surfacing the full set of business attributes required to describe a proposal, including its lead organization, sponsor, funding details, and award linkage.

The presence of LEAD_ORGANIZATION_ID among the first projected columns reflects the central importance of organizational attribution in the grants domain. Proposals are owned and led by a specific operating unit or organization, and this column is the anchor for determining which users and responsibilities may see a given proposal record.

Underlying Base Objects

The view is defined by a SELECT over IGW_PROPOSALS_ALL, the base table that stores proposal header records. The view text applies a row-level security predicate that restricts returned rows to those matching the value supplied in the CLIENT_INFO environment variable, resolved through USERENV('CLIENT_INFO'). The predicate compares the record's ORG_ID — with a fallback expression — to the decoded client information, effectively implementing Multi-Org / operating unit access control at the view layer. Records whose ORG_ID cannot be resolved default to a sentinel value of -99, which is excluded from standard access. Because IGW_PROPOSALS_ALL follows the standard "_ALL" convention in EBS, the view supplies the security-filtered counterpart that applications should consume in place of direct table access.

Key Columns

Common Use Cases and Queries

Typical use cases include proposal registers, lead-organization reporting, and integration extracts. The following query lists active proposals with their lead organization context:

SELECT proposal_id, proposal_number, lead_organization_id,
       org_id, proposal_status, proposal_title
FROM   apps.igw_proposals
WHERE  lead_organization_id = :p_lead_org_id;

To join proposal headers to awards for funding analysis:

SELECT p.proposal_number, p.award_number, p.award_amount,
       p.sponsor_id
FROM   apps.igw_proposals p
WHERE  p.proposal_status = 'AWARDED';

Because the view enforces CLIENT_INFO security, callers must set the client info in the session (typically performed automatically by EBS forms and concurrent programs) to obtain correct operating-unit-scoped results.