Results for “cust_account”

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

Overview

APPS.AST_ACCOUNT_PARTIES_V is a reporting and integration view in the Oracle E-Business Suite 12.1.1 / 12.2.2 data model that joins customer account records to their owning party records within the Oracle Trading Community Architecture (TCA) schema. The view exposes a single row per customer account, combining the account-level identifier from HZ_CUST_ACCOUNTS with the party identity attributes from HZ_PARTIES through the shared PARTY_ID foreign key. Because it is owned by APPS, it is accessible to any application user granted SELECT privileges on the APPS schema objects and is intended for read-only querying rather than transactional DML.

The view is particularly relevant where consumers require the "cust_account" context — that is, the ability to resolve a customer account to the human or organizational party that owns it, together with core descriptive attributes such as party name, party type, and person name components. In practice it serves reporting, extract, and integration requirements that need account-to-party resolution without navigating the full TCA model directly.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS through synonyms:

• HZ_CUST_ACCOUNTS (SYNONYM) — aliased as CUST_ACCOUNT in the view definition. This is the primary customer account table in TCA, holding the CUST_ACCOUNT_ID surrogate key and the PARTY_ID foreign key that links each account to its owner.
• HZ_PARTIES (SYNONYM) — aliased as PARTY. This is the central TCA party registry holding organization and person records, including PARTY_NAME and PARTY_TYPE.

The two objects are joined by the equality condition CUST_ACCOUNT.PARTY_ID = PARTY.PARTY_ID. Because the relationship is enforced through this join and each customer account references exactly one party, the view effectively returns one row per customer account. The inclusion of CUST_ACCOUNT.ROWID allows the view to be used in contexts that require a row identifier, subject to the usual restrictions on ROWID-based updates against joined views.

Key Columns

• ROWID — the row identifier from HZ_CUST_ACCOUNTS, inherited from the CUST_ACCOUNT table.
• CUST_ACCOUNT_ID — the unique surrogate key of the customer account, the primary join key for downstream account-level joins.
• PARTY_ID — the TCA party identifier shared between account and party records.
• PARTY_NAME — the display name of the party, typically the organization name or person full name.
• PARTY_TYPE — the party classification, distinguishing organization from person records.
• PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME — the decomposed name attributes used when the party is a person; these are null for organization parties.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns sourced from HZ_CUST_ACCOUNTS, used for change tracking and data lineage.

Common Use Cases and Queries

A typical requirement is to resolve customer account numbers to party names for reporting extracts. The following query lists accounts alongside their owning party:

SELECT cust_account_id, party_id, party_name, party_type
FROM   apps.ast_account_parties_v
WHERE  cust_account_id = :p_account_id;

For person-party analysis, the name components are selected directly:

SELECT cust_account_id, party_name,
       person_first_name, person_last_name
FROM   apps.ast_account_parties_v
WHERE  party_type = 'PERSON';

Because the view carries ROWID and audit columns, it is also useful for incremental synchronization jobs that stage customer account and party changes into external systems, filtering on LAST_UPDATE_DATE to capture only modified rows. It should be noted that the view is read-only in intent; DML against a multi-table join of this kind is not supported, and all maintenance must occur against the underlying HZ_CUST_ACCOUNTS and HZ_PARTIES tables.