Search Results hz_cust_acct_relate




Overview
Explore in AI Chat

Overview

APPS.ASO_PVT_ACCT_RELATE_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema. It exposes a filtered projection of customer account relationship data maintained in Oracle's Trading Community Architecture (TCA) model. The view is registered in ETRM as part of the ASO (Order Capture / Quoting) product family and is most commonly encountered by users who search on the underlying TCA entity hz_cust_acct_relate.

Functionally, the view presents the active (status 'A') relationships that exist between customer accounts, including whether a related account is designated as a bill-to or ship-to address for the primary account. Because it exposes only active records, it serves as a stable read-only interface for downstream logic in order capture, order management, and quoting flows that need to resolve account-to-account relationships without directly querying the base TCA table and reapplying the STATUS predicate. The view is also a convenient object for custom reports, BI Publisher datasets, and integration extracts where referencing a pre-filtered API-owned object is preferable to hard-coding business rules against the base table.

Underlying Base Objects

The documented metadata defines the view over a single referenced base object: HZ_CUST_ACCT_RELATE, resolved through a SYNONYM in the APPS schema. The view text is a straightforward SELECT with an equality filter:

There are no joins, aggregations, or derived expressions in the definition. As a result, the view inherits the row-level semantics of HZ_CUST_ACCT_RELATE, a key table in the TCA customer model that stores many-to-many relationships between customer accounts (for example, a corporate parent account related to its child accounts). Because the view is defined over a synonym rather than a physical table, it remains insulated from underlying schema changes as long as the APPS synonym continues to point at the TCA base table.

Key Columns

  • CUST_ACCOUNT_ID — Primary customer account identifier for one side of the relationship. Joins to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.
  • RELATED_CUST_ACCOUNT_ID — The counterpart customer account in the relationship, providing the second half of the association.
  • RELATIONSHIP_TYPE — Classifies the nature of the linkage between the two accounts (for example, bill-to/ship-to associations defined in TCA relationship lookups).
  • BILL_TO_FLAG — Indicates whether the related account may be used as a bill-to destination.
  • SHIP_TO_FLAG — Indicates whether the related account may be used as a ship-to destination.
  • ORG_ID — Operating unit / multi-org identifier, enabling the view to be filtered in a multi-organization context.

The STATUS column from the base table is not exposed; only rows with STATUS = 'A' are returned, so the view reflects currently active relationships.

Common Use Cases and Queries

The most typical use is resolving the related accounts for a given customer account, or determining valid bill-to/ship-to accounts within a sales order or quote flow. A representative query follows:

  • SELECT cust_account_id, related_cust_account_id, relationship_type, bill_to_flag, ship_to_flag FROM aso_pvt_acct_relate_v WHERE cust_account_id = :p_account_id AND org_id = :p_org_id;
  • SELECT related_cust_account_id FROM aso_pvt_acct_relate_v WHERE cust_account_id = :p_account_id AND ship_to_flag = 'Y';
  • SELECT r.cust_account_id, r.related_cust_account_id, a.account_number FROM aso_pvt_acct_relate_v r, hz_cust_accounts a WHERE r.related_cust_account_id = a.cust_account_id AND r.bill_to_flag = 'Y';

Because the view already restricts STATUS to 'A', custom code does not need to add that predicate, though callers should still supply ORG_ID and account filters for performance. The view is read-only in practice; base data must be maintained through the supported TCA account relationship APIs rather than direct DML.