Results for “ece_rsu_contact”

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

Overview

The ECE_RSU_CONTACT view is a reporting and integration object within the Oracle e-Commerce Gateway (EC) module. It presents a consolidated, denormalized picture of contact, address, and customer information tied to site-use records, combining data that would otherwise require joining four separate base tables. Its principal purpose is to flatten the relationship between a customer site use, the associated customer record, the transaction-partner address, and the contact phone details so that downstream interface programs and reports can retrieve a single row per site-use contact combination without extensive join logic.

Within the e-Commerce Gateway architecture, objects prefixed with ECE typically support the extraction and transformation of trading-partner data for inbound and outbound transaction processing. ECE_RSU_CONTACT follows this convention: it exposes the parties, locations, and contact attributes required to populate interface tables and to reconcile site-level partner data. Because it joins customer, site use, address, and contact phone sources, it is well suited to reporting scenarios where a complete party-and-location profile is needed on a single line.

Underlying Base Objects

The view text documents four referenced base objects, joined as follows:

• RA_SITE_USES_ALL (RSU) — the driving table, supplying SITE_USE_ID, CONTACT_ID, LOCATION, and ADDRESS_ID.
• RA_CUSTOMERS (RCU) — joined on ETA.CUSTOMER_ID = RCU.CUSTOMER_ID, supplying CUSTOMER_ID and CUSTOMER_NAME.
• ECE_ADDRESS_TP (ETA) — joined on RSU.ADDRESS_ID = ETA.ADDRESS_ID, supplying the transaction-partner address and reference columns.
• ECE_CONTACT_PHONE (ECP) — outer-joined on RSU.CONTACT_ID = ECP.CONTACT_ID (+), supplying contact name, job title, and phone attributes.

The outer join to ECE_CONTACT_PHONE is significant: a site use that has no matching contact phone record will still be returned, with the contact and phone columns null. ETRM notes that the view is not implemented in the reference database, and that no additional base objects are documented beyond those present in the view text.

Key Columns

• SITE_USE_ID — primary site-use identifier from RA_SITE_USES_ALL; the de facto key of each row.
• CUSTOMER_ID / CUSTOMER_NAME — the customer or trading partner owning the site use.
• ADDRESS_ID / TP_HEADER_ID — address identifier and transaction-partner header reference.
• CONTACT_ID — the contact associated with the site use.
• LOCATION — the site-use location code.
• ORIG_SYSTEM_REFERENCE, TP_LOCATION_CODE_EXT, TP_REFERENCE_EXT1/2 — external reference fields used to map the record back to the originating or partner system.
• Address columns (ADDRESS1–4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY) — the physical address of the transaction partner.
• Contact columns (LAST_NAME, FIRST_NAME, JOB_TITLE, AREA_CODE, PHONE_NUMBER) — contact identity and telephone details.

Common Use Cases and Queries

Typical scenarios include generating a site-use contact roster for e-Commerce Gateway trading partners, validating that each active site use carries a contact and phone number, and feeding address/contact data into outbound interface processing. A representative query follows.

• Report all site-use contacts for a given customer:
  SELECT customer_name, location, last_name, first_name, phone_number FROM ece_rsu_contact WHERE customer_id = :p_customer_id;
• Identify site uses lacking contact information (outer-join nulls):
  SELECT site_use_id, customer_name, location FROM ece_rsu_contact WHERE contact_id IS NULL;
• Resolve the address for a specific trading-partner location:
  SELECT address1, city, state, postal_code, country FROM ece_rsu_contact WHERE tp_location_code_ext = :p_location_code;
• Cross-reference external systems using the reference columns:
  SELECT site_use_id, orig_system_reference, tp_reference_ext1 FROM ece_rsu_contact WHERE orig_system_reference IS NOT NULL;

Because the view resolves multiple party relationships in one pass, it is generally preferred over ad hoc multi-table joins when building e-Commerce Gateway reports or validating partner data quality.