Search Results enforce_line_prices_flag




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_ORDER_TYPES_REGULAR_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the Oracle Order Entry (OE) product family and exposes a filtered subset of the order type setup data maintained in the Order Management foundation tables. Specifically, the view restricts its output to order types whose category is "Regular." The definition applies the predicate NVL(ORDER_CATEGORY_CODE, 'R') = 'R', which returns all rows where the category code equals "R" and also treats rows with a NULL category code as regular order types. This defensive coding ensures that legacy or incompletely configured order types are not inadvertently excluded.

Because order types drive numbering, workflow assignment, defaulting rules, and pricing behavior across the order-to-cash cycle, a purpose-built view containing only regular (as opposed to return or other special-category) order types simplifies downstream reporting, integrations, and validation logic. The view has a status of VALID and is documented in ETRM as an APPS-owned object. It is commonly referenced by concurrent programs, custom reports, and interface programs that must enumerate the transactional order types available to users when creating sales orders.

Underlying Base Objects

The view is defined exclusively over a single base object: the SO_ORDER_TYPES table, which is exposed to the APPS schema as a synonym. SO_ORDER_TYPES is the core Order Management setup table that stores one row per order type and holds the transactional controls, defaulting attributes, and processing options that govern how orders of that type behave. The view performs no joins, unions, or aggregations; it is a straight projection of selected columns from SO_ORDER_TYPES, wrapped in the regular-category filter described above. Consequently, the view inherits the base table's security, partitioning, and indexing characteristics, and its freshness depends solely on the underlying table's data. No additional objects, such as lookups or descriptive flexfields, are joined within the view definition, so any enrichment must be added by the consuming query.

Key Columns

  • ORDER_TYPE_NAME — The descriptive name of the order type, aliased from the base column NAME. This is the value typically displayed in order entry forms and LOVs.
  • DESCRIPTION — Free-text description of the order type's intended business purpose.
  • ORDER_TYPE_ID — The primary key of the order type, used as a foreign key throughout Order Management transactional tables.
  • STANDARD_VALUE_RULE_SET_ID — Identifies the defaulting rule set applied to standard values (such as warehouse or price list) for orders of this type.
  • NAVIGATION_PREFERENCE_SET_ID — References the navigation preference set that controls field flow behavior during order entry.
  • CYCLE_ID — Identifies the order cycle associated with the order type, governing status transitions.
  • ENFORCE_LINE_PRICES_FLAG — Indicates whether line-level prices are enforced for the order type.
  • AGREEMENT_TYPE_CODE — The agreement type used to source pricing when agreements apply.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the order type is usable.
  • SHIPMENT_PRIORITY_CODE — Default shipment priority applied to shipments for this order type.

Common Use Cases and Queries

The view is primarily used to populate LOVs, validate interface input, and drive reporting where only regular sales order types should be considered. A typical query lists currently active regular order types:

  • SELECT order_type_id, order_type_name, description FROM so_order_types_regular_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE+1)) ORDER BY order_type_name;
  • Integrations resolving an order type name to its internal ID: SELECT order_type_id FROM so_order_types_regular_v WHERE order_type_name = :p_name;
  • Reporting defaulting and pricing configuration across regular order types: SELECT order_type_name, standard_value_rule_set_id, enforce_line_prices_flag, agreement_type_code FROM so_order_types_regular_v;
  • Auditing active date coverage: SELECT order_type_name, start_date_active, end_date_active FROM so_order_types_regular_v WHERE end_date_active IS NOT NULL;

Because the view excludes non-regular categories, these queries avoid the need to repeat the ORDER_CATEGORY_CODE filter and reduce the risk of processing return or other special order types through regular-order logic.