Search Results parent_tpartner

Overview

The view EDW_TPRT_P4_TPARTNER_LTC_IV is a reporting and integration object within the Oracle E-Business Suite (EBS) environment, assigned to the BIS (Applications BIS) product family. Its name indicates a role within the Enterprise Data Warehouse / Trading Partner reporting layer, where the _IV suffix conventionally denotes an "interface view" — a database object intended to expose trading partner master data in a denormalised, read-only form for downstream consumption by reporting, ETL, and integration processes.

In the context of EBS 12.1.1 and 12.2.2, this view presents supplier/trading partner attributes (payment terms, tax registration, vendor classification, diversity indicators, and receipt controls) as a flat record set. The object is relevant to searches such as "BTB & MERCURY CORPORATION" because it exposes partner NAME and ALTERNATE_NAME columns that can be filtered to resolve specific trading partner entities. Per the documented ETRM metadata, the view is not implemented in this database, meaning the definition exists in the data model reference but the physical object is absent from the current instance. This is significant: any query referencing the view will raise ORA-00942 (table or view does not exist) unless the object is created.

Underlying Base Objects

The documented base object is EDW_TPRT_P4_TPARTNER_LTC. The view does not itself persist data; it is a pass-through projection over this single source, exposing the same column set in a defined order and appending a synthetic literal column. No other referenced base objects are documented in the ETRM metadata, and the owner attribute is blank — a common characteristic of EDW staging views that are deployed under a specific schema (typically an APPS or EDW reporting schema) after the source table is materialised.

The view text selects a fixed list of columns from the base table and appends the expression ' ' OPERATION_CODE, a single-space literal. In data warehouse interface views this construct is typically a placeholder to satisfy a fixed target column contract, allowing the view to conform to a canonical column layout expected by an extract program or downstream interface table, even though no meaningful operation code is sourced at this layer.

Key Columns

The view exposes thirty-four columns. The most functionally significant include:

• TPARTNER_PK / TPARTNER_PK_KEY / TPARTNER_DP — the primary key, a surrogate key reference, and a descriptive/display pointer for the trading partner record.
• NAME / ALTERNATE_NAME — the legal trading partner name and any secondary name, used for entity resolution queries such as locating "BTB & MERCURY CORPORATION".
• VENDOR_NUMBER / VENDOR_TYPE — the supplier number and classification used in payables and procurement joins.
• PAYMENT_TERMS / RECEIPT_REQUIRED / INSPECT_REQUIRED / ALLOW_SUB_RECEIPT / ALLOW_UNORDER_RCV — procurement and receiving control attributes.
• TAX_REG_NUM / TAXPAYER_ID — tax registration and identity fields used in tax reporting.
• START_ACTIVE_DATE / END_ACTIVE_DATE / HOLD_FLAG — effective-dating and status control.
• SMALL_BUSINESS / WOMEN_OWNED / MINORITY_GROUP — diversity and supplier-classification reporting attributes.
• SIC_CODE / ONE_TIME_FLAG / PARENT_TPARTNER / PARENT_TPARTNER_KEY — industry code, one-time supplier indicator, and parent-child hierarchy linkage.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — descriptive flexfield segments carried through for extensibility.
• INSTANCE / CREATION_DATE / LAST_UPDATE_DATE / ROW_ID — multi-org instance, audit, and row identifier columns.
• OPERATION_CODE — a synthetic single-space literal, not a stored source value.

Common Use Cases and Queries

Typical use cases are supplier master extracts, diversity-spend reporting, tax registration reconciliation, and trading partner name lookup. A representative query resolving a specific entity would take the form:

• SELECT TPARTNER_PK, NAME, ALTERNATE_NAME, VENDOR_NUMBER, PAYMENT_TERMS, TAX_REG_NUM FROM EDW_TPRT_P4_TPARTNER_LTC_IV WHERE UPPER(NAME) LIKE '%BTB%MERCURY%' OR UPPER(ALTERNATE_NAME) LIKE '%BTB%MERCURY%';
• SELECT VENDOR_TYPE, SMALL_BUSINESS, WOMEN_OWNED, MINORITY_GROUP, COUNT(*) FROM EDW_TPRT_P4_TPARTNER_LTC_IV GROUP BY VENDOR_TYPE, SMALL_BUSINESS, WOMEN_OWNED, MINORITY_GROUP;
• SELECT TPARTNER_PK, NAME, START_ACTIVE_DATE, END_ACTIVE_DATE, HOLD_FLAG FROM EDW_TPRT_P4_TPARTNER_LTC_IV WHERE HOLD_FLAG = 'Y';

Because the view is documented as not implemented, these queries require the object to be created first, and any dependent extraction job should be validated against the base table EDW_TPRT_P4_TPARTNER_LTC to confirm availability before the interface view is relied upon in production reporting.