Search Results agreement_required_flag




Overview
Explore in AI Chat

Overview

APPS.ASO_I_ORDER_TYPES_V is an Oracle E-Business Suite application view exposed under the APPS schema. It presents order type definitions — the master classification records that determine how sales orders behave in Oracle Order Management — in a form suitable for inquiry, reporting, and integration consumption within the Order-to-Cash process. The view is a thin projection over OE_ORDER_TYPES_V, the Order Management order types view, and preserves the operational semantics of that underlying definition while surfacing the columns relevant to downstream agreement and fulfillment logic.

The view is of particular interest to implementers searching for AGREEMENT_REQUIRED_FLAG, since that attribute governs whether a sales agreement (a contract or blanket purchase commitment) must exist and be referenced before an order line of the associated order type may be entered, priced, or progressed. The same view also exposes purchasing controls via PO_REQUIRED_FLAG, together with defaulting attributes for pricing, receivables, accounting, and shipping. In EBS 12.1.1 and 12.2.2 the view retains the same APPS-owned definition; 12.2.x continues to publish it in ETRM as a documented APPS view defined over OE_ORDER_TYPES_V.

Underlying Base Objects

The documented metadata lists a single referenced base object: the view OE_ORDER_TYPES_V. ASO_I_ORDER_TYPES_V therefore contains no tables of its own and adds no join logic; it is a column-selective wrapper. OE_ORDER_TYPES_V in turn derives from the Order Management order types base table and enriches it with org-level context through ORG_ID, yielding a multi-org aware result set. Consequently, any predicate on operating unit must be expressed against ORG_ID, and the view inherits the security and access characteristics of its base object rather than defining its own.

Key Columns

  • ORDER_TYPE_ID — Primary identifier of the order type; the key used to join to Order Management entities such as OE_ORDER_HEADERS_ALL.ORDER_TYPE_ID.
  • NAME — The user-facing order type name, such as a standard order or return type.
  • ORDER_CATEGORY_CODE — Classifies the type (for example ORDER or RETURN), driving the transactional behavior available to the type.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating window; the type is usable only when the current date falls within this range.
  • CUST_TRX_TYPE_ID, PRICE_LIST_ID, ACCOUNTING_RULE_ID, INVOICING_RULE_ID — Defaulting identifiers for receivables transaction type, price list, revenue accounting rule, and invoicing rule.
  • AGREEMENT_REQUIRED_FLAG — Indicates whether an agreement must be present for orders of this type; the central column for agreement-driven order validation.
  • PO_REQUIRED_FLAG — Indicates whether a purchase order reference is mandatory for orders of this type.
  • SHIPMENT_PRIORITY_CODE, SHIPPING_METHOD_CODE, FREIGHT_TERMS_CODE, FOB_POINT_CODE — Default shipping and freight attributes applied to orders of this type.
  • ORG_ID — Operating unit identifier, enforcing the multi-org partition of the returned rows.

Common Use Cases and Queries

Typical usage includes listing active order types for an operating unit, auditing agreement and PO control settings, and joining order type attributes to order headers for reporting or integration extracts. Reporting solutions frequently filter to the effective window and to a specific ORG_ID before joining to transaction data.

To locate order types that mandate an agreement:

  • SELECT order_type_id, name, agreement_required_flag, po_required_flag FROM apps.aso_i_order_types_v WHERE agreement_required_flag = 'Y' AND org_id = :org_id;
  • SELECT order_type_id, name, start_date_active, end_date_active FROM apps.aso_i_order_types_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1) AND org_id = :org_id;
  • SELECT t.name, t.order_category_code, t.agreement_required_flag FROM apps.aso_i_order_types_v t, apps.oe_order_headers_all h WHERE h.order_type_id = t.order_type_id AND h.org_id = t.org_id;

Because the view is a read-only projection, it is safe for integration queries and concurrent reporting; write operations must target the Order Management setup forms or the base order types table.