Results for “igw_prop_program_addresses”

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

Overview

The IGW_PROP_PROGRAM_ADDRESSES table is a component of the IGW – Grants Proposal module in Oracle E-Business Suite. As documented in the ETRM metadata, the product is flagged as obsolete; the table is recorded as "Not implemented in this database" under the 12.1.1 implementation data. Its stated purpose is to hold mailing information associated with a proposal, allowing a single proposal to be linked to one or more program-related addresses and their associated contact and telephone details. Within the physical schema, the object is owned by the IGW schema and contains 17 documented columns.

From a Data Vault modeling perspective, the mined classification is satellite-leaning. This suggests the object functions best as a descriptive satellite attached to a parent business key, rather than as an independent hub or a pure associative link. The presence of multiple descriptive attributes (mail description, copies, contact data) alongside a composite business key supports this interpretation as a modeling suggestion rather than a definitive designation.

Key Information Stored

The physical design separates a surrogate identifier from the business-key candidate. The primary key constraint IGW_PROP_PGM_ADDRESSES_PK is defined over the composite of PROPOSAL_ID and ADDRESS_ID, and a unique index IGW_PROP_PGM_ADDRESSES_U1 carries the same column pair, confirming these two columns as the business-key candidates. The column PROP_PGM_ADDRESS_ID appears among the documented columns and serves as an additional single-column identifier within the row structure.

• PROPOSAL_ID – identifies the owning proposal; participates in both the primary key and the foreign key to IGW_PROPOSALS_ALL.
• ADDRESS_ID – the address reference within the composite key, linking the row to a specific mailing destination.
• PROP_PGM_ADDRESS_ID – single-column identifier for the program address record.
• NUMBER_OF_COPIES – quantity of copies to be dispatched to the address.
• MAIL_DESCRIPTION – free-text description of the mailing entry.
• CONTACT_ID, CONTACT_NAME – contact identification and name for the destination.
• PHONE_ID, PHONE_NUMBER – telephone reference and value associated with the contact.
• ADDRESS – the address text stored on the row.
• PROP_GRANTOR_ID – grantor association for the mailing record.
• RECORD_VERSION_NUMBER – optimistic locking version indicator.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit columns.

Common Use Cases and Queries

Reporting against this table centers on extracting the mailing list for a proposal, including contact and telephone detail. A representative query joins the table to its parent proposal header:

• SELECT a.PROPOSAL_ID, a.ADDRESS_ID, a.MAIL_DESCRIPTION, a.NUMBER_OF_COPIES FROM IGW_PROP_PROGRAM_ADDRESSES a WHERE a.PROPOSAL_ID = :proposal_id;
• SELECT a.PROPOSAL_ID, a.CONTACT_NAME, a.PHONE_NUMBER FROM IGW_PROP_PROGRAM_ADDRESSES a JOIN IGW_PROPOSALS_ALL p ON p.PROPOSAL_ID = a.PROPOSAL_ID;
• Aggregate copy counts per proposal: SELECT PROPOSAL_ID, SUM(NUMBER_OF_COPIES) FROM IGW_PROP_PROGRAM_ADDRESSES GROUP BY PROPOSAL_ID;

Because the module is marked obsolete, any requirement touching this object should first be validated against the current implementation, as the table is not present in the sampled database.

Related Objects

The documented foreign key defines the principal dependency: IGW_PROP_PROGRAM_ADDRESSES.PROPOSAL_ID references IGW_PROPOSALS_ALL. This parent table supplies the business context for every satellite row and is the natural join partner for reporting and data extraction. The composite primary key columns PROPOSAL_ID and ADDRESS_ID further imply relationships to address and contact reference data within the IGW schema, though these are not enumerated in the supplied foreign key metadata. No additional views, APIs, or dependent tables are documented for this object in the ETRM excerpt.