Results for “ra_customer_merges_u1”

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

Overview

AR.RA_CUSTOMER_MERGES is a transactional audit table in Oracle Receivables that records the outcome of the Customer Merge program. Each row represents a single merge action involving a customer, an address, or a site use, and captures both the surviving ("winning") entity and the duplicate ("losing") entity that was removed from active use. The table is the detail-level companion to RA_CUSTOMER_MERGE_HEADERS, which stores the header-level context for a merge run initiated through the Merge Customers window in Oracle E-Business Suite 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the mined dependency profile classifies RA_CUSTOMER_MERGES as a link table. This is a modeling suggestion, not a statement of Oracle's internal design: the object predominantly resolves relationships between the surviving customer, address, and site use entities and their duplicates, with descriptive attributes attached to that association. The native primary key is CUSTOMER_MERGE_ID, and the table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10.

Key Information Stored

The table contains sixty documented columns. The most operationally significant are:

• CUSTOMER_MERGE_ID — Surrogate primary key, single-column NUMBER(15), and the sole business-key candidate via unique index RA_CUSTOMER_MERGES_U1.
• CUSTOMER_MERGE_HEADER_ID — Foreign key to RA_CUSTOMER_MERGE_HEADERS; ties each detail record to its parent merge run.
• CUSTOMER_ID, CUSTOMER_SITE_ID, CUSTOMER_ADDRESS_ID — Identifiers of the surviving customer, site use, and address.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_SITE_CODE, CUSTOMER_ADDRESS — Denormalized descriptive attributes of the surviving entity, retained for display and audit.
• DUPLICATE_ID, DUPLICATE_SITE_ID, DUPLICATE_ADDRESS_ID — Identifiers of the duplicate entity that was merged away.
• DUPLICATE_NAME, DUPLICATE_NUMBER, DUPLICATE_SITE_CODE — Descriptive attributes of the duplicate, preserving the pre-merge identity.
• PROCESS_FLAG — VARCHAR2(30) indicating whether the record processed successfully (Y) or not (N).
• DELETE_DUPLICATE_FLAG — Indicates whether the duplicate was removed following the merge.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, SET_NUMBER — Concurrent program and request tracing columns for the merge submission.
• ORG_ID — Multi-org operating unit context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and fifteen descriptive flexfield ATTRIBUTEn columns.

Common Use Cases and Queries

The principal use cases are merge reconciliation, duplicate-cleanup auditing, and post-merge reporting on which customer records were consolidated.

• Audit a merge run: join RA_CUSTOMER_MERGES to RA_CUSTOMER_MERGE_HEADERS on CUSTOMER_MERGE_HEADER_ID to retrieve all detail rows for a given set of duplicates.
• Track a duplicate's fate: query by DUPLICATE_ID or DUPLICATE_NUMBER to determine which surviving CUSTOMER_ID absorbed that record.
• Identify incomplete merges: filter on PROCESS_FLAG = 'N' to locate rows that did not process successfully.
• Tie to concurrent requests: use REQUEST_ID, PROGRAM_ID and SET_NUMBER to correlate merges with the FND_CONCURRENT_REQUESTS log.
• Resolve source records: join DUPLICATE_ADDRESS_ID and DUPLICATE_SITE_ID back to HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL to reconstruct the original structure.

A typical reporting pattern:

• SELECT m.CUSTOMER_NUMBER, m.DUPLICATE_NUMBER, m.PROCESS_FLAG, m.CREATION_DATE FROM RA_CUSTOMER_MERGES m WHERE m.REQUEST_ID = :request_id ORDER BY m.CUSTOMER_MERGE_ID;

Related Objects

RA_CUSTOMER_MERGES sits at the intersection of the Receivables merge model and the Trading Community Architecture (TCA) customer model:

• RA_CUSTOMER_MERGE_HEADERS — Parent table referenced via CUSTOMER_MERGE_HEADER_ID; stores header-level merge context.
• HZ_CUST_ACCOUNTS — Referenced through CUSTOMER_ID; the surviving customer account.
• HZ_CUST_ACCT_SITES_ALL — Referenced through CUSTOMER_ADDRESS_ID and DUPLICATE_ADDRESS_ID.
• HZ_CUST_SITE_USES_ALL — Referenced through CUSTOMER_SITE_ID and DUPLICATE_SITE_ID.
• OE_CUST_MERGES_GTT — Global temporary table that references CUSTOMER_MERGE_ID, used in Order Management merge processing.
• FND_USER, FND_LOGINS — Standard WHO column lookups for CREATED_BY, LAST_UPDATED_BY and LAST_UPDATE_LOGIN.
• FND_CONCURRENT_REQUESTS — Correlates REQUEST_ID to the concurrent program submission.

These relationships confirm the table's role as the durable link between merge headers, TCA entities, and concurrent program execution in Oracle EBS 12.1.1 and 12.2.2.