Results for “ra_customer_ship_view”

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

Overview

RA_CUSTOMER_SHIP_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, belonging to the Receivables (AR) product family. Its documented purpose is to present "information about customer who gets the shipments." In practical terms, the view exposes ship-to address and site-use information for customers, formatted in a manner that parallels the legacy RA_CUSTOMER_MASTER structures used by earlier Fusion and Receivables interfaces.

The view plays a supporting role in reporting and integration scenarios where downstream consumers — such as shipping, order fulfilment, or interface programs — require a compact, denormalised result set of customer ship-to sites without joining the full Oracle Trading Community Architecture (TCA) model manually. Because it resolves several TCA tables into a single flattened query, it simplifies the retrieval of ship-to addresses for a given customer account.

The view is catalogued as VALID in ETRM 12.2.2 and is available equivalently in 12.1.1. Note that, despite its name including the token "SHIP," the view is not the same as the shipping transaction tables (WSH) — it is an AR-owned construct referencing TCA party data.

Underlying Base Objects

The view text joins four TCA tables, all accessed through APPS synonyms:

• HZ_CUST_ACCT_SITES_ALL — the customer account site assignment, joined via CUST_ACCT_SITE_ID and providing the CUST_ACCOUNT_ID and STATUS.
• HZ_CUST_SITE_USES_ALL — site-use definitions, filtered to SITE_USE_CODE = 'SHIP_TO', supplying SITE_USE_ID and TERRITORY_ID.
• HZ_PARTY_SITES — the party-site link, joined via PARTY_SITE_ID.
• HZ_LOCATIONS — the physical address, joined via LOCATION_ID, providing ADDRESS1, CITY, STATE and POSTAL_CODE.

The join path proceeds from site use to account site, to party site, to location, restricting output to ship-to uses of customer accounts. Because the view is defined with these inner joins, a customer account site lacking complete party-site or location data is excluded from the result set.

Key Columns

The documented column list exposes eight columns:

• CUSTOMER_ID — mapped from ACCT_SITE.CUST_ACCOUNT_ID; identifies the customer account owning the ship-to site.
• SHIP_ID — an alias for SU.SITE_USE_ID; this is the column most commonly targeted by searches for "ship_id" and uniquely identifies the ship-to site use.
• TERRITORY_ID — the territory associated with the site use, typically used for tax and geography processing.
• ADDRESS1 — the primary street address line from HZ_LOCATIONS.
• CITY, STATE, POSTAL_CODE — the remaining location attributes of the ship-to address.
• STATUS — the status of the customer account site, indicating whether the ship-to site is active.

Note the deliberate aliasing: the SITE_USE_ID column is surfaced as SHIP_ID, and CUST_ACCOUNT_ID as CUSTOMER_ID. Consumers must map these aliases when correlating results with base-table identifiers.

Common Use Cases and Queries

Typical uses include validating that a customer has an active ship-to site, extracting address data for shipping interfaces, and reconciling site-use identifiers during data conversion. The most direct query retrieves all ship-to sites for a customer:

• SELECT customer_id, ship_id, city, state, postal_code, status FROM apps.ra_customer_ship_view WHERE customer_id = :p_customer_id;
• SELECT ship_id, address1, city FROM apps.ra_customer_ship_view WHERE status = 'A';

Because the view filters to SITE_USE_CODE = 'SHIP_TO', callers do not need to add that predicate themselves. Where the requirement extends to bill-to or other site-use codes, the caller must query HZ_CUST_SITE_USES_ALL directly, since this view will not return those rows.

When troubleshooting a missing SHIP_ID, verify that the underlying site use is active and that the account site is linked to a valid party site and location; broken links at any of the four base tables cause the row to be omitted. The view is a convenience projection and should be treated as such rather than as an authoritative transactional source.