Results for “sold_from_org_id”

50+ results




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

Overview

OE_AK_DELIVER_TO_ORGS_V is a view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ONT (Order Management) product family. Its purpose is to present delivery-related organization attributes for a customer's deliver-to organization, augmented with the corresponding Bill-To site use information. The "AK" prefix in the name follows the historical Oracle order-entry attribute interface ("AK" attributes) conventions that appear throughout Order Management and its related region-functionality.

The view is documented as a VALID object in the ETRM repository for both 12.1.1 and 12.2.2. Because it consolidates shipping, freight, pricing, and billing attributes in a single denormalized row, it serves as a convenient read-only source for reporting, integrations, and lookups where a flat deliver-to/Bill-To perspective is required.

Underlying Base Objects

The documented definition references two objects:

  • OE_DELIVER_TO_ORGS_V (VIEW) — the primary driving source, supplying the deliver-to organization's shipping, freight, pricing, and contact attributes.
  • HZ_CUST_SITE_USES_ALL (referenced via SYNONYM) — the Trading Community Architecture site-use table, providing the Bill-To site use link.

The two objects are joined with an outer join so that a deliver-to record contributes a row even when no active Bill-To site use exists. The join predicate restricts the TCA side to site-use code 'BILL_TO' and status 'A' (active), thereby ensuring only active Bill-To accounts are matched. The driver side, OE_DELIVER_TO_ORGS_V, is itself a view in the Order Management schema, meaning OE_AK_DELIVER_TO_ORGS_V is a view-over-view layered on TCA data.

Key Columns

The view exposes the following columns, most of which correspond to order-entry attributes controlled at the deliver-to level:

Common Use Cases and Queries

Typical usages include resolving default shipping and freight attributes for a customer organization, reconciling deliver-to records with their active Bill-To site uses, and populating Order Management integration payloads. A representative query retrieving active Bill-To mappings is shown below.

SELECT organization_id, price_list_id, fob_point_code, freight_terms_code, shipping_method_code, sold_from_org_id, ship_from_org_id, bill_to_site_use_id, invoice_to_org_id FROM apps.oe_ak_deliver_to_orgs_v WHERE organization_id = :p_org_id;

Because the join to HZ_CUST_SITE_USES_ALL is an outer join, consumers should test BILL_TO_SITE_USE_ID and INVOICE_TO_ORG_ID for null values when a deliver-to organization has no active Bill-To site use; such rows still surface the deliver-to attributes. When only active Bill-To data is wanted, an additional predicate such as bill_to_site_use_id IS NOT NULL should be applied. As with all APPS views, direct updates are not supported; changes must be made to the underlying Order Management and TCA entities.