Search Results aso_i_order_types_v




Overview
Explore in AI Chat

Overview

ASO_I_ORDER_TYPES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the ASO (Order Capture) product family and exposes the set of order types that Order Management recognizes as valid. In practice it functions as a thin projection layer that surfaces order type configuration attributes for consumption by Order Capture, Oracle iStore, quotation logic, and external integration interfaces that must determine which order types may be used when creating or validating sales documents.

Because the view is defined over OE_ORDER_TYPES_V, it does not perform any independent transformation of data; it selects a defined column list from the underlying Order Management view. This makes it a stable, join-friendly source for reporting and validation routines without requiring direct access to the OE schema objects. Applications and concurrent programs that need a normalized, ASO-scoped list of order types reference this object rather than the underlying OE view, preserving a layer of separation between Order Capture and Order Management data structures.

Underlying Base Objects

The only documented referenced base object is OE_ORDER_TYPES_V, itself a view in the Order Management schema. The view text projects the columns ORDER_TYPE_ID, NAME, ORDER_CATEGORY_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE, CUST_TRX_TYPE_ID, PRICE_LIST_ID, ACCOUNTING_RULE_ID, INVOICING_RULE_ID, AGREEMENT_REQUIRED_FLAG, PO_REQUIRED_FLAG, SHIPMENT_PRIORITY_CODE, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE, and ORG_ID.

Note that the documented column listing in the ETRM metadata shows SHIP_METHOD_CODE while the view text shows SHIPPING_METHOD_CODE; both refer to the same shipping method attribute and the discrepancy reflects naming across documentation versions. Multi-organization filtering is exposed through ORG_ID, meaning the view can be queried per operating unit inventory organization context.

Key Columns

  • ORDER_TYPE_ID — Primary key of the order type; used as a foreign key in OE_ORDER_HEADERS_ALL and related transactional tables.
  • NAME — User-facing order type name as configured in Order Management.
  • ORDER_CATEGORY_CODE — Classification of the order type, typically distinguishing ORDER versus RETURN, which drives processing flow.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating that governs whether the order type is currently usable.
  • CUST_TRX_TYPE_ID, PRICE_LIST_ID, ACCOUNTING_RULE_ID, INVOICING_RULE_ID — Default Receivables transaction type, price list, accounting rule, and invoicing rule inherited by orders of this type.
  • AGREEMENT_REQUIRED_FLAG, PO_REQUIRED_FLAG — Flags indicating whether an agreement or purchase order reference is mandatory.
  • SHIPMENT_PRIORITY_CODE, SHIPPING_METHOD_CODE — Default shipment priority and shipping method applied to the order type.
  • FREIGHT_TERMS_CODE — Freight terms default carried on the order type; a frequent search term for users validating carrier and freight term configuration.
  • FOB_POINT_CODE — Free-on-board point default.
  • ORG_ID — Operating unit / organization identifier supporting multi-org security.

Common Use Cases and Queries

Typical uses include validating whether a specific order type is active, driving LOVs in custom Order Capture extensions, and reconciling freight terms, shipping method, and pricing defaults across organizations.

Example: list active order types with their freight terms.

  • SELECT ORDER_TYPE_ID, NAME, ORDER_CATEGORY_CODE, FREIGHT_TERMS_CODE, SHIPPING_METHOD_CODE, ORG_ID FROM APPS.ASO_I_ORDER_TYPES_V WHERE SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE + 1);

Example: locate order types configured with a particular freight term.

  • SELECT ORDER_TYPE_ID, NAME, FREIGHT_TERMS_CODE, ORG_ID FROM APPS.ASO_I_ORDER_TYPES_V WHERE FREIGHT_TERMS_CODE = :p_freight_terms_code AND ORG_ID = :p_org_id;

Example: join to order headers to report the order type defaults actually applied to booked orders.

  • SELECT h.ORDER_NUMBER, t.NAME ORDER_TYPE, t.ORDER_CATEGORY_CODE, t.FREIGHT_TERMS_CODE, t.FOB_POINT_CODE FROM APPS.OE_ORDER_HEADERS_ALL h, APPS.ASO_I_ORDER_TYPES_V t WHERE h.ORDER_TYPE_ID = t.ORDER_TYPE_ID AND h.ORG_ID = t.ORG_ID;

Because the view is a pass-through to OE_ORDER_TYPES_V, query performance is governed entirely by the base view; no additional indexes or materialization exist at the ASO layer.