Search Results competitor_flag
Overview
XNC_CUST_ACCT_OVERVIEW_V is a reporting view historically shipped with the Oracle Sales for Communications (XNC) product family, a vertical solution that was ultimately classified as obsolete in Oracle E-Business Suite. The view consolidates customer account attributes from multiple Oracle Receivables, Oracle Trade Management, and party-model sources into a single denormalized projection, allowing downstream XNC forms, concurrent programs, and integration interfaces to retrieve a wide snapshot of account information without joining several base entities individually. Its documentation describes it simply as retrieving "an overview of the customer account," which reflects its design intent as a convenience layer over the customer master rather than as a transactional or updateable object.
In EBS 12.1.1 and 12.2.2, the view is not implemented in the standard database, meaning it exists only where the XNC module was deployed. In the 12.2.2 documented metadata, no owner and no referenced base objects are recorded, underscoring its obsolete status. Consumers migrating off XNC should not depend on its presence.
Underlying Base Objects
Although the 12.2.2 metadata lists no referenced base objects, the view text identifies its actual sources directly:
- JTF_CUST_ACCOUNTS_V CUST_ACCT — the primary customer account view, supplying account identifiers, status, customer type, class, priority indicator, balances, and establishment/termination dates.
- ASO_I_SALES_CHANNELS_V SALES_CHANNEL — an outer-joined source for sales channel code, name, and description.
- RA_SALESREPS SALES_REP — an outer-joined source for the primary sales representative name.
- ASO_I_PARTIES_V PARTIES — supplies the party name and is inner-joined on PARTY_ID.
- AR_LOOKUPS STATUS_LOOKUP — constrained to LOOKUP_TYPE = 'CODE_STATUS', translating the account status code into a description.
The join structure uses Oracle outer-join syntax (+), consistent with pre-ANSI conventions retained in EBS 12.x objects.
Key Columns
The view exposes a broad column set. Identifiers include CUST_ACCOUNT_ID, ORG_ID, PARTY_ID, and ACCOUNT_NUMBER. Descriptive fields include PARTY_NAME, ACCOUNT_NAME, ACCOUNT_STATUS_DESCRIPTION, SALES_CHANNEL_NAME, and PRIMARY_SALESREP_NAME. Derived business attributes include ACCOUNT_PRIORITY, computed via DECODE over HIGH_PRIORITY_INDICATOR into HIGH, LOW, or NOT SPECIFIED.
Notably, the columns most relevant to the search term third_party_flag — THIRD_PARTY_FLAG, COMPETITOR_FLAG, and CATEGORY_CODE — are projected as literal NULLs. This is a critical fact: the view declares these columns for interface compatibility but never populates them from any base table. Any query filtering on THIRD_PARTY_FLAG returns no meaningful results.
Common Use Cases and Queries
Typical usage involves retrieving account overviews for communications-sector customers, including balances, priority, and status:
- Account status and priority reporting for high-priority subscribers.
- Sales channel and sales representative attribution analysis.
- Balance and write-off exposure summaries using CURRENT_BALANCE, WRITE_OFF_AMOUNT, and related columns.
Example query:
SELECT CUST_ACCOUNT_ID, ACCOUNT_NUMBER, PARTY_NAME, ACCOUNT_STATUS_DESCRIPTION, ACCOUNT_PRIORITY, CURRENT_BALANCE FROM XNC_CUST_ACCT_OVERVIEW_V WHERE ACCOUNT_PRIORITY = 'HIGH';
Because THIRD_PARTY_FLAG is hardcoded NULL, queries referencing it are effectively non-functional. In EBS 12.1.1 and 12.2.2 this view should be treated as legacy and replaced by direct queries against JTF_CUST_ACCOUNTS_V, HZ_CUST_ACCOUNTS, and related party-model objects.
-
View: XNC_CUST_ACCT_OVERVIEW_V
12.2.2
product: XNC - Sales for Communications (Obsolete) , description: XNC_CUST_ACCT_OVERVIEW_V retrieves an overview of the customer account. , implementation_dba_data: Not implemented in this database ,
-
View: XNC_CUST_ACCT_OVERVIEW_V
12.1.1
product: XNC - Sales for Communications (Obsolete) , description: XNC_CUST_ACCT_OVERVIEW_V retrieves an overview of the customer account. , implementation_dba_data: Not implemented in this database ,