Results for “program_id_number”

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

Overview

IGW_PRPO_HEADERS_V is an Oracle E-Business Suite view owned by the APPS schema that exposes proposal header information in a flattened, interface-ready format. It is part of the Grants/IGW (formerly Oracle Grants Management, now Oracle Project Portfolio Management – Grants) module and is closely associated with the EDI/e-Government translation layer that passes proposal data to external procurement or grants systems. The view consolidates data from proposal records, third-party (translator) definitions, address/organization records and lookup values into a single denormalized row per proposal, which makes it suitable for outbound integration or reporting where a wide, pre-joined result set is preferable to joining many base tables manually.

The view is most relevant when tracing how a proposal's program_number is surfaced as program_id_number — the exact term the user searched for. That column is a direct alias of PROP.program_number, so any report or interface keyed on "program_id_number" is actually reading the proposal program number.

Underlying Base Objects

The documented metadata states that no base objects are explicitly listed, but the view text shows the object is defined over several tables and a package. These include:

• ETPD / ETPH — EDI translation and header tables supplying test flag, document type, translator code, TP description and TP reference attributes.
• ACCT_SITE — the ECE trading partner location code source.
• PROP — the core proposal record (proposal_id, proposal_number, program_number, program_title, award_number, etc.).
• RUN — a run/status table providing status_date formatted into YYYYMMDD and HHMISS segments.
• LKUP — a lookup providing meaning for notice of opportunity codes.
• SO / AO — submitting and administering person records (names, addresses, contacts).
• APORG — organization address and registration data (DUNS, CAGE, TIN, EIN, IPF code, congressional district).
• IGW_EXTENSION_PKG — supplies the person government ID via igw_extension_pkg.person_govt_id.

The view therefore acts as a join hub, hiding the complexity of relating proposals to translator configuration, people, and organizations.

Key Columns

• PROGRAM_ID_NUMBER — aliased from PROP.program_number; the identifier most users search for.
• PROPOSAL_ID / PROPOSAL_NUMBER / PROPOSAL_TITLE — proposal identity fields.
• PROGRAM_TITLE — descriptive program name.
• AWARD_NUMBER, ORIGINAL_PROPOSAL_NUMBER, NOTICE_OF_OPPORTUNITY_CODE — grant/award linkage.
• TRANSACTION_DATE — set to SYSDATE at query time, used for EDI stamping.
• ATTRIBUTE1..15 (from ETPH and ETPD) — descriptive flexfield (DFF) values for translator and document.
• SO_/AO_ name, address, phone, fax, email columns — submitting/administrating contact detail.
• APORG organization, DUNS/DUNS4, CAGE, TIN, EIN, IPF code — organizational registration data.
• PERSON_GOVT_ID — government identifier derived from the extension package.
• DOCUMENT_TYPE, TRANSLATOR_CODE, TEST_FLAG — EDI routing controls.

Common Use Cases and Queries

Typical uses include EDI outbound extraction of proposal headers, grants reporting, and troubleshooting the mapping of program number to external identifiers. A representative query is:

• SELECT proposal_number, program_id_number, program_title, award_number FROM apps.igw_prpo_headers_v WHERE program_id_number = :p_prog;
• SELECT proposal_number, ap_org_organization_name, ap_org_duns_number FROM apps.igw_prpo_headers_v;
• Filtering by test_flag or translator_code to isolate production EDI traffic.

Because transaction_date uses SYSDATE, the view should be queried live rather than materialized. Users should confirm column names against the live data dictionary in their 12.1.1 or 12.2.2 instance, as some aliases (e.g., APORG naming) may render differently in the published view definition.