Search Results ra_customer_merge_headers




Overview
Explore in AI Chat

Overview

RA_CUSTOMER_MERGE_HEADERS is the master control table for Oracle Receivables' customer account merge functionality. It stores the high-level information pertaining to each account merge request submitted through the Customer Merge program, serving as the parent record for the individual customer records that participate in a merge operation. Every merge request creates one row in this table, which then drives downstream processing across Receivables, Order Management, and other modules that reference the customer.

From a Data Vault modeling perspective, this object is best characterized as a link entity. It sits at the intersection of two customer references — the surviving account and the duplicate account — capturing the relationship and the merge event between them rather than describing a single business entity. The presence of foreign keys pointing outward to HZ_CUST_ACCOUNTS and RA_CUSTOMERS, combined with legacy descriptive attributes and audit columns, reinforces this link classification. In EBS 12.1.1 and 12.2.2 the table resides in the AR schema and is documented with 46 columns.

Key Information Stored

The table's structure separates identity, business references, merge metadata, and audit trail:

Common Use Cases and Queries

Typical activities center on monitoring merge status, troubleshooting failures, and auditing customer consolidation. A reporting query tracking pending versus completed merges might filter on PROCESS_FLAG for the operating unit:

SELECT h.customer_merge_header_id, h.customer_name, h.duplicate_name, h.process_flag, h.merge_fail_msg FROM ra_customer_merge_headers h WHERE h.org_id = :org_id AND h.process_flag IN ('N','P');

A reconciliation query joins the header to surviving accounts and duplicate records to validate that merges completed as intended:

SELECT h.customer_merge_header_id, h.customer_number AS survivor, h.duplicate_number AS duplicate, h.merge_reason_code, h.merge_fail_msg FROM ra_customer_merge_headers h WHERE h.last_update_date >= :since_date;

Because the table records the concurrent request that produced each row, DBAs can trace failures by correlating REQUEST_ID with FND_CONCURRENT_REQUESTS. Organizations also use it to audit merge volume over time, group by operating unit, and reconcile against "Customer Merge" concurrent program output.

Related Objects

  • RA_CUSTOMER_MERGES — the primary dependent table; its CUSTOMER_MERGE_HEADER_ID column references RA_CUSTOMER_MERGE_HEADERS, holding the line-level detail for each merge.
  • HZ_CUST_ACCOUNTS — referenced via CUSTOMER_ID; supplies the surviving account record.
  • RA_CUSTOMERS — referenced via DUPLICATE_ID; supplies the duplicate customer record.
  • ONT (Order Management) customer merge processes — consume header rows to update sales orders post-merge.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the originating concurrent run.
  • HZ_MERGE_HISTORY / party merge tables — TCA-side counterparts that coordinate party and account merges with this AR table.