Search Results vndr_number




Overview
Explore in AI Chat

Overview

EDW_TPRT_TRADE_PARTNER_LTC_IV is a reporting view within the Oracle EBS BIS (Business Intelligence System) module, oriented toward the Enterprise Data Warehouse (EDW) layer that consolidates trade partner — customer and supplier — reference data. The suffix "IV" denotes an interface or integration view, and "LTC" indicates that the underlying dataset conforms to a load-to-collection or "where-used" staging pattern typical of EDW extraction snapshots. The view presents a denormalized projection of trade partner attributes drawn from a single base object, EDW_TPRT_TRADE_PARTNER_LTC.

Functionally, the view mirrors its base object's column list while adding a synthetic ROW_ID (inherited from the base object's row identifier) and a hard-coded literal column, OPERATION_CODE (populated as a single space), which is a common convention used by downstream EDW change-capture interfaces to reserve a slot for insert/update/delete signalling. Because the object is documented by ETRM as "Not implemented in this database," it exists as reference metadata rather than an active schema object in the certified 12.2.2 environment, though deployments of 12.1.1 with BIS/EDW extracts may instantiate the same shape.

For users who search on vndr_number, the view is directly relevant: VNDR_NUMBER is a first-class column, allowing supplier-number-based lookups across the entire trade partner population without joining to PO_VENDORS or AP_SUPPLIERS.

Underlying Base Objects

ETRM documents no referenced base objects for this view, and the "Implementation/DBA Data" section states that it is not implemented in the database. The view text, however, is explicit: it selects from EDW_TPRT_TRADE_PARTNER_LTC, retaining the base table's ROWID as ROW_ID and projecting all remaining columns verbatim, with the sole addition of a literal space aliased as OPERATION_CODE.

The singular dependency means the view is a thin wrapper rather than an aggregation or join. Performance and cardinality therefore equal those of EDW_TPRT_TRADE_PARTNER_LTC, and no key-preserved complexity is introduced beyond the row identifier. Because EDW tables are typically populated by concurrent-program extracts from operational EBS tables (AP, AR, PO, and their trading-partner master records), the view inherits a periodically refreshed snapshot characteristic rather than real-time transactional fidelity.

Key Columns

Columns fall into three groups: identifiers, customer attributes (CUST_*), and supplier attributes (VNDR_*).

Common Use Cases and Queries

The principal use case is resolving a vendor number to its consolidated trade partner record for EDW loads, cross-reference builds, or data-quality reconciliation. Typical patterns include:

  • Retrieving supplier classification and control flags by vendor number for procurement dashboards.
  • Reconciling the EDW trade partner snapshot against AP_SUPPLIERS/PO_VENDORS for master-data governance.
  • Populating a dimensional key map using TRADE_PARTNER_PK and PARENT_TPARTNER_KEY.

Sample statements:

SELECT vndr_number, name, vndr_type, vndr_hold_flag, cust_status FROM EDW_TPRT_TRADE_PARTNER_LTC_IV WHERE vndr_number = :p_vendor_number;

SELECT trade_partner_pk, name, alternate_name, taxpayer_id, start_active_date, end_active_date FROM EDW_TPRT_TRADE_PARTNER_LTC_IV WHERE last_update_date >= :p_since_date ORDER BY last_update_date;

SELECT vndr_number, vndr_minority_grp, vndr_small_bus, vndr_women_owned FROM EDW_TPRT_TRADE_PARTNER_LTC_IV WHERE vndr_number IS NOT NULL AND UPPER(name) LIKE UPPER('%' || :p_name || '%');

Because the view is not implemented in the certified 12.2.2 database, queries should be validated against the target environment or redirected to EDW_TPRT_TRADE_PARTNER_LTC where the interface view is absent.