Results for “address_text”

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

Overview

The HZ_CUST_ACCT_SITES_ALL_M table is a staging and archival repository in the Oracle E-Business Suite Receivables (AR) module. It resides in the AR schema and stores customer account site information copied from HZ_CUST_ACCT_SITES_ALL prior to the execution of a customer account merge. The suffix "_M" denotes the merge-related nature of the object: rows are inserted here as a snapshot of the pre-merge state, allowing the merge process to preserve, audit, and, if necessary, reverse the changes applied to customer account sites during account consolidation.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This classification suggests the table functions neither as a clean hub nor as a link but as an independent historical capture of account site attributes at the moment of merge. Because it records state over a defined event (the merge), it exhibits satellite-like characteristics, yet its composite key and direct CUST_ACCOUNT_ID reference prevent a strict hub classification.

Key Information Stored

The documented physical schema for Release 12.2.2 contains 76 columns. The most significant columns include:

• CUST_ACCT_SITE_ID — The unique identifier of the customer account site, inherited from HZ_CUST_ACCT_SITES_ALL.
• CUSTOMER_MERGE_HEADER_ID — The merge batch header that caused this row to be staged.
• MERGE_REQUEST_ID — The specific merge request associated with the snapshot.
• CUST_ACCOUNT_ID — The customer account to which the site belonged; this column carries a foreign key to HZ_CUST_ACCOUNTS.
• PARTY_SITE_ID — Reference to the underlying party site record.
• ORG_ID — The operating unit context, critical for multi-org reporting and security.
• STATUS — The site status at the time of the snapshot.
• BILL_TO_FLAG, SHIP_TO_FLAG, MARKET_FLAG, KEY_ACCOUNT_FLAG — The role/usage indicators defining how the site is used in transactions.
• ORIG_SYSTEM_REFERENCE — The legacy or external system identifier for the site.
• TERRITORY_ID, TERRITORY, PRIMARY_SPECIALIST_ID, SECONDARY_SPECIALIST_ID — Territory and sales specialist assignments captured before the merge.
• ATTRIBUTE1–ATTRIBUTE20 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 — The standard EBS descriptive flexfield and global descriptive flexfield segments.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.

The documented surrogate primary key is HZ_CUST_ACCT_SITES_ALL_M_PK. The metadata lists this constraint as spanning CUST_ACCT_SITE_ID, CUSTOMER_MERGE_HEADER_ID, MERGE_REQUEST_ID, while the unique index HZ_CUST_ACCT_SITES_ALL_M_U1 is documented as a business-key candidate over the same three columns. This composite uniqueness guarantees that a given site can be staged only once per merge request, providing idempotent protection for reruns.

Common Use Cases and Queries

Data residing in this table is most often consumed for audit, reconciliation, and rollback scenarios. Typical queries include:

• Auditing a specific merge: selecting all staged sites for a given merge header to compare pre- and post-merge values against HZ_CUST_ACCT_SITES_ALL.
• Reconstructing historical site attributes: reporting the bill-to, ship-to, and territory flags that were valid before a merge for downstream BI extracts.
• Reverse engineering changes: when a merge must be undone, this table supplies the authoritative prior state.

A representative query pattern follows: SELECT CUST_ACCT_SITE_ID, CUST_ACCOUNT_ID, STATUS, BILL_TO_FLAG, SHIP_TO_FLAG, ORG_ID FROM HZ_CUST_ACCT_SITES_ALL_M WHERE CUSTOMER_MERGE_HEADER_ID = :merge_header_id ORDER BY CUST_ACCT_SITE_ID; Joining to HZ_CUST_ACCOUNTS on CUST_ACCOUNT_ID allows reporting account names alongside the archived site role flags.

Related Objects

• HZ_CUST_ACCT_SITES_ALL — The source table; rows are copied from here at the beginning of a merge and remain the live record afterward.
• HZ_CUST_ACCOUNTS — Referenced via the CUST_ACCOUNT_ID foreign key.
• HZ_CUST_SITE_USES_ALL — Site-use records that mirror the role flags captured in this staging table.
• HZ_MERGE_HEADERS / table backing CUSTOMER_MERGE_HEADER_ID — Provides the merge batch context that ties staged rows together.
• HZ_PARTY_SITES — Referenced through PARTY_SITE_ID for party-level site details.
• Customer merge concurrent programs and the HZ_MERGE_PUB / DQM merge APIs — The processes that populate and read this table during account consolidation.