Results for “edw_trd_partner_cust_fkv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EDW_TRD_PARTNER_CUST_FKV is a database view registered under the Oracle E-Business Suite Purchasing (PO) module. Its name follows the ETRM/EDW naming convention for reporting and extract layer objects, where the "EDW" prefix designates Enterprise Data Warehouse-facing content and the "FKV" suffix denotes a foreign-key-style lookup view. The view supplies a denormalized trading-partner customer key by joining the Oracle Receivables customer identifier to a decorated customer name value.

Functionally, the view acts as a lightweight lookup that maps a CUSTOMER_ID to a concatenated display value composed of CUSTOMER_NAME, a hyphen separator, and the literal string TPRT. The "TPRT" token identifies the record as a trading-partner customer designation, distinguishing these rows from other customer-derived identifiers in downstream reporting extracts. This construction allows reporting and integration processes to resolve customer identity without repeating join logic against the base Receivables tables.

Within Oracle EBS 12.1.1 and 12.2.2, the view is documented as not implemented in the reference database. This status is significant: it indicates the object is part of the standard ETRM/EDW catalog of expected reporting objects, but is not created by default in every environment. Deployments that require it must verify its presence or create it during extract-layer setup.

Underlying Base Objects

The documented view text is a single-table construct with no joins:

• RA_CUSTOMERS — the only referenced base object, supplying both CUSTOMER_ID and CUSTOMER_NAME.

The ETRM metadata records no other documented base objects, no owner, and no additional dependencies. The view is therefore a projection with an expression applied to one column of RA_CUSTOMERS, making it a very shallow abstraction over the Receivables customer master. Because RA_CUSTOMERS is the primary customer definition table in Oracle Receivables, the view's grain is one row per customer record as stored in that table, subject to whatever row-level filtering (none is documented) applies.

Key Columns

• CUSTOMER_ID — the numeric primary identifier for the customer, passed through unchanged from RA_CUSTOMERS.CUSTOMER_ID. This is the join key used by consuming reports and extracts to resolve customer identity.
• CUSTOMER_NAME — although documented in the column list under the name CUSTOMER_NAME, the projected expression is actually a concatenation: CUSTOMER_NAME || '-' || 'TPRT'. The resulting value is the customer name with the suffix -TPRT appended, functioning as a trading-partner-tagged display name. Consumers should not treat this column as a clean customer name; the suffix is an intrinsic part of the value.

Common Use Cases and Queries

The view is typically consumed by ETRM/EDW extract routines and purchasing or supply-chain reports that require a trading-partner-tagged customer label alongside the raw customer identifier. Because the concatenation is pre-built, callers avoid replicating the formatting logic. A representative query resolving a customer by identifier:

• SELECT CUSTOMER_ID, CUSTOMER_NAME FROM EDW_TRD_PARTNER_CUST_FKV WHERE CUSTOMER_ID = :p_customer_id;
• SELECT CUSTOMER_ID, CUSTOMER_NAME FROM EDW_TRD_PARTNER_CUST_FKV ORDER BY CUSTOMER_NAME;
• SELECT v.CUSTOMER_ID, v.CUSTOMER_NAME FROM EDW_TRD_PARTNER_CUST_FKV v WHERE v.CUSTOMER_NAME LIKE 'ACME%';

Before relying on the view, DBAs should confirm implementation status, since the reference database reports it as absent. Where it is missing, the equivalent projection can be created directly over RA_CUSTOMERS to reproduce the documented behavior.