Search Results hz_customer_profiles_m




Overview
Explore in AI Chat

Overview

HZ_CUSTOMER_PROFILES_M is an Oracle Receivables (AR) archive table that stores the deleted records of HZ_CUSTOMER_PROFILES during the customer account merge process. When two customer accounts are merged in Oracle E-Business Suite, the profile rows associated with the surviving account are updated, while the rows belonging to the merged (surviving-to-obsolete) account are removed from the base table and preserved here. This design provides an audit trail and supports reversal or reconciliation of merge activity, which is essential for financial compliance and for diagnosing issues that arise after a merge.

The object is owned by the AR schema and is valid in both EBS 12.1.1 and 12.2.2. It contains 120 documented columns in the 12.2.2 ETRM schema, mirroring the structure of HZ_CUSTOMER_PROFILES and adding merge-specific control columns. From a heuristic Data Vault modeling perspective, the mined relationship structure classifies this table as a standalone construct. Since it records the state of customer profile records at the point of deletion keyed by a composite merge identity, it is best modeled as a link-style or historically descriptive record rather than a pure hub or satellite.

Key Information Stored

The table's most important columns include:

The surrogate primary key is defined by the composite unique index HZ_CUSTOMER_PROFILES_M_U1 on (CUST_ACCOUNT_PROFILE_ID, CUSTOMER_MERGE_HEADER_ID, MERGE_REQUEST_ID), which also serves as the business-key candidate and is enforced by HZ_CUSTOMER_PROFILES_M_PK.

Common Use Cases and Queries

Typical usage centers on auditing and troubleshooting customer merges. A common query retrieves the archived profiles for a specific merge:

  • SELECT * FROM hz_customer_profiles_m WHERE customer_merge_header_id = :merge_id;
  • Reconciling deleted versus surviving profiles: joining the archive to HZ_CUSTOMER_PROFILES on CUST_ACCOUNT_PROFILE_ID to confirm which rows were removed.
  • Reporting credit settings lost during merges by selecting CREDIT_HOLD, CREDIT_RATING, and RISK_CODE for the merged customer account.
  • Identifying the merge requests that affected a given customer account: filtering on CUST_ACCOUNT_ID.
  • Building reconciliation reports for Receivables period close evidence.

Because the table is read-only in normal operations, writes occur only through the merge engine, not through concurrent user programs.

Related Objects

  • HZ_CUSTOMER_PROFILES – The base table whose deleted rows are archived here.
  • HZ_CUST_ACCOUNTS – Joined via CUST_ACCOUNT_ID to resolve account details.
  • AR_COLLECTORS – Joined via COLLECTOR_ID for collector assignment.
  • HZ_CUST_PROFILE_CLASSES – Joined via PROFILE_CLASS_ID for profile class rules.
  • AR_STATEMENT_CYCLES – Joined via STATEMENT_CYCLE_ID.
  • AR_AUTOCASH_HIERARCHIES – Joined via AUTOCASH_HIERARCHY_ID.
  • HZ_MERGE_PARTIES/merge header tables – Provide the merge context referenced by CUSTOMER_MERGE_HEADER_ID and MERGE_REQUEST_ID.