Search Results prim_specialist

Overview

XNC_CUST_ACCT_SITES_V is a reporting view shipped under the XNC – Sales for Communications product family. The XNC module was Oracle's vertical solution for telecommunications and communications service providers, and in Oracle EBS 12.1.1 and 12.2.2 it is documented as obsolete, meaning Oracle no longer enhances the product line and customers are expected to migrate functionality to standard Oracle Trade Management, Order Management, and Receivables objects. The view presents the physical sites or locations associated with a customer account, enriched with address attributes and the names of the primary and secondary sales specialists assigned to each site. Its role in reporting and integration is to flatten the many-to-many relationships among customer accounts, party sites, addresses, and assigned personnel into a single denormalized result set suitable for direct querying, BI Publisher data templates, and inbound or outbound interface staging.

Underlying Base Objects

The documented ETRM metadata records no owning schema and no formally documented base objects, and states explicitly that the view is not implemented in the reference database. The view text nonetheless reveals its lineage: it selects from JTF_CUST_ACCT_SITES_V (aliased ACCT_SITES), JTF_HZ_PARTY_LOCATIONS_V (aliased LOCATIONS), and two independent references to PER_PEOPLE (aliased PRIM_SPECIALIST and SECOND_SPECIALIST). JTF_CUST_ACCT_SITES_V is the JTF layer view over the TCA customer account site entity (HZ_CUST_ACCT_SITES_ALL); JTF_HZ_PARTY_LOCATIONS_V exposes party site and location data from the TCA party model (HZ_PARTY_SITES and HZ_LOCATIONS). The joins are driven by PARTY_SITE_ID, matching the account-site view to the locations view, while the two PER_PEOPLE joins are outer joins on the specialist ID columns, so sites without an assigned specialist are still returned with null names.

Key Columns

• CUST_ACCT_SITE_ID / CUST_ACCOUNT_ID / PARTY_SITE_ID — the site, account, and party site identifiers that key the record across TCA and JTF.
• ORG_ID — the operating unit context, essential for multi-org reporting and security.
• STATUS, BILL_TO_FLAG, MARKET_FLAG, SHIP_TO_FLAG — site usage and status indicators describing the business purpose of the location.
• SERVICE_TERRITORY_ID / TERRITORY_ID — territory assignments used in communications-industry coverage and sales routing.
• PRIMARY_SPECIALIST_ID / SECONDARY_SPECIALIST_ID — foreign keys to PER_PEOPLE identifying the assigned sales specialists; the names are resolved as PRIMARY_SPECIALIST_NAME and SECONDARY_SPECIALIST_NAME.
• ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTRY — the formatted address elements sourced from the party location view.
• LAST_UPDATE_DATE — the incremental-extraction watermark for delta processing.

Common Use Cases and Queries

The view is typically used for customer site listings, specialist coverage reports, and address extraction feeds. A site roster for a given account can be produced as follows:

SELECT cust_account_id, cust_acct_site_id, address1, city, state, postal_code, country, bill_to_flag, ship_to_flag, status FROM xnc_cust_acct_sites_v WHERE cust_account_id = :p_account_id AND org_id = :p_org_id ORDER BY cust_acct_site_id;

A coverage report joining specialist assignments back to PER_PEOPLE confirms the personnel behind each role:

SELECT s.cust_acct_site_id, s.primary_specialist_name, s.secondary_specialist_name, p.email_address FROM xnc_cust_acct_sites_v s, per_people p WHERE s.primary_specialist_id = p.person_id(+) AND s.org_id = :p_org_id;

For incremental interfaces, extraction is filtered on the watermark: WHERE last_update_date >= :p_since_date. Because the view is obsolete and absent from the reference database in later releases, implementations should validate its existence in the target instance and plan migration to supported TCA and Trade Management views such as HZ_CUST_ACCT_SITES_ALL and its standard JTF derivatives.