Search Results tpartner_dp




Overview
Explore in AI Chat

Overview

APPS.EDW_TPRT_P2_TPARTNER_LCV is an Oracle E-Business Suite reporting view that belongs to the ETRM (Enterprise Trade and Relationship Management / Procurement) data warehouse layer. The object is defined through the ETRM 12.1.1 and 12.2.2 metadata repository and follows the APPS.EDW_* naming convention used by Oracle's E-Business Suite data extraction views, which are constructed for reporting and integration purposes rather than for transactional processing.

The view presents trading partner information as a logical, denormalized unit. It draws its rows from the underlying bridge view EDWBV_TPRT_P2_TPARTNER_LCV and projects a stable set of columns covering the trading partner primary key, hierarchy relationships (parent trading partner), lifecycle dates, identification attributes, supplier classification flags, and procurement control settings. Because the underlying object is externalized as a view rather than a base table, its role is to provide a consistent read-only interface that abstracts the physical implementation of the ETRM trading partner warehouse.

Underlying Base Objects

The view text is a straight projection: every column in APPS.EDW_TPRT_P2_TPARTNER_LCV is selected from EDWBV_TPRT_P2_TPARTNER_LCV with no joins, filters, or transformations applied at this level. The only construction that occurs is the addition of five NULL user_attribute columns (USER_ATTRIBUTE1 through USER_ATTRIBUTE5), which are declared as literal NULLs.

This pattern is common in the EDW reporting layer, where a "bridge view" (prefixed EDWBV) carries the real extraction logic and the published APPS.EDW_*_LCV view exposes a fixed column contract to downstream consumers. The "_LCV" suffix typically indicates a logical or canonical view used to standardize column names and ordering across the ETRM extraction. Note that the ETRM metadata excerpt does not enumerate any base tables as "referenced base objects," so the only documented dependency is EDWBV_TPRT_P2_TPARTNER_LCV, which in turn resolves against the ETRM trading partner source objects.

Key Columns

Common Use Cases and Queries

The view is typically used for supplier diversity and procurement analytics. Because the user searched for "small_business," the SMALL_BUSINESS column is the most relevant attribute for filtering and aggregation.

Example — list active small business partners:

  • SELECT tpartner_pk, name, vendor_number, vendor_type, small_business, minority_group, women_owned
  • FROM apps.edw_tprt_p2_tpartner_lcv
  • WHERE small_business = 'Y'
  •   AND TRUNC(SYSDATE) BETWEEN start_active_date AND NVL(end_active_date, TRUNC(SYSDATE));

Example — count small business suppliers by vendor type:

  • SELECT vendor_type, COUNT(DISTINCT tpartner_pk) partner_count
  • FROM apps.edw_tprt_p2_tpartner_lcv
  • WHERE small_business = 'Y'
  • GROUP BY vendor_type;

The view can also be joined to downstream procurement or spend tables via VENDOR_ID or TPARTNER_PK to attribute purchasing activity to small business suppliers, supporting FAR/DFAR-style diversity reporting and ETRM integration extracts.