Results for “igw_prop_persons_tca_v”

24 results




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

Overview

The view IGW_PROP_PERSONS_TCA_V belongs to the IGW (Grants Proposal) product family within Oracle E-Business Suite, a module that is now classified as obsolete. According to the ETRM metadata, this object is documented as "10SC Only," meaning its definition and usage were confined to the Oracle Grants Proposal 10SC (ten-character) configuration and it is not implemented in the generic database against which the current ETRM documentation was generated. It therefore carries no live data dictionary entry in a standard 12.1.1 or 12.2.2 installation and should be regarded as a legacy artifact rather than an active reporting or integration interface.

Functionally, the view presents a denormalized, TCA-oriented projection of proposal personnel records. It surfaces the association between a proposal, the person acting within that proposal, and the party identifiers maintained through the Trading Community Architecture (TCA) model. Its role in reporting would have been to give Grants Proposal forms and concurrent programs a convenient join point to TCA party information without directly coupling those programs to the base transactional table.

Underlying Base Objects

The documented view text reveals a single base object: IGW_PROP_PERSONS. The view is a thin projection over that table, introducing one synthesized column through concatenation while passing through the remaining attributes unchanged. No additional base tables, synonyms, or TCA views are documented as referenced objects. In particular, despite the _TCA_V suffix and the presence of ORG_PARTY_ID, the metadata does not record a join to HZ_PARTIES or any other TCA entity; the party identifiers are sourced directly from the underlying proposal persons row. The ETRM notes that the owner and referenced base objects are not documented for the 12.2.2 release set, which is consistent with the view being absent from that database.

Key Columns

  • PROPOSAL_PERSON_PARTY_ID — A synthesized key formed by concatenating PROPOSAL_ID with PERSON_PARTY_ID. This composite value supports unique row identification in contexts where the natural pair of proposal and person party must be treated as a single identifier.
  • PROPOSAL_ID — Identifier of the parent grant proposal to which the person record belongs.
  • PERSON_ID — The internal person identifier from the HR/person model, used for foreign-key style lookups to person records.
  • PERSON_PARTY_ID — The TCA party identifier corresponding to the person, enabling linkage to TCA party-level attributes such as contacts, addresses, and relationships.
  • ORG_PARTY_ID — The TCA party identifier for the organization associated with the person's role on the proposal. This is the column referenced by the search term "org_party_id" and is the principal TCA linkage exposed by the view.

Common Use Cases and Queries

The view would have been used to report proposal personnel alongside their TCA party affiliations, most commonly when resolving the organization party for a person serving on a proposal. A representative query is:

  • SELECT proposal_id, person_id, person_party_id, org_party_id FROM igw_prop_persons_tca_v WHERE proposal_id = :p_proposal_id;
  • SELECT proposal_person_party_id, org_party_id FROM igw_prop_persons_tca_v WHERE org_party_id = :p_org_party_id;

Because the object is documented as not implemented and the IGW module is obsolete, these queries should be treated as historical reference only. Installations at 12.1.1 or 12.2.2 should not expect the view to exist and should query the base table IGW_PROP_PERSONS or the current TCA views instead.