Search Results hz_cust_profile_amts_m




Overview
Explore in AI Chat

Overview

The HZ_CUST_PROFILE_AMTS_M table is a Receivables (AR) module table owned by the AR schema that serves as a merge-history archive for customer profile amount records. It captures a snapshot of rows from HZ_CUST_PROFILE_AMTS prior to the execution of a customer account merge, preserving the financial and credit parameters that were associated with the source customer account at the moment the merge was initiated. This design allows Oracle EBS to retain an auditable record of profile amounts for both the surviving and the merged (obsolete) account, supporting post-merge reconciliation, dispute investigation, and regulatory audit requirements.

In terms of heuristic Data Vault classification, the mined FK structure indicates a standalone classification. This suggests that, from a pure foreign-key perspective, the table does not exhibit the multi-parent linkage pattern characteristic of a link table. However, given that its primary key combines the natural business key (CUST_ACCT_PROFILE_AMT_ID) with merge-context discriminator columns (CUSTOMER_MERGE_HEADER_ID, MERGE_REQUEST_ID), it functions behaviorally as a satellite-style history table indexed by a merge event. Modelers should treat it as a merge-event satellite rather than a true hub, since the same profile amount can appear multiple times under different merge headers.

Key Information Stored

The table contains 97 documented columns, of which the following are the most operationally significant:

The descriptor attributes (ATTRIBUTE1–15, JGZZ_ATTRIBUTE1–15, GLOBAL_ATTRIBUTE1–20) provide extensibility for localization and customer-specific configurations.

Common Use Cases and Queries

The principal use case is forensic analysis of customer merges: determining what credit limits, interest rates, and dunning thresholds applied to an account immediately before it was merged away. A typical query joins the merge header to reconstruct the pre-merge state:

  • Identify all archived profile amounts for a specific merge: SELECT * FROM hz_cust_profile_amts_m WHERE customer_merge_header_id = :hdr;
  • Compare pre-merge versus post-merge credit limits to detect unintended changes: join to HZ_CUST_PROFILE_AMTS on CUST_ACCT_PROFILE_AMT_ID.
  • Audit reports enumerating which accounts had non-default interest schedules at the time of merge, using INTEREST_SCHEDULE_ID and INTEREST_RATE.
  • Troubleshooting collection issues arising after a merge, where dunning amounts or statement thresholds appear to have been altered.
  • Reconciling the CE_INTEREST_SCHEDULES configuration against the archived profile amounts for regulatory reporting.

Related Objects

  • HZ_CUST_PROFILE_AMTS — the operational source table; rows are copied here before merge processing.
  • HZ_CUSTOMER_PROFILES — referenced via CUST_ACCOUNT_PROFILE_ID; drives profile-level amount definitions.
  • HZ_CUST_ACCOUNTS — referenced via CUST_ACCOUNT_ID; the customer account owning the profile amounts.
  • CE_INTEREST_SCHEDULES — referenced via INTEREST_SCHEDULE_ID; defines interest computation schedules.
  • HZ_MERGED_HEADERS (the merge header table implied by CUSTOMER_MERGE_HEADER_ID) — supplies merge context and transaction identifiers.
  • HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL — site and site-use tables referenced through SITE_USE_ID, relevant when profile amounts are site-specific.
  • The Customer Merge concurrent program and its associated PL/SQL API layer, which writes rows into this table during the merge transaction.