Search Results oe_invoice_to_orgs_v




Overview
Explore in AI Chat

Overview

The OE_INVOICE_TO_ORGS_V view is a predefined, seeded database object owned by the APPS schema within the Oracle E-Business Suite Order Management (ONT) product family. It is registered as VALID in the ETRM repository for both the 12.1.1 and 12.2.2 releases. The view presents the bill-to organization context associated with a customer site use, effectively exposing invoice-to organization, location, and address information in a denormalized form suitable for Order Management processing, reporting, and integration.

Functionally, the view shields callers from the multi-table structure of Oracle's Trading Community Architecture (TCA) customer model. Rather than joining account, site, site-use, party-site, and location entities directly, Order Management components, concurrent programs, and external integrations query this view to retrieve a single consolidated record describing the bill-to organization for a given customer destination. The organizational identifier exposed by the view is derived from the SITE_USE_ID of the underlying customer site use, meaning the view's notion of "organization" is anchored to the TCA site-use construct rather than to the HR organization model. Many standard EBS fields that are not meaningful for this object, such as business group, key flexfield identifiers, and audit columns, are deliberately projected as NULL to preserve a fixed column interface.

Underlying Base Objects

Per the documented ETRM metadata, OE_INVOICE_TO_ORGS_V is defined over the following base objects, all referenced through public synonyms in the APPS schema:

  • HZ_CUST_SITE_USES_ALL — The primary driver of the query, aliased as SITE. Site-use records describe how a customer site is used, including bill-to, ship-to, and other usage purposes. Columns such as SITE_USE_ID, STATUS, PRICE_LIST_ID, PAYMENT_TERM_ID, and the shipping tolerance and freight attributes are sourced from here.
  • HZ_CUST_ACCT_SITES — Aliased as ACCT_SITE, this object links a customer account to a physical site and supplies CUST_ACCT_SITE_ID, CUST_ACCOUNT_ID, and the account-site status.
  • HZ_PARTY_SITES — Provides the association between the account site and the underlying party site, bridging the account and location layers of the TCA model.
  • HZ_LOCATIONS — Aliased as LOC, this object contributes the address attributes, including ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, COUNTRY, COUNTY, and the merged STATE/PROVINCE value.

The view therefore sits at the intersection of the TCA account-site-use and location structures rather than directly over any Order Management transaction entity.

Key Columns

The view exposes a broad projection of columns. The most significant include:

Columns that are not applicable to this object, including BUSINESS_GROUP_ID, COST_ALLOCATION_KEYFLEX_ID, SOFT_CODING_KEYFLEX_ID, date-active fields, comments, and the ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns, are returned as NULL.

Common Use Cases and Queries

The view is typically used to resolve bill-to organization details for an order or to drive pick-list and validation logic. A representative query retrieving bill-to address and commercial defaults for a given site use is:

  • Customer bill-to lookup: SELECT organization_id, name, address_line_1, town_or_city, country, price_list_id, payment_term_id FROM oe_invoice_to_orgs_v WHERE cust_account_id = :p_account_id AND primary_flag = 'Y';
  • Integration extraction: Data-pump or interface programs select the address and contact columns to populate downstream billing, tax, or third-party systems.
  • Validation and defaults: Order Entry and pricing logic reference the price list, payment term, and shipping tolerance columns to default or validate order header values.
  • Reporting: Exceptions and order-status reports join this view to order tables on site-use or account identifiers to display customer-facing bill-to information.

Because the underlying objects are TCA synonyms, any query is subject to the standard customer and site-use security and status filtering expected in TCA-based reporting.