Search Results tp_reference_ext2




Overview
Explore in AI Chat

Overview

The view VEH_TRANSLATOR_ADDR_V is an Oracle E-Business Suite database object associated with the VEH — Automotive Integration Kit product family. The ETRM metadata catalogues this object as Obsolete and further annotates it as Retrofitted. The view presents a reconciled, union-based listing of address identifiers drawn from two distinct sources: internal customer addresses maintained in the Oracle Receivables customer model, and externally sourced trading-partner address references maintained in the ECE (E-Commerce Gateway / Electronic Commerce Exchange) staging tables. Its primary purpose is to provide a single denormalised list of addresses labelled with an internal/external origin indicator, which is the semantic captured by the user's search term INT_EXT_CODE.

As a translator view, its role is to reconcile external integration payload references (typically originating from an automotive OEM's ordering or messaging system) against the native Oracle master data model. The published ETRM documentation explicitly notes that the object is Not implemented in this database, meaning deployments should treat the definition below as reference metadata rather than a guaranteed runtime artefact.

Underlying Base Objects

The view definition is a UNION of two branches over the following documented base objects:

The internal branch joins RA_ADDRESSES to RA_CUSTOMERS on the CUSTOMER_ID key; the external branch reads trading-partner header rows without any join. ETRM records no owner and no additional documented referenced base objects beyond those appearing in the view text.

Key Columns

  • CUSTOMER_NUMBER — On the internal branch, RA_CUSTOMERS.CUSTOMER_NUMBER. On the external branch, the char-converted ECE_TP_HEADERS.TP_GROUP_ID.
  • ADDRESS_ID — On the internal branch, TO_CHAR(RA_ADDRESSES.ADDRESS_ID). On the external branch, TP_REFERENCE_EXT2, i.e. the external system's own address reference.
  • ADDRESS — On the internal branch, RA_ADDRESSES.ADDRESS1 (the first address line). On the external branch, the same TP_REFERENCE_EXT2 value, confirming that external addresses are exposed as opaque references rather than parsed address lines.
  • INT_EXT_CODE — The literal discriminator: 'INTERNAL' for rows sourced from Receivables, 'EXTERNAL' for rows sourced from ECE trading-partner headers.

Common Use Cases and Queries

The view is most useful where a receiving or ordering interface must resolve an incoming external address reference to a native Receivables address, or conversely confirm that a given customer number has a corresponding external trading-partner definition. A typical reconciliation query filters on the discriminator:

SELECT customer_number, address_id, address, int_ext_code FROM veh_translator_addr_v WHERE int_ext_code = 'EXTERNAL';

To identify customer numbers appearing on both sides of the translator:

SELECT customer_number, COUNT(DISTINCT int_ext_code) FROM veh_translator_addr_v GROUP BY customer_number HAVING COUNT(DISTINCT int_ext_code) = 2;

Because the view is documented as obsolete, not implemented, and retrofitted, teams on 12.1.1 or 12.2.2 should verify existence in ALL_VIEWS before embedding it in concurrent programs or interface logic, and should prefer direct joins to RA_ADDRESSES, RA_CUSTOMERS, and ECE_TP_HEADERS for new development.