Search Results tax_reg_num




Overview
Explore in AI Chat

Overview

EDW_TPRT_P2_TPARTNER_LCV is a reporting view owned by the APPS schema within the Oracle E-Business Suite, registered under the PO – Purchasing product family. In ETRM 12.2.2 the object is documented with a status of VALID and an object type of VIEW. The suffix convention "EDW" (Enterprise Data Warehouse) combined with the "_LCV" designation indicates that this object is a lightweight, curated layer intended to expose trading partner data in a shape suitable for downstream extraction, transformation, and load processing, rather than for direct transactional maintenance. The view presents a denormalized, reporting-friendly projection of supplier and trading partner attributes that span supplier master, purchasing, tax, and diversity classifications.

Its principal purpose is to supply a stable interface for analytics, data warehouse population, and integration programs that need partner-level attributes without joining the numerous normalized EBS base tables directly. By exposing a fixed set of columns, it insulates consumers from underlying schema changes in the Oracle Purchasing and Payables supplier model.

Underlying Base Objects

According to the documented metadata, the view is defined over a single object: EDWBV_TPRT_P2_TPARTNER_LCV. The view text is a straightforward SELECT list projection with no joins, filters, or aggregation, which confirms that all business logic, transformation, and any necessary joining reside in the referenced EDWBV object (a "base view" in the EDW naming convention).

The documentation lists no additional referenced base objects. This means the EBS tables that ultimately supply the rows — typically suppliers, supplier sites, and related classification structures — are resolved upstream within EDWBV_TPRT_P2_TPARTNER_LCV and are not visible in this layer's definition. Consumers should treat EDW_TPRT_P2_TPARTNER_LCV as a dependent, read-only presentation layer and should not assume that column-level derivations are performed here.

Key Columns

Common Use Cases and Queries

Typical use cases include supplier master extracts for a data warehouse, supplier diversity and spend reporting, and hierarchical roll-ups of spend from child partners to parent partners. The OPERATION_CODE column supports incremental change-data capture, while the effective date columns support historical snapshots.

A representative query retrieving child partners and their parent linkage:

  • SELECT tpartner_pk, parent_tpartner_fk, name, vendor_number, vendor_type, start_active_date, end_active_date FROM apps.edw_tprt_p2_tpartner_lcv WHERE parent_tpartner_fk IS NOT NULL;
  • SELECT parent_tpartner_fk, COUNT(*) child_count FROM apps.edw_tprt_p2_tpartner_lcv GROUP BY parent_tpartner_fk HAVING COUNT(*) > 1;
  • SELECT tpartner_pk, name, tax_reg_num, small_business, minority_group, women_owned FROM apps.edw_tprt_p2_tpartner_lcv WHERE TRUNC(SYSDATE) BETWEEN NVL(start_active_date, SYSDATE) AND NVL(end_active_date, SYSDATE) ORDER BY name;

Consumers should restrict access to read-only privileges and confirm that the upstream EDWBV object is valid in the target environment before relying on results.