Search Results rcv_opsm_customeraddress_v




Overview
Explore in AI Chat

Overview

RCV_OPSM_CUSTOMERADDRESS_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, registered under the PO (Purchasing) product family with a VALID status. The view consolidates shipping, customer, and party information drawn from the Oracle Order Management and Receiving schemas. Its name reflects its purpose: it supplies the order promising and scheduling module (OPSM) with the customer address data required to identify sold-to and ship-from organizations and contacts associated with shipment lines.

The view primarily supports the processing of change-of-ownership and internal shipment scenarios, where a shipment line must be attributed to a specific selling organization and contact. It surfaces a computed CHANGEOFOWNERSHIP flag, derived by evaluating the customer type from AR_CUSTOMERS_ACTIVE_V, which distinguishes internal (employee) customers from external ones. Because the object is a view rather than a base table, it presents a denormalized, read-only projection intended for reporting, inquiry, and integration lookups rather than transactional data manipulation.

Underlying Base Objects

The view is defined over a mixture of receipt, order, and trading-partner tables. Shipment data originates from RCV_SHIPMENT_LINES, which anchors the header and line identifiers and the item detail. Order context is supplied by OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, from which the sold-to organization and contact identifiers are obtained. The customer and party dimensions are resolved through the Oracle Trading Community Architecture (TCA) tables, exposed in the APPS schema as synonyms: HZ_PARTIES, HZ_CUST_ACCOUNT_ROLES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS. Customer classification is fetched from AR_CUSTOMERS_ACTIVE_V. This dependence on HZ_PARTIES and its related TCA objects explains why a search for "hz_parties" surfaces this view: the party identifier and party name columns are central to resolving sold-by and ship-from organization identities.

Key Columns

The view exposes shipment identifiers (SHIPMENT_HEADER_ID, SHIPMENT_LINE_ID, ITEM_ID, ITEM_DESCRIPTION) alongside the derived CHANGEOFOWNERSHIP flag. Sold-by attributes include SOLDBYORGID, SOLDBYCONTACTID, SOLDBYORGCODE (the HZ_PARTIES party identifier), SOLDBYORGNAME, and the associated location and address columns (SOLDBYLINE1 through SOLDBYSTATE, SOLDBYPROVINCE). Contact name resolution is performed through a scalar subquery joining HZ_CUST_ACCOUNT_ROLES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, and HZ_PARTIES, producing SOLDBYCONTACTNAME. Phone and email attributes are gathered from HZ_CONTACT_POINTS for the primary, active contact point. Parallel SHIPFROM columns (SHIPFROMORGID, SHIPFROMCONTACTID, SHIPFROMORGCODE, SHIPFROMORGNAME, SHIPFROMLOCATIONID, and the SHIPFROMLINE series) mirror the sold-by structure for the shipping organization.

Common Use Cases and Queries

Typical usage includes identifying the party and address associated with a shipment line for change-of-ownership processing, generating shipping documentation with correct sold-by and ship-from details, and populating integrations that require resolved TCA party identifiers. A representative query is:

  • SELECT SHIPMENT_LINE_ID, SOLDBYORGCODE, SOLDBYORGNAME, SOLDBYCONTACTNAME, SHIPFROMORGCODE, CHANGEOFOWNERSHIP FROM RCV_OPSM_CUSTOMERADDRESS_V WHERE SHIPMENT_HEADER_ID = :p_header_id;
  • Join the view to HZ_PARTIES on SOLDBYORGCODE = PARTY_ID to enrich reporting with full party attributes.
  • Filter on CHANGEOFOWNERSHIP = 1 to isolate transactions representing transfers of ownership rather than internal movements.

Because the underlying joins are largely based on TCA synonyms, performance is best when querying by shipment or party identifiers and when TCA indexes on PARTY_ID, CUST_ACCOUNT_ROLE_ID, and OWNER_TABLE_ID are present.