Search Results hz_cust_account_roles_m




Overview
Explore in AI Chat

Overview

The HZ_CUST_ACCOUNT_ROLES_M table is a critical data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Receivables (AR) module. It functions as a merge audit table, designed to preserve a historical snapshot of customer account role data prior to a customer account merge operation. This table is part of the TCA (Trading Community Architecture) data model and is essential for maintaining data integrity and auditability. When a customer merge is executed, the system copies the relevant records from the primary transactional table, HZ_CUST_ACCOUNT_ROLES, into this merge table before applying any updates or deletions. This ensures a complete audit trail of the role relationships that existed before the merge, which is vital for compliance and troubleshooting.

Key Information Stored

The table's primary purpose is to archive pre-merge customer account role records. Its structure is defined by a composite primary key and several key foreign key columns that link it to the merge control framework. The most significant columns include:

  • CUST_ACCOUNT_ROLE_ID: The unique identifier for the customer account role record being archived. This value originates from the HZ_CUST_ACCOUNT_ROLES table.
  • CUSTOMER_MERGE_HEADER_ID: A foreign key linking to the merge process header. This is the column referenced in the user's search and, together with CUST_ACCOUNT_ROLE_ID, forms the table's primary key (HZ__CUST_ACCOUNT_ROLES_M_PK).
  • MERGE_REQUEST_ID: An identifier for the specific merge request that triggered the archival of this record, providing another layer of process tracking.

The table will also contain a full copy of all columns from the source HZ_CUST_ACCOUNT_ROLES record at the moment of the merge, such as CUST_ACCOUNT_ID, PARTY_ID, and ROLE_TYPE.

Common Use Cases and Queries

The primary use case for this table is auditing and investigating historical customer relationships after a merge. For instance, if a user needs to understand what role assignments were transferred or removed during a specific customer consolidation, they would query this table using the merge header or request ID. A common reporting query would join this table to the customer merge header table to get context about the merge operation.

Sample SQL Pattern:
SELECT hcam.*, hm.request_number
FROM ar.hz_cust_account_roles_m hcam
JOIN ar.hz_customer_merges hm ON hcam.customer_merge_header_id = hm.customer_merge_header_id
WHERE hm.request_number = '<Your_Merge_Request>';
This query retrieves all archived role records for a specific merge request, providing a clear audit report.

Related Objects

HZ_CUST_ACCOUNT_ROLES_M has direct relationships with several core TCA and merge processing tables, as indicated by its key structure:

  • HZ_CUST_ACCOUNT_ROLES: This is the source transactional table. Records are copied from here into HZ_CUST_ACCOUNT_ROLES_M before being modified during a merge.
  • HZ_CUSTOMER_MERGES: The table likely referenced by the CUSTOMER_MERGE_HEADER_ID foreign key. This table controls and logs the overall customer merge process.
  • RA_CUSTOMER_MERGES: The merge request identifier (MERGE_REQUEST_ID) may link to this Receivables-specific merge request table, which initiates the process.

The table's existence is intrinsically tied to the customer merge workflow, acting as a dependent audit object for the primary role relationship entity.