Search Results app_party_type




Overview
Explore in AI Chat

Overview

APPS.ASO_I_ORDER_HEADERS_BALI_V is a read-only internal database view owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes a consolidated, reporting-oriented projection of order header and quotation data, joining the Oracle Order Management order header base table with the Order Capture (ASO) integration structures. The view is classified as "Oracle Internal Use Only," and Oracle Corporation explicitly does not support direct customer access to Oracle Applications data through this object except when invoked from standard Oracle Applications programs. Its FND Design Data identifier is ASO.ASO_I_ORDER_HEADERS_BALI_V, and its status is VALID in the documented environment.

The view serves as a read interface for concurrent programs, order capture flows, and diagnostic queries that need to present both sales order numbers and quotation numbers together. It is not referenced by any other database object, indicating that it functions purely as a terminal reporting object and not as a component of a broader dependency chain.

Underlying Base Objects

The documented dependencies for ASO_I_ORDER_HEADERS_BALI_V are three objects:

  • OE_ORDER_HEADERS_ALL (accessed via a synonym) — the Order Management order header table, supplying core order attributes such as order number, ordered date, order status, and flow status code.
  • ASO_ORDER_INT (package) — the Order Capture integration package that provides the quotation name and quotation number/version logic used by the view, including the QUOTE_NUMBER_VERS column.
  • HR_OPERATING_UNITS (view) — the Human Resources operating unit view, providing the OPERATING_UNIT column used to segregate data by business unit.

No database object references the view, confirming its role as an informational endpoint rather than a reusable building block elsewhere in the schema.

Key Columns

The view exposes nineteen columns across numeric, date, and VARCHAR2 datatypes. Notable columns include:

Common Use Cases and Queries

The primary use case is correlating sales orders with their originating quotations. A typical query filtering on the searched column would be:

  • SELECT ORDER_NUMBER, QUOTE_NUMBER_VERS, QUOTE_NAME, ORDER_STATUS, ORDERED_DATE FROM APPS.ASO_I_ORDER_HEADERS_BALI_V WHERE QUOTE_NUMBER_VERS = :p_quote_number_vers;
  • Reporting by operating unit: SELECT OPERATING_UNIT, COUNT(*) FROM APPS.ASO_I_ORDER_HEADERS_BALI_V GROUP BY OPERATING_UNIT;
  • Customer and sales rep analysis: SELECT ACCOUNT_NUMBER, SOLD_TO_CONTACT_NAME, RESOURCE_NAME, ORDER_TOTAL FROM APPS.ASO_I_ORDER_HEADERS_BALI_V WHERE FLOW_STATUS_CODE = :status;
  • Quotation-to-order linkage using QUOTE_HEADER_ID and HEADER_ID for traceability.

Because the object is marked Oracle Internal Use Only, customers should rely on supported Order Management and Order Capture views or APIs where possible, and reserve direct queries for diagnostic purposes under Oracle guidance.