Search Results cust_sales_rep




Overview

The view EDW_TPRT_TPARTNER_LOC_LTC_IV is a reporting and integration object belonging to the Oracle E-Business Suite BI (Business Intelligence) product family, catalogued under the BIS (Business Intelligence System) application module. Its name follows the Enterprise Data Warehouse (EDW) naming convention used for the ETRM (Enterprise Territory and Resource Management) reference model, where the _IV suffix denotes an "interface view." The view exposes trade partner and trade partner location attributes in a flattened, denormalized form intended for downstream consumption by reporting layers, extraction routines, and data warehouse staging processes.

The metadata records this object as "Not implemented in this database," indicating it is a documented reference definition rather than an active object in the sampled ETRM 12.2.2 environment. The view is documented for Oracle EBS 12.1.1 and 12.2.2.

The view surfaces customer- and supplier-facing attributes — SIC codes, ship-via and ship-partial flags, price lists, payment terms, tax configuration, territory, FOB point, and freight terms — consolidated at the trade partner location grain.

Underlying Base Objects

The view is defined over a single referenced source object: EDW_TPRT_TPARTNER_LOC_LTC. This source is a "LTC" (likely a load/transformation control or logical table construct) object in the EDW layer, and the _IV view applies a lightweight projection over it — selecting the full column set and appending an OPERATION_CODE literal set to a single space (' ' OPERATION_CODE). This pattern is characteristic of interface views that normalize the shape of a record for a downstream extractor that expects an operation-code column, even where no meaningful change operation exists.

The metadata lists no additional referenced base objects beyond this source, so any relationship to Oracle EBS base tables such as HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, or PO_VENDORS is indirect through the ETRM/EDW transformation chain rather than declared on the view itself.

Key Columns

  • TRADE_PARTNER_KEY / TRADE_PARTNER / TPARTNER_LOC_PK_KEY / TPARTNER_LOC_PK — surrogate and natural keys identifying the trade partner and its location; the core grain of the view.
  • BUSINESS_TYPE — distinguishes customer versus supplier (vendor) context for the partner.
  • NAME / LEVEL_NAME — descriptive partner name and the hierarchy level at which the record is recorded.
  • DATE_FROM / DATE_TO — effective-dating window for the location record.
  • CUST_* columns — customer attributes including SIC code, ship-via, ship-partial, primary flag, price list, payment terms, order type, territory, tax codes and classification, status, site use, demand class, FOB point, freight, and GSA indicator.
  • VNDR_* columns — supplier attributes: RFQ-only flag, purchasing site, payment terms, and payment site.
  • USER_ATTRIBUTE1–5 — DFF descriptor flexfields carried through for extensibility.
  • LAST_UPDATE_DATE / CREATION_DATE / INSTANCE — audit and source-instance tracking columns supporting incremental loads.
  • OPERATION_CODE — constant blank value enabling uniform interface consumption.

Common Use Cases and Queries

This view supports trade partner master data extraction for territory and resource alignment, customer and supplier analytics, and EDW staging. A representative query retrieving active customer locations is shown below.

SELECT TRADE_PARTNER,
       NAME,
       BUSINESS_UNIT_DP,
       CUST_TERRITORY,
       CUST_PAY_TERMS,
       DATE_FROM,
       DATE_TO
  FROM EDW_TPRT_TPARTNER_LOC_LTC_IV
 WHERE BUSINESS_TYPE = 'CUSTOMER'
   AND TRUNC(SYSDATE) BETWEEN DATE_FROM AND NVL(DATE_TO, SYSDATE);

A typical incremental extract uses the audit columns:

SELECT *
  FROM EDW_TPRT_TPARTNER_LOC_LTC_IV
 WHERE LAST_UPDATE_DATE >= :p_last_run_date;

Because the view is documented as not implemented in the surveyed database, DBAs should verify its existence and definition against the actual ETRM patch level before relying on it in production.