Results for “duplicate_name”

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

Overview

RA_CUSTOMER_MERGES is an Accounts Receivable (AR) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the AR schema. It stores the working and audit records that describe which customers, addresses, and site uses are being merged or moved during a customer merge operation. Each row represents one merge or move directive — typically identifying a source (duplicate) party record and the target (customer) record it is being consolidated into — and is linked to a parent request through CUSTOMER_MERGE_HEADER_ID. The table is populated and processed by the Customer Merge concurrent program and forms, and it acts as the staging and tracking mechanism up to the point that the merge is committed against the Trading Community Architecture (TCA) registry.

From a Data Vault modeling perspective, the documented foreign-key structure classifies this object heuristically as a link table. It resolves relationships among HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL and records the association between a customer, an address, and a site use as they are merged or moved. The table contains 60 columns in the documented 12.2.2 schema, with primary key RA_CUSTOMER_MERGES_PK on CUSTOMER_MERGE_ID and unique index RA_CUSTOMER_MERGES_U1 also on CUSTOMER_MERGE_ID.

Key Information Stored

The columns below carry the substantive business meaning of each merge or move instruction.

• CUSTOMER_MERGE_ID — surrogate primary key and unique business-key candidate (RA_CUSTOMER_MERGES_U1); the unique identifier of the merge line.
• CUSTOMER_MERGE_HEADER_ID — foreign key to RA_CUSTOMER_MERGE_HEADERS; groups all lines belonging to a single merge run.
• CUSTOMER_ID — foreign key to HZ_CUST_ACCOUNTS; the surviving customer account.
• CUSTOMER_ADDRESS_ID — foreign key to HZ_CUST_ACCT_SITES_ALL; the surviving address.
• CUSTOMER_SITE_ID — foreign key to HZ_CUST_SITE_USES_ALL; the surviving site use.
• DUPLICATE_ADDRESS_ID — foreign key to HZ_CUST_ACCT_SITES_ALL; the address being merged away.
• DUPLICATE_SITE_ID — foreign key to HZ_CUST_SITE_USES_ALL; the site use being merged away.
• DUPLICATE_ID, DUPLICATE_NAME, DUPLICATE_NUMBER, DUPLICATE_REF — identifying attributes of the duplicate (source) party.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_REF — identifying attributes of the surviving customer.
• PROCESS_FLAG — status indicator controlling whether the row has been processed during the merge.
• DELETE_DUPLICATE_FLAG — indicates whether the duplicate record or site is to be deleted after merging.
• ORG_ID — operating unit context for multi-org security.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-columns.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield segments.

Common Use Cases and Queries

Typical use cases include auditing completed merges, diagnosing partially processed or failed merge runs, and reporting on duplicate cleanup activity. A frequent pattern joins the header to retrieve all lines for a given run:

• Retrieve merge lines by customer: SELECT customer_merge_id, duplicate_number, customer_number, process_flag FROM ra_customer_merges WHERE customer_id = :cust_id;
• Find unprocessed lines: SELECT * FROM ra_customer_merges WHERE process_flag IS NULL OR process_flag = 'N';
• Join to TCA to resolve names: SELECT m.customer_number, a.account_name FROM ra_customer_merges m, hz_cust_accounts a WHERE m.customer_id = a.cust_account_id;
• Trace a merge by concurrent request for reconciliation against the merge log.

Related Objects

The most significant related objects are the referenced TCA entities and the parent header table:

• RA_CUSTOMER_MERGE_HEADERS — parent table joined on CUSTOMER_MERGE_HEADER_ID.
• HZ_CUST_ACCOUNTS — joined via CUSTOMER_ID.
• HZ_CUST_ACCT_SITES_ALL — joined via CUSTOMER_ADDRESS_ID and DUPLICATE_ADDRESS_ID.
• HZ_CUST_SITE_USES_ALL — joined via CUSTOMER_SITE_ID and DUPLICATE_SITE_ID.
• HZ_PARTIES / HZ_PARTY_SITES — downstream TCA entities updated once the merge is committed.
• AR_CUSTOMER_MERGE APIs and the Customer Merge concurrent program — the processing interfaces that consume these records.