Results for “org_party_id”
50+ 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 concatenatingPROPOSAL_IDwithPERSON_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.
-
View: IGW_PROP_PERSONS_TCA_V 12.1.1
10SC Only
APPS.IGW_PROP_PERSONS_TCA_V·↳ IGW_PROP_PERSONS·Explore IGW module →
-
Personnel included in the proposal
-
APPS.PA_PARTY_RESOURCE_DETAILS_V·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore PA module →
-
Stores the registered viewers who have portfolio assignments.
-
Table: AMS_DM_ORG_CONTACTS 12.1.1
Container for the mapping of org contacts vs org for a party, contains details for rows in AMS_DM_TARGET_STG. This table is used by Score and Model selection API.
-
Table: AMS_DM_ORG_CONTACTS 12.2.2
Container for the mapping of org contacts vs org for a party, contains details for rows in AMS_DM_TARGET_STG. This table is used by Score and Model selection API.
-
APPS.AST_BUSINESS_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore AST module →
-
Table to store the Portfolio Activities
-
View: IGS_FI_FEE_AS_RT_H 12.1.1
APPS.IGS_FI_FEE_AS_RT_H·↳ IGS_FI_FEE_AS_RT_H_ALL·Explore IGS module →
-
No longer used
APPS.IGS_FI_FEE_AS_RATE_F_TYPE_V·↳ HZ_PARTIES·↳ IGS_FI_FEE_AS_RATE·↳ IGS_FI_F_CAT_FEE_LBL·Explore IGS module →
-
APPS.PA_PARTY_RESOURCE_DETAILS_V·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore PA module →
-
This table stores new CE bank account uses information for bank upgrade purpose
-
View: CE_BANK_ACCT_USES 12.1.1
APPS.CE_BANK_ACCT_USES·↳ CE_BANK_ACCT_USES_ALL·↳ CE_BANK_ACCT_USES_OU·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
View: CE_BANK_ACCT_USES_GT_V 12.2.2
APPS.CE_BANK_ACCT_USES_GT_V·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_GT·Explore CE module →
-
View: CE_UPGA_BA_USES 12.2.2
This view is a single org view of the CE_UPGA_BA_USES_ALL table
APPS.CE_UPGA_BA_USES·↳ CE_UPGA_BA_USES_ALL·Explore CE module →
-
View: CE_BANK_ACCT_USES_LE_V 12.1.1
This view stores bank account uses information for legal entities.
APPS.CE_BANK_ACCT_USES_LE_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
Defines the individual approvers for an approval (JTF_UM_APPROVAL_B). The approvers can be defined globally, as well as overridden for a given organization (HZ_PARTIES). Approvers don't necessarily have to be specified as fnd_user, we will
-
Defines the individual approvers for an approval (JTF_UM_APPROVAL_B). The approvers can be defined globally, as well as overridden for a given organization (HZ_PARTIES). Approvers don't necessarily have to be specified as fnd_user, we will
-
This entity describes special contract based fee assessment rates
-
View: ASO_I_ORG_CONTACTS_V 12.1.1
It gives the information about Party Name,Party Type etc.
APPS.ASO_I_ORG_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_ORG_CONTACTS·↳ HZ_ORG_CONTACT_ROLES·Explore ASO module →
-
View: ASO_I_ORG_CONTACTS_V 12.2.2
It gives the information about Party Name,Party Type etc.
APPS.ASO_I_ORG_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_ORG_CONTACTS·↳ HZ_ORG_CONTACT_ROLES·Explore ASO module →
-
APPS.AST_BUSINESS_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore AST module →
-
This table stores information about your bank account uses.
-
View: CE_BANK_ACCT_USES_BG_V 12.1.1
This view stores bank account uses information for business groups.
APPS.CE_BANK_ACCT_USES_BG_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
This entity describes the method and parameters necessary for determining the amount to charge during fee assessment processing for a fee category fee liability.
-
This table stores information about your bank account uses.
-
This table is an audit table of CE_UPG_BA_USES_ALL
-
View: CE_BANK_ACCT_USES_BG_V 12.2.2
This view stores bank account uses information for business groups.
APPS.CE_BANK_ACCT_USES_BG_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
View: CE_BANK_ACCT_USES_GT_V 12.1.1
APPS.CE_BANK_ACCT_USES_GT_V·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_GT·Explore CE module →
-
View: CE_BANK_ACCT_USES_OU_V 12.2.2
This view stores bank account uses information for operating units.
APPS.CE_BANK_ACCT_USES_OU_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_OU·Explore CE module →
-
View: CE_BANK_ACCT_USES_OU_V 12.1.1
This view stores bank account uses information for operating units.
APPS.CE_BANK_ACCT_USES_OU_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_OU·Explore CE module →
-
View: CE_BANK_ACCT_USES 12.2.2
APPS.CE_BANK_ACCT_USES·↳ CE_BANK_ACCT_USES_ALL·↳ CE_BANK_ACCT_USES_OU·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
View: CE_UPGA_BA_USES 12.1.1
This view is a single org view of the CE_UPGA_BA_USES_ALL table
APPS.CE_UPGA_BA_USES·↳ CE_UPGA_BA_USES_ALL·Explore CE module →
-
View: CE_UPG_BA_USES 12.2.2
This view is a single org view of the CE_UPG_BA_USES_ALL table
APPS.CE_UPG_BA_USES·↳ CE_UPG_BA_USES_ALL·Explore CE module →
-
View: AST_LM_QUOTES_V 12.1.1
APPS.AST_LM_QUOTES_V·↳ ASO_QUOTE_HEADERS_ALL·↳ ASO_QUOTE_STATUSES_VL·↳ HR_OPERATING_UNITS·Explore AST module →
-
View: AST_LM_QUOTES_V 12.2.2
APPS.AST_LM_QUOTES_V·↳ ASO_QUOTE_HEADERS_ALL·↳ ASO_QUOTE_STATUSES_VL·↳ HR_OPERATING_UNITS·Explore AST module →
-
View: CE_UPG_BA_USES 12.1.1
This view is a single org view of the CE_UPG_BA_USES_ALL table
APPS.CE_UPG_BA_USES·↳ CE_UPG_BA_USES_ALL·Explore CE module →
-
View: IGS_OR_CONTACTS_V 12.1.1
Describes the institution Contact Details
APPS.IGS_OR_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore IGS module →
-
View: IGS_FI_FEE_AS_RATE_V 12.1.1
APPS.IGS_FI_FEE_AS_RATE_V·↳ HZ_PARTIES·↳ IGS_AD_LOCATION·↳ IGS_AS_UNIT_CLASS·Explore IGS module →
-
View: CE_BANK_ACCT_USES_LE_V 12.2.2
This view stores bank account uses information for legal entities.
APPS.CE_BANK_ACCT_USES_LE_V·↳ CE_BANK_ACCOUNTS·↳ CE_BANK_ACCT_USES_ALL·↳ CE_SECURITY_PROFILES_V·Explore CE module →
-
This table is an audit table of CE_UPG_BA_USES_ALL
-
This table stores new CE bank account uses information for bank upgrade purpose
-
View: AMS_HZ_B2B_MAPPING_V 12.1.1
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_HZ_B2B_MAPPING_V·↳ AMS_IMP_LIST_HEADERS_ALL·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
This table stores Persons or Organizations (Prospects) imported from external sources.
-
This table stores Persons or Organizations (Prospects) imported from external sources.
-
View: AMS_HZ_B2B_MAPPING_V 12.2.2
This view stores the mapping of ams_imp_source_lines table. This is used to populate the data from the data file.
APPS.AMS_HZ_B2B_MAPPING_V·↳ AMS_IMP_LIST_HEADERS_ALL·↳ AMS_IMP_SOURCE_LINES·Explore AMS module →
-
VIEW: JTF.JTF_UM_APPROVERS# 12.2.2