Results for “ece_rco_address”

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

Overview

ECE_RCO_ADDRESS is a reporting view within the Oracle E-Business Suite e-Commerce Gateway (EC) module. It consolidates address, contact, and telephone information for customers so that outbound and inbound e-Commerce transactions — such as EDI 810 invoices, 850 purchase orders, and 856 advance ship notices — can resolve trading-partner location and contact data into a single denormalized row. The view joins customer master data from RA_CUSTOMERS to address records held in the gateway's own staging tables (ECE_ADDRESS_TP) and contact phone data (ECE_CONTACT_PHONE). Its name reflects its "RCO" (Remote/Contact-Order) lineage, meaning it is intended for read-only reference by concurrent programs, Oracle Reports, and custom SQL rather than for direct DML.

The metadata indicates the view is Not implemented in this database and lists no documented owner or referenced base objects at the schema level. This means the view exists in the ETRM dictionary but may not be deployed in every environment; administrators should confirm its presence with a query against ALL_VIEWS before relying on it. Because the columns carry the TP_ (trading partner) prefix, the view plays a role in mapping third-party location codes to Oracle master identifiers.

Underlying Base Objects

The view text is defined over three base tables using ANSI-style outer joins:

• ECE_CONTACT_PHONE (ECP) — the driving table supplying contact name, job title, and phone details.
• ECE_ADDRESS_TP (ETA) — the trading-partner address staging table, joined to ECP on ADDRESS_ID with an outer (+) join so contacts without an address still appear.
• RA_CUSTOMERS (RCU) — the customer master, joined on CUSTOMER_ID to supply the customer name and the authoritative CUSTOMER_ID.

The join predicate ECP.ADDRESS_ID = ETA.ADDRESS_ID (+) makes ECE_ADDRESS_TP an optional side, while ECP.CUSTOMER_ID = RCU.CUSTOMER_ID links contacts to the customer record. No other objects are documented.

Key Columns

• CUSTOMER_ID — Primary customer identifier from RA_CUSTOMERS, the join key across the view.
• ADDRESS_ID — Address surrogate key linking contact phones to trading-partner addresses.
• CONTACT_ID — Unique contact identifier from ECE_CONTACT_PHONE.
• ORIG_SYSTEM_REFERENCE — The source-system key for the address, used in EDI mapping.
• TP_LOCATION_CODE_EXT, TP_REFERENCE_EXT1/2 — External trading-partner location and reference codes exchanged in EDI messages.
• CUSTOMER_NAME, ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — Standard mailing address attributes.
• LAST_NAME, FIRST_NAME, JOB_TITLE, AREA_CODE, PHONE_NUMBER — Contact person and telephone details.

Common Use Cases and Queries

Typical uses include validating that every trading partner address is accompanied by a contact, generating address/contact extracts for EDI envelopes, and auditing location codes prior to gateway processing.

SELECT CUSTOMER_ID, CUSTOMER_NAME, ADDRESS1, CITY,
       TP_LOCATION_CODE_EXT, LAST_NAME, FIRST_NAME, PHONE_NUMBER
FROM   ECE_RCO_ADDRESS
WHERE  CUSTOMER_ID = :p_customer_id;

To find contacts lacking addresses:

SELECT CONTACT_ID, LAST_NAME, FIRST_NAME
FROM   ECE_RCO_ADDRESS
WHERE  ADDRESS_ID IS NULL;

Because the view is read-only and may be absent in some instances, confirm availability via ALL_VIEWS and grant SELECT to reporting users rather than querying base tables directly.