Search Results trade_partner_dp




Overview
Explore in AI Chat

Overview

EDW_TPRT_TRADE_PARTNER_LCV is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema and registered under the PO - Purchasing product family. The suffix _LCV denotes a "Loadable Column View," a construct used throughout the Oracle Enterprise Data Warehouse (EDW) and Trading Community Architecture (TCA) reporting layers to expose a flattened, denormalized projection of a source object for extraction, integration, and analytical reporting. In this case, the view consolidates supplier (vendor) and customer attributes belonging to a single trade partner entity, providing a unified read model suitable for downstream ETL jobs, data marts, and BI Publisher or OBIEE report sources. Because the view is defined with column aliases and NULL placeholders rather than as a physical materialized object, it serves as a stable interface over the underlying TCA trade partner structure, insulating consumers from changes in the base schema.

Underlying Base Objects

The ETRM 12.2.2 metadata documents no explicit base tables for this view. In practice, the view text reveals that EDW_TPRT_TRADE_PARTNER_LCV is defined directly over another view, EDWBV_TPRT_TRADE_PARTNER_LCV (the "EDW Business View" layer), which in turn resolves to the TCA trade partner tables—principally HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and the supplier-facing AP_SUPPLIERS / PO_VENDORS structures. The view performs no joins of its own; it is a straight projection with column renaming and the substitution of NULL literals for USER_ATTRIBUTE1 through USER_ATTRIBUTE5. Object status is VALID, meaning the dependency chain is intact and the view compiles cleanly in the target release.

Key Columns

Columns fall into three logical groups. The trade partner identity group includes TRADE_PARTNER_PK, PARENT_TPARTNER_FK, TRADE_PARTNER_DP (a descriptive flexfield-style descriptor), NAME, and ALTERNATE_NAME. The supplier attributes group includes VNDR_NUMBER, VNDR_TYPE, VNDR_ONE_TIME, VNDR_MINORITY_GRP, VNDR_WOMEN_OWNED, VNDR_SMALL_BUS, VNDR_HOLD_FLAG, VNDR_INSPECT_REQ, VNDR_RECEIPT_REQ, VNDR_SUB_RECEIPT, and VNDR_UNORDER_RCV. The customer attributes group is the largest and includes CUST_NUMBER, CUST_ORIG_SYS_REF, CUST_STATUS, CUST_TYPE, CUST_PROSPECT, CUST_CLASS, CUST_SALES_REP, CUST_SALES_CHNL, CUST_ORDER_TYPE, CUST_PRICE_LIST, CUST_CAT_CODE, CUST_KEY, CUST_FISCAL_END, CUST_NUM_EMP, CUST_REVENUE_CURR, CUST_REVENUE_NEXT, CUST_TAX_CODE, CUST_THIRD_PARTY, CUST_ACCESS_TMPL, CUST_COMPETITOR, CUST_ORIG_SYS, CUST_COTERM_DATE, CUST_FOB_POINT, CUST_FREIGHT, CUST_GSA_IND, and CUST_SHIP_PARTIAL. The user's search term cust_type maps directly to the CUST_TYPE column, which carries the customer classification code (for example, Internal, External, or Prospect-adjacent designations sourced from the HZ customer profile). Common fields such as START_ACTIVE_DATE, END_ACTIVE_DATE, SIC_CODE, TAX_REG_NUM, TAXPAYER_ID, PAYMENT_TERMS, LAST_UPDATE_DATE, CREATION_DATE, OPERATION_CODE, VENDOR_ID, CUSTOMER_ID, and INSTANCE complete the projection.

Common Use Cases and Queries

Typical uses include loading trade partner master data into an EDW staging area, reconciling supplier and customer records that share a single TCA party, and reporting on customer classification for sales and credit analysis. Filtering by CUST_TYPE is a frequent requirement:

  • SELECT TRADE_PARTNER_PK, NAME, CUST_NUMBER, CUST_TYPE FROM APPS.EDW_TPRT_TRADE_PARTNER_LCV WHERE CUST_TYPE = 'R';
  • SELECT VNDR_NUMBER, NAME, CUST_NUMBER, CUST_STATUS FROM APPS.EDW_TPRT_TRADE_PARTNER_LCV WHERE VNDR_SMALL_BUS = 'Y' AND CUST_STATUS = 'A';
  • SELECT CUST_CLASS, COUNT(*) FROM APPS.EDW_TPRT_TRADE_PARTNER_LCV WHERE CUST_TYPE IS NOT NULL GROUP BY CUST_CLASS;

Because the view is a read-only projection, all queries should be issued under the APPS schema or a reporting responsibility with the appropriate grants. Join to HZ_PARTIES on CUSTOMER_ID or VENDOR_ID to enrich results with party contact and site detail.