Results for “mailing_address”

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

Overview

The IGW_PROP_PROGRAM_ADDRESSES_V view belongs to the Oracle Grants Proposal (IGW) product family and is documented in the ETRM as a 10SC-only object. In the 10SC (ten-something character, later "10SC Only") legacy grants accounting model, this view exposes the mailing address information associated with a proposal program address record. Its principal purpose is to present a single, human-readable MAILING_ADDRESS value assembled from the component address columns of the underlying RA_ADDRESSES table, together with copies and mail description metadata held against the proposal's program address row.

Because the ETRM records "Not implemented in this database" for the documented environment, the view should be treated as a legacy/optional object in Oracle EBS 12.1.1 and 12.2.2. Where present, it serves primarily as a reporting and integration access point rather than a transactional entity — it is read-only and is used by grants proposal reports, correspondence generation, and external interfaces that require a formatted mailing address for a proposal.

Underlying Base Objects

The view text is defined over a join of two base tables:

• IGW_PROP_PROGRAM_ADDRESSES P — the proposal-side table holding the association between a PROPOSAL_ID and an ADDRESS_ID, along with NUMBER_OF_COPIES and MAIL_DESCRIPTION.
• RA_ADDRESSES A — the Receivables/common address table holding the address components (ADDRESS1 through ADDRESS4, CITY, STATE, POSTAL_CODE) used to build the formatted address string.

The join is expressed as A.ADDRESS_ID(+) = P.ADDRESS_ID, i.e. an outer join from IGW_PROP_PROGRAM_ADDRESSES to RA_ADDRESSES. This guarantees that a proposal program address row is returned even when the corresponding RA_ADDRESSES record is missing or unresolvable, in which case the MAILING_ADDRESS expression evaluates to NULL. The ETRM documents no additional referenced base objects.

Key Columns

• ROW_ID — the ROWID of the IGW_PROP_PROGRAM_ADDRESSES row; useful as a unique row identifier.
• PROPOSAL_ID — identifier of the grants proposal to which the address belongs.
• ADDRESS_ID — foreign key into RA_ADDRESSES identifying the source address record.
• MAILING_ADDRESS — the derived column. It concatenates ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CITY, STATE and POSTAL_CODE with comma separators and then applies nested REPLACE calls to collapse occurrences of ", , " down to ", " (twice), removing empty address lines.
• NUMBER_OF_COPIES — the number of copies of the proposal to be mailed to that address.
• MAIL_DESCRIPTION — free-text description of the mail destination/purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns supporting auditing and change tracking.

Common Use Cases and Queries

The view is typically queried when a report, letter, or interface needs a proposal's mailing address in a single formatted field — for example, generating proposal submission correspondence or exporting address data for external mail-merge processing.

• Retrieving all formatted addresses for a proposal:

SELECT proposal_id,
       address_id,
       mailing_address,
       number_of_copies,
       mail_description
  FROM igw_prop_program_addresses_v
 WHERE proposal_id = :p_proposal_id;

• Filtering to only rows with a resolvable address and a specific copy count:

SELECT proposal_id, mailing_address, number_of_copies
  FROM igw_prop_program_addresses_v
 WHERE mailing_address IS NOT NULL
   AND number_of_copies > 1
 ORDER BY proposal_id;

• Auditing recently maintained rows using the WHO columns:

SELECT proposal_id, mailing_address, last_update_date, last_updated_by
  FROM igw_prop_program_addresses_v
 WHERE last_update_date >= TRUNC(SYSDATE) - 30;

Note that because the WHERE clause of the view filters nothing, callers must apply their own proposal, date, or address predicates, and should guard against NULL MAILING_ADDRESS values arising from the outer join. Availability of the view depends on the EBS patch level and the grants configuration in use.