Results for “party_relationship_type”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC.BIC_RELATIONSHIP_TYPES is a reference (lookup) table belonging to the BIC — Customer Intelligence product family, which Oracle has designated obsolete in current EBS releases. It stores the master list of relationship type codes that classify how one party (customer, contact, or organization) relates to another within the Customer Intelligence model — for example, relationships such as "spouse," "employee of," or "subsidiary of," depending on how the implementation seeded the table. Rather than holding transactional relationship instances, BIC_RELATIONSHIP_TYPES provides the permitted, display-enabled set of types that drive classification of actual party relationships elsewhere in the schema.
The ETRM metadata classifies this object, using a heuristic derived from its foreign-key structure, as a standalone Data Vault element. In Data Vault terms this is best treated as a hub-like reference dimension: it is not a link (it does not resolve many-to-many relationships between other hubs) and it is not a satellite of a single parent. Designers modeling this table as a raw vault object can treat PARTY_RELATIONSHIP_TYPE as the natural business key of the hub. Because the parent product is obsolete, the object is most commonly encountered today during legacy data migrations, discovery/impact analysis of the BIC schema, and archival reporting.
Key Information Stored
The table has eight documented columns. The most important include:
- PARTY_RELATIONSHIP_TYPE — the business-key attribute that identifies each relationship type. This is the column exposed through the unique index
BIC_RELATIONSHIP_TYPES_U1, confirming it as the true unique identifier of a row rather than the surrogate key. - DISPLAY_FLAG — a Y/N style indicator controlling whether the relationship type is presented to end users in UI lists and LOVs.
- SECURITY_GROUP_ID — the multi-tenancy/access-control column; it carries a foreign-key relationship to
FND_SECURITY_GROUPS, restricting which security group may view or use a given type. - LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO columns (audit attribution).
No separate surrogate primary-key column is documented; the sole unique index is the business-key candidate on PARTY_RELATIONSHIP_TYPE.
Common Use Cases and Queries
Typical usage centres on decoding relationship-type codes for reporting and validating that only display-enabled types are seeded:
- LOV population — retrieve the types available for selection, filtered by display flag and security group:
SELECT party_relationship_type FROM bic_relationship_types WHERE display_flag = 'Y' AND security_group_id = :g; - Code decode for joins — join a relationship fact table back to this lookup on the business key to render descriptions.
- Seed/migration validation — confirm all expected relationship types exist, especially before and after BIC-to-successor-product migration, since BIC is obsolete.
- Audit reporting — identify when types were created or last modified using the WHO columns, useful during evidence gathering for a data-governance or impact-assessment exercise.
Because the older BIC tables often duplicate security-group filtering, queries should always constrain SECURITY_GROUP_ID to avoid cross-tenant leakage.
Related Objects
- FND_SECURITY_GROUPS — joined via
BIC_RELATIONSHIP_TYPES.SECURITY_GROUP_ID → FND_SECURITY_GROUPS.SECURITY_GROUP_ID. The only documented foreign key of this table. - BIC_RELATIONSHIP_TYPES_U1 — the unique index enforcing the business key on
PARTY_RELATIONSHIP_TYPE. - Party relationship tables within the BIC schema (e.g., relationship-instance tables) — logically depend on this lookup through
PARTY_RELATIONSHIP_TYPEfor classification and validation, even though no explicit FK is documented. - BIC customer/organization objects — the parties referenced by relationships ultimately resolve to these entities.
- FND_APPLICATION — indirectly relevant for identifying the BIC product registration when tracing the obsolete module.
Given BIC's obsolete status, related-object discovery is best performed through the EBS data dictionary (FND tables and AD_ZD or DBA_ views) rather than relying on runtime dependency documentation.
-
View: JTF_RS_PTNR_MIGR_VL 12.1.1
Stores specific partner related data used for internal migration.
APPS.JTF_RS_PTNR_MIGR_VL·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →
-
View: JTF_RS_PTNR_MIGR_VL 12.2.2
Stores specific partner related data used for internal migration.
APPS.JTF_RS_PTNR_MIGR_VL·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →
-
View: ASF_HZ_PERSON_LOV_V 12.1.1
-
View: OKL_AM_CONTACTS_UV 12.2.2
APPS.OKL_AM_CONTACTS_UV·↳ OKX_PARTY_CONTACTS_V·Explore OKL module →
-
View: OKL_AM_CONTACTS_UV 12.1.1
APPS.OKL_AM_CONTACTS_UV·↳ OKX_PARTY_CONTACTS_V·Explore OKL module →
-
View: ASF_CNT_PERSON_LOV_V 12.1.1
APPS.ASF_CNT_PERSON_LOV_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore ASF module →
-
View all contacts, using hz_relationship table as the driving table. The view expose data for subject and object party. Please note that the view does not join with hz_org_contacts.
APPS.JTF_PARTY_ALL_CONTACTS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →
-
TCA obsoleted the hz_party_relationships view in R12. This is a replacement to help make the uptake easier.
APPS.QA_HZ_PARTY_RELATIONSHIPS_V·↳ HZ_RELATIONSHIPS·Explore QA module →
-
TCA obsoleted the hz_party_relationships view in R12. This is a replacement to help make the uptake easier.
APPS.QA_HZ_PARTY_RELATIONSHIPS_V·↳ HZ_RELATIONSHIPS·Explore QA module →
-
View: OKX_PARTY_CONTACTS_V 12.2.2
Party contacts
APPS.OKX_PARTY_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore OKX module →
-
View: IGS_PE_RELATIONSHIPS_V 12.1.1
APPS.IGS_PE_RELATIONSHIPS_V·↳ FND_LOOKUP_VALUES·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore IGS module →
-
View all contacts, using hz_relationship table as the driving table. The view expose data for subject and object party. Please note that the view does not join with hz_org_contacts
APPS.JTF_TASK_PARTY_CONTACTS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_CONTACT_POINTS·↳ HZ_ORG_CONTACTS·Explore JTF module →
-
View: OKX_PARTY_CONTACTS_V 12.1.1
Party contacts
APPS.OKX_PARTY_CONTACTS_V·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore OKX module →
-
View: ASF_HZ_PERSON_LOV_V 12.2.2
-
APPS.AST_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AST module →
-
View for details of Related, Subject, Object party.
APPS.CS_SR_HZ_RELATIONSHIPS_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore CS module →
-
View: ASF_CNT_PERSON_LOV_V 12.2.2
APPS.ASF_CNT_PERSON_LOV_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore ASF module →
-
sales lead contact details
APPS.AS_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AS module →
-
View: ASF_PERSON_LOV_V 12.1.1
APPS.ASF_PERSON_LOV_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore ASF module →
-
View: ASF_PERSON_LOV_V 12.2.2
APPS.ASF_PERSON_LOV_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore ASF module →
-
View to provide opportunity contact details.
APPS.AS_OPPORTUNITY_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LEAD_CONTACTS_ALL·↳ HZ_CONTACT_POINTS·Explore AS module →
-
Party relationship view
APPS.AS_PARTY_RELATIONSHIPS_V·↳ HZ_RELATIONSHIPS·Explore AS module →
-
View all contacts, using hz_relationship table as the driving table. The view expose data for subject and object party. Please note that the view does not join with hz_org_contacts.
APPS.JTF_PARTY_ALL_CONTACTS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore JTF module →
-
View: AST_ORG_CONTACTS_V 12.1.1
APPS.AST_ORG_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·Explore AST module →
-
View all contacts, using hz_relationship table as the driving table. The view expose data for subject and object party. Please note that the view does not join with hz_org_contacts
APPS.JTF_TASK_PARTY_CONTACTS_V·↳ HZ_CODE_ASSIGNMENTS·↳ HZ_CONTACT_POINTS·↳ HZ_ORG_CONTACTS·Explore JTF module →
-
View: CSD_HZ_REL_V 12.2.2
View for details of Related, Subject, Object party. Used in the Depot Repair Workbench.
APPS.CSD_HZ_REL_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore CSD module →
-
View: AST_RELATIONSHIP_V 12.1.1
APPS.AST_RELATIONSHIP_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore AST module →
-
View: AST_RELATIONSHIP_V 12.2.2
APPS.AST_RELATIONSHIP_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore AST module →
-
View: IGS_PE_HZ_REL_V 12.1.1
View based on join between IGS_PE_HZ_REL and HZ_RELATIONSHIPS
APPS.IGS_PE_HZ_REL_V·↳ FND_LOOKUP_VALUES·↳ HZ_PARTIES·↳ HZ_PERSON_PROFILES·Explore IGS module →
-
View for details of Related, Subject, Object party.
APPS.CS_SR_HZ_RELATIONSHIPS_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore CS module →
-
View: CSD_HZ_REL_V 12.1.1
View for details of Related, Subject, Object party. Used in the Depot Repair Workbench.
APPS.CSD_HZ_REL_V·↳ AR_LOOKUPS·↳ HZ_PARTIES·↳ HZ_RELATIONSHIPS·Explore CSD module →
-
APPS.AST_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AST module →
-
Party relationship view
APPS.AS_PARTY_RELATIONSHIPS_V·↳ HZ_RELATIONSHIPS·Explore AS module →
-
View to provide opportunity contact details.
APPS.AS_OPPORTUNITY_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LEAD_CONTACTS_ALL·↳ HZ_CONTACT_POINTS·Explore AS module →
-
Relationships between parties
-
It stores party/site org contacts without role type and person profile related information
APPS.AS_PARTY_ORG_CONTACTS_V·↳ HZ_CONTACT_POINTS·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·Explore AS module →
-
View: AST_ORG_CONTACTS_V 12.2.2
APPS.AST_ORG_CONTACTS_V·↳ AR_LOOKUPS·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·Explore AST module →
-
Relationships between parties
-
sales lead contact details
APPS.AS_SALES_LEAD_CONTACTS_V·↳ AR_LOOKUPS·↳ AS_LOOKUPS·↳ AS_SALES_LEAD_CONTACTS·Explore AS module →
-
It stores party/site org contacts without role type and person profile related information
APPS.AS_PARTY_ORG_CONTACTS_V·↳ HZ_CONTACT_POINTS·↳ HZ_ORG_CONTACTS·↳ HZ_PARTIES·Explore AS module →