Search Results oe_sold_to_orgs_v




Overview
Explore in AI Chat

Overview

OE_SOLD_TO_ORGS_V is a view owned by the APPS schema in Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It belongs to the Order Management (ONT) product family and is documented in ETRM under the title "View: OE_SOLD_TO_ORGS_V" with a status of VALID. The view presents a consolidated list of customers, exposing sold-to organization information that originates from the Oracle Receivables and Trading Community customer model. In practical terms, it provides a simplified, denormalized projection of customer account and party data that reporting, integration, and Order Management processing components can query without joining the underlying customer tables directly.

Although the view is associated with the ONT module, the underlying data belongs to the HZ (Trading Community) customer schema. This design is intentional: Order Management processes, including order entry and order import, reference sold-to organizations to identify the customer placing an order. The view materializes a widely used subset of customer attributes under a stable set of column names, insulating callers from changes in the physical customer model.

Underlying Base Objects

The view is defined over two base objects, both accessed through APPS synonyms:

  • HZ_CUST_ACCOUNTS (synonym) — the customer account record. Its alias CUST_ACCT supplies the account identifier, account number, status, price list, and order defaulting attributes.
  • HZ_PARTIES (synonym) — the party record. Its alias PARTY supplies the party name used as the customer name.

The join condition is CUST_ACCT.PARTY_ID = PARTY.PARTY_ID. Each row returned therefore represents a customer account joined to its owning party. No outer join is used, so an account is only surfaced when a matching party exists.

Key Columns

The column list includes several pass-through attributes from HZ_CUST_ACCOUNTS plus a large set of legacy organization columns that this view hard-codes to NULL for compatibility with prior organization-based APIs.

Columns such as BUSINESS_GROUP_ID, LOCATION_ID, TYPE, REQUEST_ID, ATTRIBUTE1 through ATTRIBUTE20, and the audit columns (LAST_UPDATE_DATE, CREATED_BY, and so on) are all returned as NULL, reflecting the legacy organization interface that this view emulates.

Common Use Cases and Queries

The view is typically used to resolve sold-to customer names for order lines, to drive order entry defaults, and to support custom reports and interfaces that reference sold-to organizations.

A representative query listing active customers:

SELECT organization_id, account_number, name, status FROM oe_sold_to_orgs_v WHERE status = 'A' ORDER BY name;

Joining to order headers to resolve the sold-to name:

SELECT h.order_number, v.name FROM oe_order_headers_all h, oe_sold_to_orgs_v v WHERE h.sold_to_org_id = v.organization_id;

Retrieving default order attributes for a given account:

SELECT organization_id, price_list_id, fob_point_code, freight_terms_code, order_type_id FROM oe_sold_to_orgs_v WHERE organization_id = :sold_to_org_id;

Because the view hard-codes many columns to NULL, it should be used only for the populated attributes listed above; callers requiring full organization attributes must query HZ_CUST_ACCOUNTS and HZ_PARTIES directly.