Results for “ece_rsu_nocontact”

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

Overview

ECE_RSU_NOCONTACT is a reporting view within the Oracle E-Business Suite e-Commerce Gateway (EC) module. It presents a consolidated, denormalized result set combining customer contact details drawn from the customer master, address/TP (trading partner) mapping data, and site-use records. Its naming reflects its function: it exposes contact and location information for parties that are not linked through the standard contact role, drawing instead on phone, address, and site-use associations. The view is intended for use in outbound or inbound e-Commerce Gateway processing, where trading partner location and contact data must be transmitted alongside document payloads, and for ad hoc reporting on customer sites that lack a conventional contact assignment.

Per the ETRM metadata for release 12.2.2, the view is not implemented in the reference database and no base objects are documented as referenced. The view definition is nonetheless fully enumerated in documentation and is reproduced below for reference.

Underlying Base Objects

The view is defined over three base tables, joined on customer and address keys:

• ECE_CUSTOMER_PHONE (ECP) — supplies customer name and telephone attributes; joined to ECE_ADDRESS_TP on CUSTOMER_ID.
• ECE_ADDRESS_TP (ETA) — the e-Commerce Gateway address/trading partner table, supplying address and trading-partner reference attributes; joined to RA_SITE_USES_ALL on ADDRESS_ID.
• RA_SITE_USES_ALL (RSU) — the Receivables site-use table, supplying the site-use identifier and location; joined to ECE_ADDRESS_TP on ADDRESS_ID.

The join predicates are: ETA.CUSTOMER_ID = ECP.CUSTOMER_ID and RSU.ADDRESS_ID = ETA.ADDRESS_ID. The view therefore returns one row per qualifying site-use/address/customer-phone combination.

Key Columns

• SITE_USE_ID — primary identifier of the Receivables site use record (RA_SITE_USES_ALL.SITE_USE_ID); the key linking to the customer site.
• CUSTOMER_ID — customer identifier sourced from ECE_CUSTOMER_PHONE, used as the join key to the customer record.
• ADDRESS_ID — the address identifier from ECE_ADDRESS_TP, matching RA_SITE_USES_ALL.ADDRESS_ID.
• TP_HEADER_ID — the trading partner header identifier from ECE_ADDRESS_TP.
• LOCATION — location value from the site-use record.
• ORIG_SYSTEM_REFERENCE — the originating system reference for the address/trading partner, supporting cross-system reconciliation.
• TP_LOCATION_CODE_EXT, TP_REFERENCE_EXT1, TP_REFERENCE_EXT2 — external trading partner location and reference codes used in gateway transactions.
• CUSTOMER_NAME — customer name from ECE_CUSTOMER_PHONE.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — the constituent address fields from ECE_ADDRESS_TP.
• AREA_CODE, PHONE_NUMBER — telephone attributes from ECE_CUSTOMER_PHONE.

Common Use Cases and Queries

The view is typically used to reconcile trading partner address data, verify that site-use locations carry complete contact information, and produce extracts for gateway document transmission. A representative query retrieves contact and address details for a specific customer:

• SELECT customer_id, customer_name, site_use_id, location, city, postal_code, country, area_code, phone_number FROM ece_rsu_nocontact WHERE customer_id = :p_customer_id;
• SELECT site_use_id, address_id, tp_header_id, tp_location_code_ext, orig_system_reference FROM ece_rsu_nocontact WHERE address_id = :p_address_id;
• SELECT country, COUNT(*) FROM ece_rsu_nocontact GROUP BY country ORDER BY 2 DESC; — address distribution by country for gateway validation.

Because the view joins three tables on customer and address keys, results depend on the presence of matching records in all three sources; rows missing a corresponding phone or trading partner entry are excluded. Users should confirm that the relevant e-Commerce Gateway trading partner and address setup have been completed before relying on this view for reporting.