Search Results hz_org_contact_roles




Overview
Explore in AI Chat

Overview

The HZ_ORG_CONTACT_ROLES table is a core data object within the Oracle Trading Community Architecture (TCA) model, specifically under the AR (Receivables) product schema. It serves as a junction table that defines the specific roles or functions assigned to a contact person associated with a business organization. This table is fundamental for managing complex business relationships, enabling a single organization contact to fulfill multiple roles, such as a primary buyer, technical approver, and billing contact, across different business contexts. Its existence is critical for maintaining referential integrity and providing a flexible, normalized structure for contact role management within Oracle E-Business Suite modules that leverage the TCA registry.

Key Information Stored

The table's primary purpose is to link a contact to their assigned roles. The key columns, as indicated by the provided metadata, include the primary key ORG_CONTACT_ROLE_ID, which uniquely identifies each role assignment record. The critical foreign key is ORG_CONTACT_ID, which references the HZ_ORG_CONTACTS table to identify the specific person acting as the contact. While the provided excerpt does not list all columns, a typical implementation includes a ROLE_TYPE column to store the code or description of the role (e.g., 'BILL_TO', 'SHIP_TO', 'BUYER'), a PRIMARY_FLAG to denote the principal role for a given context, and status columns like STATUS and START_DATE/END_DATE to manage the lifecycle of the role assignment. The table's design allows for the effective modeling of time-sensitive and hierarchical contact responsibilities.

Common Use Cases and Queries

This table is central to processes requiring precise identification of responsible parties. Common use cases include generating accurate billing documents by identifying the 'BILL_TO' contact, routing sales orders by locating the 'SHIP_TO' contact, or determining approval workflows based on a 'DECISION_MAKER' role. A fundamental query pattern involves joining HZ_ORG_CONTACT_ROLES with HZ_ORG_CONTACTS and the related HZ_PARTIES tables to retrieve a comprehensive contact profile. For example, to find all active billing contacts for a specific customer account, a query would filter on ROLE_TYPE = 'BILL_TO' and a valid status, joining through ORG_CONTACT_ID to get the contact's name and details. Reporting on contact role distribution or auditing role assignments over time are also standard operational and analytical activities reliant on this table.

Related Objects

As per the documented foreign key, HZ_ORG_CONTACT_ROLES has a direct and essential relationship with the HZ_ORG_CONTACTS table, which stores the master record of the contact person within an organization. This, in turn, relates to the broader TCA party model, including HZ_PARTIES and HZ_PARTY_SITES. The table is integral to the TCA Public APIs, such as the HZ_PARTY_CONTACT_V2PUB package, which provides the supported interface for creating and managing these role assignments. Modules beyond Receivables, including Order Management (OE), Service (CS), and Marketing (AMS), depend on the data in this table to function correctly within the unified TCA framework.