Search Results access_template_entity_code

Overview

The EDWBV_TPRT_TRADE_PARTNER_LCV view is a reporting and integration construct within the Oracle E-Business Suite Purchasing (PO) module. Its name follows the ETRM convention for "List of Values" (LCV) and "Trade Partner" (TPRT) objects, indicating that it is designed to expose a consolidated, denormalized list of trade partners—principally customers and their associated accounts—for use by downstream reporting, data warehouse, and integration consumers. In the Oracle EBS 12.1.1 and 12.2.2 environments, objects bearing the EDWBV prefix typically belong to the E-Business Data Warehouse (EDW) layer, which supplies flattened, read-only representations of transactional and master data for analytics and extract processes.

The view's role is to present trade-partner identity, account metadata, and business classification attributes in a single queryable surface. Because the source documentation notes that the view is "Not implemented in this database," the object exists as a metadata definition shipped by Oracle rather than as a physically deployed database object in every environment. Implementers encountering this view should confirm deployment status in their specific instance before relying upon it in production queries.

Underlying Base Objects

The documented metadata lists no referenced base objects, and the ETRM entry records no explicit owner. However, the view text itself reveals the principal source tables. The dominant source is HZCA, which corresponds to the HZ_CUST_ACCOUNTS table in the Oracle Trading Community Architecture (TCA) model. Supporting joins reference PARTIES (HZ_PARTIES), INST (likely a reference to an instance or organization code table), APT (appearing to resolve a name attribute, consistent with a party or account-site lookup), OT (an organization or channel type lookup), and PL (a price list or associated list reference). The concatenation of HZCA.CUST_ACCOUNT_ID, INST.INSTANCE_CODE, and the literal 'CUST_ACCT' forms the first (primary) column, providing a composite identifier for each trade-partner account.

Because the view is defined over TCA tables, its outputs inherit the multi-org and multi-organization characteristics of that data model. Consumers must therefore consider organization context when interpreting results.

Key Columns

The view exposes a substantial column list. Notable fields include:

• Trade partner identifier — The concatenated CUST_ACCOUNT_ID-INSTANCE_CODE-CUST_ACCT value, serving as the unique key for each row.
• Party display name — SUBSTRB(PARTIES.PARTY_NAME, 1, 80) combined with HZCA.ACCOUNT_NUMBER in parentheses, providing a human-readable label.
• Organizational attributes — ORGANIZATION_NAME_PHONETIC, SIC_CODE, TAX_REFERENCE, and JGZZ_FISCAL_CODE from HZ_PARTIES, supporting classification and compliance reporting.
• Account lifecycle fields — ACCOUNT_ACTIVATION_DATE and ACCOUNT_TERMINATION_DATE, enabling time-based filtering.
• Customer classification — CUSTOMER_TYPE, CUSTOMER_CLASS_CODE, STATUS, and a DECODE over TOTAL_NUM_OF_ORDERS that labels accounts as 'PROSPECT' (zero orders) or 'CUSTOMER'.
• Shipping and pricing — FOB_POINT, FREIGHT_TERM, SHIP_PARTIAL, SHIP_VIA, and a price list name derived from PL.NAME.
• Placeholder columns — Numerous NULL placeholders document attributes available in underlying vendor or party tables (for example VNDR_NUMBER, ONE_TIME_FLAG, MINORITY_GROUP_LOOKUP_CODE) that are not sourced in this view, signaling schema evolution and incompleteness.

Common Use Cases and Queries

Typical use of this view centers on trade-partner master reporting, customer/prospect segmentation, and account reconciliation between TCA and downstream systems. A representative query retrieves active customer accounts for a given fiscal context:

• SELECT trade_partner_id, party_display_name, customer_type, account_number FROM EDWBV_TPRT_TRADE_PARTNER_LCV WHERE customer_type = 'CUSTOMER' AND account_termination_date IS NULL;
• SELECT organization_name_phonetic, sic_code, fiscal_yearend_month FROM EDWBV_TPRT_TRADE_PARTNER_LCV WHERE sic_code IS NOT NULL ORDER BY sic_code;

Because the documentation confirms the view is not implemented in the reference database, all usage should be preceded by deployment verification. Where the view is absent, equivalent queries against HZ_CUST_ACCOUNTS and HZ_PARTIES can reproduce the same output.