Search Results tpartner_pk




Overview
Explore in AI Chat

Overview

EDW_TPRT_P2_TPARTNER_LTC_IV is a reporting view in the Oracle E-Business Suite environment, catalogued under the BIS (Business Intelligence System) product family. It is part of the Enterprise Data Warehouse (EDW) staging and presentation layer used to expose Oracle Procurement and Payables trading partner data for downstream analytics, extracts, and integration routines. The suffix conventions (TPRT_P2, LTC, IV) indicate a Phase 2 trading partner entity, sourced from a legacy trading community (LTC) structure, surfaced as an interface view.

Per the ETRM metadata, the object is documented as not implemented in this database. This designation is significant: the view definition exists in the data dictionary and documentation set, but the physical object may be absent or dormant in a given instance depending on the deployment of the BIS/EDW components. Practitioners searching on inspect_required typically encounter this view while tracing supplier inspection attributes that flow from trading partner setup into warehouse-driven receiving and quality workflows.

The view is read-only in nature and carries an Oracle Proprietary, Confidential classification. It should be treated as a technical integration surface rather than an end-user reporting object.

Underlying Base Objects

The view is defined over a single documented base object: EDW_TPRT_P2_TPARTNER_LTC. The metadata lists no additional referenced base objects. The view text is a straightforward projection with aliasing — it selects the full column list from the base table and appends a literal empty string as OPERATION_CODE, plus a ROWID alias ROW_ID. This pattern is characteristic of interface views (the _IV suffix) consumed by EDW extraction jobs, where the constant OPERATION_CODE column signals downstream merge logic that the row is an insert/update candidate.

Because the view exposes ROW_ID derived from the underlying physical row identifier, it is not suitable for persisted references across database reorganizations or table moves. Join relationships to standard EBS supplier tables (for example AP_SUPPLIERS or PO_VENDORS) are not documented in the ETRM metadata and would need to be confirmed against the local implementation.

Key Columns

Common Use Cases and Queries

The principal use cases are supplier master extracts, receiving policy audits, and quality/inspection analysis. A typical query to isolate partners requiring inspection is:

  • SELECT TPARTNER_PK, NAME, VENDOR_NUMBER, INSPECT_REQUIRED, RECEIPT_REQUIRED, HOLD_FLAG FROM EDW_TPRT_P2_TPARTNER_LTC_IV WHERE INSPECT_REQUIRED = 'Y';
  • SELECT VENDOR_NUMBER, NAME, START_ACTIVE_DATE, END_ACTIVE_DATE FROM EDW_TPRT_P2_TPARTNER_LTC_IV WHERE SYSDATE BETWEEN START_ACTIVE_DATE AND NVL(END_ACTIVE_DATE, SYSDATE + 1);
  • SELECT INSTANCE, OPERATION_CODE, COUNT(*) FROM EDW_TPRT_P2_TPARTNER_LTC_IV GROUP BY INSTANCE, OPERATION_CODE;

Before relying on the view, confirm its installation status, since the ETRM metadata records it as not implemented in the referenced database. Where the view is unavailable, query the base object EDW_TPRT_P2_TPARTNER_LTC directly, noting the absence of the synthesized ROW_ID and OPERATION_CODE columns.