Search Results oe_order_types_v




Overview
Explore in AI Chat

Overview

OE_ORDER_TYPES_V is an APPS-owned view in the Oracle E-Business Suite Order Management (ONT) module that exposes order transaction types scoped to a specific organization and language. It is a convenience wrapper that filters the underlying multilingual transaction type definitions so that only sales order types — those whose transaction type code equals 'ORDER' — are returned, and it excludes types flagged as internal or otherwise non-order document categories. The view carries a status of VALID across the ETRM 12.2.2 reference set and is equally applicable to 12.1.1 deployments.

The view plays a supporting role in reporting and integration. Because it presents a denormalized, readable projection of order type configuration, developers and analysts routinely use it in custom SQL, Oracle Reports, and BI Publisher data models where the objective is to list or validate order types for a given operating unit without navigating the full OE_TRANSACTION_TYPES_VL definition directly.

Underlying Base Objects

Per the documented metadata, the sole referenced base object is OE_TRANSACTION_TYPES_VL, itself a view over the transaction types base tables (OE_TRANSACTION_TYPES_B and its translation table). OE_TRANSACTION_TYPES_VL supplies the language-specific NAME and DESCRIPTION along with the transactional attributes; OE_ORDER_TYPES_V selects from it and applies two predicates:

The first predicate limits the result set to order entry transaction types. The second removes types whose sales document type is 'B'. The view therefore inherits the multi-language behavior of the VL view, returning rows whose name and description reflect the session language, while the organization context is carried through the ORG_ID column.

Key Columns

The view exposes the full transactional attribute set of the underlying transaction type. Prominent columns include:

Common Use Cases and Queries

Typical scenarios include listing active order types for an operating unit, driving LOV queries in custom forms, and validating configuration before order import.

List order types for a specific organization:

SELECT order_type_id, name, order_category_code FROM oe_order_types_v WHERE org_id = :p_org_id ORDER BY name;

Retrieve default attributes for a single order type:

SELECT name, price_list_id, warehouse_id, demand_class_code FROM oe_order_types_v WHERE transaction_type_id = :p_type_id;

Filter to currently active types:

SELECT order_type_id, name FROM oe_order_types_v WHERE org_id = :p_org_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Because the view already restricts to TRANSACTION_TYPE_CODE = 'ORDER', queries do not need to repeat that predicate. Analysts should remember that name and description are language-dependent and that ORG_ID must be supplied to scope results to the intended operating unit.