Search Results ece_tp_location_code

Overview

JTF_CUST_ACCT_SITES_V is a CRM Foundation (JTF) view owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes customer account site information maintained within the Oracle Trading Community Architecture (TCA) model, retrieving information about customer sites where one customer account can have multiple associated sites. As a view rather than a base table, it provides a stable, read-oriented access layer over the underlying TCA entity, allowing forms, concurrent programs, reports, and integration interfaces to query account site data without direct dependency on the physical table definition.

The view is widely referenced across CRM, Order Management, Receivables, and Service modules, since customer account sites represent the address-level relationships between a party and a customer account, including bill-to, ship-to, and market usage designations. Its presence in the JTF layer is significant because CRM Foundation historically supplied generic "party" and "account" views that predate or abstract the richer HZ (TCA) schema introduced later in the EBS architecture.

Underlying Base Objects

Per the documented ETRM metadata, JTF_CUST_ACCT_SITES_V is defined directly over HZ_CUST_ACCT_SITES_ALL, referenced via a synonym. The view text is a straightforward projection: it selects ROWID as ROW_ID alongside the full column list of the base table, and applies no filter, join, or aggregation. Consequently, the row count and row identity of the view mirror the base table exactly.

Because the view resolves to a synonym pointing at HZ_CUST_ACCT_SITES_ALL, it returns records across all operating units unless the consuming query adds an ORG_ID predicate. This matters in multi-org environments, where the "_ALL" suffix denotes a table whose rows are partitioned by operating unit through ORG_ID.

Key Columns

The view surfaces the complete attribute set of the base entity. The most functionally significant columns include:

• CUST_ACCT_SITE_ID — Primary key identifying the customer account site record.
• CUST_ACCOUNT_ID — Foreign key to the customer account, establishing the one-account-to-many-sites relationship.
• PARTY_SITE_ID — Reference to the underlying party site in the TCA party model, linking the account-specific usage to the physical location.
• ORG_ID — Operating unit identifier controlling multi-org visibility.
• STATUS — Active/inactive indicator for the site assignment.
• BILL_TO_FLAG, SHIP_TO_FLAG, MARKET_FLAG — Usage flags denoting whether the site functions as a billing, shipping, or marketing address.
• KEY_ACCOUNT_FLAG — Designates the site as a key account location.
• CUSTOMER_CATEGORY_CODE and LANGUAGE — Classification and linguistic attributes of the site.
• SERVICE_TERRITORY_ID, PRIMARY_SPECIALIST_ID, SECONDARY_SPECIALIST_ID, TERRITORY_ID — Territory and resource assignment columns supporting CRM service coverage.
• ADDRESS_TEXT — Denormalized address representation for display and reporting.
• ATTRIBUTE1–20 and GLOBAL_ATTRIBUTE1–20 — Flexfield extension columns, with ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE_CATEGORY providing context.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus concurrent request audit columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical consumption patterns include listing all sites for a customer account, filtering by usage flag, and restricting by operating unit. The following query returns active ship-to sites for a given account within a specific operating unit:

• SELECT cust_acct_site_id, party_site_id, address_text, ship_to_flag FROM jtf_cust_acct_sites_v WHERE cust_account_id = :p_account_id AND ship_to_flag = 'Y' AND status = 'A' AND org_id = :p_org_id;

Because the view performs no filtering, every query should apply STATUS, ORG_ID, and appropriate site-usage predicates explicitly. For address-level detail, join PARTY_SITE_ID to HZ_PARTY_SITES to obtain structured location attributes rather than relying solely on ADDRESS_TEXT. In integration scenarios, the view serves as a convenient, stable source for extracting account-site relationships into external CRM or middleware systems without querying the HZ table directly.