Results for “edi_generated_date”

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

Overview

IGW_PROPOSALS is a reporting view within the Oracle E-Business Suite Grants Proposal module (product code IGW). The ETRM metadata classifies this product as "Grants Proposal (Obsolete)" and annotates the view description simply as "10SC Only." The "10SC" designation refers to Oracle Grant Proposal 10SC, the legacy grants management application that predated the consolidation of grants functionality into Oracle Grants Accounting and the broader E-Business Suite grants family. The product is effectively retired in EBS 12.1.1 and 12.2.2 environments, and the metadata explicitly states "Not implemented in this database," confirming the view is not created by default in current releases.

Functionally, the object presents grant proposal header and tracking information — proposal identity, sponsor data, funding solicitation references, deadline handling, sponsor actions, and award linkage — as a security-filtered, organization-scoped query layer over a hidden base table (IGW_PROPOSALS_ALL). Its role in reporting and integration was to provide a stable read interface for proposal data without exposing the underlying table directly.

Underlying Base Objects

The view text reveals that IGW_PROPOSALS is defined as a simple projection over IGW_PROPOSALS_ALL, selecting an explicit column list and applying a multi-org security predicate on ORG_ID. No other base tables, joins, or aggregations are present, so the view is a direct, row-for-row filtered subset of the base table. The ETRM metadata documents no referenced base objects, which is consistent with the internal naming convention in which the _ALL table is the concrete storage object and the corresponding view is the reporting and security wrapper.

The ORG_ID predicate is the classic Multi-Org Access Control (MOAC) pattern used throughout EBS R12. It reads the current operating unit from the CLIENT_INFO context via USERENV, then compares it to the row's ORG_ID. Rows with a NULL ORG_ID (global or shared rows) are included by the NVL logic, and rows outside the user's operating unit context are excluded.

Key Columns

• PROPOSAL_ID — Primary identifier of the proposal record; the unique key used in joins.
• PROPOSAL_NUMBER — User-facing proposal number, used for external and internal reference.
• LEAD_ORGANIZATION_ID, SUBMITTING_ORGANIZATION_ID, ORG_ID — Organizational context: the lead organization, the submitting organization, and the MOAC operating unit responsible for the record.
• PROPOSAL_STATUS, PROPOSAL_TYPE_CODE, ACTIVITY_TYPE_CODE — Lifecycle classification of the proposal.
• PROPOSAL_START_DATE, PROPOSAL_END_DATE — The planned performance period.
• PROPOSAL_TITLE — Descriptive title of the proposal.
• ORIGINAL_PROPOSAL_NUMBER, ORIGINAL_AWARD_NUMBER, ORIGINAL_PROPOSAL_START_DATE, ORIGINAL_PROPOSAL_END_DATE — Predecessor/continuation references linking to a prior proposal or award.
• SPONSOR_ID, FUNDING_SPONSOR_UNIT, SPONSOR_PROPOSAL_NUMBER — Funding sponsor identity and the sponsor's own reference number.
• NOTICE_OF_OPPORTUNITY_CODE, PROGRAM_NUMBER, PROGRAM_TITLE, PROGRAM_URL — Funding opportunity and program details.
• DEADLINE_DATE, DEADLINE_TYPE — Submission deadline tracking.
• EDI_GENERATED_DATE, SPONSOR_ACTION_CODE, SPONSOR_ACTION_DATE — Integration and sponsor response tracking.
• AWARD_NUMBER, Award_AMOUNT — Resulting award linkage and amount.
• NARRATIVE_TYPE_CODE, NARRATIVE_SUBMISSION_CODE — Narrative/attachment submission metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive Flexfield (DFF) segments.

Common Use Cases and Queries

Because the object is obsolete and documented as not implemented in EBS 12.1.1 or 12.2.2, any query should first verify existence. On legacy 10SC environments, the primary use cases were proposal reports, deadline monitoring, and sponsor pipeline analysis. Typical queries include:

SELECT proposal_number, proposal_title, proposal_status,
       proposal_start_date, deadline_date, award_number
FROM   igw_proposals
WHERE  proposal_status = 'SUBMITTED'
ORDER BY deadline_date;

Sponsor pipeline and opportunity tracking:

SELECT sponsor_id, notice_of_opportunity_code, program_number,
       COUNT(*) AS proposal_count, SUM(award_amount) AS total_awarded
FROM   igw_proposals
GROUP BY sponsor_id, notice_of_opportunity_code, program_number;

Award linkage and continuation analysis:

SELECT p.proposal_number, p.original_proposal_number,
       p.award_number, p.award_amount, p.sponsor_action_code,
       p.sponsor_action_date
FROM   igw_proposals p
WHERE  p.award_number IS NOT NULL;

On current 12.1.1 and 12.2.2 instances, dependent reports and custom integrations referencing IGW_PROPOSALS will fail with an invalid-object error. Replacement functionality should be sourced from supported grants objects and their corresponding views, and any historical migration from 10SC should target those supported structures rather than this obsolete view. In the context of an external search such as "gotland HV project," the object may still appear in aged documentation, but it has no active role in modern EBS deployments.