Search Results inspect_required




Overview
Explore in AI Chat

Overview

The view EDW_TPRT_P4_TPARTNER_LCV is a reporting and extract layer object delivered within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, associated with the PO – Purchasing product family. Its name follows Oracle's Enterprise Data Warehouse (EDW) naming conventions, where the _LCV suffix denotes a "Load Column View" – a flattened, denormalized projection intended to feed downstream data warehouse staging, extract-transform-load (ETL) routines, or operational reporting extracts.

The view presents trading partner (supplier/vendor) attributes in a form suited to bulk extraction. It is important to note that the ETRM documentation states this object is "Not implemented in this database" in the reference environment, meaning the view definition is documented but may not be deployed in every instance. The object exposes columns that surface the VENDOR_NUMBER attribute the user searched for, placing it among the standard supplier-identification reporting objects. The view is proprietary to Oracle and carries confidentiality markings.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single dependent object, EDWBV_TPRT_P4_TPARTNER_LCV, as shown in its view text:

  • EDWBV_TPRT_P4_TPARTNER_LCV – the sole documented base object. The EDWBV prefix indicates an EDW "base view," confirming this LCV is a further projection layered atop an EDW base object rather than directly over EBS transactional tables such as PO_VENDORS or PO_VENDOR_SITES_ALL.

The ETRM metadata records "Referenced base objects: none documented" at the physical level, so the underlying lineage to AP/PO supplier tables is not enumerated in the supplied documentation. The columns exposed (including TPARTNER_PK, VENDOR_ID, and VENDOR_NUMBER) strongly imply a lineage traceable to supplier master and trading-partner data, but the documented dependency is limited to the EDW base view.

Key Columns

The view exposes thirty-plus columns. The most significant include:

Common Use Cases and Queries

Typical uses include supplier master extracts, vendor-number reconciliation between EBS and external systems, purchasing analytics on diversity classifications, and EDW staging loads. A representative query retrieving vendor numbers and key attributes is:

  • SELECT VENDOR_NUMBER, VENDOR_ID, NAME, VENDOR_TYPE, PAYMENT_TERMS, HOLD_FLAG FROM EDW_TPRT_P4_TPARTNER_LCV WHERE VENDOR_NUMBER = :p_vendor_number;
  • SELECT VENDOR_NUMBER, NAME, START_ACTIVE_DATE, END_ACTIVE_DATE FROM EDW_TPRT_P4_TPARTNER_LCV WHERE SYSDATE BETWEEN START_ACTIVE_DATE AND END_ACTIVE_DATE;
  • SELECT VENDOR_NUMBER, MINORITY_GROUP, WOMEN_OWNED, SMALL_BUSINESS FROM EDW_TPRT_P4_TPARTNER_LCV WHERE SMALL_BUSINESS = 'Y';

Because the object is documented as not implemented in the reference database, administrators should verify availability via ALL_VIEWS before relying on it in production extracts.