Results for “cust_site_use”

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

Overview

EDW_TPRT_TPARTNER_LOC_LCV is a reporting and interface view exposed within the Oracle E-Business Suite trading community data model, catalogued under the Purchasing (PO) product group. The name follows Oracle's enterprise data warehouse (EDW) naming convention: the _LCV suffix denotes a "logical current view," a denormalized projection intended primarily for extract, reporting, and integration consumption rather than for transactional data entry. The view presents trade partner location information — the addresses, site usages, and trading attributes belonging to suppliers, customers, and other trading partners — merged into a single flat structure.

Its central purpose is to reconcile the trading partner's vendor-side and customer-side location attributes into one row per trade partner location, identified by TPARTNER_LOC_PK and TPARTNER_LOC_ID. Because the ETRM schema has historically treated supplier sites (PO/AP) and customer sites (AR/Order Management) as related but separately modeled entities, this view provides a consolidated perspective suitable for master data hubs, data warehouse staging, and cross-module reporting.

Underlying Base Objects

The view text documented in the ETRM 12.2.2 metadata defines it as a direct projection over a single base object, EDWBV_TPRT_TPARTNER_LOC_LCV, with no joins, unions, or aggregation visible in the definition. All column references map one-to-one to the underlying object, and the metadata records no additional referenced base objects. This is characteristic of the EDW staging layer, where a "BV" (base view) object provides the physical extract and the LCV layer exposes it through a stable, published column contract.

The view is documented as "Not implemented in this database" in the source metadata, meaning it exists in the ETRM reference model as a defined object but may not be physically installed in every environment. Consumers should verify existence against ALL_VIEWS before relying on it in a query or concurrent program.

Key Columns

• TPARTNER_LOC_PK / TPARTNER_LOC_ID — Primary and alternate identifiers for the trade partner location record.
• TRADE_PARTNER_FK — Foreign key to the parent trade partner (supplier or customer party).
• ADDRESS_LINE1–4, CITY, COUNTY, STATE, POSTAL_CODE, PROVINCE, COUNTRY — The location's postal address components.
• NAME — The location or site name.
• BUSINESS_TYPE, TPARTNER_LOC_DP, DATE_FROM, DATE_TO — Classification, descriptive flexfield reference, and effective dating for the location.
• VNDR_PURCH_SITE, VNDR_RFQ_ONLY, VNDR_PAY_SITE, VNDR_PAY_TERMS — Supplier-side site usage flags and payment terms.
• CUST_SITE_USE, CUST_LOCATION, CUST_PRIMARY_FLAG, CUST_STATUS — Customer-side site usage and status attributes.
• CUST_TERRITORY — The customer territory assignment, the column most directly relevant to searches for cust_territory; it carries the territory code used for sales and receivables territory-based processing.
• CUST_PAY_TERMS, CUST_PRICE_LIST, CUST_ORDER_TYPE, CUST_FREIGHT, CUST_SHIP_VIA, CUST_FOB_POINT — Order management and pricing defaulting attributes for the customer site.
• CUST_TAX_REF, CUST_TAX_CODE, CUST_TAX_CLASSFN, CUST_TAX_HDR_FLAG, CUST_TAX_ROUND — Tax determination and rounding attributes.
• CUST_SALES_REP, CUST_SORT_PRTY, CUST_DEMAND_CLASS, CUST_GSA_IND, CUST_SIC_CODE, CUST_ORIG_SYS_REF, CUST_SHIP_PARTIAL — Additional customer site attributes.
• INSTANCE, LAST_UPDATE_DATE, CREATION_DATE, OPERATION_CODE, LEVEL_NAME — Multi-org instance, audit, and migration/operation control columns.
• USER_ATTRIBUTE1–5 — Hardcoded as NULL in the view definition, reserved placeholders.

Common Use Cases and Queries

The most frequent use of this view is territory-oriented analysis: identifying which customer sites are assigned to a given sales territory, or reporting sites that lack a territory assignment. A representative query follows.

• Territory reporting: SELECT TPARTNER_LOC_ID, NAME, CITY, COUNTRY, CUST_TERRITORY, CUST_SALES_REP FROM EDW_TPRT_TPARTNER_LOC_LCV WHERE CUST_TERRITORY = :p_territory;
• Missing territory check: SELECT TPARTNER_LOC_ID, NAME, CUST_STATUS FROM EDW_TPRT_TPARTNER_LOC_LCV WHERE CUST_TERRITORY IS NULL AND CUST_SITE_USE IS NOT NULL;
• Consolidated partner extract: select address, business type, and the vendor and customer usage flags for loading into an external master data repository.
• Data warehouse staging: use the CUST_TERRITORY and CUST_SALES_REP columns to join to territory and salesperson dimensions.

Because the view is a thin projection over EDWBV_TPRT_TPARTNER_LOC_LCV, all filtering and aggregation logic must be supplied by the calling query. Environments where the object is not implemented will return an ORA-00942 error, so existence should be validated prior to deployment.