Search Results wsh_order_types_regular_v




Overview
Explore in AI Chat

Overview

The APPS.WSH_ORDER_TYPES_REGULAR_V view is a Shipping Execution (WSH) reporting and integration object that exposes the set of "regular" order types — that is, order transaction types that are classified as sales orders rather than returns. It is defined in the APPS schema and is marked VALID. The view presents a curated subset of the columns available from the Order Management transaction type definitions, filtering to the sales order category and the ORDER transaction type code. This makes it a convenient, pre-filtered source of order type reference data for shipping, delivery, and integration logic that must operate only on regular (non-return) order types.

Because it exposes the ENFORCE_LINE_PRICES_FLAG and related pricing/agreement attributes alongside shipping priority, it serves as a compact lookup for both order-entry configuration and shipping-relevant defaults. The view is widely used in reports, LOVs, and interface programs where a list of valid order types grouped by pricing enforcement behavior is required.

Underlying Base Objects

The view is defined over OE_TRANSACTION_TYPES_VL, the Order Management transaction types view. The documented view text selects the columns NAME (aliased as ORDER_TYPE_NAME), DESCRIPTION, TRANSACTION_TYPE_ID (aliased as ORDER_TYPE_ID), ENFORCE_LINE_PRICES_FLAG, AGREEMENT_TYPE_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE, and SHIPMENT_PRIORITY_CODE. The WHERE clause restricts results to rows where NVL(ORDER_CATEGORY_CODE, 'ORDER') <> 'RETURN' and TRANSACTION_TYPE_CODE = 'ORDER', thereby excluding returns and any non-order transaction categories.

In Oracle EBS 12.1.1 and 12.2.2, the documented metadata notes that the referenced base object resolves through OE_TRXT_TYPES_NOORGS_VL, a view that supplies transaction type definitions without organization context. This is consistent with the multi-org independence of order transaction type setup, which is defined at the operating-unit-independent level in the Order Management schema.

Key Columns

  • ORDER_TYPE_NAME — the display name of the order transaction type, sourced from NAME on the base view.
  • DESCRIPTION — the descriptive text associated with the transaction type.
  • ORDER_TYPE_ID — the transaction type identifier (TRANSACTION_TYPE_ID), used as a foreign key in many order and shipping tables.
  • ENFORCE_LINE_PRICES_FLAG — indicates whether line-level pricing is enforced for the order type; central to pricing validation logic and the primary column of interest for price-related reporting.
  • AGREEMENT_TYPE_CODE — the default agreement (blanket/contract) type applied to the order type.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the transaction type.
  • SHIPMENT_PRIORITY_CODE — the shipping priority default used for shipments generated from this order type.

Common Use Cases and Queries

The view is typically used to populate LOVs and validation lists limited to active, non-return order types, and to analyze pricing enforcement configuration across order types.

  • Listing order types with line-price enforcement enabled:
    SELECT order_type_name, order_type_id, enforce_line_prices_flag FROM apps.wsh_order_types_regular_v WHERE enforce_line_prices_flag = 'Y';
  • Retrieving shipping priority and agreement defaults for an order type:
    SELECT order_type_id, agreement_type_code, shipment_priority_code FROM apps.wsh_order_types_regular_v WHERE order_type_name = 'Standard Order';
  • Restricting to currently active types:
    SELECT order_type_name FROM apps.wsh_order_types_regular_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Because the view already filters out returns, integrators and report developers can rely on it as a clean source for regular order classification without duplicating the ORDER_CATEGORY_CODE exclusion logic.