Search Results xnc_acct_relationship_v

Overview

XNC_ACCT_RELATIONSHIP_V is a reporting view belonging to the XNC – Sales for Communications product family, which Oracle designates as obsolete in Release 12.1.1 and 12.2.2. The view presents relationship records that link a customer account to one or more related customer accounts, resolving descriptive attributes such as the related account name, number, status code, and the translated status description. In the ETRM 12.2.2 documentation the view is flagged as "Not implemented in this database," indicating that the underlying object set is not deployed in a standard installation and the view should be treated as a legacy artifact rather than an active data source. Where present, its role is analytical and integration-oriented: it supplies a denormalized, human-readable projection of account-to-account relationships suitable for reporting layers, extracts, and communication-industry data models that require reciprocal or hierarchical account structures. The searched term "account_status_description" corresponds directly to the ACCOUNT_STATUS_DESCRIPTION column, which is the descriptive lookup value for the related account's status.

Underlying Base Objects

The documented ETRM metadata records no referenced base objects for this view; the definition is exposed only through the view text. That text shows the view is built over three sources:

• JTF_HZ_CUST_ACCT_RELATE_V (alias ACCT_RELATE) — the relationship view supplying CUST_ACCOUNT_ID, RELATED_CUST_ACCOUNT_ID, RELATIONSHIP_TYPE, CUSTOMER_RECIPROCAL_FLAG, and STATUS.
• JTF_CUST_ACCOUNTS_V (alias CUST_ACCT) — the customer account view supplying ACCOUNT_NAME and ACCOUNT_NUMBER for the related account.
• AR_LOOKUPS (alias STATUS_LOOKUP) — the Oracle Receivables lookup table supplying DESCRIPTION, constrained to LOOKUP_TYPE = 'CODE_STATUS'.

Joins are equi-joins on RELATED_CUST_ACCOUNT_ID = CUST_ACCOUNT_ID and on STATUS = LOOKUP_CODE. Because two of the three sources are themselves views (the JTF_HZ_* and JTF_CUST_* family), the object inherits the security and party-model behavior of the Trading Community Architecture layer. No direct base tables are documented, so dependency tracing must resolve through those intermediate views.

Key Columns

• ROW_ID — the row identifier projected from ACCT_RELATE.
• CUST_ACCOUNT_ID — the primary customer account in the relationship.
• RELATED_CUST_ACCOUNT_ID — the associated account on the other side of the relationship.
• RELATED_ACCOUNT_NAME / RELATED_ACCOUNT_NUMBER — descriptive identifiers of the related account, sourced from JTF_CUST_ACCOUNTS_V.
• LAST_UPDATE_DATE — the last modification timestamp of the relationship record.
• RELATIONSHIP_TYPE — classification of the linkage between the two accounts.
• CUSTOMER_RECIPROCAL_FLAG — indicates whether the relationship is reciprocal.
• RELATED_ACCOUNT_STATUS — the stored status code of the related account.
• ACCOUNT_STATUS_DESCRIPTION — the decoded status description obtained from AR_LOOKUPS for LOOKUP_TYPE 'CODE_STATUS'.

Common Use Cases and Queries

Typical usage centers on reporting account hierarchies and filtering related accounts by status. A representative query lists all related accounts for a given primary account together with their status descriptions:

• SELECT cust_account_id, related_cust_account_id, related_account_name, related_account_number, account_status_description FROM xnc_acct_relationship_v WHERE cust_account_id = :p_account_id;
• SELECT related_account_number, relationship_type, account_status_description FROM xnc_acct_relationship_v WHERE account_status_description = 'Active';
• SELECT cust_account_id, related_cust_account_id FROM xnc_acct_relationship_v WHERE customer_reciprocal_flag = 'Y' AND related_account_status = :p_status;

Because the view is obsolete and documented as not implemented, these statements should be validated against the target instance before reliance, and equivalent functionality should be sought in supported TCA relationship views in current releases.