Results for “current_role_state”

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

Overview

HZ_CUST_ACCOUNT_ROLES is the Oracle Receivables (AR) table that records the roles parties perform within customer accounts. It is the central intersection between a party (HZ_PARTIES), a customer account (HZ_CUST_ACCOUNTS), and optionally a specific account site (HZ_CUST_ACCT_SITES_ALL), enabling Oracle E-Business Suite to model real-world relationships such as sold-to contact, ship-to contact, bill-to contact, drawee, and end customer. The table is owned by the AR schema and is validated in both Release 12.1.1 and 12.2.2, where the documented physical schema contains 73 columns. Because contact persons, sites, and responsibilities are all anchored to this single role record, HZ_CUST_ACCOUNT_ROLES functions as the master reference for contact identity across Order Management, Receivables, Projects, and CRM.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is hub-leaning. HZ_CUST_ACCOUNT_ROLES anchors the CUST_ACCOUNT_ROLE_ID business key and links outward to multiple hubs (party and customer account) and to subordinate satellites, which makes it suitable as a hub with associated link and satellite structures in a warehousing model.

Key Information Stored

The table is defined by a single surrogate primary key and one unique index. The most significant columns are:

• CUST_ACCOUNT_ROLE_ID — Surrogate primary key, defined by HZ_CUST_ACCOUNT_ROLES_PK and the unique index HZ_CUST_ACCOUNT_ROLES_U1; this is the value referenced by every downstream foreign key.
• PARTY_ID — Foreign key to HZ_PARTIES identifying the person or organization acting in the role.
• CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS identifying the customer account in which the role applies.
• CUST_ACCT_SITE_ID — Foreign key to HZ_CUST_ACCT_SITES_ALL, restricting the role to a specific account site where applicable.
• ROLE_TYPE — Classifies the role (for example, contact versus responsibility) and drives downstream usage across modules.
• PRIMARY_FLAG — Indicates whether the role is the primary contact for the account or site.
• CURRENT_ROLE_STATE and CURRENT_ROLE_STATE_EFFECTIVE — Track the current status of the role assignment and when it took effect.
• BEGIN_DATE and END_DATE — Define the effective dating window for the role.
• STATUS — Active/inactive indicator for the record.
• ORIG_SYSTEM_REFERENCE — Captures the source system reference for imported or integrated role data.
• SOURCE_CODE — Identifies how the record was created.
• OBJECT_VERSION_NUMBER — Supports optimistic locking during concurrent updates.
• CREATED_BY_MODULE and APPLICATION_ID — Identify the originating module and application.
• Standard audit columns (LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN) plus the ATTRIBUTE1–25 and GLOBAL_ATTRIBUTE1–20 descriptive flexfield columns.

Common Use Cases and Queries

The table is queried whenever order, invoice, or project records must be resolved to a contact person. A typical reporting pattern joins the role to the party and account:

• Resolving ship-to and invoice-to contacts for an order header by joining OE_ORDER_HEADERS_ALL.SHIP_TO_CONTACT_ID or INVOICE_TO_CONTACT_ID to HZ_CUST_ACCOUNT_ROLES.CUST_ACCOUNT_ROLE_ID and then to HZ_PARTIES for the contact name.
• Listing all active roles for a customer account, filtered on STATUS and the BEGIN_DATE/END_DATE window.
• Identifying primary contacts per account site using PRIMARY_FLAG and CUST_ACCT_SITE_ID.
• Reconciling historical order contacts through OE_ORDER_HEADER_HISTORY, which also carries DELIVER_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, SOLD_TO_CONTACT_ID, and END_CUSTOMER_CONTACT_ID foreign keys to this table.
• Receivables reporting that links RA_CUSTOMER_TRX_ALL.BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, DRAWEE_CONTACT_ID, and SOLD_TO_CONTACT_ID back to role records.

Related Objects

HZ_CUST_ACCOUNT_ROLES participates in a broad web of foreign key relationships. The most significant related objects include:

• HZ_PARTIES — referenced via PARTY_ID; supplies the party identity behind each role.
• HZ_CUST_ACCOUNTS — referenced via CUST_ACCOUNT_ID; the customer account to which the role belongs.
• HZ_CUST_ACCT_SITES_ALL — referenced via CUST_ACCT_SITE_ID; the specific site for the role.
• HZ_CUST_CONTACT_POINTS and HZ_ROLE_RESPONSIBILITY — reference CUST_ACCOUNT_ROLE_ID, extending contact points and responsibilities.
• OE_ORDER_HEADERS_ALL and OE_ORDER_HEADER_HISTORY — reference the role through SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, SOLD_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID, and END_CUSTOMER_CONTACT_ID.
• OE_ORDER_LINES_ALL and OE_ORDER_LINES_HISTORY — reference END_CUSTOMER_CONTACT_ID, INTMED_SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, and DELIVER_TO_CONTACT_ID.
• OE_BLANKET_HEADERS_ALL, OE_BLANKET_HEADERS_HIST, OE_BLANKET_LINES_ALL, and OE_BLANKET_LINES_HIST — reference the role for blanket agreement contacts.
• RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL — reference BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, DRAWEE_CONTACT_ID, and SOLD_TO_CONTACT_ID.
• AR_CUSTOMER_CALLS_ALL, AR_BR_TRX_BATCH_RPT, PA_PROJECT_CONTACTS, and RA_INTERFACE_LINES_ALL — additional dependent objects referencing CONTACT_ID or CUST_ACCOUNT_ROLE_ID.